Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83 (MC840302); site boring.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!mcvax!boring!jack From: jack@boring.UUCP Newsgroups: net.unix-wizards Subject: Re: inode number -> pathname? (4.2BSD) Message-ID: <6509@boring.UUCP> Date: Mon, 15-Jul-85 01:56:01 EDT Article-I.D.: boring.6509 Posted: Mon Jul 15 01:56:01 1985 Date-Received: Wed, 17-Jul-85 05:17:39 EDT References: <11465@brl-tgr.ARPA> Reply-To: jack@boring.UUCP (Jack Jansen) Organization: AMOEBA project, CWI, Amsterdam Lines: 11 Apparently-To: rnews@mcvax.LOCAL Adding a system call to set the current directory to a given inode/device pair is not only dirty, it also messes up security. It is possible to create a directory in which a user has all permissions, but which he cannot reach, because the parent directory is unsearchable. This can be a very useful feature at times. -- Jack Jansen, jack@mcvax.UUCP The shell is my oyster.