Page MenuHomeFreeBSD

bsdinstall: complete whitelabeling the installer
ClosedPublic

Authored by oshogbo on Jan 28 2024, 6:57 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, May 14, 9:43 AM
Unknown Object (File)
Fri, May 10, 7:52 PM
Unknown Object (File)
Fri, May 3, 5:43 PM
Unknown Object (File)
Sun, Apr 28, 12:52 PM
Unknown Object (File)
Thu, Apr 25, 10:25 PM
Unknown Object (File)
Apr 16 2024, 10:10 PM
Unknown Object (File)
Apr 1 2024, 1:14 PM
Unknown Object (File)
Mar 5 2024, 2:17 AM
Subscribers

Details

Summary

The commit 147585b4893bc38698aaa971af336b241477eac3 introduces
whitlabeling. This commit addresses couple more places where the
os name was missed.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Seems reasonable to me.
Who will be using this?

This revision is now accepted and ready to land.Jan 28 2024, 8:43 PM

LGTM

usr.sbin/bsdinstall/startbsdinstall
4

Off-topic/bikeshed, an idea for the future, I wrote a similar comment in another review.
Here we are importing thousands lines of code to know only the value of OSNAME. Paradoxically it is not used by bsdconfig so we could move OSNAME="FreeBSD" to bsdinstall. Maybe in bsdinstall/startbsdinstall or a new file bsdinstall/customization. It could be easier to document and change for users than to have a variable in an unrelated bsdconfig file.

In D43638#995136, @imp wrote:

Seems reasonable to me.
Who will be using this?

I don't have any particular user in mind. It was originally started by Netgate. However, I can imagine that any product that uses a FreeBSD customized installer like pfsense, opnsense, etc. might fight that useful. Or actually, anything that wants to brand FreeBSD.

usr.sbin/bsdinstall/startbsdinstall
4

That's an interesting idea; I might look into that.