Date: Tue, 01 Apr 2003 14:38:23 -0500 (EST) From: "J. Seth Henry" <jshamlet@comcast.net> To: Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com> Cc: questions@freebsd.org Subject: Re: /dev on a read-only filesystem? Message-ID: <20030401134625.E3405-100000@whitetower.gambrl01.md.comcast.net> In-Reply-To: <44adfbdwnb.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I'll have to give this a try. Right now, I am just remounting / read-only after boot as part of my /usr/local/etc/rc.d scripts. I'd prefer to eliminate all writes, though. <sigh> I suppose this means I'm going to have to repartition the microdrive again. /usr keeps getting smaller and smaller. Thanks for the help, Seth Henry On Mon, 31 Mar 2003, Lowell Gilbert wrote: > "J. Seth Henry" <jshamlet@comcast.net> writes: > > > The trick is, if I make / read-only, I run into problems with /dev. During > > boot, I get numerous error messages - and things don't seem to work quite > > right. Is there a way to mount / read-only, while maintaining a working > > /dev? Can /dev be mounted from another filesystem - or, preferably (since > > the OS is already running) be linked to, say, /usr/dev? > > I think you still need the devices on the root filesystem, even if you > later mount something else over the directory. That's because there's > a chicken and egg problem -- they need to be there for the other > filesystems to be mounted in the first place. So the symlink approach > won't work, but mounting it on top of /dev from elsewhere would work. > > I believe the typical approach on diskless machines is to put it into > an mfs, but you'd have to doublecheck the documentation on it. > > You could also use devfs, of course, but I'm not sure, offhand, how > well that worked before 5.x. > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030401134625.E3405-100000>