SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am currently running Slackware 8.0 and would like to use some of the new 10 and 10.1 packages but can't because I have the wrong version of glibc running. Just wondered what I would need to do in order to upgrade to the same version of glibc that slackware 10.1 uses without breaking anything particularly my existing slackware 8 and 8.1 packages.
Upgrading glibc will most likely cause problems, with thing you already have installed that were built against it. your better off just upgrading everything. but if you want to give upgrading glibc a shot. go to the source directory on a slackware ftp download the tarball and the buildscript for it and build it. if it causes problems you could always revert back to you original version
Originally posted by steveoelliott I've e-mailed the Slackware support team and waiting for an official answer. I really don't want to upgrade everything because you know soethings gonna break.
This seems to be a topic that never seems to have a complete answer. I'm curious what the official responce is from Slackware support. Please post it here when they reply.
My understanding though is that as long as the major verion doesn't change then it should be compatible with the previous versions, not requiring a reinstall/recompile. So, for instance, if your system is working with glibc 2.3.4 and it upgrades to 2.3.5 you should be OK. But when glibc 3.0 comes out then you have a problem. At least this is what is explained in Running Linux 4th edition regarding upgrading libraries.
Don't do IT! unless you want to break your system completely. The only way to upgrade from 8.0 or 8.1 is to replace every single package in your installation except for 'noarch' packages.
This CAN be done but not from your running system. You'd have to run 'pkgtool' from an installation CD or some other way.
However, Slackware 8.1 is KILLER stable. I'm currently building a new distro that goes BACK to some of the light GTK-1.2 programs used in Slackware-8.1, but compiled against GLIBC from slack-current.
If I were you, I'd just download the source code for the newer programs that you want to use and compile them on your system.
Of course a fresh installation would be much easier in a way... Either way hope you make backups of your data and have rescue floppies around.
That's the most intelligent solution. You may occassionally find something that won't work because of needing newer libs.
I'm building a new Amigo version that knid of reproduces slackware 8.1, but with current packages. Except I drag up all the old GTK-1.2 and GNOME 1.4 software, like gnucash, abiword and gnumeric.
The basic desktop is built around pure GTK-1.2 apps though, with a panel, ROX-Filer and cool WindowMaker with no DOCK or miniwindows! 280MB including about 20 GUI accessories. Then you just add mega-packages to add options -all the way up to 1.4GB with KDE and 120 other GUI apps, including GTK-2 stuff.