Skip to main content

Poll Results

It's been a long two months since Slackware 12.1 is published and people have given their vote for the poll and it's time to show the result of the poll. The question was "Slackware 12.1 Released. What would you do?" We have a definite winner and here's the result:
Run fresh installation 131 (57%)
Manually upgrade (using upgradepkg) 39 (17%)
Automatic upgrade (using tools, such as slackpkg) 25 (10%)
Wait for public review and testing 3 (1%)
Running test in other test system 3 (1%)
Running in virtualization system 5 (2%)
Stick with the old version for now 11 (4%)
Stick with the Linux distribution i used currently 2 (0%)
Migrating to Slackware 10 (4%)

The majority of the voters chose to run fresh installation with more than half of the votes. Probably because they didn't want to go intro troubles for manual upgrades. The main reason is that you must do the proper ways unless you want to have a broken system (for example segfault condition all the time just because you forgot to upgrade glibc-solibs library in the beginning of the upgrade process).

Some people also love the availability of automatic tools that could help them upgrade to the next version. While i don't like this approach, some people think of it as a shortcut, because they don't have to think about lots of things as it has been taken care by the tools. Some tools are good at doing their jobs, and some don't, so pick it wisely big grin

I personally picked manually upgrade using upgradepkg, because i used -Current on my daily basis, so the default Slackware package management tools (pkgtools) is adequate for me. As long as you read the instructions, you will not get burned cool I have proven this for myself, as my laptop was based on Slackware 10.1 and i never ran fresh installation whenever next Slackware has been released. I upgraded them manually using upgradepkg and so far, it works perfectly love struck

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