With the motherboard of my laptop removed and carefully assembled outside the case, I can boot the system reliably. I am experimenting with what it will take to make it reliably boot in its case, and alternatively, what kind of alternate casing it could be placed in as a desktop. One problem with the Dell Inspiron 8500, in my opinion, is that the cooling is woefully inadequate (although perhaps I just had the bad luck to get a bad fan, or perhaps Linux overrides some heat-based throttling that windows would do). It doesn't matter a lot -- while I would like morose to become a desktop, the fraternal twins are on their way (my two 17" laptops, CMU-owned and me-owned), and they'll be the main show either way. With the way the orders went, they were effectively ordered at the same time, so it's anyone's guess which system will arrive first. I have not yet named them, but am thinking of appropriate things in my naming scheme.
Firefox has seen fit to update itself. I have been impressed with Firefox's ability to keep itself current and manage its own updates, but I think there's a bit of a screw-up with the most recent update -- the new update version identifies it as 1.5, but it's really 1.5RC2, not properly 1.5. I also wonder if people using most versions of Firefox are even going to be able to use this feature -- one of the features of most packages (and it's a useful feature) is that the package has its own copy of all the files that are part of the installation on the hard drive, or at least knows how big they are, can verify that they're installed properly, etc. The self-update mechanism makes it hard to do that (at best). Both are useful, and they can't coexist without making a mess worse than either of them. What is one to do?
Recently, with two parts of my life, I've found myself dealing with obligations on me in different ways that are kind of uncomfortable. Broadly speaking, two of the obligations contradict each other, putting me on an interesting course between that I'm not entirely comfortable steering. The third is even more complex, but I don't feel conflicted, just a bit burdened. For various reasons, it would be unwise for me to discuss either with anyone. I further want to warn those of you who would attempt to guess the situations, no, I very much doubt either are what you might think.
From a book I've been reading recently:
A few days ago, I downloaded two OS ISOs to play with them. Gnoppix is a GNOME version of Knoppix. Knoppix is well-engineered, cute, and you get the feel they thought of everything. Gnoppix is not nearly as polished or useful -- it feels like a proof-of-concept rather than something people might actually use. Then again, I was trying Gnoppix 2.12beta1, so perhaps they'll improve things up to the point to being useful. It'll be hard to beat Knoppix though. The other ISO was that of an eComStation demo. It did show some of the cool things about OS/2 simply because it provided much of the base system, and the cool OS/2 things related mostly to the design of the workplace shell (which was and is still uniquely OO and cool). Unfortunately, it makes a poor advertisement for buying it, not showing much in the way of interesting applications or ways to be productive. They admittedly had a hard task ahead of them, because IBM effectively abandoned OS/2 at the time I stopped using it, and eventually most of the software vendors caught the hint. Trying to sell eComstation/OS2 today is like trying to sell the Amiga. I suppose the best use of it is to show people who claim that having an OS that's very OO is pretty much impossible. Then again, OO is no longer the buzzword it once was. It's not like OS/2 didn't have its own severe problems.
I was just very very lazy. Instead of getting up and walking 10 feet to one of my other computers that's within plain sight to wiggle the mouse to get the screen out of screensaver mode, I sshed to that system, became root, and did a chvt 1, waited for a second, and then did a chvt 7. I then killed the program I wanted over there, knowing that it didn't have anything to say because I could read the screen, and started it up where I am.
I have more to write, but it'll have to wait.