Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!rochester!pt.cs.cmu.edu!drycas.club.cc.cmu.edu!zardoz.club.cc.cmu.edu!ddj
From: ddj@zardoz.club.cc.cmu.edu (Doug DeJulio)
Newsgroups: comp.sys.next
Subject: Re: Preserving file ownerships on OD?
Keywords: userid, uid, OD, Optical, reassignment
Message-ID: <1991Jun21.143109.5273@zardoz.club.cc.cmu.edu>
Date: 21 Jun 91 14:31:09 GMT
References: <1991Jun20.220525.5015@ccu.umanitoba.ca>
Organization: The Castle Anthrax
Lines: 28

In article <1991Jun20.220525.5015@ccu.umanitoba.ca> grdetil@ccu.umanitoba.ca (Gilles R. Detillieux) writes:
>I have been reading this group for a while, but haven't seen this question
>addressed:  Why does the NeXT reassign ownership of all files on an
>Optical Disk to the user ID of the person logged in?  Can this be disabled?

It makes sense.  If you want to excange data with somone, you need to
do this.  If you want to use the same disk on machines that have the
accounts set up differently, you need to do this.  It happens not
because it's an OD, but because it's a removable medium.  The same
thing happens with floppy disks, or with external SCSI disks that
aren't normally mounted.  It's the automounter's "fault".

>Am I the only NeXT user to think that this is a REALLY stupid "feature" in
>the NeXT's Optical Disk support?

Well, I think it's a really good idea.

>If anyone has found a way to defeat this annoying "feature", could you let
>me know?  If NeXT is listening, how about a fix for this in the next release?

Bypass the automounter.  Don't put the floptical in the cube.  Su to
root, and type "mount /dev/od0a /floptical".  It'll prompt you to
insert the disk.  It'll then treat it like a hard drive instead of
like removable media (ie. ownership won't have anything to do with
who's at console, and you can chown stuff).
-- 
Doug DeJulio
ddj@zardoz.club.cc.cmu.edu