SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The usb-and-pxe-installers/usbimg2disk.sh script uses rsync to copy slackware packages to a USB flash drive (if requested through command line options). The flash drive will usually have the FAT32 filesystem which can only store timestamps in multiples of 2 seconds. If the Slackware packages being copied are on a Linux filesystem it is likely that their timestamps will not be quantised to 2 second intervals. As a result, subsequent runs of the usbimg2disk.sh script (to update the flash drive with the latest versions of packages) will unnecessarily re-copy many unchanged packages since the source and destination timestamps differ.
To stop this, could "--modify-window 2" be added to the rsync command in usbimg2disk.sh?
A modify window of 1 could be sufficient in theory. However, I am unsure that a timestamp of (say) 01:02:03.8 would be rounded up to 01:02:04. If it were rounded down to 01:02:02 instead then a modify window of 2 will be needed. Since there's little reason to prefer 1 over 2 I would be included to go with 2 in order to be sure that it will have the desired effect.
switch default package/other compression algorithm to zstandard
Suggest to switch installation package default compression algorithm to zstandard.
initramfs image also could be compressed with zstandard by default, Slackware generic kernel already has zstandard for initramfs support enabled (CONFIG_RD_ZSTD=y).
It offers very fast decompression speed, in the order of GB+ per second.
So system installation will happen much faster, especially with a good ssd storage.
Compared to xz, zstandard can achieve close compressions ratio.
Considering the Arch Linux report on move to zstandard compression, I think the Slackware installation packages size will increase not more than 1 to 5 percent.
https://en.wikipedia.org/wiki/Zstandard:
"Arch Linux added support for zstd as a package compression method in October 2019 with the release of the pacman 5.2 package manager,[26] and in January 2020 switched from xz to zstd for the packages in the official repository. Arch uses zstd -c -T0 --ultra -20 -, the size of all compressed packages combined increased by 0.8% (compared to xz), the decompression speed is 1300% faster."
Last edited by dgusev; 03-19-2021 at 09:39 AM.
Reason: fix title, add url
Why should we do that?
5.11 is a non LTS kernel version.
Quote:
Originally Posted by Roman Dyaba
Hello, friends !
Switch to Linux Kernel 5.11.7 as mainstream.
Cause:
Smaller iso and downloadable distro and actual CPU and hardware listing, security issues.
Because after unpacking more than 800MB, only the kernel sources.
Anyone having a problem with samba? I don't usually use it but geeqie binds to it and I get this error:
Code:
geeqie: symbol lookup error: /usr/lib64/libkrb5samba-samba4.so undefined symbol: krb5_set_default_tgs_ktypes, version krb5_3_MIT
I found an identical error on a Fedora list but they fixed it there. Beats me why a simple graphical viewer needs samba or kerberos either!
Reinstall the krb5 package. Probably aaa_libraries was installed after it and clobbered the library versions in the krb5 package (which unfortunately do not properly increment a minor library version with new releases).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
switch default package/other compression algorithm to zstandard
