With all the possible tweaks I performed in Firefox and Chromium looks like below with two tabs open in both:

$ ps -aux | grep firefox
salix 11287 0.0 0.1 10616 1552 pts/5 S+ 13:23 0:00 /bin/sh /usr/bin/firefox
salix 11300 0.0 0.1 10668 1604 pts/5 S+ 13:23 0:00 /bin/sh /usr/lib64/firefox-3.6.13 ...

I downloaded the SLKBUILD package from http://people.salixos.org/djemos/salix-13.1/skype/ and slkbuild it and executied ./builpkg.sh which further created skype-2.1.0.81-x86_64-1dj.txz. Installed it with installpkg and went all well.

But when I try to launch skype in commandline, it reports ...

I tried to build it from the slackbuild, but could not as the dependencies are not met and some are not compiled.

Will there be salix packages for these two packages? I meant twinkle and chromium-latest.

@vikrang: good to learn that the issue is solved!! Enjoy Salix!

@sqlpython: After reading your post, I tested seamonkey, firefox and chromium and still chromium is the fastest and using the lowest among all

BTW, has anyone chromium-latest package built? If so, kindly point the link (could not find myself)! Thanks!

Read in this bug report (https://bugs.launchpad.net/ubuntu/+sour ... bug/477430) that removing this line in grub.cfg:

if [ -n ${have_grubenv} ]; then save_env recordfail; fi

solves the issue. You can test.

In that case, just upgrade to a new version or flash your BIOS with a new one compatible with the chip.

And it is right that with ata module, the OS runs pretty slow, I agree

IMO, it is a BIOS-related issue (http://tldp.org/HOWTO/Large-Disk-HOWTO-4.html).

May I suggest to reinstall grub with ata-module enabled. If you cannot access to the current installation, then I suggest to use http://www.supergrubdisk.org/wiki/SuperGRUB2Disk and then boot to your installation. And ...

After reading this vulnerability report (http://www.kb.cert.org/vuls/id/258423), I didn't find any other ways than to compile the latest release of chromium from source with the slackbuild script available at http://darkstar.ist.utl.pt/slackware/addon/slacky/slackware-13.1/network/chromium/11.0.652 ...

Thanks shado for the 'dirty hack' ;-)

BTW, I am having a weird problem. Once I start an lxc-container, gdm instances uses the entire resources of both of the processor.

How can I disable gdm and start x directly. I tried with a solution here (http://www.fprimex.com/linux/slackware/tips.html#log-in ...