From owner-cvs-all Sat Jan 9 11:15:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29952 for cvs-all-outgoing; Sat, 9 Jan 1999 11:15:14 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29918 for ; Sat, 9 Jan 1999 11:15:09 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id UAA17482; Sat, 9 Jan 1999 20:13:58 +0100 (CET) To: Dag-Erling Smorgrav cc: committers@FreeBSD.ORG Subject: Re: sysctl descriptions In-reply-to: Your message of "09 Jan 1999 20:02:14 +0100." Date: Sat, 09 Jan 1999 20:13:58 +0100 Message-ID: <17480.915909238@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk In message , Dag-Erling Smorgrav writes: >Poul-Henning Kamp writes: >> In message <86u2y0btan.fsf@niobe.ewox.org>, Dag-Erling Smorgrav writes: >> >The attached patches implement a mechanism for retrieving a sysctl's >> >description. I haven't tested the patches yet, but they compile >> >cleanly against a fairly recent (couple of hours old) -current. >> This was deliberately not done initially, sticking goops of ascii >> in the kernel doesn't seem optimal. >> >> 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 > > >OK, let's just ignore that somebody has spent time and effort to >produce actual, working, value-adding code, [...] > OK, Lets for a moment not even bother examining the history of the stuff we're hacking around in, and just forge ahead on a tangent, and get boiling mad when somebody tells us that we may not have thought enough about it. >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. It is, just ask small@freebsd.org what adding a lot of text to the kernel will do. Many sysctl descriptions would need to be several kbyte worth of ascii to come even close to a decent description. If you insist on putting it in the kernel, stick it in a section which isn't loaded by default, and have sysctl(8) pull it out of kern.bootfile. >How will the system you describe deal with sysctls located in >third-party, binary-only KLDs? How they intend to document their sysctl's is their problem. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message