Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 4 Jan 2016 17:41:21 +0000
From:      Colin Percival <>
To:        Warner Losh <>
Cc:        Warner Losh <>, src-committers <>, "" <>, "" <>
Subject:   Re: svn commit: r293115 - head/etc
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 01/04/16 09:09, Warner Losh wrote:
> On Mon, Jan 4, 2016 at 10:00 AM, Colin Percival <
> <>> wrote:
>     On 01/03/16 11:18, Warner Losh wrote:
>     >   Fix the read-only
>     >   root case with horrible kludge of mounting rw removing the files, then
>     >   mounting ro.
>     The solution I intended when I introduced this (and used elsewhere) was to
>     set $firstboot_sentinel in /etc(/defaults)?/rc.conf.  This case is precisely
>     why it's a shell variable, in fact.
> Except that's not exactly useful. NanoBSD boots with no filesystems writable
> that are permanent.  So I could set it to /var/firstboot or something like that,
> and the error would go away. However, that wouldn't solve the problem
> because /var is repopulated from base seed files every boot with NanoBSD
> so we'd get firstboot behavior on every single boot. Or, we could remount
> / rw and remove the file and remount it ro when a read-only root was
> requested.

Huh, ok.  I assumed that you had a /conf/ or something like that for storing
persistent configuration data.

> I wondered to myself why we didn't use the same mechanism as nextboot
> for this feature. Do you know?

Doesn't that still write to the filesystem?

Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | | Online backups for the truly paranoid

Want to link to this message? Use this URL: <>