What features/changes would you like to see in future Slackware?
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.
I'd like efibootmgr to be runnable from the installation DVD.
You mean, be able to use it even if Slackware is not yet installed? What use case do you have in mind?
Anyway that shouldn't be an issue as the binary is not heavy and all dependencies are already shipped in the installer. I could add that to the Slint installers with its manual page if someone is interested (in the small ones as well).
Click here to see the post LQ members have rated as the most helpful post in this thread.
Having efibootmgr on installation cd/dvd would facilitate repairs to efi boot menu when unable to boot to installed root partition. Of course, so long as you can boot the disk in efi mode, then you should be able to boot the root partition from there, install efibootmgr from there, and do repair. So long as the efivars kernel module is available once booted to root. If installed kernel and boot kernel don't match, then loading modules is a bit more work; I guess they should be available by mounting the installation media. Geepers, I could argue this circle into an oval.
From the github documentation, it seems they are waiting on some last minute i80n data to be submitted before they release 2.26 out as final.
Quick random note, it is i18n, because there is 18 letters in between the i and n in the word internationalization. Sometimes you will see l10n, which is the same concept but for localization.
Quick random note, it is i18n, because there is 18 letters in between the i and n in the word internationalization. Sometimes you will see l10n, which is the same concept but for localization.
This is is not about preferences. A GPL library restricts your licensing options for your own code, if you import it. So it's no-go terroritory, wasted. For this specific reason LGPL was created.
Having efibootmgr on installation cd/dvd would facilitate repairs to efi boot menu when unable to boot to installed root partition. Of course, so long as you can boot the disk in efi mode, then you should be able to boot the root partition from there, install efibootmgr from there, and do repair. So long as the efivars kernel module is available once booted to root. If installed kernel and boot kernel don't match, then loading modules is a bit more work; I guess they should be available by mounting the installation media. Geepers, I could argue this circle into an oval.
Another program that would very useful to have included on the usbboot.img would be to have the static version of testdisk with photorec. Having this available would make most repairs, saving partitions and copying data from shaky disks possible. strace and gdb could be useful to have there too.
Another program that would very useful to have included on the usbboot.img would be to have the static version of testdisk with photorec. Having this available would make most repairs, saving partitions and copying data from shaky disks possible. strace and gdb could be useful to have there too.
I like it. I should try to find time to modify an image to have just such additions. I'm a bit swamped, but I should create a todo list so I can add this to it.
I like it. I should try to find time to modify an image to have just such additions. I'm a bit swamped, but I should create a todo list so I can add this to it.
Would be great to have this updated image. It would promote this to the best rescue disk.
Would be great to have this updated image. It would promote this to the best rescue disk.
You do not even have to modify the Slackware installer, only the bootable ISO. Isolinux has a little known feature that it can use multiple initramfs image files and combine them on the fly when booting the kernel.
I once created a modified Slackware mini ISO for a friend who needed an installer that additionally needed to contain ethtool and tcpdump. Instead of modifying the initrd.img file (which contains the Slackware installer), I created a second initramfs file.
I extracted the binaries and libraries from the Slackware packages for ethtool and tcpdump into a temporary directory (dumping binaries in ./sbin and libraries in ./lib64) like this:
Loop-mount the ISO image and modify the isolinux configuration to take the addons.img into account:
Code:
#mkdir -p /mnt/iso
# mount -o loop slackware_x86_64-14.1-mini-install.iso /mnt/iso/
# mkdir ~/workdir
# cp -a /mnt/iso/* ~/workdir/
# cp -a tmp/addons.img ~/workdir/isolinux
# sed -i 's/initrd.img/&,addons.img/' ~/workdir/isolinux/isolinux.cfg
Which lets isolinux do its magic of combining two separate initramfs images into one filesystem for the kernel to boot with, thus making the addons part of the installer transparently.
Finally a new ISO needs to be created from that workdir, something like this:
Code:
# cd ~/workdir
# mkisofs -o ~/slackware-mini-install.iso \
-R -J -V "Slackware Mini Install" \
-hide-rr-moved -hide-joliet-trans-tbl \
-v -d -N -no-emul-boot -boot-load-size 4 -boot-info-table \
-b isolinux/isolinux.bin \
-c isolinux/isolinux.boot \
-sort isolinux/iso.sort \
-publisher "The Slackware Linux Project - http://www.slackware.com/" \
-A "Slackware-14.1 for x86_64 Mini Install CD - build $(date +Y%m%d)" \
.
After which you can collect the modified ISO in your homedirectory.
If you are using PXE boot then you do not even have to create new ISO images of course, just dump the addons.img file in the pxeboot directory and update the configuration file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.