Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!swrinde!mips!pacbell.com!att!princeton!shade.princeton.edu!sksircar
From: sksircar@shade.princeton.edu (Subrata Sircar)
Newsgroups: comp.sys.next
Subject: Re: Preserving file ownerships on OD?
Keywords: userid, uid, OD, Optical, reassignment
Message-ID: <11043@idunno.Princeton.EDU>
Date: 22 Jun 91 02:46:15 GMT
References: <1991Jun20.220525.5015@ccu.umanitoba.ca> <1768@toaster.SFSU.EDU>
Sender: news@idunno.Princeton.EDU
Organization: SPAMIT
Lines: 25
Nntp-Posting-Host: shade.princeton.edu

eps@cs.SFSU.EDU (Eric P. Scott) writes:
>In article <1991Jun20.220525.5015@ccu.umanitoba.ca>
>>Am I the only NeXT user to think that this is a REALLY stupid "feature" in
>>the NeXT's Optical Disk support?
>
>It's not just in OD support.  It's in all mountable media EVEN IF
>automount=no is set in the disk label.

Wait.  Are you people saying that if I log in to the Next, and insert a backup
optical disk (made by root) that all of the files on that disk are now owned
by me?  Even if the mountable media has root-owned files?

If so, that's not just stupid, that's criminal.  What's to prevent anyone 
from doing ANYTHING they want to a mountable medium, for example a source disk
mounted over a network?

Has anyone mailed this to Next's bug fix address, or called it in?  Seems to
me that totally destroys the usefulness of mounting optical disks as network
server volumes ...

-- 
Subrata Sircar | sksircar@phoenix.princeton.edu |Prophet& SPAMIT Charter Member
	I don't speak for Princeton, and they don't speak for me.
"May their souls rot in easy-listening hell!" - Johnny Melnibone, GRIMJACK #76
"I seem to suffer from irrelevant flashbacks." - Paul, PAUL THE SAMURAI #1