How to Install and Uninstall libslz.i686 Package on Fedora 38
Last updated: November 02,2024
1. Install "libslz.i686" package
This guide let you learn how to install libslz.i686 on Fedora 38
$
sudo dnf update
Copied
$
sudo dnf install
libslz.i686
Copied
2. Uninstall "libslz.i686" package
This is a short guide on how to uninstall libslz.i686 on Fedora 38:
$
sudo dnf remove
libslz.i686
Copied
$
sudo dnf autoremove
Copied
3. Information about the libslz.i686 package on Fedora 38
Last metadata expiration check: 2:35:13 ago on Sun Mar 17 04:59:58 2024.
Available Packages
Name : libslz
Version : 1.2.0
Release : 7.fc38
Architecture : i686
Size : 55 k
Source : libslz-1.2.0-7.fc38.src.rpm
Repository : fedora
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 : 7.fc38
Architecture : i686
Size : 55 k
Source : libslz-1.2.0-7.fc38.src.rpm
Repository : fedora
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.