Date: Mon, 28 Jan 2002 11:14:19 -0700 From: Nate Williams <nate@yogotech.com> To: Justin White <justinfinity@mac.com> Cc: nate@yogotech.com (Nate Williams), freebsd-stable@FreeBSD.ORG Subject: Re: firewall config (CTFM) Message-ID: <15445.38139.56874.444902@caddis.yogotech.com> In-Reply-To: <6085443A-141A-11D6-AD14-000393092F82@mac.com> References: <15445.34866.827021.644844@caddis.yogotech.com> <6085443A-141A-11D6-AD14-000393092F82@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> i'm not trying to be mean, but if you don't read the docs > > > > A comment in a configuration file that the user should never have to see > > is considered documentation? > > no, the user _should_ making a point to see that configuration file. if > they're changing /etc/rc.conf, they should be reading the corresponding > defaults file. if they're changing /etc/rc.conf without previously > reading the defaults file, too bad. > > by your logic, when someone configures a new kernel, they shouldn't need > to look at LINT? I doubt most users look at LINT for building their kernels. I rarely do, since it rarely contains information *I* need for my kernels. Only when I add them to my local workstation do I look (for things like sound drivers and such), and more often than not, I need to check the archives or ask a local question since I'm not sure *what* configuration is right for my box. So, in answer to your question, I don't consider /etc/defaults/rc.conf proper documentation, nor do I consider LINT proper documenation. It's better than nothing, but it's not adequate for many tasks. (And, as stated before, what 'documentation' exists for the variable is poorly worded, so the documentation we have currently is not only inadequate, it's bad.) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15445.38139.56874.444902>