On 25/11/05, Josi M. Fandiqo <[EMAIL PROTECTED]> wrote: > > Also the system is probable to suffer electrical failures and since OBSD > > is contained in a CF card I become very interested in running it over an > > unique read-only partition. > > > > The first option was add the "ro" flag to the fstab file, but it's ignored > > and the system leaves the root fs in "rw" mode. The second (and desesperate) > > option was add "mount -o ro /" to /etc/rc.local which seems cause a kernel > > panic (no suprise here) > > > > is it possible to have a root fs in read-only mode with OBSD?
Last time I did this, I did the ramdisk trick as well. I hard linked /dev/MAKEDEV into /etc instead of copying it. Rather than making just a few devices, I did MAKEDEV all, because on a ramdisk, MAKEDEV runs quite quickly. I also patched /etc/rc in a few places where the disk is actually written - /var/db/host.random, ssh/isakmpd keys, rndc keys.. these would write the disk, so i changed rc to generate the file in /tmp, mounted the disk read-write, copied the key to where it was supposed to go, and then remouted read-only. Other directories (/var/log among others) were populated from a tar file in root's home directory. On top of that, I added a crontab to remount the disk read-only on a regular basis in case I have to change something and then forget to mount it read-only before I log out. CK -- GDB has a 'break' feature; why doesn't it have 'fix' too?
