When I move a hard drive from one controller to another, I want the operating system to recognize it by the data on the drive, rather than by the cable its attached to. install command, and of /etc/fstab. If I need to reorganize a system, and /dev/hda3 suddenly becomes /dev/hde3, I shouldn’t have to muck with /etc/fstab to get it right. Why? Because it seems like the only time I edit /etc/fstab is under times of duress. Something’s down, something’s wrong, you’ve just booted off the rescue disk, you have a only have minimalist editor (e.g. /bin/ae) handy, and you find yourself doing emergency repairs to /etc/fstab. You should be able to ask a disk partition “what are you?”, and have the disk partition reply, and have the mount command respond to that.
To relax and play the latest speculating games out of exactly what info is on which control sucks
Their bad when you’ve shown you resources partition. In such cases, you will end dealing with one exemplory instance of the reflect, rather then the whole thing. You will find an option challenging causes as to how one to gets wedged such a position, but it’s just not strange. Anyhow, in such a case, one has two (or higher?) duplicates out of /etc/fstab when you look at the enjoy. Which will get utilized gets a purpose of new bootloader, this new rescue diskette, brand new arbitrary BIOS push numberings program, and you can user confusion. With the virtually any reboot, brand new /etc/fstab you to gets used may or may not become one you simply had done editing.
Ext2fs names. The high you could lay a label into the ext2fs with the fresh e2label order. But did you know that if you make a good RAID-step one reflect /dev/md1 out-of /dev/hda1 and you will /dev/hdc1, and set an Ext2fs identity in it, that most about three of those products are certain to get equivalent ext2fs label? Brands are essential from the take off-equipment level 
, therefore the identity must accept the true storage media getting branded. The newest install order, and /etc/fstab need to take block-product labels, perhaps not file-system labels.
The modern Linux md subsystem uses ‘raid superblocks’ to keep an excellent UUID and you will cache other details. But there are no products that really allows you to search at this information, neither to place a label in there. Never ever notice that you need their partition type of to get 0xfd and never 0x83, and yada yada yada.
Perhaps MSDOS-suitable hard disk partition dining tables try completely wrong? Maybe one of several almost every other partition dining table appearance is ideal? If the I’m not running MSDOS or Windows towards the server, Really don’t have to take the newest MSDOS partition table. Where’s the newest HOWTO that covers stuff at that height? How can we score equipment to utilize these specific things?
File-system names are fascinating, but they are maybe not a whole answer
This new LILO (variation twenty five.5.step 3.1) has gone insane. My personal history sorts of LILO didn’t whine that all of my personal hard drives was on 0x80. Today it does. Today I have to give the explicitly, that drive step one is actually 0x80 and you will drive 2 is actually 0x81. What exactly is step 1 and you may 2? I dunno. So what does 0x80 and you may 0x81 denote? We dunno, a wild & lucky suppose. And, throughout the keeping with new heritage away from computers starting everything you informed these to would, in the place of what you wanted these to do, LILO has grown to become really, really effective at carrying out a boot sector which is unbootable. This is certainly entirely inappropriate.
My personal supply partition is reflected. I have a copy of / on the each other /dev/hda1 and on /dev/hdc1. Once i tell LILO which i wanted a footwear field hung on the /dev/hda as well as on /dev/hdc, in order to mount sometimes /dev/hda1 otherwise /dev/hdc1 because the sources partition, that is what Needs. I really don’t want which L 40 forty 40 shit. I do not need LI 80 80 80 sometimes. I do not need it delivering confused about what type is /dev/hda and you may that’s /dev/hdc. I specifically do not want they discovering another viewpoint on which are hence, compared to the my personal cut diskette.