Xref: utzoo comp.unix.wizards:15371 comp.databases:2261 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!killer!rpp386!jfh From: jfh@rpp386.Dallas.TX.US (John F. Haugh II) Newsgroups: comp.unix.wizards,comp.databases Subject: Re: getcwd() and friends. Message-ID: <14689@rpp386.Dallas.TX.US> Date: 4 Apr 89 18:37:39 GMT References: <3675@ficc.uu.net> Reply-To: jfh@rpp386.Dallas.TX.US (John F. Haugh II) Organization: River Parishes Programming, Dallas TX Lines: 18 In article <3675@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes: >One thing that really would make things a lot easier would be a fchdir() >call, that took a file descriptor and tried to chdir to it. All the info >that UNIX needs for the chdir is available via the fd. Cromix worked this way, perhaps not with a fchdir() call, but most of the system calls under Cromix had file descriptor versions. However ... all of the information needed for a chdir() is not present in the file descriptor. It is possible to be handed a file descriptor which you would not be able to have opened because some component of the search path denies access now, but at some point in the past did allow access. -- John F. Haugh II +-Quote of the Week:------------------- VoiceNet: (214) 250-3311 Data: -6272 | "Porsche does not recommend InterNet: jfh@rpp386.Dallas.TX.US | exceeding any speed limits" UucpNet : !killer!rpp386!jfh +-- -- Porsche Ad ------------