Date: Sat, 26 Aug 2000 01:47:50 +0000 From: Alan Clegg <abc@firehouse.net> To: Greg Lehey <grog@lemis.com> Cc: freebsd-questions <freebsd-questions@FreeBSD.ORG>, freebsd-small@FreeBSD.ORG Subject: Re: read only / filesystem Message-ID: <20000826014750.F32393@diskfarm.firehouse.net> In-Reply-To: <20000826110117.F52219@wantadilla.lemis.com>; from grog@lemis.com on Sat, Aug 26, 2000 at 11:01:18AM %2B0930 References: <20000824002732.A45983@dogma.freebsd-uk.eu.org> <20000824101341.D66923@wantadilla.lemis.com> <20000824130404.A51338@dogma.freebsd-uk.eu.org> <20000825111535.F548@wantadilla.lemis.com> <20000824234917.A93373@mammalia.org> <20000826110117.F52219@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Unless the network is lying to me again, Greg Lehey said: > Basically, I think our current layout isn't really suited to a > read-only root file system. Somebody should think out a better > approach (and wonder whether the change is worth the effort). Greetings... In my recent bashing around with my NIC and NFS booting, I've come across several issues regarding both read-only / and problems with installing on NFS-only systems. I can see that both of these are intertwined, and I'd be willing to work on this project. I'd recommend working with (around?) the existing /etc/rc.diskless[12] which already deal in a rather painful (when mount_null is disfunctional) way with a possible read-only /. As to the question of it being worth the effort, yes, it is, if for no reason other than '-small' installations that may rely on booting from un-modifiable devices such as CD-ROM, or from devices with a limited write-lifetime such as flash. Anyway, Yes, I'll take up the banner (in my spare time 8-) to get this on-task. AlanC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000826014750.F32393>