Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!lll-tis!ptsfa!hoptoad!academ!killer!pollux!bobkat!m5
From: m5@bobkat.UUCP (Mike McNally )
Newsgroups: comp.unix.wizards
Subject: Re: symbolic links
Message-ID: <1376@bobkat.UUCP>
Date: Wed, 1-Jul-87 15:45:37 EDT
Article-I.D.: bobkat.1376
Posted: Wed Jul  1 15:45:37 1987
Date-Received: Tue, 7-Jul-87 01:36:33 EDT
References:  > <2211@bunker.UUCP> <1097@mtune.ATT.COM> <21681@sun.uucp> <1101@mtune.ATT.COM> <6026@brl-smoke.ARPA>
Reply-To: m5@bobkat.UUCP (Mike McNally (Man from Mars))
Organization: Digital Lynx, Inc; Dallas, TX
Lines: 22
Keywords: symbolic links

In article <6026@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) ) writes:
>In article <1101@mtune.ATT.COM> jhc@mtune.UUCP (Jonathan Clark) writes:
>>... I realize that the kernel would then have to keep
>>track of where you are in the file system, that's unfortunate.
>
>The kernel has to do this anyway, in order to resolve relative
>pathnames during an open().

All the kernel needs to keep track of is the inode number of the current
working directory.  That's why the code for getwd() is more than just
"ask the kernel for the current wd path".  

Perhaps that's what Doug meant.




-- 
Mike McNally, mercifully employed at Digital Lynx ---
    Where Plano Road the Mighty Flood of Forest Lane doth meet,
    And Garland fair, whose perfumed air flows soft about my feet...
uucp: {texsun,killer,infotel}!pollux!bobkat!m5 (214) 238-7474