Date: Fri, 12 Mar 1999 14:59:53 -0800 From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> To: Steven Young <dreamer@freelow.ninsei.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: visual config editor Message-ID: <24926.921279593@zippy.cdrom.com> In-Reply-To: Your message of "Fri, 12 Mar 1999 15:49:03 MST." <Pine.BSF.4.05.9903121541510.20290-100000@freelow.ninsei.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hm, well now. The help text would be pretty easy to put in the LINT
> file - probably something simple like just putting a comment block above
> each option, and that will be imported as the help text. However, as
I think the comment block should contain some sort of standardized
"record" of not just help text, but possible values for certain fields
(or information which denotes that they're display-only, or whatever).
> far as including a list of required/possible arguments.. hm. Are the
> arguments listed in the LINT file all the _possible_ arguments for a
> particular option, or are they just the required ones? I'm hoping it's
"Yes" :) The answer is that LINT represents something of a pastiche'
of formats. Some drivers have all their flags and such enumerated
there, others expect you to read the man page, etc.
Nobody has ever really tried to use LINT as more than a, well, lint
checker on the kernel ("does LINT still config and build?") even
though it's now evolved far beyond that as a kind of documentation
repository, driver checklist file ("what do we support?"), home for
experimental drivers (that will never see GENERIC), etc. It is in
dire need of a "given what we know now" sort of review and if you can
get the end result by Bruce, you'll be able to get it by anybody.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24926.921279593>