Posts tagged ‘Slackware’

[video] Slackware64 -13.0 with Bootsplash

Please note: I made this video with a mobile phone cam and so the Video is pretty poor quality. Also I had to use Audioswap to replace the barking of my dog. ūüėõ
For those who believe that Slackware is just another geeky distro with no eye-candy, well you are wrong. It’s all about customization. Anything you can do with any GUI-based distros like Ubuntu or openSUSE, you can do those with Slackware.
First of all apologies for poor video quality, took this one with my mobile phone cam. This is just to show an idea to the world that Slackware is not all about “all text and no fun”.
Using splashy with Slackwar64 – current [but works in 13.0 as well] and Fluxbox with a conky on top and Gkrellm.

Advertisements

[slackware] Upgrade to Firefox 3.5.6

Fixed in Firefox 3.5.6

MFSA 2009-71 GeckoActiveXObject exception messages can be used to enumerate installed COM objects
MFSA 2009-70 Privilege escalation via chrome window.opener
MFSA 2009-69 Location bar spoofing vulnerabilities
MFSA 2009-68 NTLM reflection vulnerability
MFSA 2009-67 Integer overflow, crash in libtheora video library
MFSA 2009-66 Memory safety fixes in liboggplay media library
MFSA 2009-65 Crashes with evidence of memory corruption (rv:1.9.1.6/ 1.9.0.16)

The last 3 are critical fixes. Currently Slackware has 3.5.5 if you have been following the Security-fixes, else 3.5.2 which comes in Slackware 13.0.

What you need to do is find the package cairo-1.8.6 and remove it.Slack64 users:


removepkg cairo-1.8.6-x86_64-3-upgraded-2009-12-17

Then download and build the cairo-1.8.8 package. You can get the slackbuild script in your DVD in directory:  /l

Then installpkg it. Now download the Firefox 3.5.6 source code from here and use the build script in /xap directory to build the Firefox3.5.6 package. Then:


upgradepkg mozilla-firefox-3.5.6-x86_64-1_slack13.0

NOTE: While using the Slackbuilds don’t forget to change the versions to the latest.

EDIT: Pycairo can be upgraded as well. It built without the pyCairo upgrade so I didn’t notice. Thanks to JokerBoy for bringing it to my notice. Source , slackbuilds can be found in /l like cairo.

Regards

[conv] Why Slackers are labeled as geeks and ubuntuers as n00bs?

A conversation in LinuxQuestions forum I thought was worth sharing:

Hi Forum,
Being rather ecletic relating to “the best distro” to do a job… used several already, from RHEL/Fedoras to Suses, Ubuntus/Debians, and now Slackware… I never understood something…
Why ppl get tagged because of using Distro X, and not Distro Y…. ?
For instance, among ppl that knows I use Slackware, I am “deemed” as an arrogant person, by those that do not know me that well… some colleagues of mine that use Ubuntu, are deemed as n00bs, ppl that use FreeBSD are deemed Ultimate Geeks… etc…

Why is that so….?

Arrogant… ? how come…? conservative, maybe, reliability-fundamendalist, sure… but… “arrogant” …?

Don-t understand… don’t know enough of Distro History…. can someone please explain…?

BRGDS

Alex

Read more…

[info] Virtual Box “nmi_watchdog” error

Error:

After compiling the 2.6.32 kernel, I was unable to load virtualbox modules as it complained of nmi_watchdog being active. Even after passing the “nmi_watchdog=0” in kernel parameters, the problem was active. recently I came accross this bug http://www.virtualbox.org/ticket/4529

Cause:

Apparently they renamed CONFIG_PERF_COUNTERS to CONFIG_PERF_EVENTS in 2.6.32. Hence vbox couldn’t detect it.

The changes will be applied and fixed in a future release. However, if you are getting this error and would like to fix it, you can use these patches.

Fix:

http://www.virtualbox.org/changeset/25365

http://www.virtualbox.org/changeset/25366

You have to patch the file /usr/src/vboxdrv/linux/SUPDrv-linux.c

However, this file didn’t exist in that specified location for me. So I guess it depends on your distro. Best would be to use:


sudo updatedb
locate SUPDrv-linux.c

And find out the exact location, for me in Slackware64 ~ 13.0 it was this file: /opt/VirtualBox/src/vboxdrv/linux/SUPDrv-linux.c

Instead of manually making the changes you can simply download the raw text file and replace the older one with this one: http://www.virtualbox.org/svn/vbox/trunk/src/VBox/HostDrivers/Support/linux/SUPDrv-linux.c

Hope this helps someone.

EDIT: Alternate Fix:

As Bruce Hill [a fellow LQ member] told me that he wasn’t getting these errors I was confused,then when I posted about this CONFIG_PERF_EVENTS change, he said he had the option built in as a compatibility placeholder. Both the options are present and you can enable them and re-compile your kenel. This way even if an app uses a deprecated name, you won’t get affected. Lesson learnt. Thanks again Bruce.

Regards

Pimp my Slack!

I am a KDE fan. Besides the eye-candy, I love the KDE apps. They are much better at functionality than their Gnome counterparts, e.g-> Brasero in Gnome has caused a lot of burn failures, whereas K3b is just perfect. Gnome just gets in your way of doing things. Anyway, this article is about what I did with my default Slackware install to make it more beautiful. Before I proceed let me tell you, I will be using Slackware 13.0 with vbatts KDE4.3.1 packages, but that shouldn’t be a problem for you if you are using any other KDE version!

What changes are we going to make?

Read more…

Improving Slackware boot time

Slackware by default takes a long time to boot. We can minimize this. I am going to write down exactly what I did, you read that and do it on your own.

First login as root using “su” and continue:

# nano /etc/lilo.conf

Write compact in the global section or uncomment it. [it’s there somewhere at the top]

Next find the append line and add “quiet” at the end. My append line reads:

append=” vt.default_utf8=0 quiet”

Using the”printk” statements during boot, a lot of time is consumed hence the “quiet” option.

Now that it’s done run :

# lilo

Read more…

[example] Compiling 2.6.32 kernel in Slackware 64

Please Note: You should atleast read Eric Hameleers’ Guide once if you are new to kernel compiling. I always refer this guide to people who just started kernel compiling since it’s very well-written and explained in details. Here is the link.

This is my second kernel compile guide [actually more like a report of my experience]. A few things I did differently than last time, so instead of updating the previous guide I thought of creating a new one. So, here goes.

Read more…