Date: Sun, 22 Jul 2012 10:24:58 -0500 From: "Sam Zehr" <sam@athyriogames.com> To: "'Andreas Nilsson'" <andrnils@gmail.com> Cc: freebsd-fs@freebsd.org Subject: RE: Boot disk read-only? Message-ID: <01f601cd681e$297f2b40$7c7d81c0$@com> In-Reply-To: <CAPS9%2BStQY%2B3W3aYHaXsqOeFGus18Mt0x1pGV1OTYOvRc1Wf=vw@mail.gmail.com> References: <01bf01cd66d4$84756b40$8d6041c0$@com> <CAPS9%2BStQY%2B3W3aYHaXsqOeFGus18Mt0x1pGV1OTYOvRc1Wf=vw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks Andreas
I read the section on NanoBSD, but did not find any reference to 'touch
/etc/diskless/
I also had advice to check to see what files are changing:
find / -mtime -1d -print
Returns changes in /dev, /tmp, and /var only
/tmp and /var are memory disks, I assume this is expected behavior.
Sam
From: Andreas Nilsson [mailto:andrnils@gmail.com]
Sent: Sunday, July 22, 2012 5:02 AM
On Sat, Jul 21, 2012 at 2:05 AM, Sam Zehr <sam@athyriogames.com> wrote:
{edited for brevity}
How do I make a disk in FreeBSD 9.0 _completely_ read-only?
rc.initdiskless is working
1. Add noatime to fstab options
2. Add vfs.nfs.diskless_valid=1 to /boot/loader.conf
So far this is not working on BSD 9.0. It looks like something is changing
on the disk during boot
Sysctl vfs.nfs.diskless_valid returns 0 once booted up
Please note that I am not just concerned about files - the entire disk needs
to be locked, like ROM.
Or perhaps a reason why setting vfs.nfs.diskless_valid=1 in
/boot/loader.conf does not appear to work?
Perhaps start by reading
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/nanobsd/index.html which
should contain the basics plus some nice extra features.
Short version: did you do 'touch /etc/diskless' ?
Best regards
Andreas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01f601cd681e$297f2b40$7c7d81c0$>