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. attach 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 try out the fresh speculating online game from exactly what data is on what operator sucks
The even worse when you’ve reflected you resources partition. In these cases, you often finish handling only 1 illustration of the newest reflect, rather than all of it. There’s an option tricky causes on how one becomes wedged such a posture, however, it isn’t uncommon. Anyway, in this case, you have one or two (or more?) duplicates out-of /etc/fstab during the play. Which one gets utilized gets a purpose of the bootloader, the save your self diskette, the newest random BIOS push numberings strategy, and you can operator distress. Continue reading “Particularly, I’m considering the newest”
