I found a bug on my one etch system and was about to open a bug, but
wasn't sure what package to open it for. Looking around at various
debian bugs I found 381008, where Norbert Preining asks:
> So I am really interested how other distributions find the node of du
> when you type
> info du
and I can report that on my debian sarge system, "info du" shows me
the info page "File: coreutils.info, Node: du invocation", which is good.
I was looking for documentation for the "tail" program on my etch machine.
The end of the man page shown by "man tail" on etch, I see this:
The full documentation for tail is maintained as a Texinfo manual. If
the info and tail programs are properly installed at your site, the
command
info tail
should give you access to the complete manual.
But when I run "info tail" I just get another copy of the man page,
which again shows me the above text.
On my machine running sarge if I run "info tail" it shows me the info
page (not the man page) for tail.
Oddly enough, the man page for tail on my sarge machine says this:
The full documentation for tail is maintained as a Texinfo manual. If
the info and tail programs are properly installed at your site, the
command
info coreutils tail
should give you access to the complete manual.
And "info coreutils tail" also works (on sarge). That works as well
on etch, so reading the man page from sarge would lead me to do
something which works on etch.
Reading the man page on etch would lead me to do something which works
on sarge, but not on etch!
So I see no problem on sarge, but definitely a problem on etch.
There seem to be many related bugs, some long standing, floating
around the debian BTS. So I see no need to open yet another bug.
Bug 139569 (over 4.5 years old) appears like it might be root cause of
all this. (But note that my sarge system does not have this problem.)
It looks like it will be a chore just to find all the bugs that should
be merged for this problem.
IMHO it is not appropriate to label this bug "wishlist", for the
documentation is leading the user astray while attempting to point the
user at the complete documentation. It is at least a documentation
bug. We cannot expect all users to understand what "coreutils" is and
how to go looking in coreutils documentation to find the complete
documentation for many common unix utilities.
-Tim Shepard
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
