This is read-only-file-systems in view mode; [Up]
Date: Sun 03-Mar-1989 01:29:55 From: Unknown Subject: read-only file systems This may be a real dumb question, but how do I get around the NeXT machines partitioning the file system so that I can't write to various partitions? Specifically, I want to put some files (i.e. TeX fonts) in /usr/lib/tex, but the machine thinks (knows) it is a read only file system. I know that /etc/fstab says it is read only also, but /etc is also read-only, so i can't change it either. I've tried umounting, but the device is obviously busy. When I first set up the machines, given the lack of documentation, I only assigned machine names, but no disk names. Could this be the source of my problem. I also want to run NFS between our machines, but since I can't change /etc/fstab, it makes it hard. Any help or suggestion would be greatly appreciated. Peter ----------------------------Peter Flur---------------------------- USMAIL: Box 32500 Georgia Tech, School of Electrical Engineering, Atlanta, GA 30332 USENET: ...!{allegra,hplabs,ihnp4,ulysses}!gatech!gt-eedsp!flur INTERNET: flur@gt-eedsp.gatech.edu, flur@gt-eedsp.uucp, gteedsp!flur@gatech.edu, gt2500a@prism.gatech.edu PHONE: (404) 894-2908 ext. 6 or (404) 894-2955 >From: jgreely@diplodocus.cis.ohio-state.edu (J Greely)
Date: Sun 03-Mar-1989 17:20:16 From: Unknown Subject: Re: read-only file systems Computer and Information Science In article <619@gt-eedsp.UUCP> flur@gt-eedsp.UUCP (Peter W. Flur) writes: >This may be a real dumb question, but how do I get around the NeXT >machines partitioning the file system so that I can't write to various >partitions? The answer is, of course, to edit /bootdisk/Admin/Private/conf/fstab (alias /etc/fstab), to make /bootdisk/NeXT rw. >I know that /etc/fstab says it is read only also, but /etc >is also read-only, so i can't change it either. I've tried umounting, >but the device is obviously busy. The file system reorganization bit *you*! /etc/fstab is a symbolic link to /bootdisk/Admin/Private/conf/fstab, which is located on the root partition, which is mounted read-write. Many of the configuration files are shipped without the write bit turned on. Important safety tip: if you're an emacs user, make sure you're editing the files in their proper NeXT location. Don't try to edit /etc/fstab; it's just a symlink. (wouldn't it be nice if mount supported the SunOS remount option?) -=- J Greely (jgreely@cis.ohio-state.edu; osu-cis!jgreely) >From: pvo1478@neptune.uucp (Paul O'Neill)
Date: Sun 04-Mar-1989 05:49:59 From: Unknown Subject: Re: read-only file systems In article <38013@tut.cis.ohio-state.edu> J Greely <jgreely@cis.ohio-state.edu> writes: > >In article <619@gt-eedsp.UUCP> flur@gt-eedsp.UUCP (Peter W. Flur) writes: >> ..........................................I've tried umounting, >>but the device is obviously busy. > What brave soul is going to port ``ofiles'' (what a sweet program!) to the NeXT? :-) Have any Mach wizards come up with a program to show what processes have a file open and what files are open by a process? Paul O'Neill pvo@oce.orst.edu Coastal Imaging Lab OSU--Oceanography Corvallis, OR 97331 503-754-3251 >From: bayes@hpfcdc.HP.COM (Scott Bayes)
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.