Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 exptools; site whuxlm.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!whuxlm!jph
From: jph@whuxlm.UUCP (Holtman Jim)
Newsgroups: net.unix,net.unix-wizards
Subject: Re: Tape drives and protection of tapes (using tar)
Message-ID: <725@whuxlm.UUCP>
Date: Tue, 2-Apr-85 23:27:15 EST
Article-I.D.: whuxlm.725
Posted: Tue Apr  2 23:27:15 1985
Date-Received: Wed, 3-Apr-85 07:56:54 EST
References: <1634@psuvax1.UUCP> <9638@brl-tgr.ARPA>
Distribution: net
Organization: AT&T Bell Laboratories, Whippany
Lines: 16
Xref: watmath net.unix:4099 net.unix-wizards:12693

> You need a utility for allocating (and deallocating) devices (should
> also work with any type of file).  When unallocated, the device would
> be owned by, say, "public".  The allocator would be set-UID "public"
> (set-UID "root" on non-AT&T systems) and would give the device to the
> requestor if someone else didn't already have it.
> 
> This is just the simplest sketch of what such a utility should do.
> I have complete design notes for a full system that handles daemon
> processes, failure to deassign upon logout, generic device classes,
> and sundry other considerations.  Unfortunately I never got around
> to implementing the design.  Some such utility should be standard.

If UNIX(tm) were really a user friendly system, it would support
`labeled' tapes and then you would have this problem. The system
would read the tape label before writing on it to ensure it really
was the one that was requested.