Skip to contentSkip to conversation

setarch treats all x86 variants as i686?

DISCUSSION Phillip Susi 2 participants 4 messages Feb 6, 2014 – Feb 8, 2014 Util-Linux package

lore
Share & tools
lore
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

setarch i486
uname -m
i686

Is this a bug?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS8/ZgAAoJEI5FoCIzSKrwfT4IAJKywIsfNUQfT4Yf7tR3+Ej9 Wkyipwm6UYqx3xrv+0ndVTPUXINBBFVTqPdpmkvdNhz92aqdHQy7xEWX5/c9oV63 jw9GL/UU0GygdXsHYJEtLUE2FZMSNej9czmi04h3K8eKO/dYpzw4JSiqGUlGmRtS VrL5vFZZuYBYxf4LRk4NP6+WZhsjY8vQnryctFBrOlj358D0twohPhMCP5WxBJYs 0LFCQK3BuLcJqX8wW483Oi80PEwbAryvJlt1UcI0Buj7iOpq6t3vuf6Ak93elRh0 ml+9zlqmbxfmtC6eVf6W1znJGQ9/F+M7HL3vdzEKeXynHSN5LpSiU3xx4LXLI4w= =v7iW
-----END PGP SIGNATURE-----

#1 lore raw
Quoted 5 lines · On Thursday, February 06, 2014 15:53:52 Phillip Susi wrote:

setarch i486
uname -m
i686

Is this a bug?

no. setarch is merely calling the kernel and the kernel is doing this. see man personality for more details.
-mike

#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Quoted 2 lines · Mike Frysinger

no. setarch is merely calling the kernel and the kernel is doing this. see man personality for more details.

Ahh, looking at the syscall it is clear that there is only a generic linux 32 vs 64 bit flag, so setarch must be aliasing ix86 to the generic 32 bit flag. The man page probably should be a little more clear that these aliases all map to the same thing.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJS9lG8AAoJEI5FoCIzSKrwKDoIAJI1+SHLvv20ZPBbNjG7ieT3 KDgBBD8kj50qQVTVdXBlp/TkdDNBO0GuuabQ+6PZm8UAUNSpfiYEOdMlma3y/o/g ZfDBR43XBiqNK7ppnIZ/Ro9MS4rn7yze/UdLgg9t+Shm4RHHarl2VKaNEh0FB0UT onUJt9SBG2czPY3evFGNWlmsaGNJ04nW70SHgiCLA14mIgaSx7tSU8FuCeEjg1dG XFIMhbgCl4qeBqTEcwl/kwzz23wYoHpWHWHK0eMbc4j4CJCk0G7nbbnWI2IEdgzz QGYdDurLT4lCdPDx5l5LoP8xTQzdvRy35HLjnZrVM0T6nAZXxf89h3wG64K+zBY= =waCb
-----END PGP SIGNATURE-----

#3 lore raw
In reply to Mike Frysinger

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 02/08/2014 06:26 AM, Mike Frysinger wrote:

Ahh, looking at the syscall it is clear that there is only a generic linux 32 vs 64 bit flag, so setarch must be aliasing ix86 to the generic 32 bit flag. The man page probably should be a little more clear that these aliases all map to the same thing.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJS9lG8AAoJEI5FoCIzSKrwKDoIAJI1+SHLvv20ZPBbNjG7ieT3 KDgBBD8kj50qQVTVdXBlp/TkdDNBO0GuuabQ+6PZm8UAUNSpfiYEOdMlma3y/o/g ZfDBR43XBiqNK7ppnIZ/Ro9MS4rn7yze/UdLgg9t+Shm4RHHarl2VKaNEh0FB0UT onUJt9SBG2czPY3evFGNWlmsaGNJ04nW70SHgiCLA14mIgaSx7tSU8FuCeEjg1dG XFIMhbgCl4qeBqTEcwl/kwzz23wYoHpWHWHK0eMbc4j4CJCk0G7nbbnWI2IEdgzz QGYdDurLT4lCdPDx5l5LoP8xTQzdvRy35HLjnZrVM0T6nAZXxf89h3wG64K+zBY= =waCb
-----END PGP SIGNATURE-----