Path: utzoo!attcan!uunet!twwells!bill
From: bill@twwells.com (T. William Wells)
Newsgroups: comp.unix.wizards
Subject: Re: File Sys Hierarchies
Message-ID: <1989Jul1.160820.26651@twwells.com>
Date: 1 Jul 89 16:08:20 GMT
References: <20140@adm.BRL.MIL> <5748@rpi.edu>
Organization: None, Ft. Lauderdale, FL
Lines: 25

In article <5748@rpi.edu> night@pawl.rpi.edu (Trip Martin) writes:
: In article <20140@adm.BRL.MIL> rbj@dsys.ncsl.nist.gov (Root Boy Jim) writes:
: >Another annoying thing is that the superuser's home directory is `/'.
: >This make it difficult to have a private bin directory and use the
: >same .cshrc and .login scripts as my user account.
:
: Is there any good reason to leave root's home directory as "/"?  Or
: is this just another convention that's been around so long that no one's
: bothered to change it?

Well, you want root's home directory to be on the boot file system so
that root is not dependent on other file systems.

My solution is this: in /.profile, I check to see if there is a
/usr/home/root directory. If not, I leave the home directory as /. If
there is, I fake things so that /usr/home/root becomes the root home
directory. Programs generally useful to root that aren't needed when
/usr is down go in /usr/home/root/bin; those needed under all
conditions go in /etc/bin.

(Yeah, I'd probably do it differently if I had symbolic links.)

---
Bill                    { uunet | novavax | ankh | sunvice } !twwells!bill
bill@twwells.com