Archive for slackware

News and Guides: Slackware-stable Kernel Upgrade

Posted in Operating System with tags , , on August 20, 2009 by muhrizky

Yesterday, i read an email from [Slackware-security] which said that they found a serious bug inside Slackware-stable release. The team informed by Google® security team on this security bug. I use Slackware Linux since 2003 where in that year is quite hard to find community, especially from where i lived, can give an information when I encountered problems in Linux. In that year, I was using Slackware 9 with kernel 2.4 and I have succeed to upgrade the kernel (not officially) into 2.6 version. Kernel 2.6 was a brand-new interesting things back in the early year of 2K.

Then yesterday after I read the email, I even think about not to respond for the patches. Because I completely forgot about how to upgrade the kernel. But now in 2K9 it is quite easy to find guide about kernel upgrading. Actually I only need two pages from Google® search. Ok now here’s the guide:

1. Download all the kernel packages you need and put them inside one directory, I recommend you to put them inside /usr/src/linux- directory. The packages itself including: kernel-generic-smp, kernel-headers, kernel-modules-smp, and kernel-source in order to compile your 3D graphic drivers. Also don’t forget to grab the kernel-mmap_min_addr_4096 package from the FTP site. FYI, this is the one that has been reported as the bug because of the kernel map addressing size.

2. Deploy all of the kernel packages by using command:
#installpkg kernel*
Be careful when you execute command with star (*) wildcard and be sure that all of the packages is served.

3. Install the kernel patch in terms of the map addressing size:
#installpkg kernel_mmap-min-addr-4096.tgz

4. Reconfigure mkinitrd, read about another articles that explains about Linux system init at my blog:
#cd /boot
#mkinitrd -k -m ext3 -f ext3 -r /dev/sda2

Wait, what is -m, -f, -r functions for? Refer to the mkinitrd man pages.

5. Modify lilo bootloader configuration by using vi editor:
#vi /etc/lilo.conf
Find the line that starts with:

#Linux bootable partition config begins
image = /boot/vmlinuz-generic-smp-
initrd = /boot/initrd.gz
root = /dev/sda2
label = Slackware
#Linux bootable partition config ends

6. Reinstall lilo by running command:
#lilo -v

7. Restart your machine. Wait and see if all of our system init is working normally and not shows you Kernel panic!!! message.

8. Download the new svgalib_helper package, recompile it for this new kernel subversion, then do install.
#installpkg svgalib_helper-1.9.2_2.6.27.31.tgz

9. Reinstall your 3D graphic drivers. It will be better if you have the latest version.

NB. If you find an error related to alsa sound, so it’s need to be reconfigure. Run this command:
#alsactl store

How-To Install VirtualBox on Slackware 12.2

Posted in Operating System with tags , , on December 30, 2008 by muhrizky

VirtualBox is a virtualization software from Sun Microsystems. In easy words, it means that we can run one or more operating systems inside one machine. This notes will guide you to deploy VirtualBox on a Slackware 12.2 machine.

1. First, you need to prepare all package dependencies for VirtualBox, which are:

  • icu4c
  • xerces-c
  • xalan
  • acpica
  • libatomic_ops
  • libsamplerate
  • libsnd
  • pulseaudio

You can get all of this packages from SlackBuilds so it can be more simple and centralized. We also need to learn how-to compile the source with help of pre-defined SlackBuilds scripts by reading their documentation.

2.1. Get the appropriate installer from VirtualBox that we need to execute on Slackware platform. Looks for the one with .run file extention.

2.2. You can also grab VirtualBox OSE packages from SlackBuilds. This is including virtualbox-ose and virtualbox-kernel. Then compile and execute them in the same way as you did on previous packages dependencies. Read the instructions carefully. If you choose this method for installation, after this you can skip directly to step sixth.

Note: According to VirtualBox sites, they mention about Qt4 as another dependencies. So here you can compile Qt4 before virtualbox-ose, but this is optional. Warning!!! It tooks so long to compile Qt4. I do that for two and a half hour on my machine with Pentium D 805, 4 Gigs DDR-II, and SATA-AHCI.

3. Third, modify the installer permissions by running this command as root:

#chmod 755

This will assign permissions so that only root can modify the installer and the others group can only read and execute.

4. Run the installer as root:


5. Next, we need to create a symbolic link from a specific file:

#ln -s /lib/ /lib/

This fifth step is a problem that i discover from kernel message. But until this notes was published, i still don’t know from where this problem arise.

6. Sixth, insert your user account into vboxusers group:

#usermod -a -G vboxusers username

Here you can also use KUser an X application from KDE environment.

7. Seventh, assume everything is working well, we can find the VirtualBox launcher from KMenu>>System>>Sun xVM VirtualBox.

Finally, don’t forget to read the User Manual for instruction guides which locates at /opt/VirtualBox-xxx/