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'm going to install Slackware 13.1 soon and I may also install the 32-bit compatibility libraries from Eric (Alien BoB).
I'd like confirmation on the process of updating multilib Slackware when there's a security patch. I'm talking about running the -stable branch, by the way.
Under the normal methods of updating (e.g. 'slackpkg upgrade-all' or using the script I developed to download a local mirror of the patches directory and install from there, or even doing it by hand), the regular 64-bit packages will get updated.
However, the 32-bit compatibility versions of those files won't get updated. Right?
So I'll need to download the new 32-bit patches, run the convertpkg-compat32 script on them, and then upgradepkg the new files.
I haven't done this yet, but the way I understand it is this: when an update happens for one of the libraries that you have as both 64-bit native and compat32, you need to download both from the <path to your favorite mirror>/slackware64-13.1/patches/packages and ../slackware-13.1/patches/packages.
Upgradepkg the native one.
Run the AlienBob script to make the 32-bit one a compat32 library and then upgradepkg that one too.
AlienBob has a script I've used for years "rsync_slackware_patches.sh" that I modified for my own use and how I have my Slackware tree set up on my archive drive. I have it set for a monthly cron to grab both x86 and x86-64 patches. I then check for anything new, update the 64-bit patches, check for the same 32-bit patches, run 'convertpkg-compat32' and then update those.
On the other hand, since Slackware64_13.1 came out, and I installed the multi-lib stuff, there've been only a few patches that need to be converted to compat32: libtiff, libpng, and seamonkey-solibs.
That's not too much to keep track of. ;)
You're right, once the multilib is installed there will not much to keep track. However, with compat32pkg you'll not have to do this by hand, and, you could also create a cron job to automate this.
Moreover, when using compat32pkg to install the 32-bit part of the multilib from the network (ex: compat32pkg --mirror @USA-13.1 --install /etc/compat32pkg/multilib-32bit-packages.lst), it will be installed automatically in a safe state, with all the available updates, unless when explicitly excluded ( ie using --exclude list:patches/.* )