Fluxbox: How I make it feel like home

In the wars between GNOME and KDE (which now has even split between the two factions warring over KDE4 and KDE3.5), some of the other environments get lost in the shuffle and are often forgotten about.

One which I think is underappreciated is Fluxbox. Based on the original Blackbox 0.61.1 code, Fluxbox is a blindingly fast, simplistic approach to providing a graphical user environment while staying out of one’s way. Easy to use, easy on resources, and easy on the eyes, Fluxbox is an elegant choice that is often overlooked when the options are weighed between other graphical environments on Linux machines.

I started using Fluxbox when I was on some extremely quarrelsome hardware and needed something with a lot less going on than GNOME or KDE so that I could more effectively troubleshoot it. What I found out was that Fluxbox had an extremely tweakable interface… and I like things I can tweak and customize. I also discovered that it ran extremely fast on the limited hardware I had at the time, something else that KDE and GNOME didn’t have.

Intrigued, I stuck with it for a while and over time I learned a few good hacks that I thought I would share with the three or four readers I’ve acquired here.

Continue reading

Great Slackware writeup

I make no secret of my Slackware evangelism. In a recent post I told the story of how I came to Slackware, and why I still use it.

I’ve been meaning to do an in-depth writeup on Slackware, and I probably still will, and most likely it will be in pieces, because I think there’s a lot to discuss. However, someone else has done a great writeup on my favorite distro and I felt the need to share it with the four or five readers I have (thanks for the link, Joe!).

From The beginner’s guide to Slackware Linux:

“It’s not trying to win enormous desktop market share, nor is it loaded with blinking lights, hold-your-hand graphical wizards and package managers that change with every release. Slackware is about as pure a GNU/Linux system as you can get – at least, without all the arduous leg work of Linux From Scratch.”

KDE4

For those of you who may be reading this that are expecting a review, you might as well stop reading right now. This is not a review, this is a rant.

I want to like KDE4.  I really do.

But every time I’ve tried it the experience just makes me furious. The entire time I’m struggling with it, I’m thinking “THIS? THIS is what they dumped KDE3.5 in favor of? THIS?”.

I can appreciate moving to Qt4. I can understand the excitement — as someone who has worked as a developer — of developers drooling over a new set of tools and the enthusiasm of “Wow, we can do some REALLY COOL STUFF with this!!!!”. I can understand the appeal of “let’s dump the entire codeset and start from scratch, rather than just migrate KDE3.5 over to Qt4″.

But from every time I’ve played around with KDE4 with the intention of forcing myself to use it for a while to “get used to it”, I abandon it after less than two days. Why? Because it’s garbage, at least at this point.

I know, the common response is “you just don’t like it because it’s different!”. It is different, but that’s not my problem with it. I don’t like it because I can’t DO anything with it. Seriously. The KDE developers have gone off their rockers. I can appreciate the eye candy, but if you are transitioning from KDE3.5 to KDE4.2, you’ll be losing 80% of what you’re used to being able to do with your desktop environment.

And I’m not a GNOME fanboi either. I dislike GNOME, even when it’s relatively well-implemented, like in Ubuntu. It seems like with every release, the GNOME people remove more functionality from their product. I don’t like that kind of philosophy. I want options, damn it! There’s almost nothing more frustrating to me than to click on “preferences” for something and find only two options in there, and NOTHING about the relatively simple thing I want to do.

Continue reading

The story of how I found Slackware Linux, or “Once You Go Slack, You Never Go Back”

I’ve told this story to a lot of people who have asked me why I use an old-and-crusty distro like Slackware. I do have some pretty good reasons, and most of them lie in this tale.

A long, long time ago — back in 1999 or so — I had a computer that gave me nothing but trouble. It was one which I had bought from a vendor that did business with my employer then, so I got it for cheap. It was a Pentium 3 450 MHz (slot CPU, not socket!) machine with 256 Mb of RAM and a 10 GB hard drive, in a nice coffee-stain beige tower. When I bought it I also bought a Windows 98se license (and they actually shipped it with the full install media!!!!! Remember back in the days when computer vendors still did that?), and that’s what I set up on it when I got it.

Continue reading

Partitioning: A Different Perspective with Encryption and RAIDs

Introduction

Everybody’s got an opinion, and I’m no different. After reading Trent’s piece yesterday, I thought I’d add my two cents as my partitioning scheme is quite complex (though I can think of several ways to make it worse). For newbies, some of this is unlikely something to try, but you might want to read anyway to get an idea of what can be done.

For starters, I have 1GB of physical RAM, and 4GB of swap space split over two drives. I have two 120GB drives that I use for my primary system that are split into 8 partitions (and a logical ninth). Most of these partitions mirror (RAID-1) each other so that if one drive fails, the other maintains the system until I can replace it. You may note that the swaps are not mirrored, but both swaps and the md08 array are encrypted. Like Trent, I intended a dual boot with Windows, so the first partition on sda is NTFS. (Of course, I haven’t actually had a Windows OS on that partition in about two years, but it’s nice to know I have it if I find a game that won’t play nice in Wine.) Also note that /boot is a mirrored partition, which keeps the data safe, but upon bootup the boot loader (LILO/GRUB) accesses only one of the two drives (i.e., sda3, not md3).

Continue reading

How I do my partitioning in Slackware

One Linux topic on which everybody seems to have an opinion is partitioning. “What’s the best way to partition my system?” newbies ask, and if they do so in a public Linux forum frequented by experienced penguin techies, they are bound to get at least a dozen answers, many of them completely different from each other.

So what is the best way? Simple. Whichever way you find works best for you.

When I first started out with Linux, I didn’t know either, and I did a lot of reading on the subject, and as a result I created a partitioning scheme that works best for me, and that’s still more or less what I stick with.

With my recent Ubuntu installation I didn’t do any manual partitioning, mostly because for one, I wasn’t planning on dual-booting that laptop with anything else, and for another, I wanted to accept the defaults so that I could see what Ubuntu does on its own.

However, when I’m setting up a Slackware machine, I have a method that I follow.

One word of caution. If you’re setting up your partitions presumably to hold a Linux installation, write down what you’re designating what (i.e., “hda1 = Windows”, “hda5 = swap”, “hda7 = root”, et al) so that you have it to refer to when you’re installing later. Nothing quite like coming to the point in the install where it asks you “where do you want to mount your home directory?” and you don’t remember which partition you created with /home in mind.

Been there, done that.

Continue reading

Ubuntu screenshot time

Just another quick blurb. I’ve uploaded a screenshot of my laptop as it appears now that I’ve tweaked my Ubuntu installation to the way I like it.

I’m more of a KDE 3.5 kind of guy, so I rearrange GNOME to have the main stuff (panels/toolbars whathaveyou) a bit more like I’m used to, but I still like the way this looks so far.

I’m still learning where things are in Ubuntu (well, GNOME, mostly, since that’s the main thing that’s different for me here), but one thing that has struck me is how impressive the speed is. Remember, before this, I was running Slackware 12.0 on this exact same laptop, and I was using Fluxbox as my window manager — not exactly a visually heavy system.

So for me to say that Ubuntu runs pretty snappy on this laptop is saying a lot, and I’m not much of a fan of the bloat in GNOME, so I think that’s significant.

To be fair, I think what this says is how well the Canonical people have their act together at optimizing GNOME for their project. Nice job, guys. Coming from a Slackware guy, I’m here saying that I’m not only impressed with the setup process, but I’m impressed with the performance so far too.