looking for error codes

[Andrew Duane]

My work around read-only systems extended this, to allow a general FreeBSD system to come up with "main media" write locked. In the RC files, MFS partitions were made for /tmp, /var, and other places we needed to write. Now that we're upgrading to a later BSD, I hope to refit these with union filesystems instead, to save space and complexity.

--
Andrew Duane             Juniper Networks
978-589-0551              10 Technology Park Dr
aduane at juniper.net      Westford, MA  01886-3418

________________________________________
From: owner-freebsd-hackers at freebsd.org [owner-freebsd-hackers at freebsd.org] On Behalf Of Warner Losh [imp at bsdimp.com]
Sent: Saturday, April 02, 2011 11:54 AM
To: perryh at pluto.rain.com
Cc: freebsd-hackers at freebsd.org; m.e.sanliturk at gmail.com; avg at freebsd.org; freebsd-arch at freebsd.org
Subject: Re: looking for error codes

On Apr 2, 2011, at 1:50 AM, perryh at pluto.rain.com wrote:
>
>> With respect to my knowledge , no one of the operating systems
>> has a facility to separate read-only and modifiable parts ...
>
> SunOS 4 had a partial solution to this, by rearranging the FS layout
> so that /usr could be mounted read-only (and often, from a server --
> IIRC a single /usr could be shared among multiple diskless clients).
> They used quite a few symlinks so that things could be found in
> their accustomed places although actually located elsewhere.  The
> scheme was fairly well described in the SunOS 4 manual set; granted
> _finding_ a SunOS 4 manual set these days may be a challenge :)

FreeBSD can do this too.  In fact, NanoBSD relies heavily on having most of the system mounted read-only, and has MFS partitions for /etc and /var.

Warner


_______________________________________________
freebsd-hackers at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"