[SOLVED] cpu optimisations and slackware - Any '486 users?
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
As I promised, I got to try an install on my old pentium. I failed, but the reason is interesting.
We have all forgotten the bios hard disk limitations of the time. My old 486 had a 487 meg hard disk, as there was a 512mb limit. That applied to all 486 boxes. A compiled kernel is over 600MB! That was followed by the massive advance to 2 Gigabytes using LBA, which was more space than anyone could use, ever . In fact, I have a 2.5 Gig disk which works in the pentium, but my current install looks nearer 5 gigs.
Now my old box sat down with hard disk trouble, because the disk in it is iffy, and it just didn't want to know about the other disks I have lying about. It has one of those bios that never lets you in to adjust things. I gave up quickly.
Unpacked, the kernel source is less than 400MB. My Huge kernels are just above 5MB. And I put a 850MB drive in my 386 if my memory serves me right. That disk was later put in a 486 that I still have for certain CAD under DOS.
Yeah, well it's clear that on a real i486, it is impossible to install the latest slackware. If Pat V wants to move it up to i586, then he can without any worries ... if he wants to, of course.
This thread should not be about compiling a kernel on a 486 box... that would be insanity. Use a fast modern computer to compile your software.
The Slackware 13.1 kernel is a few megabytes, and the total of all kernel modules is a little over 100 MB. Compile a custom kernel for that old 486 and you can get a away with a few megabytes total.
An old computer like a 486 should not be used as a desktop computer and run a GUI. A typical use would be as a server in your network (file- print mail- or streaming audio server for instance). A full installation of Slackware would not be required.
Quote:
Originally Posted by mlpa
So Slackware 13.1 can't run in a 486
That is not the correct conclusion to draw from business_kid's post.
And you still have not proven that there is a real performance gain to be made from a recompilation for a i686 target.
We have all forgotten the bios hard disk limitations of the time. My old 486 had a 487 meg hard disk, as there was a 512mb limit. That applied to all 486 boxes.
Linux does not use the BIOS, so does (and did) not have this problem.
However, this geometry stuff plays a role in the interpretation of partition tables, so if Linux shares a disk with for example DOS, then it needs to know what geometry DOS will think the disk has. It also plays a role at boot time, where the BIOS has to load a boot loader, and the boot loader has to load the operating system.
Well, in fact the real problem is the 2.1G limit on BIOSes before April 1996, because the system hang if you use a hardisk capacity beyond this value...
Distribution: Debian 5 - Slackware 13.1 - Arch - Some others linuxes/*BSDs through KVM and Xen
Posts: 329
Rep:
Why can't slack13.1 run on a 486?
If you can take the time to, let's say, recompile the kernel without stuff like USB, wireless, OCFS, and lots of other things...
On installation time you could pick carefully what you want to get (no KDE, for example). Or perhaps you could get a swag of old 1GB disks and set up a RAID-0 array or a LVM VG so you can get all the programs installed and later choose what to uninstall - I did it once with a 486-DX2 and two 800MB HDDs, with slack12 if memory serves me correct
EDIT: 800 * 2 = 1600 MB, right? I had to start without X, actually. But I got a minimal X system working later
Well, in fact the real problem is the 2.1G limit on BIOSes before April 1996, because the system hang if you use a hardisk capacity beyond this value...
I do not consider that a valid argument against.
You can stuff a very functional server machine and even a trimmed-down desktop in 2 GB of hard disk. Look for the various threads on "small slackware" on this forum.
The questions is not if a modify version of Slackware runs in a 486, but if the actual version unchange version runs.
If you said that modify this and that to run in a 486, so you have no problem recompile to i486.
The question is, how many of you think installing the actual Slackware in a 486 without change a thing?
Because the vote in this poll i486 are a minority and then aren't running Slackware 13.1.
I known that the performance may not be so significant, but should have enough impact to the other distro change.
The questions is not if a modify version of Slackware runs in a 486, but if the actual version unchange version runs.
I state that an unmodified Slackware 13.1 installs and runs on a 486 computer. It will not be a full installation if you need to keep the installed footprint below 2 GB.
I guess this will be my last contribution to this thread...you are entitled to yur opinion that Slackware should abandon the i486 target. I still do not see the advantage of a full recompilation of the distro for a different target, to get improvements that nobody is able to corroborate with evidence.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.