Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!uw-june!pardo From: pardo@june.cs.washington.edu (David Keppel) Newsgroups: gnu.utils.bug Subject: Re: Where to install gnu stuff in the file system? Message-ID: <8006@june.cs.washington.edu> Date: 26 Apr 89 16:27:43 GMT References: Reply-To: pardo@cs.washington.edu (David Keppel) Distribution: gnu Organization: U of Washington, Computer Science, Seattle Lines: 35 ham@polya.Stanford.EDU (Peter R. Ham) writes: > Is there a standard place to install gnu stuff in a Unix file > system? We put `unsupported' things in /uns/... We have: /uns/bin -- at least one for each machine type (e.g., VAX, PMAX, Sequent, ...). There is usally a `home' machine that all the other machines (of a given type) will NFS (Network File System) mount from at boot time. /uns/include -- same as /uns/bin /uns/lib -- same as /uns/bin /uns/man -- same as /uns/bin /uns/src -- a real directory on one machine, just mounted via NFS on most other machines. This has a subdirectory `GNU' for all the GNU software. /uns/usr -- contains a soft link named `local' back to /uns. Then, when we build, say, gcc, we can just do make prefix=/uns and things that appear to be in, say, /uns/usr/local/bin, are really in /uns/bin, where we want them. Works great! ;-D on ( Less filling, too! ) Pardo -- pardo@cs.washington.edu {rutgers,cornell,ucsd,ubc-cs,tektronix}!uw-beaver!june!pardo