Subject: defopt'ing before 1.4
To: None <email@example.com>
From: Erik Bertelsen <firstname.lastname@example.org>
Date: 03/19/1999 08:13:53
Is it the intention to defopt most/all common kernel
configuration options before releasing 1.4 ?
At least I think that options that are "almost always"
used in a kernel should be defopt'ed. This has largely
already happened with the MI options, but some MD options
still need to defopt'ed.
A criterion might be that for each port, at least one
"useful" configuration should cause no diagnostics from
Doing this can be considered at kind of clean-up that should
be doable without problems, as it does not change any kernel
interfaces or features.
E.g. on my pmax I get
config -v SOCKDEV
SOCKDEV:7: warning: undeclared option `MIPS1' added to IDENT
SOCKDEV:27: warning: undeclared option `HZ=256' added to IDENT
on my mac68k I get (some MI, some MD):
config -v Q610
../../../../arch/mac68k/conf/std.mac68k:8: warning: undeclared option `HZ' added to IDENT
Q610:11: warning: undeclared option `NKMEMCLUSTERS' added to IDENT
Q610:12: warning: undeclared option `NMBCLUSTERS' added to IDENT
Q610:32: warning: undeclared option `M68040' added to IDENT
Q610:33: warning: undeclared option `FPSP' added to IDENT
What's the opinions ?
- Erik Bertelsen