Skip to main content

Security Update and Next Development Cycle

There was one security update releases yesterday and that was subversion. No other changes were made, both on stable and current release.

It's been almost 4 months since Slackware 14.1 gets released last November and there's no sign of the start of -current development again. Usually (based on history), it will start after 3-4 months after the last -stable release to give Pat some time to break from endless testing and debugging preparing for the stable release.

One of the most problematic problem for the next cycle is probably upstream's decision to integrate systemd in some projects. While this does not apply to all upstream projects, but i do hope that if it does, it should not be mandatory to have systemd installed and there's a configure parameter that can disable or build without systemd.

Speaking about systemd, Bart van der Hall has attempted to build systemd on top of Slackware and he has published his work on this home page. There's also a lengthy discussion about it on LQ, which is interesting to follow if you are curious about how to implement systemd on Slackware.

Personally i don't like the idea of systemd which tried to handle everything on your system with a massive changes, but i have my respect to Bart who keep doing his good work and finally produce something which is proven to be a working system without breaking compatibility with Slackware. He has given two options for users to build system with/without PAM support. Some members of LQ has given an early test and they reported it was working on their machines. Kudos to Bart.

For me personally, next current development cycle will be very interesting to follow. Well, it's always interesting to see every -current cycle :)

Slackware-Current is the development snapshot for the next Slackware release. It's considered beta testing even though 99% of all cases it is very stable (it rarely break and if it does, it gets fixed very quick) and i even used it on my desktop and workstation at home and in the office.
Nevertheless, you should stick to Slackware 14.1 if you prefer to enjoy a stable release.

Popular posts from this blog

Running Rsync Via Proxy

One way to get the latest Slackware updates is by running rsync to syncronize your local repository and the main repository that hold the Slackware packages. Eric Hameleers has provided a great script called and how i modified this tool has been discussed on my previous post. In general, it works, except for one problem, when your computer is connecting to the Internet through a proxy.

My workstation at my office is connected to the Internet through a proxy, so i can't use normal rsync to work normally. I browsed the web and i found this site which tells us about how we should modify our squid configuration to allow rsync connection from any computer from our local networks. I asked my sysadmin to try this script. He agreed and he updated the squid configuration on the proxy.

Next, i need to update my environment variable RSYNC_PROXY to the host of the proxy and also the port. Let's say you are running a proxy on and port 8080, then you need to run …

NVidia Legacy Unix Driver Update

NVidia has released an updated legacy drivers to support X.Org 1.19 with ABI 23. It has been mentioned in the UNIX drivers, but you can directly find the drivers from the links below:
NVidia 304.134 (x86x86_64)NVidia 340.101 (x86, x86_64) I have tested the 304.134 driver and it's working great here. I can finally remove x from my /etc/slackpkg/blacklist file since it's a showstopper for me.
Aside from legacy driver, NVidia has also released their latest driver 375.26 (x86, x86_64), which brings support for newer cards and also many new features (including X.Org 1.19 with ABI 23 support). 

Security Update: firefox, irssi, pidgin

Three security updates were released for today:
firefox: Upgraded to 45.4.0esr for 14.1 and 14.2 and 49.0 for currentirssi: Upgraded to 0.8.20pidgin: Upgraded to 2.10.11, 2.10.12, and 2.11.0 for all stable Slackware releases depending on their support Some minor update in current:
mkinitrd: Add dmsetup supportemacs: Upgraded to 25.1qt: Fix multilib issue network-scripts: Fix minor issue