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 believe grub uses UUID instead of the kernel name for device naming.
At least this is the default when using grub, yes. You can change it in /etc/default grub if you want (but why would you?)
Quote:
I have seen several problems on multiboot system when I don't use persistent device names (i.e UUID) in my elilo.conf file.
This hit a few minutes ago: adding a drive in a VM changed the devices naming and bingo!
Code:
Kernel panic - not syncing: VFS: having unable to mount rootfs on unknown-block(8,66)
Quote:
One of my hopes for Slackware 15 is that they go to persistent device naming in both eliloconfig and fstab.
Of course. I will propose a way to do that, using lsblk as in EFI3M.
PS Even more fun
The entry for Slint in the EFI3M boot menu still starts Slint, But... As /dev/sda2 is mounted on / in /etc/fstab, when it switches to / I get the desktop from Solus, whose / is now on the (newly named) /dev/sda2! It took me a few seconds to realize what happened...
Last edited by Didier Spaier; 07-12-2018 at 02:32 PM.
The entry for Slint in the EFI3M boot menu still starts Slint, But... As /dev/sda2 is mounted on / in /etc/fstab, when it switches to / I get the desktop from Solus, whose / is now on the (newly named) /dev/sda2! It took me a few seconds to realize what happened...
Yup, this has happen to me, a couple of times after Window 10 Creators Update. Seems that they like to, on occasion, add a partition directly after the main windows partition during Creator updates. This screws up the partition order downstream of the new partition and will causing mounting issues with them if you don't have persistent device naming. BTW I don't see this as a MS issue, but rather an issue with not using persistent device name.
Quote:
Originally Posted by Didier Spaier
I will propose a way to do that, using lsblk as in EFI3M.
PS Even more fun
I must confess that I knew that you would read my reply and hoped that you would take up the cause. Any chance that eliloconfig can be changed to ask before overwriting the elilo.conf file?
Yup, this has happen to me, a couple of times after Window 10 Creators Update. Seems that they like to, on occasion, add a partition directly after the main windows partition during Creator updates. This screws up the partition order downstream of the new partition and will causing mounting issues with them if you don't have persistent device naming. BTW I don't see this as a MS issue, but rather an issue with not using persistent device name.
I must confess that I knew that you would read my reply and hoped that you would take up the cause. Any chance that eliloconfig can be changed to ask before overwriting the elilo.conf file?
I am now listing all the enhancements I will consider for the Slint installer and related scripts, among which eliloconfig (and also liloconfig, by the way). I could then post this list of possible enhancements as an RFC in this forum, to gather opinions, questions and suggestions from Slackware users, then propose patches for the Slackware installer. This would include a few modifications already made in the Slint installer, like checking that the user follows the installation steps listed in the setup script in a consistent order. What do you think?
Last edited by Didier Spaier; 07-13-2018 at 06:09 AM.
Reason: First sentence modified to explicitly mention eliloconfig and liloconfig.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.