svn commit: r366626 - head/sbin/reboot

[Eugene Grosbein]

12.10.2020 10:33, Alexey Dokuchaev wrote:

> On Sun, Oct 11, 2020 at 09:17:42PM -0600, Warner Losh wrote:
>> On Sun, Oct 11, 2020, 8:13 PM Alexey Dokuchaev wrote:
>>> ...
>>> I still don't understand how could rm be better than graceful disabling
>>> alternative configuration with nextboot_enable="NO".  I most certainly
>>> do *not* like when my custom config files are being removed, especially
>>> silently.  When I see nextboot_enable="NO"<space> I know that the file
>>> had been processed, and processed by the machine, not me (since I would
>>> never add trailing space).  When I don't see the file, I'd be questioning
>>> myself if I've ever added it here, or maybe I put in the wrong location.
>>
>> Nextboot.conf is special. It will be deleted. It doesn't belong to you, it
>> belongs to nextboot(8).
> 
> OK, I see your point.
> 
>>> Personally I find them quite useful, except when they contradict the
>>> reality (like this time).  In these cases, I'd fix them.
>>
>> For now, it's fine.

Note that testing kernel sometimes *requires* additional set of loader settings
like kernel parameter tuning and/or set of kernel modules loaded including NICs or GEOMs like gjournal/graid
that may affect boot process. And our loader does apply such settings when processing nextboot.conf.

Maybe this is the reason nextboot.conf should be removed after it fired once.
I personally edit it manually every time I use this feature and I keep a copy of the file with distinct name
to restore it for another run.