2) keeping problems on one partition from raising trouble on another
partition. e.g., filesystem corruption in a home directory keeping
the root from being able to boot, or filling up a mail directory
keeping people from logging in.
today we have live CDs.
and - UFS doesn't get totally corrupted, just few files lost etc.
files and directories that are not written for a long never get corrupted
so you will always have kernel and /rescue anyway
i said tradition - because very old unix filesystems (25 years ago.. or
more) was different and sometimes got totally corrupted.
Of course if hardware will fail, you can lose all filesystem.
or all filesystems with multiple partitions. end effect is the same.
3) fsck: Background fsck can't be done on the root filesystem, so if
you have a large root, that amounts to a substantial delay booting
after a crash.
i STRONGLY advise all to add
because background fsck DO make problems
4) backups: dump(8) works on a filesystem basis, so organizing the
data for backup (with dump) means organizing according to
filesystem. The same applies to snapshots.
you have to dump all anyway, and you have chflags nodump to mark
directories and files that should not be backed up.
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"