Skip to main content

Poll Result

It's a bit late, but only for one day, so it wasn't a big one. So, without any ADO, here's the poll result from last month's question: "What is your opinion about KDE 4 on Slackware?"

I totally agree 23 (26%)
It should be on /extra or /testing 40 (46%)
It's not stable enough 15 (17%)
I totally disagree 2 (2%)
I didn't use KDE 6 (6%)

So, based on the votes, people thinks that KDE 4.x should be placed in /extra or /testing rather than being the default window manager in next Slackware release. I can understand that, as many critics has been addresses towards KDE on the development progress, but after 4.1 release few days ago, i believe that it's getting more stable and when next Slackware gets released, it will be as mature as KDE 3.5.x and most application will have been ported to KDE 4.x. So there is a good chance that KDE 4.x will be shipped in next Slackware.

Also if you look on the changelog on July 28, Pat updates the sysvinit-scripts to reduce the verbose level as he's "playing" with KDE 4 (my assumption) which generates more error while booting up. I guess this can be an indication that the next KDE will be used rather than 3.5.x.
a/sysvinit-scripts-1.2-noarch-21.tgz: For now, quiet error output from update-mime-database, since KDE4 causes some "noise".

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