How to Install and Uninstall libslz.x86_64 Package on Rocky Linux 8
Last updated: November 13,2024
1. Install "libslz.x86_64" package
Please follow the guidelines below to install libslz.x86_64 on Rocky Linux 8
$
sudo dnf update
Copied
$
sudo dnf install
libslz.x86_64
Copied
2. Uninstall "libslz.x86_64" package
Learn how to uninstall libslz.x86_64 on Rocky Linux 8:
$
sudo dnf remove
libslz.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the libslz.x86_64 package on Rocky Linux 8
Last metadata expiration check: 0:16:31 ago on Mon Sep 12 10:27:18 2022.
Available Packages
Name : libslz
Version : 1.2.0
Release : 2.el8
Architecture : x86_64
Size : 40 k
Source : libslz-1.2.0-2.el8.src.rpm
Repository : epel
Summary : StateLess Zip
URL : http://www.libslz.org/
License : MIT
Description : SLZ is a fast and memory-less stream compressor which produces an output that
: can be decompressed with zlib or gzip. It does not implement decompression at
: all, zlib is perfectly fine for this.
:
: The purpose is to use SLZ in situations where a zlib-compatible stream is
: needed and zlib's resource usage would be too high while the compression ratio
: is not critical. The typical use case is in HTTP servers and gateways which
: have to compress many streams in parallel with little CPU resources to assign
: to this task, and without having to limit the compression ratio due to the
: memory usage. In such an environment, the server's memory usage can easily be
: divided by 10 and the CPU usage by 3.
Available Packages
Name : libslz
Version : 1.2.0
Release : 2.el8
Architecture : x86_64
Size : 40 k
Source : libslz-1.2.0-2.el8.src.rpm
Repository : epel
Summary : StateLess Zip
URL : http://www.libslz.org/
License : MIT
Description : SLZ is a fast and memory-less stream compressor which produces an output that
: can be decompressed with zlib or gzip. It does not implement decompression at
: all, zlib is perfectly fine for this.
:
: The purpose is to use SLZ in situations where a zlib-compatible stream is
: needed and zlib's resource usage would be too high while the compression ratio
: is not critical. The typical use case is in HTTP servers and gateways which
: have to compress many streams in parallel with little CPU resources to assign
: to this task, and without having to limit the compression ratio due to the
: memory usage. In such an environment, the server's memory usage can easily be
: divided by 10 and the CPU usage by 3.