Skip to main content

Slackware-Current Hidden Activities

There hasn't been any public activities in the -Current tree. The last update committed was in September 6 and since then, there has been a lot of changes happening in the open source world. Some people might ask "Why wouldn't Slackware development tree gets updated lately?"

In the past, when i first learned about Slackware and started to follow Slackware-Current tree few years ago, i had the same feeling. The main reason why i pick Slackware-Current so that i will get the most bleeding-edge system filled with the latest version of every applications that are supported in Slackware. In fact, this is not what Slackware-Current idea is all about. Slackware-Current is the place where development of the next release of Slackware is being cooked, baked, tested by many people around the world to produce another great release of Slackware when the time come.

Even though Pat has gave a warning about using -Current as your base system, i find that -Current is as stable as the -Stable release. In fact, some fixes will be incorporated in -Current first and then in some cases it will be backported to -Stable (mostly deals with security fixes). Sometimes -Current does break some system when a faulty package being added, but it's just a special case. I only had problems with -Current when a new modular XOrg packages were introduced and since then, i never had any problems with -Current.

Back to the topic about Slackware-Current public activities. Even though the changelog doesn't show anything at all, it doesn't mean that the development of Slackware stopped. In fact, the Core team (Pat and Slackware Crews) works day to day to internally test the packages before releasing it to public to ensure that the packages won't break user's system when they try it.

Looking at the long inactivity of the -Current tree, i suspect a huge batch of updates is coming up with lots of new applications being updated to the latest version and probably some new applications will be added (for example if Pat decided to upgrade to KDE 4.7.1, then lots of new applications and libraries will need to be added into the repository). Be prepared for the big surprises by Pat.

Since i'm leaving on Monday until the next ten days for travelling with my new wife, i may not be able to post anything if the prize has been unveiled by Pat, so stay tune to the Changelogs if you want to see the big changes happening in Slackware-Current daydreaming

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 rsync_current.sh 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 192.168.1.1 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