On Mon, Jan 4, 2016 at 10:41 AM, Colin Percival <cperc...@tarsnap.com> wrote:
> On 01/04/16 09:09, Warner Losh wrote: > > On Mon, Jan 4, 2016 at 10:00 AM, Colin Percival <cperc...@tarsnap.com > > <mailto:cperc...@tarsnap.com>> 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. > It does. But all that's mirrored in a MFS and it takes an explicit command to write it all back. This is poorly matched with where the firstboot files are actually removed. > > 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? > So it does. I thought it mucked about with flags and such. Warner _______________________________________________ svn-src-head@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
