Place of Stuff

Long time fans of this space will be aware that I’m a Slacker.  However, when something wasn’t working as easily as it could, I installed Kubuntu to see what the latest version (Hardy Heron) was like and whether it could tempt me to switch permanently.

Firstly, even though all Linux distros are pretty identical at heart (largely the same commands, file structures and so on) there are a number of differences that can make one set of users argue incessantly with another set.  Firstly, Slackware is now the oldest distro still in use - Slackware first began in 1993, followed by Debian, followed by Red Hat.  You will notice that I have left off Suse, that’s because it started life using a Slackware base and then used a Red Hat base.  So in terms of “pure” distros, Slackware was first, followed closely by Debian, followed closely by Red Hat.  In fact, almost all Linux distros use one of those three as their base, as shown on the graphical timeline.  And to wind this paragraph up, Kubuntu is the KDE variant of Ubuntu, which is based on Debian.  There may be a large number of available distributions out there, but there are very few distros to base them off.

In terms of approach and use, Kubuntu and Slackware are very different.  The Slackware methodology is that almost everything should be done by hand: installing programs, configuring programs and so on.  Kubuntu focuses on ease of use: installation of programs is via the Adept Package Manager and using the apt command.  There are also wizards and you know when updates are available by the icon in your system tray.  It is also notable that Slackware come with plain vanilla KDE whereas Kubuntu has a very attractive configuration of KDE installed.
Continue reading ‘Slackware vs Kubuntu: A Subjective Review’ »

As any reader of this blog will know, I am a big fan of installing from source. My OS of choice, Slackware, makes this very easy and doesn’t break anything if you do this. I am, though, well aware that this isn’t for everyone - in fact, I break my own rule if it’s convenient.

Slackware packages end in .tgz, which can be confusing since that is also the way that normal tar balls can end. The usual way to install these is to type (as root) installpkg <packagename>.tgz and let the dialogue run. This then expands the archived install files into the correct places on your system. Removing or upgrading packages is equally as easy, simply exchange the installpkg for removepkg or upgradepkg. This method is inbuilt to Slackware and is the most basic way of installing Slackware packages. You could also use pkgtool which gives an ncurses frontend to a number of Slackware commands.

If you like automated downloads, you could use Swaret, Slapt-Get or Slackpkg, each of which will download the install files to your system and install them for you. These three methods are very much automated, though, and this can mean that things will break and you won’t immediately know why. Use them at your own risk, though I have only ever broken my system through my own stupidity.
Continue reading ‘Slackware Linux Installation Methods’ »

Just like everyone else, I like to listen to music. I have an iPod for when I’m on the train or walking and I have my music files stored in iTunes. Unfortunately, Apple have so locked down their proprietary format that you just can’t listen to your music in the native format on non Windows or Apple computers.

By converting your music to MP3 format you can extend the number of media players it will play on. As a KDE user, I like to use Amarok. I won’t go into the method I used to convert the files here, I’m unsure of the legality and I’m sure you can all use search engines by now. What I will do is to explain, with pictures and words, how I go about installing Amarok to give as full functionality as I need. Your methods may vary, but this works for me. I did something similar in the post Words and Pictures in Linux and that still works as a handy reference for me.

Firstly, I am using Slackware 12.0 with KDE 3.5.7. I will be installing practically everything from source. All of the programs I install will probably have prepackaged versions for your own distro (.rpm, .deb or whatever) and there are also likely to be Slackbuilds available. I still like to install from source so that’s what I’ll be doing.
Continue reading ‘Amarok Installation’ »

Having tried a number of different distros over the years, I always enjoy reinstalling and running Slackware. For a number of reasons, I was running Kubuntu for a while - if you need to be up and running in little time and have a fully functional and straightforward desktop, you could do a lot worse than use one of the *buntus.

However, Pat released Slackware 12.0 and I had to have it. One of the reasons that I was using Kubuntu was that 12.0 was a release candidate (meaning it was almost finished) and the pain of going from 11.0 to 12.0 via the upgrade route just seemed a bit too much like hard work.

So, what did I do? Well Drew kindly suggested a download site for the .iso (since my torrent download seemed corrupt). I tried getting just CD1 and it wouldn’t work. I even installed the USB boot disk to an old Dell 64mb USB stick I had lying around and still no go. I eventually obtained the full DVD iso file form belnet.de - it was fast, just 4 hours for a full download and the file worked. And lo, I was ready to rock and roll.
Continue reading ‘Slackware 12 in Da House’ »

Hey Slack fans! The awaited release of Slackware 12.0 is upon us. Go to the website and get it.

Read the official announcement. Download the disk(s). If you like proper .iso files and don’t want the hassle of torrenting, look here - I know I did!

Revel in the fact that you run the same OS as Team Awesome!