From owner-cvs-all Mon Jan 11 05:07:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00473 for cvs-all-outgoing; Mon, 11 Jan 1999 05:07:39 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA00455 for ; Mon, 11 Jan 1999 05:07:28 -0800 (PST) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.1/8.9.1) id PAA51480; Mon, 11 Jan 1999 15:05:17 +0200 (SAT) (envelope-from reg) Date: Mon, 11 Jan 1999 15:05:17 +0200 From: Jeremy Lea To: Nik Clayton Cc: Dag-Erling Smorgrav , committers@FreeBSD.ORG Subject: Re: sysctl descriptions Message-ID: <19990111150517.B3187@shale.csir.co.za> References: <86u2y0btan.fsf@niobe.ewox.org> <19990110132507.A24731@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990110132507.A24731@catkin.nothing-going-on.org>; from Nik Clayton on Sun, Jan 10, 1999 at 01:25:07PM +0000 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Hi, On Sun, Jan 10, 1999 at 01:25:07PM +0000, Nik Clayton wrote: > I do think that in order to ensure the information is kept up to date > the documentation strings *must* be kept close to the code they document. > But actually keeping those strings in the kernel isn't necessary. Building > a kernel could also update /usr/share/doc/sysctl/_KERNELNAME_/_LANGCODE_/* > with the information, and sysctl(8) could be patched to read from these files > instead. Where _KERNELNAME_ is your current kernel name (different kernels > might have different sysctls enabled) and _LANGCODE_ is 'en', 'ja', 'de' > and so on. What about reversing this, and having the kernel (compiled with 'options I_HAVE_LOTS_OF_RAM_AND_DONT_CARE') pick up all of it's strings (prompts, help, card identification, etc.) from files in /usr/src/sys/doc/_LANG_/? Or if you're PHK, then copy/link it into /boot/doc/? Doesn't satisfy the condition of keeping the docs near the code... Instead of having /boot, why not have /_KERNEL_? One directory per kernel config file, named after the config file, and will all of the stuff built for that kernel. eg: /SHALE loader kernel kernel.old /modules *.ko //Modules must match kernel... /man *.1k.gz //Kernel taylored help /lib libkvm.so //'nuff said... /boot -> SHALE //Maybe... Regards, -Jeremy -- | "Come home my prodigal son, come home and lets be one, --+-- don't want to see you cry, don't make me tell you why, | you've lived in a house with me, my blood has set you free, | in the world you'll surely die, nothing else will satisfy." -MIC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message