Is there a method to get a 586 (i586 text) install to a 486 level? I am looking for information guidance on this. I have looked into using debian/386 which stinks in my opinion, slackware doesnt quite have it either.
So I am wishing/hoping there is a NOT TO painful way to get a 586 install to run on a 486 chip.
I have been searching but havent found anything useful. If anyone knows what might need to be done I would appreciate it.
Jerry
On Fri, Jun 20, 2008 at 09:55:17PM -0400, Jerry Geis wrote:
Is there a method to get a 586 (i586 text) install to a 486 level? I am looking for information guidance on this. I have looked into using debian/386 which stinks in my opinion, slackware doesnt quite have it either.
So I am wishing/hoping there is a NOT TO painful way to get a 586 install to run on a 486 chip.
I have been searching but havent found anything useful. If anyone knows what might need to be done I would appreciate it.
Sorry, I have no clue about your question. However, I have several AMD K6 chips (pentium-equivalent) lying around should you trip over a motherboard that'll run them. That would solve your 486 problem, I think, so let me know if such a chip would help you out.
Jerry Geis wrote:
Is there a method to get a 586 (i586 text) install to a 486 level? I am looking for information guidance on this. I have looked into using debian/386 which stinks in my opinion, slackware doesnt quite have it either.
So I am wishing/hoping there is a NOT TO painful way to get a 586 install to run on a 486 chip.
This would be almost impossible with centos.
The reason is that there are things that glibc will compile in that are not i486 compatible
You would be much better off trying to do this with debian I think.
If it were possible, it would be by installing the i386 glibc, i386 openssl and editing the kernel spec file and the config file.
You can try to change the processor type to i386 or i486 and see if it will work ... however I do not think it is possible on other than centos-3 to get an i386 compile.
I have been searching but havent found anything useful. If anyone knows what might need to be done I would appreciate it.
I tried RHEL 3 (I believe) on a Pentium class system, and that did not work well.
For everything but the kernel, there was a 386 version available (glibc, ssl, etc), so we recompiled the kernel for the 586.
Unfortunately, glibc, when you compile it for anything below a 686, did not support NTPL threads, causing nothing but heartache. Luckily, before we got too far, we learned we didn't have to target the Pentium based computer anymore. I am happy we didn't have to validate everything still worked when something as major as glibc is rebuilt (since I started looking whether it was possible to rebuild glibc for 586 and NTPL). Kernels are less risky, since people rebuild them more frequently.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Johnny Hughes Sent: Friday, June 20, 2008 8:49 PM To: CentOS mailing list Subject: Re: [CentOS] centos 4.6 - 586 install - how to get that to a 486 level if possible
Jerry Geis wrote:
Is there a method to get a 586 (i586 text) install to a 486 level? I am looking for information guidance on this. I have looked into using debian/386 which stinks in my opinion, slackware doesnt quite have it either.
So I am wishing/hoping there is a NOT TO painful way to get a 586 install to run on a 486 chip.
This would be almost impossible with centos.
The reason is that there are things that glibc will compile in that are not i486 compatible
You would be much better off trying to do this with debian I think.
If it were possible, it would be by installing the i386 glibc, i386 openssl and editing the kernel spec file and the config file.
You can try to change the processor type to i386 or i486 and see if it will work ... however I do not think it is possible on other than centos-3 to get an i386 compile.
I have been searching but havent found anything useful. If anyone knows what might need to be done I would appreciate it.
No virus found in this incoming message. Checked by AVG. Version: 8.0.100 / Virus Database: 270.4.1/1511 - Release Date: 6/20/2008 11:52 AM
Sorry, I have no clue about your question. However, I have several AMD K6 chips (pentium-equivalent) lying around should you trip over a motherboard that'll run them. That would solve your 486 problem, I think, so let me know if such a chip would help you out.
Fred - thanks for the offer - however I do have a specific device I am targeting. Ebox2300sx. I have no options on the hardware. It would be a great solution hardware wise but software is being a bit of a pain at this time.
Johnny - thanks for the info. I actually have debian booted on the device but then EVERYTHING is so much different on debian than centos. I was also trying a redhat 9 install and put a 2.6 kernel on it. However, I realize this is not the best solution. BUT - to try it out and get something working with the other programs I need I thought that might be a valid short term path to check things out.
Thanks guys,
Jerry
on 6-21-2008 6:17 AM Jerry Geis spake the following:
Sorry, I have no clue about your question. However, I have several AMD K6 chips (pentium-equivalent) lying around should you trip over a motherboard that'll run them. That would solve your 486 problem, I think, so let me know if such a chip would help you out.
Fred - thanks for the offer - however I do have a specific device I am targeting. Ebox2300sx. I have no options on the hardware. It would be a great solution hardware wise but software is being a bit of a pain at this time.
Johnny - thanks for the info. I actually have debian booted on the device but then EVERYTHING is so much different on debian than centos. I was also trying a redhat 9 install and put a 2.6 kernel on it. However, I realize this is not the best solution. BUT - to try it out and get something working with the other programs I need I thought that might be a valid short term path to check things out.
Thanks guys,
Jerry
I still think Debian, Ubuntu, Gentoo, or one of the BSD's will be your best option on that hardware. But Gentoo would take forever to compile/install on that hardware.
Scott Silva wrote:
I still think Debian, Ubuntu, Gentoo, or one of the BSD's will be your best option on that hardware. But Gentoo would take forever to compile/install on that hardware.
I thought I read at some point that Debian etch dropped 486 support.
Another option may be CentOS 3.x or CentOs 2.x, I'd think one of them would support 486, and in theory at least they are still getting security updates. Older hardware often needs older software to run, at least there's an option to run older software that's still supported.
nate
nate wrote:
Scott Silva wrote:
I still think Debian, Ubuntu, Gentoo, or one of the BSD's will be your best option on that hardware. But Gentoo would take forever to compile/install on that hardware.
I thought I read at some point that Debian etch dropped 486 support.
Another option may be CentOS 3.x or CentOs 2.x, I'd think one of them would support 486, and in theory at least they are still getting security updates. Older hardware often needs older software to run, at least there's an option to run older software that's still supported.
The real issue is that glibc compiled for --target i386 is not really 100% i386 compatible ... also NTPL doesn't work (is turned off). This will potentially affect many other packages.
Upstream just made many assumptions in glibc and, the bottom line is that centos is just not designed to work on less than an i586 machine ... well really i686, but i586 SHOULD work with the proper mods.
However, IMHO, i486 is impossible to get working (reliably) without rebuilding everything with the new glibc/gcc.
On one of our servers wtmp is growing very fast. The binary file is about 50M but when I change it to ascii with fwtmp command, The ascii file is only 10M.
binary file is being 5 times bigger than text file ? Any suggestion ?
-
Centos -
fred smith -
Jerry Geis -
Johnny Hughes -
Kevin K -
nate -
Scott Silva