Robert Davies wrote:
> One possible con I've spotted is that having / and /usr on different disks
> makes you more vulnerable to disk failure. On some UNIX systems /lib stuff
> is really in /usr/lib, and /usr contents are generally pretty useful, so it
> may make recovery harder....
Robert, you really need to try Slackware!!!
True story from a couple of years back: /usr is trashed, so I boot without it,
mount /usr from another machine via NFS (read-only!), use that to fix the duff
partition, and reboot. 15 minutes work and all problems sorted.
I don't know about RedHat or Debian, but you don't get it that easy with SuSE
and that's a fact; so your comments were probably valid for some distros.
On a Slack system everything is pretty close to the letter of the FHS.
You don't need anything from /usr to boot, it can be mounted read-only coz ALL
writable bits are symlinked to /var, and best of all X11 still works coz
/usr/X11R6/bin/X is a symlink to /var/X11R6/bin/X which is a symlink back to
/usr/X11R6/bin/{your X server} which means one /usr partition can suffice for a
whole network regardless of different video hardware on each machine.
Me Likee Slackware!
-- Regards,Sean King seanie@merciless.org.uk -------------------------------------------------------------------- http://www.lug.org.uk http://www.linuxportal.co.uk http://www.linuxjob.co.uk http://www.linuxshop.co.uk --------------------------------------------------------------------
This archive was generated by hypermail 2.1.3 : Thu 22 Nov 2001 - 13:10:51 GMT