[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
howtos:slackware_admin:how_to_configure_fstab_and_lilo.conf_with_persistent_naming [2016/08/17 13:15 (UTC)] – Article finished -- awaiting any corrections/suggestions before I remove the FIXME bassmadrigalhowtos:slackware_admin:how_to_configure_fstab_and_lilo.conf_with_persistent_naming [2017/02/10 13:55 (UTC)] – Oops... don't need to test lilo a second time. bassmadrigal
Line 1: Line 1:
 <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). --> <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). -->
  
-FIXME This is a work in progress. It is not complete and may screw up your system if you follow it. I will not be blamed for any nuclear wars started because of this. It should be finished in the next day or two. FIXME +====== How to configure fstab and lilo.conf with persistent naming ======
- +
-====== How to configure lilo.conf and fstab with persistent naming ======+
  
 Have you ever had your /dev/sda and /dev/sdb drives switch order? Has plugging in a USB device before booting your computer caused a kernel panic? Do you frequently unplug or plug in new devices into your computer, thus changing the order of the device names? If you said yes to any of those, you might be a good candidate to use persistent naming within your bootloader and fstab. Have you ever had your /dev/sda and /dev/sdb drives switch order? Has plugging in a USB device before booting your computer caused a kernel panic? Do you frequently unplug or plug in new devices into your computer, thus changing the order of the device names? If you said yes to any of those, you might be a good candidate to use persistent naming within your bootloader and fstab.
Line 244: Line 242:
 The LBA32 warning is normal with Slackware's ''lilo.conf'' and can be ignored (however, you can get rid of it by added ''LBA32'' in the Global section of your ''lilo.conf''). The main thing we're looking for is that all of our stanzas were added and no errors were issued. If that worked, then we can run lilo by itself to finish the process. The LBA32 warning is normal with Slackware's ''lilo.conf'' and can be ignored (however, you can get rid of it by added ''LBA32'' in the Global section of your ''lilo.conf''). The main thing we're looking for is that all of our stanzas were added and no errors were issued. If that worked, then we can run lilo by itself to finish the process.
  
-<code>root@darkstar:~# lilo -t+<code>root@darkstar:~# lilo
 Warning: LBA32 addressing assumed Warning: LBA32 addressing assumed
 Added Slack-partuuid  +  * Added Slack-partuuid  +  *
 howtos:slackware_admin:how_to_configure_fstab_and_lilo.conf_with_persistent_naming ()