This allows Linux to boot even if the disk is not fully supported. BIOS only sees the first 20 MB. Linux will interact directly with the drive and ignore BIOS once booted.
swap
swap
256 MB
Linux Swap
Primary swap partition. In case we find some way to run out of physical RAM. This is a safety net, of sorts. RAM is cheap. If you're regularly using significant amounts of swap space then buy twice the amount of RAM you think you might use. Linux performs magic when it has loads of extra RAM. (Hint: caching :-)
LABEL=Root
/
2.0 GB
Ext2
This is the root of the file system. Machine-specific garb resides here. This is what distinguishes Daneel from some other x86-based Linux machine.
LABEL=User
/usr
7.6 GB
Ext2
User applications and sharable data are here. This is commonly shared among a group of computers with similar architectures and is preferably mounted read-only.
Western Digital
100 Mb/s
LABEL=Home
/home
60.2 GB
Ext2
All of the user's personal effects reside here. This should be shared among all computers on a network. Everything is strictly accessible only by the owner (0700). A publicly readable (0755) directory exists in /home/public/username which is soft-linked to /home/username/public for convenience.
Barracuda
400 Mb/s
LABEL=Storage
/auto/storage
2.1 GB
Ext2
Housed in a Power User SCSI storage unit; this drive can easily be moved between machines.
Device Node Notes
I am mounting disk partitions based on their LABEL (Manual Section 8: e2label) rather
than the physical connection point. Normally, you would mount /dev/hda1 to /boot and such.
I found that this is extremely annoying when I wanted to remove some disks and add the 60 GB. I
recalled reading about using labels for volume management. After about 5 minutes I
had switched to this method exclusively.
A better method might be to assign UUID's to each
disk partition. Linux Ext2 supports UUID's for each partition. I don't see the advantage. You are
going to have to change either the UUID, LABEL, or fstab to replace old disks with new. Moving
any disk except the BIOS boot disk requires no configuration changes with either UUID or LABEL.
If one has managed to flash their CMOS/BIOS chip with LinuxBIOS
then the boot disk problem goes away.
This thing is in a cavernous server box that I stripped out and have installed custom hardware mounts. (Server box is thanks to Steve Lipps.) It could be anywhere, doing anything, at any time. I honestly don't have any specific purpose for this thing. It's exists so I can try new things without trashing a working system. Look out 'cause It bites!
Dave's Web 
