Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!decwrl!ucbvax!agate!eris.berkeley.edu!mwm From: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) Newsgroups: comp.sys.amiga.tech Subject: Re: Soft links vs hard links (was Re: yet another 1.4 request) Message-ID: <25961@agate.BERKELEY.EDU> Date: 2 Jul 89 03:56:56 GMT References: <8906302004.AA16719@postgres.Berkeley.EDU> <401@xdos.UUCP> Sender: usenet@agate.BERKELEY.EDU Reply-To: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) Organization: Missionaria Phonibalonica Lines: 16 Oh yeah - second note on the locklinks (for lack of a better name) I just proposed. It might be nice to be able to specify that the file linked to is to be executed with the rest of the path name (plus data about the type of access wanted by the opener) as an argument, and it will return a lock to be handed to the opener. Of course, that's probably just a pipe dream.