From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <20000731173818.23498.qmail@g.bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Installing the updates 
In-Reply-To: Message from "Doug Henderson" <djhender@telusplanet.net> 
   of "Mon, 31 Jul 2000 08:53:04 MDT." <001c01bffaff$09b49fa0$0500a8c0@telusplanet.net> 
Date: Mon, 31 Jul 2000 13:38:18 -0400
From: Scott Schwartz <schwartz@bio.cse.psu.edu>
Topicbox-Message-UUID: eff284ae-eac8-11e9-9e20-41e7f4b1d025

One thing you can do, at the cost of some preparatory work, is to
create a tree of source directories in your home directory, and then
bind -ac each one in front of the corresponding system source directory.
Then your changes stay private, and you don't have to run as adm or use
kfscmd allow.

(With some more preparation you could write a fileserver that just
interposed itself at the root of a subtree, and let the originals
show through.)

Speaking of inst, one probablu ought to unpack with -r /n/kfs, so that
bindings in one's profile don't confuse it.

An example of such confusion was that my bin/386/ip was was bound ahead
of /bin/ip.  /lib/namespace binds /386/bin to /bin, instead of unioning
/386/bin onto /bin, so later binds leak names into /386.  I think it
ought to make the union right at the outset, instead.