Thread View: comp.sys.next.sysadmin
4 messages
4 total messages
Started by aoml
Mon, 28 Sep 1992 19:35
chown under 3.0
Author: aoml
Date: Mon, 28 Sep 1992 19:35
Date: Mon, 28 Sep 1992 19:35
12 lines
756 bytes
756 bytes
We just add a new hp drive purchased from TECOR, when ever we change the onwership of user's files, the whole disk's ownership randemly changed back to one
of our user after few seconds.
The command I use is chown -R directory-name
With -R option, chown seem not only going decending but also going
up to the whole disk.
has anybody experienced that problem ?
We are using 2 NeXT stations trubo clolrs on a small network
aoml,Ying-Yuang Chen
Re: chown under 3.0
Author: Hal.Varian
Date: Mon, 28 Sep 1992 21:41
Date: Mon, 28 Sep 1992 21:41
30 lines
1492 bytes
1492 bytes
In article <28SEP92.15351318@enh.nist.gov> aoml@enh.nist.gov
writes:
> We just add a new hp drive purchased from TECOR, when ever we
change the onwership of user's files, the whole disk's ownership
randemly changed back to one
> of our user after few seconds.
>
> The command I use is chown -R directory-name
>
> With -R option, chown seem not only going decending
but also going
> up to the whole disk.
>
> has anybody experienced that problem ?
> We are using 2 NeXT stations trubo clolrs on a small
network
>
> aoml,Ying-Yuang Chen
The same thing happened to me with my Fujitsu drive. I was
running 3.0 beta PR2 when it happened, so I decided to wait for
the official release before I tried to figure out what was going
on.
Does anyone know?
--
Hal.Varian@umich.edu Hal Varian
voice: 313-764-2364 Dept of Economics
fax: 313-764-2364 Univ of Michigan
Ann Arbor, MI 48109-1220
Re: chown under 3.0
Author: Louis Mamakos
Date: Tue, 29 Sep 1992 00:23
Date: Tue, 29 Sep 1992 00:23
34 lines
1726 bytes
1726 bytes
In article <1992Sep28.214104.25073@lsa.umich.edu> Hal.Varian@umich.edu writes: >In article <28SEP92.15351318@enh.nist.gov> aoml@enh.nist.gov >writes: >> We just add a new hp drive purchased from TECOR, when ever we >change the onwership of user's files, the whole disk's ownership >randemly changed back to one >> of our user after few seconds. >> >> The command I use is chown -R directory-name >> >> With -R option, chown seem not only going decending >but also going >> up to the whole disk. >> >> has anybody experienced that problem ? >> We are using 2 NeXT stations trubo clolrs on a small >network >> >> aoml,Ying-Yuang Chen > >The same thing happened to me with my Fujitsu drive. I was >running 3.0 beta PR2 when it happened, so I decided to wait for >the official release before I tried to figure out what was going >on. Yes, don't allow the workspace to auto-mount the disk. When it does, the file system is mounted such the each file appears to be owned by the user that's currently logged in. If you think about it, that's the correct behaviour for removable media such as a floppy. The solution is configure an entry in /etc/fstab and wherever the hell it goes in netinfo for that file system. louie
Re: chown under 3.0
Author: David Lemson
Date: Tue, 29 Sep 1992 05:30
Date: Tue, 29 Sep 1992 05:30
13 lines
1114 bytes
1114 bytes
louie@ni.umd.edu (Louis Mamakos) writes: >The solution is configure an entry in /etc/fstab and wherever the hell >it goes in netinfo for that file system. Well, you needn't put it in netinfo...the netinfo fstab map is only read for type nfs filesystems, as type 4.3 filesystems are already mounted by /etc/rc before netinfo is even running. (at least in 2.1...) -- David Lemson (217) 244-1205 University of Illinois NeXT Campus Consultant / CCSO NeXT Lab System Admin Internet : lemson@uiuc.edu UUCP :...!uiucuxc!uiucux1!lemson NeXTMail accepted BITNET : LEMSON@UIUCVMD
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads