[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug in command "uname"
From: |
Eric Blake |
Subject: |
Re: Bug in command "uname" |
Date: |
Sat, 21 Jun 2008 16:25:43 -0600 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080421 Thunderbird/2.0.0.14 Mnenhy/0.7.5.666 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Rastislav Vojtko on 6/21/2008 3:31 PM:
| Dear developers,
|
| The "uname" command contains two bugs.
|
| If I type "uname -r" in terminal the result is "#1 SMP Wed May 28
| 20:27:26 UTC 2008",
| if I type "uname -v" in terminal the result is "2.6.24-18-generic"
| These two flags "-v, -r" of the "uname" command are most probably replaced.
Thanks for the report. However, this is a bug in coreutils, since it
merely outputs exactly what the kernel reported in the release and version
fields of struct utsname in uname(2). POSIX doesn't really describe in
much details what these fields must contain, so there is a lot of room for
variance between different operating systems.
http://www.opengroup.org/onlinepubs/009695399/basedefs/sys/utsname.h.html
In general, uname(1) output is not very portable, since uname(2) is so
loosely standardized.
- --
Don't work too hard, make some time for fun as well!
Eric Blake address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkhdf+cACgkQ84KuGfSFAYA5ZgCfZw4bGbetnV5FxpwzmjN8v+c6
dEcAn1gn4N3mzVefFX9tkEbCFNdK1P3r
=fuNa
-----END PGP SIGNATURE-----