Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!ames!sdcsvax!ucsdhub!jack!man!sdeggo!dave
From: dave@sdeggo.UUCP (David L. Smith)
Newsgroups: comp.unix.wizards
Subject: Re: Symbolic Links
Message-ID: <83@sdeggo.UUCP>
Date: Sat, 5-Sep-87 14:16:31 EDT
Article-I.D.: sdeggo.83
Posted: Sat Sep  5 14:16:31 1987
Date-Received: Sun, 6-Sep-87 08:15:05 EDT
References: <1254@mhres.mh.nl> <1809@munnari.oz> <2924@ulysses.homer.nj.att.com>
Organization: Lazy Programmer's Society of San Diego
Lines: 26



Here's an idea:  Why not just define a new file "..." to _always_ mean go back 
to the parent directory you had in the path you used.  Then we'd have ., the 
current directory, .. the parent directory and ... the directory which was the 
parent in the path we specified during the chdir().  At login, .. and ... would 
be equal.  Or, this could be swapped for those who have been screaming about how
.. should always be the parent directory specified in the path.  This info
could just be stored on a per-process basis by the kernel, no problem.  
Nothing breaks and we don't need any funky modes to confuse everyone.

Any problems with this idea?


-- 
David L. Smith
{sdcsvax!sdamos,ihnp4!jack!man, hp-sdd!crash}!sdeggo!dave
sdeggo!dave@sdamos.ucsd.edu 
Oxymoron: Unix Documentation


-- 
David L. Smith
{sdcsvax!sdamos,ihnp4!jack!man, hp-sdd!crash}!sdeggo!dave
sdeggo!dave@sdamos.ucsd.edu 
"How can you tell when our network president is lying?  His lips move."