Your message dated Mon, 12 Sep 2011 14:01:00 -0400
with message-id <[email protected]>
and subject line uname: -i and -p options give unhelpful answers
has caused the Debian Bug report #193170,
regarding uname: -i and -p options give unhelpful answers
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
193170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=193170
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: coreutils
Version: 5.0-1
Severity: normal

According to the manual, uname has the following options:

`-i'
`--hardware-platform'
     Print the hardware platform name (sometimes called the hardware
     implementation).

`-p'
`--processor'
     Print the processor type (sometimes called the instruction set
     architecture or ISA).

On my system, though, both of them return "unknown".  This is less than
useful.  I'm not sure what "uname -i" should do on a PC, but "uname -p"
should return something like "i386", which I suspect could be set at compile
time if there turns out to be no way to get it out of the kernel.

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux wraith 2.4.20 #2 Wed Jan 22 16:53:10 GMT 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages coreutils depends on:
ii  libc6                         2.3.1-16   GNU C Library: Shared libraries an



--- End Message ---
--- Begin Message --- This bug seems not to want to die, but what I said in the last message stands: code that wants this is doing something wrong. I suggest looking at the flags: section of /proc/cpuinfo if writing a shell script, or various runtime processor feature tests as appropriate. Nobody has proposed a use case for this in the past several years, so I hope the bug can stay closed this time.

Mike Stone


--- End Message ---

Reply via email to