Bug 195901 - Addition of a well-commented default /etc/src.conf file
Summary: Addition of a well-commented default /etc/src.conf file
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-11 22:10 UTC by George
Modified: 2015-11-17 20:04 UTC (History)
1 user (show)

See Also:


Attachments
example version of proposed /etc/src.conf file (19.18 KB, text/x-matlab)
2014-12-11 22:10 UTC, George
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description George 2014-12-11 22:10:45 UTC
Created attachment 150487 [details]
example version of proposed /etc/src.conf file

I am proposing that a full /etc/src.conf file be included in the base system, at least initially populated by the contents of the src.conf(5) man page.

I initially proposed this for Tim Kientzle's Crochet builds scripts for small systems (https://www.github.com/kientzle/crochet/crochet-freebsd), and I was advised it might be more useful in the base system.

This would allow a clear direction for those interested in minimizing the base system's footprint with customized base builds and updates, particularly with space-restricted systems such as Raspberry Pi and BeagleBone builds.  However, this would also enable users with full-sized systems to remove extraneous base system parts.  It would be a rare case today in which a system needs floppy disk support (WITHOUT_FLOPPY=yes) or all three of the packet filters included in the base (ipf, ipfw and pf).

There are additional settings to add not documented in the man page in the future.

Ideally, this could be respected in the initial installation of a system.
Comment 1 Enji Cooper freebsd_committer 2015-11-10 13:08:40 UTC
This just duplicates src.conf(5) though and will bitrot over time if it's not maintained :(... If anything, it should be manually generated, however... I'm not sure if this provides much value to be honest :/...
Comment 2 Enji Cooper freebsd_committer 2015-11-10 13:09:03 UTC
(In reply to NGie Cooper from comment #1)

manually -> automatically
Comment 3 George 2015-11-17 20:04:46 UTC
I concur with your comments ngie.

Originally, this was meant for Tim Kientzle's crochet, but it was recommended to be a PR here.

Despite my apprehensions, I submitted here...  I agree it could/should be automatically generated, but I think it's much more relevant for particular platforms and use-cases, such as embedded or SoC systems like RPis.