On Thu, Oct 04, 2001 at 09:02:03AM +0100, Tim Waugh wrote:
> On Wed, Oct 03, 2001 at 12:43:37PM -0600, Charles Curley wrote:
>
> > But what the heck goes on with the stuff in /etc/sysconfig?
>
> Take a look in /usr/share/doc/initscript-*/sysconfig.txt. If a
> sysconfig file is not documented in there, file a bug for the package
> it belongs to.
Thank you! It took starting a tempest in a teapot to finally get a
useful answer.
Let me see if I can state a general rule to go from a file, foo, to
finding some documentation on it if "man foo" and "info foo"
fail. First find out to what package it belongs. "rpm -qf foo". With
luck, that will tell me that foo belongs to the bar-xxx package. I
then go to /usr/share/doc/bar-xxx and start looking for likely files
to read.
This has a problem: not all files are associated with packages:
[ccurley@charlesc ccurley]$ rpm -qf /etc/sysconfig/network
file /etc/sysconfig/network is not owned by any package
Is this documented anywhere, such as in the "Getting Started Guide"?
On a quick inspection, I don't see it there. If not, perhaps a bug
report is in order.
May I suggest that in the future the maintainers cross reference
documentation files in the scripts they document. A line like:
# For more information, see /usr/share/doc/bar-xxx/foo.txt
If you want to get fancy, a bit of perl hacking could even automate
the process.
--
-- C^2
The world's most effective anti-virus software: Linux.
Looking for fine software and/or web pages?
http://w3.trib.com/~ccurley
PGP signature
