Showing posts from December, 2009

Security Update: Seamonkey

Seamonkey packages has been upgraded to 2.0.1, the latest version which synchronized with latest Firefox release yesterday. Along with these packages, akonadi and liblastfm was rebuilt. I'm not sure why.

It's a small updates, so it won't take too long to get the updates on your system

Managing Ipod Using gtkpod

I have an iPod with me and i used to use Apple iTunes to manage it on Windows. Since i now completely wiped out Windows on my laptop and i never logged in to my Windows on my desktop, i need to find a way to be able to manage my iPod on Linux.

I have heard about gtkpod project since a long time ago, but i never tried to use it until yesterday. There's a SlackBuilds script written by Robby Workman on SlackBuilds project, so i just use the script to build the package and it runs perfectly

At first, i'm a little bit confused with how it works, but after some testing (i tested by wiping all my music collection on my iPod and adding a new one), i finally managed to see how it works and yes, it does works on my iPod. gtkpod has supported many kinds of Apple's iPod products, starting from the first generation up to the fifth generation of iPod, including iPod Touch. To see whether your version or not, please visit this page.

In general, gtkpod has successfully replaced iTunes for d…

KDE 4.3.4, Firefox, and Many More

Big bunch of updates happened today on -Current. KDE stock has been upgraded to KDE 4.3.4 and many libraries are upgraded as well. I'm quite surprised, since KDE 4.4.x will land on January/February and KDE 4.3.4 might be the last maintenance release due to developers are focusing on KDE 4.4.x release. Besides that, Firefox and many other applications are being upgraded as well.

There are two more libraries added on this updates as well.

Here's the complete list of Slackware-Current changelog today:
Thu Dec 17 20:51:37 UTC 2009
d/ruby-1.9.1_p243-i486-4.txz: Rebuilt.
Added deprecated headers needed to build kdebindings.

kde/amarok-2.2.1-i486-1.txz: Upgraded.

kde/k3b-1.69.0-i486-2.txz: Rebuilt.

kde/kdeaccessibility-4.3.4-i486-1.txz: Upgraded.

kde/kdeadmin-4.3.4-i486-1.txz: Upgraded.

kde/kdeartwork-4.3.4-i486-1.txz: Upgraded.

kde/kdebase-4.3.4-i486-1.txz: Upgraded.

kde/kdebase-runtime-4.3.4-i486-1.txz: Upgraded.

kde/kdebase-workspace-4.3.4-i486-1.txz: Upgraded.


K3B Upgraded

When Slackware 13.0 is released, K3B application was considered broken, thus Pat decided to put the old version of K3B on extra/ directory along with some old KDE 3 libraries so that people could use that version to have a working K3B.

Nowadays, people have reported that the version used in KDE 4 is working and today, the K3B on -Current has been upgraded again to the latest version of K3B, which is 1.69.0 Alpha 4. Even though it's considered Alpha version, but it's quite stable for daily usage, so give it a try and you will love it

Well, that's the only update for today.

Security Update: GIMP

GIMP has been upgraded to the latest version to fix security problem. Mozilla Thunderbird is also upgraded to 3.0, the latest version which has been released few days ago by Mozilla. Congratulations to Mozilla and enjoy the new applications.

Here's the -Current changelog:
Sat Dec 12 04:51:11 UTC 2009
xap/gimp-2.6.8-i486-1.txz: Upgraded.
This fixes integer overflows in the image handling plugins that could lead to the execution of arbitrary code or an application crash if a malicious image is loaded.
For more information, see:
(* Security fix *)

xap/mozilla-thunderbird-3.0-i686-1.txz: Upgraded.
Congrats to Mozilla Messaging on the great new Thunderbird release!

Security Update: ntp

NTP package has been upgraded to fix security problem, which was a denial-of-service attack involving spoofed mode 7 packets. This is the only update for today. I'm still waiting for KDE 4.3.4, even though it would be better to wait until KDE 4.4 is coming on Slackware-Current. I'm sure Robby and Eric are now testing the first beta version.

Security Update: Kernel

It's very rare to see Slackware released a security update on kernel packages, but today it happened. Slackware patched the kernel due to problem found by David Ford which can caused the system to immediate hang when it received an over-sized IP packets.

Here are the changes in -Current today:
Tue Dec 8 20:44:44 UTC 2009
a/kernel-firmware- Rebuilt.

a/kernel-generic- Rebuilt.
Patched a bug (CVE-2009-1298) where oversized IP packets cause a NULL pointer dereference and immediate hang.
For more information, see:
(* Security fix *)

a/kernel-generic-smp- Rebuilt.
Patched CVE-2009-1298.
(* Security fix *)

a/kernel-huge- Rebuilt.
Patched CVE-2009-1298.
(* Security fix *)

a/kernel-huge-smp- Rebuilt.
Patched CVE-2009-1298.
(* Security fix *)

a/kernel-modules- Rebuilt.


Detecting 4GB of RAM

As you probably have known, i have bought a new desktop and laptop, both equipped with 4 GB of RAM, but i'm still using 32bit Slackware Linux, so there's a limitation from the OS to correctly detect 4 GB of RAM. In order to solve that, in most article says that we have to start using 64bit version.

That is the easy solution, but what happened if you are too lazy to reinstall and reconfigure everything? Well, if your processor support PAE, then you are quite lucky, since you only need to recompile your kernel and enable HIGHMEM64G config and it will try to enable PAE extension as well. When you are finished, the Slackware 13.0 will detect your 4GB of RAM. Look the results using free or cat /proc/meminfo

Development Application Updated

There are several updates related to development tools and also libraries on -Current today. Here's the changes:
Sun Dec 6 03:23:23 UTC 2009
a/sed-4.2.1-i486-1.txz: Upgraded.

d/git- Upgraded.

d/python-2.6.4-i486-1.txz: Upgraded.

d/subversion-1.6.6-i486-1.txz: Upgraded.

l/libxml2-2.7.6-i486-1.txz: Upgraded.

l/libxslt-1.1.26-i486-1.txz: Upgraded.

l/neon-0.29.0-i486-1.txz: Upgraded.

Small Updates on Ruby

Ruby packages has been updated to fix symlink problem. Please refer to the -Current changelog for the changes.

Security Update: BIND

BIND is (again) patched to fix security vulnerability. Along with this security update, some packages are upgraded as well. Have a look on -Current changelog below for more detail information:
Wed Dec 2 20:51:55 UTC 2009
a/xz-4.999.9beta-i486-1.tgz: Upgraded.

ap/rpm-4.7.2-i486-1.txz: Upgraded.

ap/sudo-1.6.8p12-i486-2.txz: Rebuilt.
Added --with-env-editor to ./configure flags so that users can do this: VISUAL=/usr/bin/pico visudo OR EDITOR=/usr/bin/pico visudo
d/ruby-1.9.1_p243-i486-1.txz: Upgraded.

kde/koffice-2.1.0-i486-1.txz: Upgraded.
Note that there's a _really_ ugly patch that was used to make this compile, otherwise it fails with this error: kis_jpeg_source.cpp:(.text+0x79): undefined reference to `jpeg_resync_to_restart(jpeg_decompress_struct*, int)' I would welcome any hints about how to compile koffice without this patch.

kdei/koffice-l10n-*: Upgraded.

n/bind-9.4.3_P4-i486-1.txz: Upgraded.
BIND 9.4.3-P4 is a SECURITY PATCH for BIND 9.4.3-P3. It addresses a potential cache poison…

Prediction Time

While -Current hasn't officially started, we have seen some changes in -Current tree for a while and i think it will keep going like this until eventually something break the compatibility with Slackware 13.0 towards 13.1 release.

Pat usually never decide a fixed date for Slackware release. He will release it when it's considered ready and stable enough for production use, so let's just take this month's poll to predict when will next Slackware 13.1 be released.

Please note that this is just a poll and it will not have any effect of the real release date of next Slackware (probably 13.1). The decision is still on Pat's hand.

Poll Results

November is past now. It's coming to December and that means poll is now closed and we come to this result:

< 15 minutes 18 (28%)
15 - 30 minutes 29 (46%)
30-60 minutes 10 (15%)
more than 60 minutes 6 (9%)

Almost 50% of the responders voted that they finished the Slackware 13.0 installation ranging from 15 - 30 minutes, which is the normal condition of Slackware installation. Under 15 minutes comes in second with 28%, which usually experienced by someone who are used with Slackware installation and they know what they are doing (and they love doing it so).

Keep in touch with a new poll for this month