Date: Fri, 29 Jun 2001 20:28:07 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org> Cc: <arch@freebsd.org>, <audit@freebsd.org>, <athlete@kta.att.ne.jp> Subject: Re: CFR: Crusoe LongRun Support Message-ID: <Pine.BSF.4.33.0106292023230.4374-100000@herring.nlsystems.com> In-Reply-To: <20010630041951I.iwasaki@jp.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 30 Jun 2001, Mitsuru IWASAKI wrote: > Hi, > > > > > I'd like to have the patches reviewed in terms of sysctl namespace, > > > > security issues and other problems. > > > > > > Any suggestions or objections about this? > > > I'll commit this 3 days later. > > > > I think you should probably commit it. I would really like to see a > > manpage committed at the same time which describes the implications of the > > various longrun values. > > OK, I'll do that based on Hattori-san's page on LongRun > http://home.att.ne.jp/delta/athlete/longrun/longrun_e.html > and add short descriptions at the last argument of sysctl_add_oid(). > > BTW, is sysctl(8) good place to be documented? I think we'd better to > have another documentation system for the hypertrophied MIBs (like > /boot/default/loader.conf for tunables, sys/i386/conf/NOTES for kernel > config options). I don't think that sysctl(8) is really the right place since there really isn't enough space for nontrivial documentation and documenting many things in a single place doesn't really scale that well. I would like to see something like longrun(4) which described the sysctls and indicated what each longrun level actually means. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.33.0106292023230.4374-100000>