Re: ls 6.7 man page bugs (unterminated bold macros)

From: [EMAIL PROTECTED] Subject: Re: ls 6.7 man page bugs (unterminated bold macros) Date: Sun, 15 Apr 2007 18:47:01 -0600 amores perros wrote: > >From: Eric Blake > >Thanks for the report. However, the man page is generated using the > >'help2man' tool from the 'ls --help' output, so you ma

Re: ls 6.7 man page bugs (unterminated bold macros)

Please ignore my previous query about help2man. RTFM looks pretty straightforward and I will try to just imitate the sample. http://www.gnu.org/software/help2man/ _ Download Messenger. Join the i’m Initiative. Help make a differenc

Re: cut manpage is buggy

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Rudolf Kastl on 4/5/2007 6:33 AM: >> Hello to you! >> >> actually the cut manpage has a bug in it: > > Which is generated from 'cut --help', but that has the same problem. > >> >> SYNOPSIS >>cut [OPTION]... [FILE]... >> >> implies that it

uname

Hi All, uname does not work on the debian port to a mips based asus router... uname -p unknown but: uname -a Linux asus-debian 2.6.19.2 #9 Tue Apr 3 21:30:54 CEST 2007 mips GNU/Linux is correct. Any ideas what we can do to fix this? Thanks! - DL __

Re: cut manpage is buggy

Jim Meyering meyering.net> writes: > > Thanks for the suggestion, but I prefer simply to remove > the brackets to indicate that an OPTION is required. > > * src/cut.c (usage): Adjust synopsis to show that an OPTION is required. > Reported by Rudolf Kastl. Your wording choice sounds

Removing link to a directory

*Symptom*: Could not remove a link to a directory, got the message >rm current/ rm: remove directory `current/'? y rm: cannot remove directory `current/': Is a directory current is a symbolic link to directory. *OS*: Red Hat Linux. ___ Bug-co

Re: uname

Dr. Douglas Lyon wrote: Hi All, uname does not work on the debian port to a mips based asus router... uname -p unknown but: uname -a Linux asus-debian 2.6.19.2 #9 Tue Apr 3 21:30:54 CEST 2007 mips GNU/Linux is correct. Actually, I'm getting the same behavior on my i686 Ubuntu 6.10.1 install.

Re: cut manpage is buggy

Eric Blake <[EMAIL PROTECTED]> wrote: > Jim Meyering meyering.net> writes: >> Thanks for the suggestion, but I prefer simply to remove >> the brackets to indicate that an OPTION is required. >> >> * src/cut.c (usage): Adjust synopsis to show that an OPTION is required. >> Reported by Rud

Re: Removing link to a directory

"Mohammad Seth" <[EMAIL PROTECTED]> writes: > *Symptom*: Could not remove a link to a directory, got the message > >>rm current/ > rm: remove directory `current/'? y > rm: cannot remove directory `current/': Is a directory > > current is a symbolic link to directory. Once you specify the trailing

Re: uname

Micah Cowan <[EMAIL PROTECTED]> writes: > given that /proc/cpuinfo has useful info, perhaps -p shouldn't > be "unknown"? If Linux ever gives us a system call to get the processor type reliably then we'll use that. In the meantime, it's not clear what the relationship is between processor type an

Making of coreutils-6.9-3 failed

Hello! PASS: dot-rel ./inaccessible: /sw/src/fink.build/coreutils-6.9-3/coreutils-6.9/ tests/rm: not writable by user `nobody' ./inaccessible: skipping this test SKIP: inaccessible ./unread3: /sw/src/fink.build/coreutils-6.9-3/coreutils-6.9/tests/rm: not writable by user `nobody' ./unread3: