From owner-cvs-all Sat Jan 9 03:32:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17315 for cvs-all-outgoing; Sat, 9 Jan 1999 03:32:47 -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 DAA17308 for ; Sat, 9 Jan 1999 03:32:41 -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 MAA16344; Sat, 9 Jan 1999 12:31:30 +0100 (CET) To: Dag-Erling Smorgrav cc: committers@FreeBSD.ORG Subject: Re: sysctl descriptions In-reply-to: Your message of "09 Jan 1999 12:05:20 +0100." <86u2y0btan.fsf@niobe.ewox.org> Date: Sat, 09 Jan 1999 12:31:30 +0100 Message-ID: <16342.915881490@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk 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. > >So what do you think? Go or no go? 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 -- 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