Page MenuHomeFreeBSD

nextboot.8: clarify that loader(8) does not delete nextboot.conf file, add missing serial comma
ClosedPublic

Authored by danfe on Aug 6 2020, 9:20 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 10, 3:14 PM
Unknown Object (File)
Wed, Nov 6, 2:53 AM
Unknown Object (File)
Mon, Nov 4, 5:07 PM
Unknown Object (File)
Wed, Oct 30, 8:04 AM
Unknown Object (File)
Oct 5 2024, 7:55 AM
Unknown Object (File)
Sep 7 2024, 9:00 AM
Unknown Object (File)
Sep 6 2024, 1:17 AM
Unknown Object (File)
Aug 23 2024, 8:25 PM
Subscribers

Details

Summary

Right now, the nextboot(8) manual page suggests that the loader(8) would delete the /boot/nextboot.conf file or its contents which is 1) not the most user-friendly way of working with custom configurations, and 2) simply not true.

In reality, what happens is that when next-boot kernel is being configured, nextboot_enable="YES" line is added at the top of that file. After loader(8) reads the configuration, it would not delete it, but simply change the setting to "NO", that is, disable it.

While here, add one missing serial (Oxford) comma and fix some bogus line wraps along the way.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

danfe requested review of this revision.Aug 6 2020, 9:20 AM

Anything else required to move this forward? Interested folks can read the actual nextboot-support code in stand/forth/support.4th and stand/lua/config.lua files.

bcr added a subscriber: bcr.

It's fine for me to commit it with at .Dd bump.
Thanks for the reminder.

This revision was not accepted when it landed; it landed in state Needs Review.Oct 11 2020, 10:40 AM
This revision was automatically updated to reflect the committed changes.