Skip to main content

Poll Results

It's been two months and now it's time to recap the poll results. There are 134 voters for this poll and i thank you all who have voted for this, so without further ado, here are the final results:
2.6.35.12 2 (1%)
2.6.37.6 64 (47%)
2.6.38.4 33 (24%)
2.6.39-rc4 2 (1%)
Custom Kernel 33 (24%)

Nearly 50% of the voters decided to use the default kernel shipped with Slackware 13.37. It seems that they believe in Pat's choice. I also believe this is the best option at the time Slackware 13.37 was released, even though 2.6.38 has been released.

24% chose to pick 2.6.38.4, which supports better hardware and also provides better performance if combined with the correct xorg, mesa, and intel driver package, but there's a power consumption problem spotted on this release by Michael Larabel of Phoronix.

Another 24% picked to build custom kernel for their machine. I think Slackware's kernel configuration is nearly perfect for day to day configuration, but some people (like me for example) wanted to optimize the kernel or even trimming down the unneeded modules or filesystems, so we end up tweaking the kernel configuration to have different configuration and build it by ourself.

I would like to thank to all voters and see you in the next poll

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