Re: POSIX misunderstanding

2004-08-18 Thread Albert Cahalan
On Wed, 2004-08-18 at 23:34, Paul Eggert wrote: > Albert Cahalan <[EMAIL PROTECTED]> writes: > > > On Wed, 2004-08-18 at 13:49, Paul Eggert wrote: > >> Albert Cahalan <[EMAIL PROTECTED]> writes: > >> > >> > Well, so does the --lines option. > >> > >> No, that uses an allowed extension. It's not

Re: POSIX misunderstanding

2004-08-18 Thread Paul Eggert
Albert Cahalan <[EMAIL PROTECTED]> writes: > On Wed, 2004-08-18 at 13:49, Paul Eggert wrote: >> Albert Cahalan <[EMAIL PROTECTED]> writes: >> >> > Well, so does the --lines option. >> >> No, that uses an allowed extension. It's not prohibited, the way that >> multi-digit options are prohibited.

Re: POSIX misunderstanding

2004-08-18 Thread Albert Cahalan
On Wed, 2004-08-18 at 13:49, Paul Eggert wrote: > Albert Cahalan <[EMAIL PROTECTED]> writes: > > > Well, so does the --lines option. > > No, that uses an allowed extension. It's not prohibited, the way that > multi-digit options are prohibited. Where? You can have a "-W lines=42" option. Guide

Re: POSIX misunderstanding

2004-08-18 Thread Albert Cahalan
On Wed, 2004-08-18 at 11:44, Paul Eggert wrote: > Albert Cahalan <[EMAIL PROTECTED]> writes: > > > a POSIX-conforming "head" program may > > support a "-1" option. It may also support a > > "-2" option, and so on. > > That violates POSIX Utility Syntax Guidelines 3 and 11. See: > > http://www.o

"printf" documentation clarifications

2004-08-18 Thread Paul Eggert
I installed this documentation to clarify how "printf" behave. 2004-08-18 Paul Eggert <[EMAIL PROTECTED]> * coreutils.texi (printf invocation): Clarify how "printf" is supposed to work with extra arguments, missing arguments, etc. Index: coreutils.texi =

Re: POSIX misunderstanding

2004-08-18 Thread Paul Eggert
Albert Cahalan <[EMAIL PROTECTED]> writes: > Well, so does the --lines option. No, that uses an allowed extension. It's not prohibited, the way that multi-digit options are prohibited. > I think "violates" is too strong of a word for > anything called "Guidelines", but anyway... The standard s

Re: su strange behaviour

2004-08-18 Thread Alfred M. Szmidt
Hmm... I'm quite sure that I didn't send this email. Unless I somehow managed todo that by accident... ___ Bug-coreutils mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: su strange behaviour

2004-08-18 Thread Alfred M. Szmidt
And check that you (the OP) have debugging symbols in su and/or libc, otherwise anything that gdb will say will be useles. ___ Bug-coreutils mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: su strange behaviour

2004-08-18 Thread Alfred M. Szmidt
___ Bug-coreutils mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: su strange behaviour

2004-08-18 Thread Paul Eggert
This looks more like a bug with your password database than with "su". If it is an "su" bug, please try to figure out what went wrong by using GDB on your copy of "su". (You might start by making sure you're using coreutils "su", and which version it is: my impression is that most people use some

Re: POSIX misunderstanding

2004-08-18 Thread Paul Eggert
Albert Cahalan <[EMAIL PROTECTED]> writes: > a POSIX-conforming "head" program may > support a "-1" option. It may also support a > "-2" option, and so on. That violates POSIX Utility Syntax Guidelines 3 and 11. See: http://www.opengroup.org/onlinepubs/95399/basedefs/xbd_chap12.html#tag_12_

su strange behaviour

2004-08-18 Thread Marcel Reese
Dear Reader! I recently had to change user mare's user id. This has also been done for all his files's owner tags. After this su doesn't work properly anymore for any user except for root. It accepts correct passwords and waits after typing wrong passwords, but it never logs in the specified us