Subject: Re: Read-only root filesystem
To: None <email@example.com>
From: =?ISO-8859-1?Q?Mikael_Nystr=F6m?= <firstname.lastname@example.org>
Date: 05/21/2007 21:03:28
On 21 maj 2007, at 14.35, Ingbert Meyer wrote:
> Ignatios Souvatzis wrote:
>> On Sun, May 20, 2007 at 11:30:12AM +0200, Mikael Nystr=F6m wrote:
>>> I have other partitions that are mounted read-write so every =20
>>> file that needs to be updated regulary resides on these =20
>>> partitions (actually softlinks for motd/resolv.conf etc), but =20
>>> how about /dev? Don't I need it to be read-write?
>> Modern answer:
>> Remove all device nodes from it. /sbin/init will create a MFS and =20
>> the device nodes when you boot.
> But be careful: current /sbin/init creates a MFS with only 1024 =20
> inodes, so you will probably have to tweak MAKEDEV or patch /sbin/=20
> init, if you want to do a "MAKEDEV all".
>> Ancient answer:
Is this applicable to NetBSD 3.0? I'm running the i386-port in =20
Parallels Desktop for development, the real machine will be running =20
the latest stable release when I'm finished.
Removing everything except MAKEDEV (correct?) and reboot results in =20
``warning: no /dev/console'', there's no more output beyond this =20
point. So, is init trying to run ``MAKEDEV all'' at this stage when =20
it realizes that there's nothing in /dev, and runs out of inodes in =20
the MFS? A ``MAKEDEV all'' on the i386 creates well over 1024 devices =20=
and files in /dev ...
Is it the best (easiest) solution to patch MAKEDEV according to my =20
Thanks for the help!
> Ingbert Meyer
> orceo GmbH
> Landsberger Str. 398
> 81241 M=FCnchen
> Fon: +49 89 4613-1215
> Fax: +49 89 4613-1999
> Email: email@example.com
> Web: http://www.orceo.com/
> Gesch=E4ftsf=FChrer: Nicolas Wild
> HRB 158845, Amtsgericht M=FCnchen
> UID: DE 245 334 938