Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!gt-eedsp!flur
From: flur@gt-eedsp.UUCP (Peter W. Flur)
Newsgroups: comp.sys.next,git.next
Subject: read-only file systems
Summary: how do you get around this problem?
Keywords: file-system, NFS, mount
Message-ID: <619@gt-eedsp.UUCP>
Date: 3 Mar 89 01:29:55 GMT
Reply-To: flur@gt-eedsp.UUCP (Peter W. Flur)
Followup-To: flur!gt-eedsp@gatech.edu
Distribution: usa
Organization: School of Electrical Engineering, Ga. Tech, Atlanta, GA  30332
Lines: 26


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