Date: Sun, 10 Jan 1999 21:21:09 -0800 From: Mike Smith <mike@smith.net.au> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: mike@smith.net.au (Mike Smith), brian@Awfulhak.org, committers@FreeBSD.ORG Subject: Re: sysctl descriptions Message-ID: <199901110521.VAA86573@dingo.cdrom.com> In-Reply-To: Your message of "Sun, 10 Jan 1999 21:22:59 PST." <199901110522.VAA05798@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> According to Mike Smith: > > Since it's quite clear you really haven't grasped the core of the > > problem, I'll present you with a simple example, and you can explain to > > me how you propose to deal with it. > > > > I have a driver for a new peripheral. It's from a vendor that doesn't > > want to distribute source code, so the driver comes as a KLD module. > > The driver has a number of tuning options, which are exposed via the > > sysctl MIB. > > Let's call this driver foobar. > > > Please explain how I am to find documentation for these tuning options > > in the system manpages. Suggest how your approach is better than, for > > man foobar Care to post the code fragment that sysctl uses to know to execute this when it's asked for a description of the OIDs from the foobar module, and the filter that it will use to extract the one-line descriptions from this manpage, and then how you plan to fit all of this on a compact system (manpages, manpage processing tools, extra bloat in sysctl) where < 20k of kernel stuffage (about 5k on disk) would have done the trick? -- \\ 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?199901110521.VAA86573>