Date: Sun, 10 Jan 1999 23:27:26 -0800 From: Mike Smith <mike@smith.net.au> To: Darren Reed <darrenr@reed.wattle.id.au> Cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), phk@critter.freebsd.dk, des@flood.ping.uio.no, committers@FreeBSD.ORG Subject: Re: sysctl descriptions Message-ID: <199901110727.XAA87311@dingo.cdrom.com> In-Reply-To: Your message of "Sun, 10 Jan 1999 22:20:10 %2B1100." <199901101120.WAA15560@avalon.reed.wattle.id.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > As I'm not familiar with the KLD issue, I cannot say what would and > wouldn't be a good way to resolve the problem. If it were applied > to KLM's, then my response would be to have the "modload process" > involve more than just "modload foo.o". It might be that a wrapping > program or script is needed (modload already supports something similar > with the -e command line option). If the interface is truely lacking > in a way to support this feature then perhaps the interface needs to > change. It's difficult to know how to proceed in all cases, which is the issue here. If the module is fetched off a floppy disk by the bootloader to be aggregated into the kernel object, it's not possible to bring the description text in any way other than with the module. > I'm not trying to say that the descriptions shouldn't be there, but at > least try to be smart about considering alternatives and the work involved. Believe me, many of us have. The only way to tie the descriptions directly to the variables they describe is to do just that. Any other solution involves several alternative mechanisms and opportunities for incomplete or innacurate descriptions. > Personally, I view the sysctl description code as done by DES as the > "easy solution". It's more than likely what most people would do if > they had the same problem to solve. I don't know whether I would go > on to say that this is the "correct" solution for "this problem" (but > then people may not be at all interested in the "correct" solution). A "correct" solution, meeting all the criteria, would be wonderful; the criteria just seem to me to be fairly close to impossible to satisfty; DES' approach (and Poul's before it) is "adequate" in that it provides the desired result without offending too much in any other direction. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901110727.XAA87311>