Thanks for maintaining a less-than-glorious, but useful utility.
I did check to make sure I was getting the expected version of uname:
which uname
/bin/uname
, but attempting to repeat the symptom got proper behavior!??:
uname -a
Linux cloudy 2.6.25-14.fc9.x86_64 #1 SMP Thu May 1 06:06:21 EDT
2008 x86_64 x86_64 x86_64 GNU/Linux
A look at my history shows the command I originally used:
uname -a
uname: extra operand `-a'
Try `uname --help' for more information.
"Oh goody, identical commands, different behavior..."
cat | od -c
uname -a
0000000 u n a m e 342 200 223 a \n \n
0000014
It appears that the web page I cut-n-pasted from was rendered using a
UTF8 character (0xE28093) that just happens to look like a hyphen on my
terminal.
Nevermind :-)
Sorry about the .sig; it's the burden that comes of working for a
financial company.
Further sorry about the false alarm.
Walter
-----Original Message-----
From: Eric Blake [mailto:[EMAIL PROTECTED]
Sent: Monday, December 08, 2008 7:31 PM
To: Walter Coole
Cc: bug-coreutils@gnu.org
Subject: Re: Bug in uname
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Walter Coole on 12/8/2008 1:28 PM:
> uname -a
>
> uname: extra operand `-a'
Thanks for the report. Are you sure you don't have any aliases or shell
functions interfering? Depending on your shell, 'which uname' or 'type
uname' will tell you.
...
_______________________________________________
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
