Glass Panes That Separate

transparent barriers to communication

Tag: linux

  • hat trick

    A couple days ago, the Fedora project released their latest effort, Fedora 11. The IT guy from the high school had been giving me a hard time about not trying harder to like Fedora. I had been hearing good things about Fedora 11, so I figured I’d give it a try. I should mention first that I’m doing this on an older laptop, so I won’t be too concerned with speed, except as it relates to performance of other linux distributions on this same laptop.

    After letting the Live CD load up (not sure why you can’t have a ‘just install it for me’ option like Ubuntu), I started the installer. I wasn’t interested in playing around with a Live CD on this old laptop. It’s just too painful, and I was getting kernel failures like mad. Once I started the installer, things were going well, it even detected the computer name from the previous Ubuntu install. Then we got to the partitioning step. This is the place where we tell the installer how we want to use our hard drive (or let it do it’s own thing).

    Being the optimist that I am, I let it do it’s own thing. It failed. The best part about this is, if the partitioner fails, it exits setup, and you have to start the installer again. That’s not quite as painful as it sounds, but still frustrating. I tried it again. Fail. Ok, I’ll do it myself. I created a swap partition, and then went to do my root partition. Hmm, no reiserfs, so I’ll stick with tried and true ext3. Fail. The install image on the CD was created from an ext4 filesystem, and somehow it’s impossible to use anything but ext4 on your root partition. Ok, whatever, I’m trying to give this a serious try, so I won’t let that stop me. Recreate the partition with ext4. Fail. You can’t boot from an ext4 formatted partition. From other reading, this is ridiculous, since Ubuntu (released a couple months ago) can boot from ext4 file systems just fine. Ok, so we’ll create a small ext2 formatted partition for /boot. Oddly enough, it recommended ext3, which is stupid, since the journal will eat up a good portion of your partition, and waste precious disk space. Some other fun things I noticed along the way. If you press the escape key while creating a partition, it actually creates the partition, instead of cancelling like it should. The arrow keys also cycle through the partition size options backwards as well. Finally, let’s do this install thingy. And it worked. One other item of note that I liked (because I’m an ntp nerd and run two of my own servers), is that it let you setup network clock synchronization during the installation process.

    After completing the install, the display resolution on my laptop was not right, so I started trying to figure out how to fix that. I found a way, and had to install system-config-display. And then I remembered why I disliked Fedora before (and Red Hat, and Suse). RPM’s are the devil. After all that fun, what I really wanted to know, was how the speed compared to Ubuntu and Xubuntu on this laptop. So naturally, I have to go back and install them too. I timed the Fedora boot time: 1 minute and 20 seconds. It’s a far cry from the 20 seconds they mention as their target for this release, but I’m on slow hardware, and 1:20 is actually pretty good. I installed Xubuntu, and remembered that it wasn’t just Fedora that had issues with my display. In Ubuntu (and thus Xubuntu), I have to create the config file that sets the refresh rate for my monitor, and then it works at the right resolution. I timed Xubuntu. Ouch. It came in at over 1 minute and 45 seconds. My Ubuntu CD was apparently busted, so I burned a new one at work the next day. I had heard rumours that Xubuntu was kind of inefficient, but this just confirmed it. It seemed a tiny bit faster on loading menus and other trivial tasks, but nothing that would convince me to stick with it. I installed Ubuntu the next day, expecting something above 2 minutes for a boot time, and was pleasantly surprised. It booted almost identical to Fedora. So, thought I, I’ll go back to Fedora and just try living with it for a while to see how I like it (other than the RPMs).

    Then the nightmare began. I had thought all the partitioning errors were behind me, but the Fedora installer was just getting started. I tried the same partitioning setup as before, and it went all the way to the end of copying the install image to the hard drive. Fail. It claimed it couldn’t load my /boot partition. I tried again, and it wouldn’t even load the partitioner. Then I got it to load if I told it I wanted a custom layout. It went all the way to the end again, and failed. After several more failures, of different types, I went to Google. It turns out that the partitioner for Anaconda (the Fedora installer) had been completely rewritten for this release. It was also completely in a broken state, and some people recommended using fdisk to partition your disks, instead of the installer. Hmm, yup, that’s going to be a great option for people that want to try out Linux. For the record, it does work, although I actually recommend cfdisk instead of fdisk.

    Anyway, it’s installed now, and the fun will ensue shortly. I’ll have another post about that in a month or so.

  • phonic

    A while back, Ubuntu released their latest update, Jaunty Jackalope. Yes, a Jackalope… Anyway, I usually wait a while to update my home computer because our internet connection is slower there (than at work). A couple nights ago, I decided the time was right, so I started the download and let it run overnight. The next day, I finished the upgrade, and rebooted. While I was at work, I got a call from my wife. We had no sound on the computer. Nothing was muted, and the speaker volume was fine. Great…

    When I got home, I started troubleshooting, trying various audio settings, and changing volume levels on pretty much everything. I finally had some success when I switched the audio engine to OSS. I’ve been using Linux long enough to know that it wasn’t the solution I wanted. OSS is an old, deprecated sound system that is only kept around because some applications haven’t been updated in ages.

    This at least gave me a starting point in my search on the Ubuntu forums, which are always super helpful. But audio issues on Linux are a dime a dozen, so it took me a while before I stumbled upon this post. I tried a couple of the things they mentioned, but nothing was working. Finally, there was mention of another post, which includes some information from one of the lead PulseAudio developers. As it turns out, the original implementation of PulseAudio by Ubuntu was very poorly done, and if you were upgrading, you still had all those broken settings lying around now that they’ve fixed things in Jaunty Jackalope. I followed the instructions for removing all the broken stuff, and tada, I had sound again. I celebrated by watching Hancock, and cranking the volume.

  • bloat

    Many of you probably already know that I use Linux. One of the awesome things about linux is choice. It was also the mantra of the first Linux distribution that hooked me on Linux–Gentoo. One of the choices that I made early on, was to use GNOME for my ‘Desktop Environment’. Of course, this begs a definition of ‘Desktop Environment’ for anyone who doesn’t use Linux.  It consists of the icons, toolbars (dock, taskbar), wallpapers, desktop, widgets, menus, etc. Perhaps the best way to explain this is by comparison. The biggest noticable difference between Windows 98 and XP (or between XP and Vista or even Mac OS) is the Desktop Environment. It’s what allows you to launch programs, and manage your files, and even determines how it all looks to some extent.

    Now, back to linux. For those of us that use Linux, we get to choose between a hundred different Desktop Environments (and that’s probably underestimated). To the less eccentric, there’s typically only two choices though: GNOME and KDE. As I said before, I’ve chose GNOME pretty early on, but I actually tried KDE first, since it was what I had used when I bought my SuSE 7.2 discs back in the day (I subsequently sold those discs on eBay, and gave up on Linux for about 2 years). KDE has always been the eye-catching option, but as I’m a bit of a minimalist, GNOME struck my fancy. It seemed easier to customize, and had a leaner feel overall.

    Every once in a blue moon I’m tempted by the allure of KDE once more, and today was one of those days. I’ve been sick, and bored, so I started installing Gentoo (I’ve used Ubuntu for the last 5 years) in a virtual machine (it’s like taking a chunk of your hard drive and making a spare computer out of it). I wasn’t going to do much more than that, but then the bug bit me. So once I had everything else working, I started preparing to install KDE on Gentoo. It was going to install 3.5.9, but I had already tried that version, and wanted to check out version 4. I found a nicely done tutorial, and wanted to see everything that would be installed. That’s when it happened. It smacked me right in the face. I almost fell over. It wanted to install MySQL. MySQL is a full-fledged database application commonly found on servers. This is a Desktop system, running Desktop applications. What could possibly require MySQL?

    It turns out that Akonadai, part of the PIM (personal information management) set of packages is the culprit. Apparently, some people have so much personal information (contacts, calendar data, email, etc.), that SQlite (the former choice) doesn’t cut it anymore. That just boggles my mind. Of course, it shouldn’t, when I’ve seen college presidents that have over twelve thousand emails (just in the Inbox), several thousand contacts, and calendars that could choke a hippo.

    In KDE’s defense, at least they don’t require you to actually setup the mysql server. However, KDE will have to be pretty slick to convince me that the extra little bit of fat is worth the switch this time. I’ve always found it to be bloated, and adding extra icing just adds more calories.