simonb@netbsd.org (Simon Burge) writes:
> We could even have an /etc/rc.d
> script set some of these up on boot by parsing a /etc/system type file :)
> 
> Seriously, is this worth taking further?

(1) if you go there, they all need to be patchable kernel variables, too.

(2) in the world of static configuration of everything, in tables,
this doesn't make as much sense.  in the world of startup-time
configuration of file systems, etc., it makes some more sense, though
the implementation is a bit hokey still.  (you'd want the 'set'
function to register or unregister the fs.)  For syscalls, this
quickly becomes... cumbersome.

(3) what you (may) really want is the state where 'optional' feature
sets are in loadable modules, which you can disable at will...


You might want to take it further, but i don't think it's the right
way to go, architecturally, and i think at some point down that path
lies madness...


cgd