Xref: utzoo comp.unix.wizards:6301 comp.arch:3256
Path: utzoo!utgpu!water!watmath!clyde!rutgers!gatech!bbn!oberon!cit-vax!mangler
From: mangler@cit-vax.Caltech.Edu (Don Speck)
Newsgroups: comp.unix.wizards,comp.arch
Subject: Re: R/O root (was: Jerry Pournelle on UNIX)
Summary: readonly /usr
Message-ID: <5363@cit-vax.Caltech.Edu>
Date: 29 Jan 88 11:44:28 GMT
References: <1495@osiris.UUCP> <2126@haddock.ISC.COM> <1497@osiris.UUCP> <14227@oddjob.UChicago.EDU>
Organization: California Institute of Technology
Lines: 14

In article <14227@oddjob.UChicago.EDU>, matt@oddjob.UChicago.EDU (Java Man) writes:
> If I were out to set up a r/o root, I'd make a r/o /usr also - there
> are even more seldom-modified files there.

A pair of my vaxen have had a read-only /usr on a dual-ported
disk since 1985.  It's a pain to update, though; every couple
of months they come down to bring their /usr into sync with the
vax that has /usr/src.

Mounting read-only is the price of dual-porting.  I dual-ported
it because /usr is 200 MB (/usr/font and /usr/local are HUGE).

Don Speck   speck@vlsi.caltech.edu  {amdahl,ames!elroy}!cit-vax!speck
		  ^^^^ vax with read-only /usr