Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 UW 5/3/83; site uw-june
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!houxm!vax135!cornell!uw-beaver!uw-june!gordon
From: gordon@uw-june (Gordon Davisson)
Newsgroups: net.news,net.eunice
Subject: Re: Origin of the name grep (actually Eunice!)
Message-ID: <1818@uw-june>
Date: Sat, 6-Oct-84 02:48:49 EDT
Article-I.D.: uw-june.1818
Posted: Sat Oct 6 02:48:49 1984
Date-Received: Thu, 4-Oct-84 02:29:46 EDT
References: <1082@t4test.UUCP> <1084@t4test.UUCP>, <341@genrad.UUCP> <17@watcgl.UUCP> <152@rlgvax.UUCP>
Organization: U of Washington Computer Science
Lines: 22
Guy Harris suggests a way around Eunice's problems with links:
>Use links (i.e., multiple directory entries pointing to the same file), but
>replace the "unlink" routine by one that just removes the link and doesn't
>delete the file (or "mark the file for deletion" or whatever). Keep a
>reference count in the history file, and delete the file when the last link
>disappears.
>
>Will this work? Can a user-mode Eunice program do all this, or do you have to
>be running in supervisor or executive mode or not be built from Eunice to
>create/delete directory entries and mark files for deletion?
I don't know much about Eunice, but if it lets you use the VMS system
services (and I don't see how it could avoid doing this), you can do it
with RMS calls: sys$enter and sys$remove. You can also manipulate links
with the undocumented DCL commands "set file /enter="
and "set file /remove".
--
Human: Gordon Davisson
USnail: 5008 12th NE, Seattle, WA, 98105
UUCP: {ihnp4,decvax,tektronix}!uw-beaver!uw-june!gordon