svn commit: r366626 - head/sbin/reboot

Kyle Evans kevans at freebsd.org
Sun Oct 11 13:59:50 UTC 2020


On Sun, Oct 11, 2020 at 8:30 AM Alexey Dokuchaev <danfe at freebsd.org> wrote:
>
> On Sun, Oct 11, 2020 at 04:08:09PM +0300, Toomas Soome wrote:
> > > On 11. Oct 2020, at 16:01, Alexey Dokuchaev wrote:
> > >> ...
> > >> Also nextboot.conf not generic configuration file (such as loader.conf
> > >> or loader.conf.local), but the implementation specific file, part of
> > >> special feature.
> > >>
> > >> That is, one should not assume the presence of nextboot.conf file, make
> > >> assumptions about its content, or perform manual edits on it.
> > >
> > > Do we want it to be the second-class citizen like this?  Would it make
> > > better sense by documenting it more completely instead?
> >
> > It is not really about being second-class citizen, it really is about if
> > and how we can implement the feature. With UFS there is a limited write
> > (write to existing, allocated disk blocks), with ZFS there is no write to
> > file system at all.
>
> I see; that would explain why loader(8) replaces the "YES" -> "NO"<space>,
> but I guess I'd have to read the discussion on -rc@ which lead to r177062,
> because I don't see the reason for it to be removed (twice) if it's being
> disabled by the loader(8) earlier anyway.
>

IMO both steps are important. You have to (at least try to) disable it
in case it doesn't get you all the way to multi-user, but then you
don't want the old contents of nextboot.conf being inadvertently used
on another boot if someone's habitually `nextboot -a`ing.


More information about the svn-src-head mailing list