lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1ejnlxh4j.fsf@ebiederm.dsl.xmission.com>
Date:	Mon, 19 Mar 2007 11:44:44 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Oliver Falk <oliver@...ux-kernel.at>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: axp question 'bout uname voodoo

Oliver Falk <oliver@...ux-kernel.at> writes:

> Hi!
>
> We have a discussion on alpha mailinglist at the moment, because of uname -mpi.
>
> AFAIK, uname -m should do some glibc call, which calls kernel, right?
>
> However, I have two machines:
>
> AS1000A:
> [root@...kie ~]# uname -mpi && cat /proc/cpuinfo | grep model
> alpha alpha alpha
> cpu model               : EV56
>
> DS10:
> [root@...a ~]# uname -mpi && cat /proc/cpuinfo |grep model
> alpha alpha alpha
> cpu model               : EV67
>
> Shouldn't uname rport alphaev67 and alphaev56? Maybe it's just a .config
> problem. Maybe the kernel needs to be compiled for the different sub-arches!?
>
> Any help would be great.

The kernel uname function at least does not have fields that
report processor or hardware platform.

Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ