Date: Mon, 11 Jan 1999 03:46:37 +1030 (CST) From: Mark Newton <newton@atdot.dotat.org> To: des@flood.ping.uio.no Cc: cvs-all@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, phk@critter.freebsd.dk Subject: Re: sysctl descriptions Message-ID: <199901101716.DAA02993@atdot.dotat.org>
next in thread | raw e-mail | index | archive | help
Dag-Erling Smorgrav <des@flood.ping.uio.no> writes:
> Poul-Henning Kamp <phk@critter.freebsd.dk> writes:
> > In message <86u2y0btan.fsf@niobe.ewox.org>, Dag-Erling Smorgrav writes:
> > >The attached patches implement a mechanism for retrieving a sysctl's
> > >description.
> >
> > The intention was to have a program perambulate /sys and gather
> > the stuff into a man-page or share/misc/sysctl.desc file or similar
>
> If having sysctl descriptions in the kernel really is a problem for
> some people, it's trivial to add a kernel option to disable my code.
Hmm - Why not put descriptions for the standard sysctls into a KLD which
uses some kind of registration mechanism to tell the sysctl infrastructure
about them?
> How will the system you describe deal with sysctls located in
> third-party, binary-only KLDs?
By the same mechanism suggested above?
- mark
--------------------------------------------------------------------
I tried an internal modem, newton@atdot.dotat.org
but it hurt when I walked. Mark Newton
----- Voice: +61-4-1958-3414 ------------- Fax: +61-8-83034403 -----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901101716.DAA02993>