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.
So this works with what version of Slackware ? 13.0 ? I'd be surprised. If it does, then I guess we have to stick to i486.
It doesn't affect me any, I use x86_64.
Of course that AlienBOB's toy works with 13.0, because it's a i586 (or i686 ?) with MMX and all bells and they run (probably, minimum) at 1GHz and use a 640GB Western Digital SATA2 harddrive...
Because of this nice geekie toy, we are doomed to stuck in an architecture that remember the Tyrannosaurus Rex thing.
Wait a second! Dear AlienBOB, please, explain...
I imagine that the Slackware developers use a magical script that rebuild everything after changing... ie GCC?
Or NOT?
Really, we can rebuild the current Slackware Linux Operating System, from sources, using the current kernel, GCC & Co. toolkit? Or NOT?
Last edited by LuckyCyborg; 05-23-2010 at 09:50 AM.
Of course that AlienBOB's toy works with 13.0, because it's a i586 (or i686 ?) with MMX and all bells and they run (probably, minimum) at 1GHz and use a 640GB Western Digital SATA2 harddrive...
Because of this nice geekie toy, we are doomed to stuck in an architecture that remember the Tyrannosaurus Rex thing.
Wait a second! Dear AlienBOB, please, explain...
I really have had enough of you, so this will be my last post answering anything you write.
Quote:
I imagine that the Slackware developers use a magical script that rebuild everything after changing... ie GCC?
Or NOT?
Unfortunately you are not getting an answer to that question.
Quote:
Really, we can rebuild the current Slackware Linux Operating System, from sources, using the current kernel, GCC & Co. toolkit? Or NOT?
Certainly, there are several other people I know, how are rebuilding or have rebuilt Slackware with other compiler options. Join the gang, I'd say. It'll keep you busy for a while.
For what gain, I don't know. But, the sources used to build the Slackware packages are on any mirror, all of them.
I really have had enough of you, so this will be my last post answering anything you write.
That's sad.
Quote:
Originally Posted by Alien Bob
Unfortunately you are not getting an answer to that question.
Because this thing don't exist?
Quote:
Originally Posted by Alien Bob
Certainly, there are several other people I know, how are rebuilding or have rebuilt Slackware with other compiler options. Join the gang, I'd say. It'll keep you busy for a while.
For what gain, I don't know. But, the sources used to build the Slackware packages are on any mirror, all of them.
Eric
From your speak, I'm barely believe that an outsider is able to rebuild from source the Slackware Linux. This is real problem. IF the Slackware Linux CAN be rebuild by sources, this thread have no-sense. Because we can have an i486, i586 i686 and x32_64 (even ARM) in few days.
Last edited by LuckyCyborg; 05-23-2010 at 11:56 AM.
From your speak, I'm barely believe that an outsider is able to rebuild from source the Slackware Linux. This is real problem. IF the Slackware Linux CAN be rebuild by sources, this thread have no-sense. Because we can have an i486, i586 i686 and x32_64 (even ARM) in few days.
Why don't you rebuild for i686, and if it's wonderful share it? You'll get what you want and learn something in the process. You may even want to check out LFS and just build your own system your own way?
Why don't you rebuild for i686, and if it's wonderful share it? You'll get what you want and learn something in the process. You may even want to check out LFS and just build your own system your own way?
I love, to build the i686 target in few hours after the official release, but I don't believe that it's possible to rebuild our current from /source directory.
I love, to build the i686 target in few hours after the official release, but I don't believe that it's possible to rebuild our current from /source directory.
I don't agree with the reasoning that the compilation level should change just because the default slackware installation medium cannot boot on certain really old i486 systems because of lack of memory to boot. It is still completely possible to install using other methods. When I tried installing on one of my own 486's, I booted from ZipSlack, but manually installed the packages for the latest slackware.
There are also newer 486-derivative systems that have more memory.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
