Alien Pastures

My thoughts on Slackware, life and everything

Tag: glibc (Page 2 of 4)

Multilib glibc patched for GHOST vulnerability (CVE-2015-0235)

January 30, 2015 / / 13 Comments

There was some unrest about the most recent glibc update in the stable releases of Slackware (slackware-current excluded). Glibc was patched against a new vulnerability, CVE-2015-0235, for which the only known exploit currently is in the MTA Exim (software which is not part of Slackware) and an exploit for this vulnerability is difficult to write apparently. I usually am quite fast in following up on Slackware updates for gcc and especially glibc. This time, I was busy with answering questions about the new KDE 5 at night, and buried in shit at work during the day.

Nevertheless, when there were no updated multilib versions of glibc the next day, some people asked when they could expect a patched package. Others were less polite and demanded updated packages. That sucked.

Here is where you can find the updated packages:

For the un-initiated: multilib is needed if you want to use binary-only 32-bit software on 64-bit Slackware. Examples of that are Skype, Valve’s Steam Client, the WINE emulator, the Pipelight browser plugin, Citrix client etc.

Instructions on how to add or update multilib on your 64-bit Slackware can be found on the Slackware Documentation Project.

Cheers, Eric

 

Rebuild for glibc-2.17_multilib in slackware-current

April 21, 2013 / / 0 Comments

Pat’s inquery on LinuxQuestions.org about how to “backtrack to sanity” in order to stabilize slackware-current and start laying out the next release, resulted in a kernel upgrade (3.8.8) and accompanying glibc rebuild.

I built the “companion” update of the glibc multilib packages last night. They can be downloaded from:

Remember, multilib configuration is (only) needed if you want to use binary-only 32-bit software on 64-bit Slackware – think of Valve’s Steam Client, the WINE emulator, Citrix client etc.

If you are looking for instructions on how to add or update multilib on your 64-bit Slackware, check out our Slackware Documentation Project which has this information and much more.

Cheers, Eric

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

November 13, 2011 / / 14 Comments

 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

March 27, 2011 / / 8 Comments

… 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:

Enjoy! Eric

Slackware 13.37 Release Candidate 2

March 16, 2011 / / 15 Comments

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

« Older posts Newer posts »

© 2026 Alien Pastures

Theme by Anders Noren — Up ↑