From owner-cvs-all Sun Jan 10 10:49:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27609 for cvs-all-outgoing; Sun, 10 Jan 1999 10:49:26 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27604 for ; Sun, 10 Jan 1999 10:49:24 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id DAA06783; Sun, 10 Jan 1999 03:25:49 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpddH6781; Sun Jan 10 11:25:41 1999 Date: Sun, 10 Jan 1999 02:25:46 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: Mike Smith cc: Poul-Henning Kamp , Dag-Erling Smorgrav , Darren Reed , committers@FreeBSD.ORG Subject: Re: sysctl descriptions In-Reply-To: <199901100738.XAA03998@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk I'm with you on this however poul's already nuked the commit. can something be done about this. how does one apply to core for an un-nuking of a nuke by core? On Sat, 9 Jan 1999, Mike Smith wrote: > > There is NO reason whatsoever to load it with the kernel. Next thing > > you will what to stick documentation for all ioctl(2) calls into the > > kernel. > > > > KLD's could easily stick files into: > > > > /usr/share/doc/sysctl/desc/this/is/my/sysctl.txt > > > > with descriptions. > > No, they can't. There's also no guarantee that the KLD module file > will be readable at run time. Please start thinking "dynamic kernel > appears from nowhere". There is no guarantee that you can do anything > related to the kernel without going to or through the kernel for it. > Live with it. > > > Yes, I agree that sysctls should be better documented, No, I don't > > agree that there is any reason for wasting RAM on it. > > If you don't want the descriptions, don't build them into your kernel. > > Meantime, please feel free to work out a compromise solution whereby > descriptions can come from more than one source. And then a better one > where you can guarantee that the two sources will always stay in sync. > > As it is, sysctl-as-it-is' life it limited. Don't get too emotional > about another bandaid on its creaking frame. > > -- > \\ 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