Date: Fri, 14 Feb 1997 23:46:43 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: undocumented kernel options... Message-ID: <Mutt.19970214234643.j@uriah.heep.sax.de> In-Reply-To: <199702141834.LAA13492@narnia.plutotech.com>; from Justin T. Gibbs on Feb 14, 1997 11:34:20 -0700 References: <199702140807.AAA14402@lestat.nas.nasa.gov> <199702141834.LAA13492@narnia.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
(Killed an overly long Cc list.) As Justin T. Gibbs wrote: > >In our world, config(8) is simply too flexible, and having to update > >the GUI to deal each time would .. suck. > > I don't think that this has to be the case. The last time I looked into > the config system, I thought, "Hmm. What if all configurable driver > options could be dynamically registered/deregistered from the syctl tree?" I also think it would be a maintenance nightmare, but only if this tool wouldn't automatically pick up the existing reference files (LINT, sys/conf/options, sys/<arch>/conf/options.<arch>), and present the information from them. Maintaining this tool separately from the above files would be stupid. I also don't think i would really use that tool for my day-to-day development kernels, but if it's good, i could even imagine using it e.g. for the customer's machine i gonna ship next week, or such. I've already got very used to sysinstall's `Configure' screen at installation time for those machines, despite of knowing where all this has to go into /etc/sysconfig. It's simply more convenient then. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970214234643.j>