b0rken laptop

Well, anyone who knows me knows how much I hate the POS gateway laptop I've had for the past year and half. This is a laptop that managed to break down literally the day after the warranty expired. Now the screen has a huge crack in it. Anyone who was with me at Red Hat orientation last summer will know exactly what I mean. (Think of the Macbook)

In order to convince people they should never buy a gateway product if they can help it, let me air some of my grievances

  • The screen was never very bright, and hard to read in direct daylight.

  • Partially due to a bug in gnome-power-manager that was simply not aware of this 'feature', the backlight could be turned off completely when given the wrong brightness setting. Having the screen 'dim' would cause the monitor to flicker annoyingly.

  • The screen would react to pressure and ripple.

  • The power connector was fragile and towards the end of its life, (and by that i mean a whole third), the connection was incredibly shaky, proving to be a real PITA to stay connected. This would cause the screen to dim, and I refer you to my previous grievance, as the flickering would make it hard to do work.

  • The battery life, advertised as a 6 cell battery that would last me a good 3 hours doing casual work would last no more than 1 hour and 40 minutes on a light load. Doing coding related work brought power lifetime down to a measly 1 hour.

  • I'm not sure if 58C is a healthy temperature for a Core 2 Duo chip at moderate load.

  • Linux friendliness was non-existent. Certain things in the bios, like on screen displays for brightness, suspend, hardware reinitialization were a joke. At least the kernel was smart enough to work around and ignore these buggy features.

  • Because of the acid in my sweat, the case picked up some rather unattractive stains that would have made resale nearly impossible.


In Gateway's favour, I have a friend who bought the tablet, the C-140, and for her needs, the laptop works like a dream. Granted she isn't running Linux, but none of these hardware issues have cropped up for her. Furthermore, the big selling point is the quality of the sound system when it comes to spatialisation of sound. When the musical artist takes the time to post process their music, certain sounds can be processed to sound like they are coming from around you. To achieve this effect, it requires a certain level of fidelity from the speakers, which both Gateway laptops excelled at.

Bottom line is this. Between my router being crazy, and suffering the hiccups it has been for the past few months, and my laptop being super crazy and suffering the hiccups, belches, farts, and other expressions of sorrow, it's really discouraging to have to sit down at my computer and work. I want to point out that the same condition also applies to software in some degree. While many people reading this blog enjoy tinkering with hardware and solving problems, many people, especially non developers and engineers often times have a job to do. Creating a system that suffers such subtle problems only angers customers and users alike. It's bad for branding and quality, and it only serves to reinforce customers who hate all products with a certain name. I can safely say that both OpenWRT and Gateway, for what they may be worth are on my disencourage by all means list.

Penn Pilsner

Why, oh why, oh sweet tasty Penn Pilsner beer do you have to taste like a lager? My experiences with beer in this state has been excellence, despite Dan Onorato's plan to stop it through a 10% tax on alcohol. Quite a few of the beer's I've picked up here have been excellent, rivaling some of the beers I've had in Germany and the Netherlands. After having a Penn Weizen, which wasn't the best weizen I've ever had, but certainly had a very authentic weizen beer flavour, I was expective an authentic Bavarian style pilsner when I opened that bottle of Penn Pilsner.

What does a Bavarian 'Pils' entail? you might ask. A Pils tends to be spicy, with a clear sharp hops flavour. Some pilsners have a slight smell of skunkweed, owing to its near relative strain of marijuana for a cousin. It is a flavour meant to be sipped through a narrow thing class with a slightly tapered opening, that leaves you feeling perhaps a bit refreshed afterwards. An Edel-Pils is a variety that is aged a bit more, and has a yeastier flavour. This is my favourite lager beer.

(Some american brewers actually brew some interesting beers that are cleverly designed to taste and smell like all sorts of strains of marijuana. I highly recommend Trögenator's Nugget Nectar for this reason alone. The taste is uncanny.)

So when I poured myself myself that Penn Pilsner, The last thing I expected was something smelling and tasting like a very good pretzel. This is the hallmark of a great "Helles" beer. It is your standard bread and butter lager with a strong grain flavour that almost makes you feel like you're drinking a pretzel. It's golden colour makes you want to frolic through a field with some blond bavarian Mädel while a big oompah band plays in the background.

I'm not complaining, the beer was great. I just think someone misprinted the label.

Sorry to disappoint.

I'm sorry to disappoint all you folks with those tantalizing screenshots of Smolt reporting SELinux data. I want to clear up some of the misunderstandings involved in understanding how Smolt will work in the future. When the user installs the latest version of Smolt, a cron job is set up to run at some random time in the month. In the best case scenario we have even distribution over every minute of the first 28 days of the month. In the middle case scenario, we will have even distribution for each of the first 28 days of the month. If you are running a lab with 10,000 machines that you only turn on once a month, I ask that you please hand modify Smolt not to crash our servers. We're banking on you not actually existing.

This means, that from the day the new version of Smolt hits all the repos, it will take anywhere between 28 to 31 days for all the data to be considered 'current', assuming they all upgrade that day. I hesitate to use that term, because there will still be a number of machines that are considered 'stale' and they'll have null data for SELinux as well. In other words, ignore all percentages. The only information that you will have the actual number counts.

I apologize that I haven't had the time to fix all the ugly reporting issues we've had. Man hours aren't cheap.
So a thousand words times a thousand is a quintillion?
The future is worth a thousand words, especially when it's a picture full of words.

Smolt and Filesystems

Mike and I are planning on doing a release of Smolt soon, and I'm trying to get some of the latest features in. I've spoken about two others before, anonymous public URLs and SELinux reporting. I would like to formally announce two more things.

First of all, both the client and server will not be backwards compatible with older servers and clients. I've decided that because of the apparent privacy issues with the UUID, it would not be sane to support them. Therefore, the first feature is that there is now less code in both components.

Second of all, a file system engineer asked for some detailed reporting about file systems. I'm still refining what information is filtered out, but we will now store the following information about client machines:

  • A list of all the file systems in use, and sizes
  • The information that would be available from stat -f for each file system
  • A mapping of mount points to file systems only when the mount point is already in the file system package in Fedora (or an equivalent list provided by the distro maintainer or administrator.)
Understandably a /boot partition would not be used in the same way a /home partition would be used. We'll have full documentation of exactly what would be provided by the Smolt client to the Smoon server. There will be filtering controls available through the configuration file, so you don't have to report all those Linux machines that are secretly running on ZFS if you don't want to.

Oops

Apparently when I 'bricked' my router, I did no more than install buggy firmware. How so many things worked together to convince me I bricked an otherwise excellent piece of hardware is a fairly long story. I got the router last summer, and put Open-WRT and X-WRT's web interface on it. For never having used a Linux router before, it was amazing. Over the next few months I learned the truth about Open-WRT's firmware and all its nasty bugs. Chances are, things were misconfigured. Even so, I would have problems where the router had to be rebooted manually about once every 5 days. Over those 5 days, performance would degrade so much that I couldn't even SSH into the router anymore. Rebooting fixed that, although I never did figure out what caused it. I was too busy.

I switched the firmware over from the 'stable' but aging WhiteRussian over to the new and supposedly improved Kamikaze. I assumed it would have more up to date versions of the tools I was using, as WhiteRussian was out of date. I also did a bit of tinkering with the layout of my network as well. That last bit is the important part. WhiteRussian and other WRT54 specific distributions save their configuration information in the NVRAM, so it can be saved when reflashing. Kamikaze took a more general approach, and would only import settings from NVRAM. Instead, it would save everything to a flat file format. So my router still held all the old settings from before I switched over.

When push came to shove, I was having problems configuring the firewall to forward connections to different servers in Kamikaze. Again, I might have been missing some crucial detail, but the WebIF interface is incomplete, and madifying text files did not do the trick. I began shopping around, and came across Tomato, a modification of the original Linksys firmware with a very snazzy interface. I decided to give it a try. When I installed it, however, my computer failed to get an IP address from DHCP. When I gave it its old IP as a static IP, that didn't work either. I assumed the worst.

Thanks to a few pointers, I figured out how to get into the emergency TFTP mode, and reflash the firmware. Realizing that a) I successfully reflashed the firmware, without needing any JTAG madness, and b) the problems continued with Tomato, I figured maybe the router was good, and something inside Tomato was broken. On a whim, I tired the older IP address that it used from the WhiteRussian era. Suprisingly it worked, so well that I could get to the snazzy web interface. There I found out that Tomato started with DHCP Disabled!

I cannot stress how bad that is for a piece of wireless software that prides itself on its interface to be lacking DHCP. It boggles my mind that someone forgot to enable the technology that lets you plug things in and go. Even more surprising is the level of quality in everything else in Tomato. The web interface manages to present pretty much every standard use feature one would expect from a router, plus everything possible directly with the WRT54. There are so many settings there that I never knew existed, and certainly never would have found in OpenWRT. For example, apparently, you can increase the transmission power of the wireless antenna up to 25 times the default. I am now able to get a wireless signal in my sun room on the other side of my house. With a bit of overclocking and extra powerful cooling, I'm sure I could make the connection reach all the way across the street to my neighbors. I think I might just have to blog sometime about some of the other fun things exposed by Tomato.

So what went wrong? Lack of community standards in configuration settings for WRT54 firmwares. Pure negligence or stupidity on one person's part, and just an overall panicked nature from yours truly. Thanks a lot to everyone who had something helpful to say, and the 15 or so internet sites I pieced together everything from.