Alien Pastures » multilib

Multilib version of Slackware’s “11-11-11″ glibc

alienbob — Sun, 13 Nov 2011 01:59:38 +0000

The glibc packages in Slackware -current were updated to 2.14.1 a few days ago. Unfortunately, a couple of issues were reported, you will find them in this LinuxQuestions thread.

Since I had to compile my multilib version of glibc still, I decided to wait a bit with releasing them, and that allowed me to find and apply the patch reported in the above thread that seems to solve the issues. The patch comes from Linux From Scratch and appears to be upstream fixes that are going to be in the next release of glibc. I upgraded my laptop with this new multilib glibc package, and can confirm that applications like firefox, libreoffice, calibre, mplayer run without any issues here.

I know that several people have mentioned this patch to Pat Volkerding already, and if the patch gets applied to Slackware’s glibc package I will simply rename my own multilib versions from “1alien” to “2alien” in order to stay in sync with the versioning of the originals.

Along with the updated mulitilib glibc packages, I also uploaded a new version of the “compat32-tools” package to the “current” section, containing a bug-fixed convertpkg-compat32 script. I also refreshed the “slackware64-compat32” subdirectory which contains the packages converted by the “massconvert32.sh” script.

Eric

Slackware has the answer to all

alienbob — Sun, 27 Mar 2011 12:51:27 +0000

… perhaps even to the Ultimate Question of Life, the Universe, and Everything.

Just kidding of course. From today’s ChangeLog.txt for Slackware “current“:

Sun Mar 27 08:28:47 UTC 2011
There have been quite a few changes so we will have one more release
candidate:  Slackware 13.37 RC 3.14159265358979323846264338327950288419716.
Very close now!  But we'll likely hold out for 2.6.37.6.

Well there you have it. The answer you all have been looking for, all that time!

The list of changes is again pretty long. It shows that “declaring a Release Candidate” has a good reason. People ask from time to time, why these release candidates? Thy are nothing similar to what the bigger distros use in their progression towards a stable release. Things like “feature freeze” and “show stopper bugs” are used in Slackware development too, but you won’t see those mentioned in the ChangeLog. They are not relating one-to-one to any of the Release Candidates. Instead, the first call of a Slackware Release Candidate causes many people to try and install Slackware-current for the first time in a development cycle. Not many people are anxious to use a development release, especially since all of us keep repeating “when you are running -current, we expect that you know what you are doing, and that you are able to fix a suddenly broken system by yourself (with the help of the community)“. The Release Candidates are a sign of stability for those people. And we need all of you to help with the final stage of development! All these new people testing the pre-release result in many bugs found and forgotten features requested, and this causes a surge in the stabilization process which makes Slackware the rock solid distro we all know.

Multilib fans (slackware64), pay attention!

A new kernel again (2.6.37.5) and as the ChangeLog.txt says, there will likely be one more before the final release of Slackware 13.37. This means, you get a recompiled multilib version of glibc from me – and there will be another recompile if we see yet another kernel update.

Grab the updated multilib glibc packages from the usual locations:

http://slackware.com/~alien/multilib/current/ (primary site)
http://taper.alienbase.nl/mirrors/people/alien/multilib/current/ (fast mirror)

Enjoy! Eric

Slackware 13.37 Release Candidate 2

alienbob — Wed, 16 Mar 2011 14:25:12 +0000

We have progressed to the second release candidate for the upcoming release of Slackware stable (version 13.37 no less). There is probably not going to be a lot of other updates before final release; the TODO list should be quite short now. The only one to know for sure is Pat Volkerding… I am only speculating of course.

Noticable is that the Slackware -current’s kernel has again been updated – this time to 2.6.37.4. And again, as part of a Slackware kernel update, the glibc packages were rebuilt against the new kernel’s header files.

If you have enhanced your 64bit Slackware-current with multilib capabilities, you can upgrade to the new multilib glibc packages that I compiled for you.

Get the glibc packages for your multilib Slackware64-current at http://slackware.com/~alien/multilib/current/ as usual (or visit my mirror at http://taper.alienbase.nl/mirrors/people/alien/multilib/current/).

I also updated the content of the slackware64-compat32 directory. In there you will find a copy of all the packages which are created by running the massconvert32.sh script. Install these packages on top of your multilib Slackware64-current in order to make your computer fully support 32bit applications (or use “upgradepkg –install-new” if you already installed a previous set of these packages).

No idea what I have been talking about?

If you want to know about 64bit Slackware Linux (which is a pure 64bit OS) and how to “upgrade” to a multilib system (supporting 32bit as well as 64bit applications), you should definitelty read http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib …

Eric

Multilib updates to go with new kernel

alienbob — Wed, 09 Mar 2011 17:09:09 +0000

Hi folks!

Slackware -current’s kernel has been updated to 2.6.37.3 (something many of you probably did not expect) as part of the large update leading to the first release candidate for Slackware 13.37.

This newer kernel seems to work better on all the developers’ computers especially for X sessions.Also speakup (a kernel driver for speech synthesizers) is now part of the kernel since 2.6.37, which means that a separate kernel containing a speakup patch could be dropped from the installer.

Anyway, as part of the kernel update, Pat Volkerding rebuilt the glibc packages against the new kernel headers.

Those of you who run a multilib-enhanced version of Slackware64 know what that means… I have updated my own multilib repository with rebuilt glibc-2.13 packages. This is not an urgent or mandatory upgrade for you, as the previous version of the multilib glibc packages will probably work fine. But for compiling new software that wants to use the kernel api you’d want to go with the rebuilt versions.

Get the new glibc packages at http://slackware.com/~alien/multilib/current/ as usual.

As a bonus, I have also updated my massconvert32.sh script which is part of the compat32-tools package in the same directory. Several packages have been added for the benefit of compiling and running wine. Please tell me if more packages have to be added to that script!

I also updated the content of the slackware64-compat32 directory which holds a copy of all the packages which are created by running the massconvert32.sh script (to make it easier for you if you have your doubts about how to use that script).

Eric

New multilib gcc and glibc packages for slackware-current

alienbob — Fri, 11 Feb 2011 08:43:37 +0000

Patrick Volkerding has been busy again. See the Slackware ChangeLog.txt for a series of big updates!

There’s a new kernel. Slackware tries to stick to the 2.6.35.xx “long term support” kernels for the next release. The new kernel along with updated mesa and xf86-video-ati packages should make the owners of Ati graphics hardware happy. And my Lenovo T400 laptop with its Intel graphics feels better using this version of mesa too (no freezes in X.Org anymore). Other updates in today’s batch are primarily security fixes (quite alot actually), and fixes for software bugs.

The real reason for this post is of course the fact that there were updates to glibc and gcc. As you know, people running a multilib 64-bit Slackware-current need to install multilib versions of glibc and gcc or they lose the ability to run and compile 32-bit programs. I have new multilib versions of glibc (2.13) and gcc (rebuilt 4.5.2) packages for you.

Check out http://slackware.com/~alien/multilib/current/ if you want to download these packages.

You will also find a subdirectory “slackware64-compat32“. That directory contains all packages that are generated by the massconvert32.sh script. In other words, everything you need (along with my gcc/glibc and compat32-tools packages) to turn your Slackware64-current into a multilib system. The choice is yours: either you download and install/upgrade the packages in the “slackware-compat32” directory which I converted for you, or you run the “massconvert32.sh” script to convert these packages from the Slackware originals and install those.

If you are new to this, and want to know what the difference is between 64-bit Slackware and a multilib system, I have written detailed installation/upgrade instructions in a Wiki article at http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib .

Good luck! Eric

Try my fast mirror at http://taper.alienbase.nl/mirrors/people/alien/multilib/current/
Rsync access offered through rsync://taper.alienbase.nl/mirrors/people/alien/multilib/current/

Updates for multilib gcc and glibc packages

alienbob — Tue, 11 Jan 2011 09:09:49 +0000

After a period of silence, Pat updated the Slackware ChangeLog.txt again!

Apart from the latest in stable KDE4 releases (4.5.5), you will find a new kernel. The choice for 2.6.35.10 was made because the 2.6.35 series has long-term support and Pat is probably trying to stabilize toward a new release. More on-topic for this article, there are new glibc (2.12.2) and gcc (4.5.2) packages. For those of you running a multilib-enhanced 64-bit Slackware this means you need an updated set of multilib packages, which I already created for you.

Check out http://slackware.com/~alien/multilib/current/ which contains my multilib versions of the new gcc and glibc packages in Slackware-current.

For installation/upgrade instructions see the multilib README or even better, read my Wiki article at http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib .

Good luck! Eric

PS:

Fast mirror at http://taper.alienbase.nl/mirrors/people/alien/multilib/current/

Rsync access offered through rsync://taper.alienbase.nl/mirrors/people/alien/multilib/current/

Another glibc multilib update

alienbob — Fri, 29 Oct 2010 22:29:55 +0000

Barely a week has passed, and we have yet another local root hole in glibc that needed patching. The Slackware ChangeLog said it like this:

a/glibc-solibs-2.12.1-x86_64-3.txz: Rebuilt.
Patched “The GNU C library dynamic linker will dlopen arbitrary DSOs
during setuid loads.” This security issue allows a local attacker to
gain root by specifying an unsafe DSO in the library search path to be
used with a setuid binary in LD_AUDIT mode.
Bug found by Tavis Ormandy (with thanks to Ben Hawkes and Julien Tinnes).
For more information, see:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3856

http://seclists.org/fulldisclosure/2010/Oct/344

(* Security fix *)

Of course, I was out of town for a few days when this happened, so it took a little longer to build updated multilib versions for glibc.

But… they are available now for your 64-bit Slackware 13.0, 13.1 and -current. Grab them here: http://slackware.com/~alien/multilib/. If you need guidance, read the README or better even, check out the Wiki page on Slackware multilib.

I hope this is the last hole for a while, it sucks having to rebuild all of this.

Mirrors: http://taper.alienbase.nl/mirrors/people/alien/multilib/ and http://slackware.org.uk/people/alien/multilib/.

Eric

New multilib glibc packages fix local root hole

alienbob — Thu, 21 Oct 2010 08:28:46 +0000

New glibc packages for Slackware arrived on the mirrors last night. They close a serious local root hole. From the ChangeLog:

Patched “dynamic linker expands $ORIGIN in setuid library search path”.
This security issue allows a local attacker to gain root if they can create
a hard link to a setuid root binary. Thanks to Tavis Ormandy.
For more information, see:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3847

http://seclists.org/fulldisclosure/2010/Oct/257

(* Security fix *)

I have already created new multilib versions of the updated glibc packages for Slackware64-current, get them here: http://slackware.com/~alien/multilib/current/ or mirrored here: http://taper.alienbase.nl/mirrors/people/alien/multilib/current/ and here: http://slackware.org.uk/people/alien/multilib/current/.

When I return from work, I will also create I have also created updates to my multilib glibc packages for Slackware64 13.0 and 13.1. Stay posted, I will write a note in the comments section of this article.

Eric

New multilib packages for 64-bit Slackware-current

alienbob — Wed, 13 Oct 2010 22:22:40 +0000

As you may have noticed already, there are interesting updates in the Slackware ChangeLog.txt !

A new kernel, and new glibc plus gcc packages means there has to be an updated set of multilib packages too or else you bunch of hybrid lovers would be left out in the cold.

Well actually there is an update to my multilib packages too! . The http://slackware.com/~alien/multilib/current/ is a new directory with goodies for your consumption.

For installation/upgrade instructions see the multilib README or even better, read my Wiki article at http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib (which has not yet been updated with package versions for slackware64-current, but that will change soon).

In the slackware64-compat32 subdirectory I added the set of packages which have been generated by the massconvert32.sh script, i.e. that directory contains all the support libraries you need (along with my gcc/glibc and compat32-tools packages) to turn your Slackware64-current into a multilib system.

Good luck! Eric

PS:

Fast mirror at http://taper.alienbase.nl/mirrors/people/alien/multilib/current/

Rsync access offered through rsync://taper.alienbase.nl/mirrors/people/alien/multilib/current/

Slackware 13.1 is here

alienbob — Mon, 24 May 2010 21:23:42 +0000

Just to add another message to the turmoil of cheering blog posts

Slackware 13.1 has been released today.

Read all about it in the official announcement or read the ANNOUNCE.TXT directly.

As usual, it is recommended (but not mandatory) to buy a copy of the DVD or CD-set which helps funding the development of the distro (no, I am not getting any money out of that). The ISOs are of course available for free, and Bittorrent is the fastest way to get them: http://www.slackware.com/getslack/torrents.php

Alphageek’s “sligdo files” are a very fast way of creating byte-exact copies of the official ISOs in case you already have a local mirror-copy of the full Slackware 13.1 tree. The ISOs you create with sligdo (http://alphageek.dyndns.org/linux/sligdo/) will pass the GPG verification test. I just hope he will have those sligdo files ready for downlooad in time. If not, I have copies here: http://alien.slackbook.org/sligdo/ .

If you want to know more about how to create a Slackware USB installer if your computer does not have a CD or DVD drive, read this older article of mine: http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ – or for the Windows users: http://alien.slackbook.org/blog/welcome-windows-user/

If you install or upgrade to the 64-bit version of Slackware 13.1 and want to have a system which is capable of running 32-bit software too (Slackware64 itself is a pure 64-bit distro), then you can make your Slackware64 multilib – read all about the process (which is fairly easy and straight-forward): http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib

To celebrate the occasion, I have created Slackware 13.1 packages for the VideoLAN Player (VLC) with added support for the new WebM video format which has the potential of becoming the default video format in the implementation of the HTML5 “video” tag. Packages here (look for vlc-1.1.0.rc – at the moment of publishing this post I am still building them on a fresh Slackware 13.1…): http://www.slackware.org.uk/people/alien/restricted_slackbuilds/vlc/ . An example .webm video file is here if you want to try: http://www.jbkempf.com/~jb/yt3.remux.webm with thanks to Jean-Baptiste Kempf of the Videolan team.

Have fun! Eric