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.
Do you use 32-bit compatibility libraries on a 64-bit OS ? Of course you have to upgrade the 32-bit fontconfig library, too. The old 32-bit fontconfig does not understand the configuration files of the new fontconfig.
Thanks Petri.
Of course! silly me. didn't think of that! Will wait for Eric to update his multilib repo.
I wrote two simple config scripts for initrd and grub: initrdconfig and grubconfig. For now they are part of the testing installer, but it would be nice to have them in mkinitrd and grub packages.
Tested so far: BIOS:
/dev/vda1 root
/dev/vdb1 home
UEFI:
/dev/vda1 EFI
/dev/vda2 root
/dev/vdb1 home
/dev/vda1 EFI
/dev/vda2 /boot
/dev/vda3 LVM (swap root home)
/dev/vda1 EFI
/dev/vda2 /boot
/dev/vda3 LUKS LVM (encrypted swap root home)
I didn't even need to use the expert setup for initrd and grub. The minimal install option doesn't include lilo, elilo and kernel-huge. So far everything works fine.
@ivandi: I plan to provide enhancements to the installer too, but am busy learning a bit of C right now. I will have a look at your ISO later. Meanwhile, I propose a simpler and hopefully more robust way of detecting the EFI partitions, see the code snippet at the bottom of post #1982 of this thread.
PS It'd be nice to check that this method does detect an EFI partition in KVM virtio. Could you please test and also give the output of the commands I posted in the first post of this thread, possibly posting your findings there?
Speaking of boot scripts, how about adding the ability to run right after the "/etc/rc.d/rc.modules" a script named "/etc/rc.d/rc.local_early" ?
No, I do not ask about adding that "/etc/rc.d/rc.local_early" by default, but similar with the "rc.local_shutdown" case, about adding just the following snippet into "/etc/rc.d/rc.S"
Code:
if [ -x /etc/rc.d/rc.local_early ]; then
/etc/rc.d/rc.local_early
fi
Many times I hit the need to run some commands early on the boot stage. E.g.
That BFQ I/O scheduller works much better than the default CFQ when you have mechanical hard drives, from my own experiences. So, I use it.
Just so you know, this would apply that scheduler to every sata drive, whether it's an SSD or mechanical (not sure if that's your desired outcome or not). It might be better to set a udev rule where you specify the scheduler for just mechanical (rotational) drives.
You can throw that snippet in a rules file like 60-scheduler.rules under /etc/udev/rules.d/.
If you want to set a specific scheduler for SSDs, you would copy that to a new line and just change the ATTR{queue/rotational} to 0 and the scheduler to your desired scheduler. I have the following on my system, because I prefer deadline for my SSD drive (prioritizes reads over writes so even when a lot is going on, hopefully it limits bogging down my system).
Just so you know, this would apply that scheduler to every sata drive, whether it's an SSD or mechanical (not sure if that's your desired outcome or not).
Yep, that behavior is intentional, as I use (both) mechanical hard drives and NVMe drives in my boxes, mounted via PCIe x4 adapters, instead of SATA SSD ones. And the NVMes uses /dev/nvme* devices.
To be honest, I am a huge fan of those NVMe drives, because they are quite fast and no SATA cables are needed.
BUT, I will agree that your UDEV rules may be better when in the system are present SATA SSD drives.
It gives you both a NVMe (the bottom one) and a M2 SATA slot (the upper one), together with a SATA3 port, and it costs around $25 in Romania.
PS. Probably that you known already that I am quite happy with the on-board graphics, then using the PCIe x16 for another purposes does not bother me, when a particular motherboard does not have secondary PCIe x8 slots.
Last edited by Darth Vader; 09-14-2018 at 12:36 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.