From owner-freebsd-fs@FreeBSD.ORG Sun Jul 22 15:25:26 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28EAC106564A for ; Sun, 22 Jul 2012 15:25:26 +0000 (UTC) (envelope-from sam@athyriogames.com) Received: from madonna.sslcatacombnetworking.com (madonna.sslcatacombnetworking.com [174.133.19.130]) by mx1.freebsd.org (Postfix) with ESMTP id E5B488FC0C for ; Sun, 22 Jul 2012 15:25:25 +0000 (UTC) Received: from c-98-206-215-156.hsd1.in.comcast.net ([98.206.215.156] helo=laptopv) by madonna.sslcatacombnetworking.com with esmtpa (Exim 4.69) (envelope-from ) id 1Ssxu5-0003EU-Uq; Sun, 22 Jul 2012 10:17:06 -0500 From: "Sam Zehr" To: "'Andreas Nilsson'" References: <01bf01cd66d4$84756b40$8d6041c0$@com> In-Reply-To: Date: Sun, 22 Jul 2012 10:24:58 -0500 Message-ID: <01f601cd681e$297f2b40$7c7d81c0$@com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac1n79ThjOimdovbTMyGtPbKxV0izQAKc7tA Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - madonna.sslcatacombnetworking.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - athyriogames.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: RE: Boot disk read-only? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 15:25:26 -0000 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 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