Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 2 Apr 2011 12:36:16 -0400
From:      Andrew Duane <aduane@juniper.net>
To:        Warner Losh <imp@bsdimp.com>, "perryh@pluto.rain.com" <perryh@pluto.rain.com>
Cc:        "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, "m.e.sanliturk@gmail.com" <m.e.sanliturk@gmail.com>, "avg@freebsd.org" <avg@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>
Subject:   RE: looking for error codes
Message-ID:  <AC6674AB7BC78549BB231821ABF7A9AEB52F1950CE@EMBX01-WF.jnpr.net>
In-Reply-To: <CEB5BE4D-5F52-4A64-A22F-168D2BE40CEA@bsdimp.com>
References:  <4D95E162.40605@FreeBSD.org> <F98114A0-0C00-46EF-BD0C-E48F97FFF3E1@bsdimp.com> <AC6674AB7BC78549BB231821ABF7A9AEB52F1950BB@EMBX01-WF.jnpr.net> <4D95ECDE.1020504@FreeBSD.org> <BANLkTik_ypKnZPn1TXT6LwNH%2BX1tO2eu0w@mail.gmail.com> <4d96d545.e/wWTIUATgk2CGjt%perryh@pluto.rain.com>, <CEB5BE4D-5F52-4A64-A22F-168D2BE40CEA@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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 part=
itions were made for /tmp, /var, and other places we needed to write. Now t=
hat we're upgrading to a later BSD, I hope to refit these with union filesy=
stems instead, to save space and complexity.

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

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

On Apr 2, 2011, at 1:50 AM, perryh@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@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AC6674AB7BC78549BB231821ABF7A9AEB52F1950CE>