Showing posts from May, 2011

Please Welcome Linux Kernel 3.0

There has been a lot of debates whether Linus will release the next major Kernel as 2.6.40, 2.8, or 3.0. Well, the answer is now definite. Linus will use a new naming as Linux Kernel 3.0 for the next release as he already tagged 3.0-rc1. The reason is because the number in the current 2.6.x series has reached 39 and the development has grown so much. In fact, previous 2.2 and 2.4 didn't get this big, so he thought it would be nice to bump the kernel version to a fresh one and thus it goes to 3.0.

So, the next Slackware release will likely use Linux Kernel 3.0 for it's default kernel. It has big improvements to previous kernel releases, but there might be some drawbacks. The 3.0 kernel will likely to remove some old hardware supports, so if you are using an old hardware, this is probably the perfect timing to invest for new hardware in the future.

If Slackware keeps using SLACKWARE_VERSION.KERNEL_VERSION naming scheme, then the next Slackware release could be 14.30 14.0 (Thanks t…

GCC Recompiled

GCC is being rebuilt to enable Garbage Collection feature on Objective-C. Even though it only affects gcc-objc package, all of the GCC packages must be rebuilt to syncronize the version number.

Meanwhile, file has been upgraded to 5.0.7. I hope this fixes a problem described in LQ

Security Update: BIND

Another security update has been released. The latest advisory is related to BIND. ISC has released an advisory that describe the attack details and also the workaround on their home page. This security update is released for -Current and back to older Slackware release. Since i only host up to Slackware 12.2, i can only tell that it's propagated back to 12.2, but further version might be updated as well.

Security Update and -Current Development

Two security updates were released and this updates were similar to the previous security updates regarding apr-* and httpd packages. If you are using -Current, then there's more interesting news besides normal security updates.

Pat has started to upgrade several basic packages in -Current tree. This means that -Current development is now starting again (it's a warm up level as far as i can see, as there are no major changes besides the Kernel for now).

Gentleman, start your engine for -Current again

Some notable highlights:
Kernel upgraded to with some changes in the configurationGCC upgraded to 4.5.3, still no luck with GCC 4.6Glibc is rebuilt, no further release yetSome development tools are upgraded (Perl 5.14, GIT is upgraded to latest stable 7.10.2 along with libdrm 2.4.25The other were minor upgrade and may not be that interesting for most people.

VMWare Restored and Patch for Linux Kernel 2.6.39

After being frustated for few months due to my VMWare not functioning, i finally able to revive it again. It seems the culprit was the removal of HAL (Hardware Abstraction Layer). VMWare still depends on HAL, so by removing HAL, it would break the application.

In order to get it working again, i trace the syscall of VWware, but found nothing. At last, i found it in VMWare's log called ui.log in /tmp/vmware-<username> directory. It clearly said that i should start hald as root. I checked my /etc/rc.d/rc.hald script and it didn't have any execute permission, meaning that it wasn't started at boot. So, what i did was add an execute permission and start it manually. After that, i re-run VMWare and voila... it works

Also, if you need to patch your VMWare in Linux Kernel 2.6.39, get the patch from here.

Using Kernel Linux 2.6.39

As soon as the new stable kernel has been released by Linus Torvalds, i downloaded them and install it on my workstation few days ago. It was a nice release, and one thing i would like to test is the new EXT 4 SMP scalability and also further performance improvements after they removed the BKL (Big Kernel Lock) and many other patches from the kernel developers. At that time, i didn't install it on my desktop first, since i'm not really sure whether the current NVidia driver already supported this new kernel or not.

Since few days ago NVidia launched a new driver, 270.41.19, i quickly downloaded this driver and then compile the new kernel on my desktop and at the moment, i'm compiling it on my laptop as i'm writing this post. The new NVidia driver already have support for Linux Kernel 2.6.39, so if you are curious about the new kernel and you are using NVidia, go for it

Here's the result on my workstation:
Linux office 2.6.39-smp #1 SMP Thu May 19 21:31:28 WIT 2011 i6…

Donation Target Acquired

Less than a week. That's the time required to collect the money needed to replace the server that is hosting several Slackware-related projects in What an amazing progress and this are contributed work of a lot of people in SBo, LQ, and many other communities around Slackware users

Robby Workman has just announced that they have acquired enough money to get a better server than what they planned before and yet, they still can send substantial money to Pat

It's a great achievement from Slackware community and this again shows how Slackware communities are so loyal to it's main project, Slackware Linux and also their beloved BDFL, Patrick Volkerding

Security Update: apr

Apr library is reported to have a security vulnerabilities and for that reason, it has been upgraded to the latest version and so does apr-util package and also httpd package even though it's only a bug fix release. The httpd must be recompiled since there's a change in the apr, so it's included by this batch of update as well.

Support Needed

Most of the Slackware Crew's work that we enjoyed nowadays are hosted at There are SlackBook, Slackpkg, Sbopkg, Robby Workman's web, AlienBOB's Wiki and Blog, an official mirror for XFCE, netfilter/iptables tutorial, mailing lists for, DNS and email for, and many more.

There was no problem with the hosting server, but recently, the old server was having a rough time maintaining it's availability and it's causing more and more problems to the maintainers, so the Crew thought it is probably the right time to migrate to a new server. Check Robby's post on SlackBuilds-User mailing list.

FYI, Cardinal is an old 1u server with dual P3 Coppermine procs and 3G of ram and it's running Slackware 13.37. Check the personal system information page if you don't believe me

Alan Hicks is making a new spec for new server and it would cost around USD 1000++ (They are going to add more disk storage onto it so th…

Better GTK/KDE Integration

If you are KDE users but you used a lot of GTK-based applications, there is a solution for you to make the look-n-feel much likely the same. Eric has build a new package called oxygen-gtk, a port of the default KDE widget theme to GTK. By installing this package, all GTK-based applications will have the same look-n-feel as in KDE apps.

Don't forget to copy /usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc configuration file to your home directory into the file ~/.gtkrc-2.0 and make sure you logged out and logged in again to see the effect.

KDE 4.6.3 for Slackware 13.37

While Slackware-Current development has not publicly visible, Eric keeps maintaining KDE 4.6.x series in his KTown repository and now releasing KDE 4.6.3 series for Slackware 13.37 and -Current (basically they are still in the same level for now). It's another monthly maintenance version of KDE, so it's safe to upgrade since there are no new features on this update, only bug fixes and translations updates.

UKDW Repository has finished mirroring the packages and it's ready to be downloaded through this url: Please note that there is a new package on this release besides the regular one in deps, which is bluedevil. This notes are taken from Eric's blog post:
Bluedevil is the new bluetooth connection manager for KDE. It integrates well with KDE (you will find a “send to bluetooth device” in Dolphin’s context menu for instance). The old “kbluetooth” application is no longer developed and the GTK application in Slackware “blueman” is not …

What's Next?

Slackware 13.37 has been proven to be a stable and secure release. But that won't stop Slackware development towards next release (even though we might not see the next release in short time). Slackware is evolving as the upstream goes since it tries to deliver a complete Linux distribution that is up to date without sacrificing it's motto of keeping it simple, secure, and stable.
I have no idea what will the next Slackware codename be. It could be 14.0 (back to the old Slackware naming style) or probably it will use the current SLACKWARE_VERSION.KERNEL_VERSION naming just what we have in Slackware 13.37. What i'm quite positive is that it will be a major upgrade, so it will have a Slackware version of 14.

So here's what i had in my mind about what should be in the next Slackware release. Remember that this is my personal wishlist, not Pat's mind, so the final outcome will definitely NOT 100% accurate:
KDE 4.7.xXFCE 4.8.x
Linux Kernel 2.6.40.x/2.6.41.x
Python 2.7.x/3.1.…

Coreutil Upgraded

It's not a security fix, but there's one package being upgraded in -Current branch only, which is safe to be backported to 13.37 as at this time, Slackware 13.37 is still in the same level as -Current as it hasn't changed it's basic toolchain.

You might wonder, why an upgrade to this package? Well, someone on LQ reported that the current version of coreutil included in Slackware 13.37 will have a problem if it's being used in Linux Kernel 2.6.38.x and future 2.6.39.x series. Eventually it wasn't included in -Current at that time, but probably Pat decided to upgrade this once 13.37 is released and he just did.

The release notes of Coreutil can be seen at Savannah Server of GNU

Security Update: Firefox, Thunderbird, and Seamonkey

Three security updates were released today. They are packs of Mozilla's products: Seamonkey, Firefox, and Thunderbird. These packages are intended for Slackware 12.2 and onwards up to 13.37 and also -Current (except for Seamonkey which doesn't come up in -Current as it already uses the latest beta version and it wasn't affected by the vulnerabilities).

These two packages in -Current are the first batch of updates in -Current, but we won't see it changes daily just as before. Development of -current will be visible to public in about 2-3 months from now. During this time, it's most likely that Pat and the Team are resting and probably preparing for the upcoming release of next Slackware release (will it be 14.0 ??).

For now, just enjoy Slackware 13.37

Don't Forget to Reboot

You might think it's kinda strange to say "Don't Forget to Reboot" to Linux users as those saying should be said to Windows users, but this happened to me when i upgraded to KDE 4.6.2 using AlienBOB's package in my new Slackware 13.37 installation in my office. I rsynced my local repository and then upgraded using SSH remotely from my house last Saturday.

I haven't tried to run KDE since then until this morning. I got several KDE crashes and i didn't see any useful information at the error messages. I have make sure that every .new config files has been merged, but still persis. Finally i re-checked the README that comes with KDE 4.6.2 by Eric himself and in the last part of the README, it says Then reboot your system.

I was like . I forgot to reboot the system since i upgraded KDE. I remembered that i have rebooted, but it was due to new kernel compiled, not because of KDE update.

Now, everything seems to be working just fine. Akonadi didn't crash on …

Slackware 13.37 ARM Released

Shortly after Slackware 13.37 has been released, now follows the Slackware 13.37 ARM gets released. For those who don't know what this is, i take the short description from the official website:
Slackware ARM (“ARMedslack”) is the official port of the Slackware® Linux distribution to the ARM architecture. Currently, the project focuses its efforts on supporting the Plug Computers, and can also be used under the QEMU emulator.

Slackware ARM 13.1 and onwards is built for ARMv4t, little endian, soft float, EABI.This version is released a month after it's first RC appeared and it's synced with Slackware 13.37.

If you are interested with this Slackware 13.37 ARM, see the GetSlack page for more information.

New Poll

Time to start a new poll. As we know, Slackware 13.37 comes with several kernels. The default kernel is, while is available in extra/ for those who would like to see "the patch that does wonders" work by Ingo Molnar and Mike Galbraith.

There's also 2.6.39-rc4 config files if you plan to build them. For those who need a longterm kernels, Pat provides config files for you to build it by yourself.

All of the those plus a custom kernel will be the options for the next two months poll. Go vote for it.

Poll Result

It's been two months since the poll started and the timeframe was not that different with what i expected since Slackware 13.37 was just released few days ago. Even though the title of the poll was misleading (it was supposed to be 13.2, but Pat jumped to 13.37 instead), but it didn't stop voters to vote and we have a new record for the poll. 228 votes counted

Here are the results:
Yes, definitely 129 (56%)
No, i prefer my present version 15 (6%)
I have been running -Current 72 (31%)
I don't use Slackware, but considering to install it 12 (5%)

People are pleased with the quality and stability of Slackware 13.37 and they will upgrade/install Slackware 13.37 when it's released and now it's your chance to prove it.

Supporting Slackware Linux Project

Slackware 13.37 has been released, so i guess it's time for us to support Slackware Linux Project in real action by buying items at Slackware Store.

The latest limited edition of T-Shirt for Slackware 13.37 is also out now in Slackware Store. It's cool and so stylish. Check it here:

If you want to see the text in the back side, here you are:

We will start buying those items when all of the interested members has submitted their items to buy to me and i will start ordering those items.

If you wish to support Slackware Linux Project, this is your chance to do so. The deadline for the item submission is next Friday, May 6 2011. The procedure can be seen in ID-Slackware mailing list.