Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I don't think it has to. I run 32bit apps on 64bit kernels. I think you just don't get the performance benefits of running true 64bit code on the kernel.
One certainly can run 32-bit apps on a 64-bit system, if the system is multilib. But you can look at parts of the system itself to verify that it's 64-bit. Like this, for example
Code:
file /sbin/init
/sbin/init: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), for GNU/Linux 2.6.16, dynamically linked (uses shared libs), stripped
What am I running here? is that 64 bit OS??
Because some of applications acting like it is 64 bit?
Do I need to go back in i386?
my cpu info
If it was 64-bit, there would be a 64 in it. i386 is old-school 32-bit for the 386, 486, and early Pentiums and AMD. The i686 tag is modern 32-bit OS that includes extensions and performance-enhancements for most Pentium-class CPUs and AMD processors.
What am I running here? is that 64 bit OS??
Because some of applications acting like it is 64 bit?
Do I need to go back in i386?
i686, that is 32bit. No need to 'go back' to i386, your CPU has no problems with i686. If its even possible to get an i386 kernel for your distro.....
BTW, "linux 2.6.22.5-31-default", is that openSUSE 10.3? If it is, you should really get a newer version, or a different distro- openSUSE 10.3 has been out of support' for years now (end of life for 10.3 was 31st of October, 2009).
Quote:
Originally Posted by markhud
The i686 tag is modern 32-bit OS that includes extensions and performance-enhancements for most Pentium-class CPUs and AMD processors.
Just FYI, the original 'pentium' class intel CPUs are only i586, not i686. The 1st i686 (P6) intel CPU was the Pentium Pro/Pentium II, the 1st AMD i686 CPU was the athlon, and I honestly forget what the 1st i686 VIA/cyrix CPU was.
If you want to check you system kernel than if you will use manually code to check it. it may be that code can be wrong or process can be wrong. but if you will use Linux Boot Disk to check your kernel. than you will get right answer.
Most Gnu/Linux install CD/DVD provide a means to boot the system. You can then use the booted system to diagnose or work on the system in question. One can look at '/proc/cpuinfo' since the booted kernel provides this information. You can also use ' dmidecode' to identify system information.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.