Wednesday, May 30, 2007

Auto Mounting on Slackware

Remember Big Updates i wrote yesterday? Well, this post is the next part of the updates. Since Pat includes HAL on the last updates, i was wondering, whether the auto mount feature will be available on Slackware-Current (Since auto mount needs KDE to be recompiled with HAL being enabled), so today i upgraded my system to the latest batch updates, compiling the latest kernel, and also testing the auto mount feature. Guess what? It's finally ON. Slackware is now officially has auto mounting feature (at least in Slackware-Current, but when it will be released, it will be official by that time).

I tried to plug my portable HD and wait for a few seconds and new window popped up and asking me what should the system do with it? It's automatically mounted on /media/sda1. The same goes to CDROM and also USB Flash Drives. Everything worked like a charm. One thing you should remember that if you want to use the auto mounting feature, you will have to edit your /etc/fstab entry and comment the CDROM and Flash Drive line, or else this entry will be used instead of the auto mount feature, since HAL respects /etc/fstab entry and if it exists, it will use the fstab rather than doing an auto mount.

Well, auto mount is a nice technology, but it may cause problems also. Since it's mounted automatically by the system, it doesn't mean that you can unmount it easily. When i used my fstab,i could mount/unmount my devices using my normal account, but since i used HAL, i had to switch to root user to unmount the devices, since it's not listed in fstab. Also when i looked the disk usage by typing df, i saw a negative value for my portable HD, which should not be there.

I don't know whether i should use HAL or use the old ways. For CDROM, perhaps i will continue to use HAL, but for removables devices, such as portable HD or USB Flash Drive, probably i will stick with the old methods (using an alias to mount/unmount them). It gives me a safety up to now.

Really Big Updates

Finally -Current changelog get updated. It's not just small updates, bug quite big one, and FINALLY, Pat introduced HAL as one of the official Slackware packages (starting in -Current, but it will officially supported when Slackware 11.1 comes out). It also introduced a new KDE, GIMP, Kernel, and many more packages. See the Changelog for yourself for the detailed changes of the Slackware-Current.

Sunday, May 27, 2007

A Week Without Updates

It's been a week that the -Current changelog hasn't been updated by Pat. I know he's busy working on many packages that needs to be build and making sure that everything works perfectly and released them as a big batch once at a time. I was worried that it will be a big and quite major changes which might have better chance to break systems. I hope that KDE 3.5.7 will be included in the next updates, with MySQL 5.0.41 included and also other packages as well, which should be recompiled with the latest package version.

Let's just wait for now

Thursday, May 24, 2007 Released

Kernel's -Stable team has released to public and it contains quite a lot of patches compared to the previous One of them is the SiS900 bug which caused PV was forced to patch the kernel manually (he seldom gave patches to the source, unless it's very critical and causing problems to the users). For full changes, please see the Changelog. I'm downloading it now and i will upgrade to this version when i had some time in the next few days (along with other Slackware-Current updates which i haven't installed, including configuring my system for new Apache 2 package. I'm waiting for PV to release MySQL 5.0.41 before i upgrade my Apache 2, since i will recompile my PHP and use the latest MySQL version on one step).

Update (25 May 2007 09:41AM): This version has been superseded by which has been released short after release after the -Stable team fix 1 problem with GEODE-AES.

Sunday, May 20, 2007

Apache 2 Goes to -Current

If you look on today's -Current changelog, you will notice that Pat has removed apache package and replace it with Apache2 (the package is changed into httpd2 and not using apache again). This big upgrades comes with several other updated and added packages as well, such as obexftp, php, udev, wireless-tools, etc. It's perfect time to include Apache 2 since it's still in development cycle, so things might change in the future if there has been a problem with the current Apache version.

Thursday, May 17, 2007

Quick Fix

Yesterday i wrote an email to Patrick Volkerding about a problem after i upgraded my sysvinit-scripts package which contains a new call to wait for I/O to finish their job and today, Pat has released an upgrade to the package by removing it (back to the old nature) and also released a security fix for libpng library. This is what i like about Slackware. When concerning about security and user's problems, Pat reacts very fast so the impact could be minimized. Those who haven't upgraded the sysvinit-script package before should download the latest build or you will have the same problem as i did yesterday and ended up booting into single user mode to fix it.

Wednesday, May 16, 2007

Waiting Forever

Pat has released another batch of updates today and no big changes at this time (some perms fixes, some configuration tweaks, adding missing symbolic links, add missing files, etc). I have just upgraded all of this packages and when i tried to reboot and test it, it stopped at GPM service. After running GPM, it should load the /etc.rc.d/rc.local on my system so when i looked at the -Current changelog, Pat has add some wait/sync/sleep call in the /etc/rc.d/rc.M file and this caused trouble on my system. It waited forever and i couldn't logged in into my own system. Here's the changelog entry:
a/sysvinit-scripts-1.2-noarch-8.tgz: Removed the sysvinit runlevel directories.
Added a wait/sync/sleep before rc.local to be sure all I/O is done.
Thanks to Mark for the advice on that.

The solution is quite easy actually, but since i couldn't do anything on normal runlevel (3 or 4), i had to do it in single user mode. After logging in, open /etc/rc.d/rc.M file and change the new added line:
# An old *NIX trick to be 100% sure that drive activity is done.
# For example, "ldconfig &" might cause problems if it's still
# running and rc.local uses hdparm on the drive.
sleep 1


# An old *NIX trick to be 100% sure that drive activity is done.
# For example, "ldconfig &" might cause problems if it's still
# running and rc.local uses hdparm on the drive.
#sleep 1

You probably want to leave the sleep 1 line as it won't hurt your system and just giving some delays.

Monday, May 14, 2007

NVidia Logo Came Back

Yesterday, i upgrade my Slackware packages to the latest batch updates of -Current. Before i started my X Window, i tried to look on the xorg.conf and see the default Depth and it was using 16. I remember one of NVidia's developers reply to my email about the bug i had with NVidia driver newer than 1.0-9631 that was causing the screen to became blurred when i logged out from KDE. They told me to change the default depth to 24, but i haven't tried that again and this time, i tried it and voila.... the NVidia logo re-appeared again (it was missing after i upgraded to -Current due to XOrg upgrades). So if you have problems like i do (Missing NVidia logo at the startup), try to change the default depth to 24 and hopefully it will fix your problem.

Saturday, May 12, 2007

Pidgin in Unsupported

I was quite surprised after looking at -Current changelog today:
xap/pidgin-2.0.0-i486-2.tgz: Here's a little excerpt from:
"We have no developers using Slack, and furthermore, several of us actively dislike that distribution for its history of broken installs, as well as for its non-existant package management. You cannot create true packages for Slack."
Well, I'm somewhat shocked by this, having never (to my knowledge) done anything to any of the former GAIM or Pidgin developers to make them mad at me, Slackware, or anyone on the Slackware team. I guess if they feel it's not possible to make a "true" Pidgin package for Slackware, there's no point in continuing to try. Having put out 7 security advisories on GAIM, I'm quite sure there will be less work here if Pidgin is not included.
The Pidgin package has been moved to the "unsupported" directory. For the record, I do not actively dislike Pidgin or any of their developers, but I do plan to use Kopete from now on.

This entry has been changed into this by the time i browsed the site:
We have no developers using Slackware, and we do not support it, due to a history of problems which are caused or made unnecessarily difficult to solve by the fact that its package system does not support automatic dependency resolution. We also recommend that users do not attempt to compile Pidgin from source on Slackware, but instead use the packages provided by the Slackware team. If you insist on trying this out yourself, the only advice we can give you is to ask for help in ##slackware on, or on the Slackware mailing lists.

Nevertheless, pidgin has been placed under unsupported directory which means that Pat will no longer support this great application anymore (unless he changed his mind). I do hope that he will still support this great application. On my personal experience, Gaim/Pidgin packages build by Pat always worked for me and he always provides all the dependencies required by Gaim/Pidgin packages (it's the fact that Slackware package management doesn't do dependency checking, but it has been there for more than ten years and everybody loves it and there's a lot of community out there willing to help you if you have problems with Gaim/Pidgin).

Well, if Pat doesn't change his mind, all Gaim/Pidgin fans will have to download the SlackBuild script that Pat used to build previous version and build it manually or grab the SlackBuild in SlackBuilds project or wait until someone build a Gaim/Pidgin packages on LinuxPackages. It is a pity to lose such a great IM client.

Thursday, May 10, 2007

Chapter 17 Finished

Finally i had some time to update Slackbook project. I have committed the translations of Chapter 17 to the CVS server. For those who followed the Slackbook guidance, please update your local repositories by running cvs -z6 update on your Slackbook directory. I'm hoping that i can finish next Chapter this week.

Thursday, May 3, 2007

Kernels Upgraded in -Current

Pat has just upgraded all the kernel packages in -Current to, the latest stable kernel we had for now. All new kernels will have several version, and it depends on you who will use it. Since i'm using custom kernel, i won't need many of those packages, except for kernel-headers and glibc-* packages. I probably will have to upgrade to in order to sync with the latest kernel being used in Slackware, but the problem is in Internet Connection. As i already moved back to Jogja, i will have to wait until i had Speedy installed on my house before i can start downloading the big packages :(