> I want the user to have control of what's going on at compile time, and
> I'd like the ability for the user to be able to re-configure it at
> userconfig time as well.
> The problem with sysctl is that it's trying to be all things to all men,
> and like M$ Registrty, it becomes too complex and unweildy since *all*
> configuration is dumped into it's bowels, so keeping the namespace sane
> is almost impossible. And, assuming you've done a good job of keeping
> the namespace separated out, you have to understand *how* it's separated
> in order to use it, which means that your average user won't know which
> know to tweak until after he's read the poorly documented 14 page book
> that explains each of the sysctl knobs.
> Excpecting the users to know/understand each and every tweakable know is
> ludicrous. By making the knob/hooks settable in the config file
> (something they already know how to deal with, or will know how to deal
> with) means it's *really* obvious which device they are messing with, so
> the learning curve is much less.
And in the same spirit, I'd like to be able to specify in the config file
the same stuff that gets specified by the 'pnp' commands when you do boot
with the -c option. Having it in the /kernel.conf file is sort of kludgy.
It would be nice to be able to extend the config file syntax to build
Another instance of this capability might be used to specify SCSI
quirks, rather than modifing the source code, and making sure it doesn't
get zapped next time you do an upgrade.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message