Bug 22339

Summary: request to add new kernel config "GENLINT"
Product: Base System Reporter: rick <rick>
Component: confAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.1-RELEASE   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
GENLINT.gz none

Description rick 2000-10-27 06:20:01 UTC
Often those who reconfig their kernels like to start with GENERIC and
go through LINT for additional options.  There's a tendancy to mistype
options when adding from LINT to GENERIC, and starting with a LINT
base is just a huge jump (plus certain options/comments in GENERIC
don't appear in LINT).  Along comes GENLINT, a cross between the two.
GENLINT is a GENERIC kernel with the LINT look.  It has all the lines
from LINT with the options of GENERIC.  Brave users can start with
GENLINT (having the same config as a GENERIC), yet easily look for
and replace options, instead of trying to merge two long config files.
GENLINT = GENERIC plus commented LINT options...

This is not intended (yet) as a replacement to GENERIC or to LINT but
as a configuration that has been merged to speed up the re-config time
for experienced users.  Normal/inexperienced users can still use
GENERIC, but I know that many hackers would like this addition.  It is
truly a merge of the two:  I went through LINT line-by-line, comparing
to GENERIC lines, ensuring that remaining lines including additional
comments in GENERIC are included in GENLINT.  Through this long
process I discovered options present in GENERIC and not in LINT!

I usually spend 20-30 minutes each release to create my own GENLINT.
If it comes down to it, I am willing to regenerate!!! and submit a
GENLINT for the Project for **each release** if it will get onto the
ISO images and save me (and others) time while performing upgrades...
(I've been doing GENLINT since 2.2.2 in case anyone wants old copies,
contact me!)

Fix: uudecode the following file and ungzip it to: usr/src/sys/i386/conf/
Comment 1 Poul-Henning Kamp freebsd_committer freebsd_triage 2000-12-18 20:57:21 UTC
State Changed
From-To: open->closed

I don't think you will be able to sell this idea. 

The general move is towards a module based kernel, here you can 
either load modules at runtime or link them in at kernel compile time. 

How we will configure this is anyones guess, but I don't think adding 
another kernel config file is it.