Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site bu-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!bu-cs!root
From: root@bu-cs.UUCP (Barry Shein)
Newsgroups: net.unix
Subject: Re:  file archiving
Message-ID: <586@bu-cs.UUCP>
Date: Fri, 16-Aug-85 22:07:53 EDT
Article-I.D.: bu-cs.586
Posted: Fri Aug 16 22:07:53 1985
Date-Received: Tue, 20-Aug-85 06:02:19 EDT
References: <445@brl-tgr.ARPA> <49600006@convexs>, <715@brl-tgr.ARPA>
Organization: Boston Univ Comp. Sci.
Lines: 18

The find command seemed like a good start for file archiving, while
we're simulating TOPS-20 with a few shell commands why not go a little
farther...either replace the file's contents with the tapeid or (if
you're worried about inodes) append a line 'filename tapeid' to a user's
$HOME/.archive file? Sure would make it easier to get it back when they
panic about it being gone. Also, would let them know what happened.

Of course, mine would be:

	% cat .archive
	.archive	TAPE00777
	% :-)

	-Barry Shein, Boston University

P.S. as I remember TOPS could generate a tape mount request to the
operator automatically upon an open of an archived file, maybe we should
make a symbolic link to the tape and then...oh this is getting weird, sorry.