Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!yale!cs.yale.edu!yarvin-norman
From: yarvin-norman@CS.Yale.EDU (Norman Yarvin)
Newsgroups: comp.unix.wizards
Subject: Re: Stupid man pages
Message-ID: <25367@cs.yale.edu>
Date: 10 Jun 90 02:39:53 GMT
References: <2281@ariel.unm.edu> <1831@pyrltd.UUCP> <618@modus.sublink.ORG>
	<1990Apr22.083636.9250@lsuc.on.ca> <8591@goofy.Apple.COM>
	<1990Jun8.162656.14993@nbc1.ge.com> <ANSELMO-ED.90Jun9095657@bigbird.cs.yale.edu>
Sender: news@cs.yale.edu
Reply-To: yarvin-norman@CS.Yale.EDU (Norman Yarvin)
Organization: Yale University Computer Science Dept, New Haven CT  06520-2158
Lines: 22

Anselmo-Ed@cs.yale.edu (Ed Anselmo) writes:
>Most of the old paths still work (/usr/man, /usr/spool, /usr/adm), so
>most users don't notice the change.

Until they do something like 

%ls -l /usr/include | more
lrwxrwxrwx  1 root        19 May 31 10:00 /usr/include -> /server/usr/include/
%

and then have to try again with /server/usr/include.

It's no big deal, but these things add up.  With 590 symbolic links in /usr,
and 24 NFS mounts, learning where things are becomes like trying to find
your way around in Adventure.  Once you've found a file, you have to decide
which is the officially sanctioned path (i.e. the path that's not going to
disappear tomorrow).  It just occurred to me to check $PATH for
redundancies; it turns out that /bin is redundant.  It's a symbolic link to
/usr/bin.

	Norman Yarvin			yarvin-norman@cs.yale.edu
  "Obviously crime pays, or there'd be no crime." -- G. Gordon Liddy