Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!ncis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!purdue!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: jhd%maths.bath.ac.uk@nss.cs.ucl.ac.uk (James Davenport)
Newsgroups: comp.sys.sun
Subject: Re: the /usr partition
Message-ID: <8901151750.AA23371@rice.edu>
Date: 19 Jan 89 11:40:50 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 22
Approved: Sun-Spots@rice.edu
Original-Date: Sun, 15 Jan 89 15:44:18 GMT
X-Sun-Spots-Digest: Volume 7, Issue 113, message 2 of 11
X-Issue-Reference: v7n102

In Volume 7, Issue 102, message 11 of 18, Scott Menter says
> Well, this has been said before, but the point is that /usr should be
> mounted read-only under 4.x.

I buy this argument for clients (in fact, I do the same already under
SUNos 3.x). BUT, on the server I mount it r/w because I typically make 1/2
(one or two) edits a week to it: adding to /usr/etc/printcap ot termcap or
updating shell scripts in /usr/local/bin or ...

I don't run 4.0 (yet:-)) - what's the argument that says /usr should be
r/o on the server?

[[ As I recently found out, you need it even to boot single user, since
most of the executables are on /usr (for example, /bin is a symlink to
/usr/bin!) as well as the shared library.  If it is mounted r/o, then a
crash that doesn't even have a chance to sync (such as a power outage or a
"L1-A" followed by "b") won't leave the partition in an inconsistent
state.  Of course, if you aren't writing to it anyway, it probably doesn't
matter.  --wnl ]]

James Davenport
jhd@uk.ac.bath.maths