I'm starting with the sensorsd.conf and sensorsd man pages. And this page from Calomel.org has some tips on what /etc/sensorsd.conf does, how to start the sensorsd daemon.

I'm not holding my breath, but if I could run OpenBSD (or FreeBSD or NetBSD) on my Gateway Solo 1450 laptop with the fan properly managed, I'd love to be dual-booting it with Debian.

Debian Lenny note: While many bugs seemingly got fixed in the Epiphany Web browser in Lenny, one new bug unfortunately has crept in.

Whenever you start the Epiphany browser, the check box to "work offline" is automatically checked. And the result is that you get versions of Web pages that you looked at the last time you were working "online." It's like a freaky time machine. Right now, you have to go under the file menu and uncheck the "work offiline" box to get Epiphany to pull up real live Web pages. I did see a bug report for this, sort of, but it doesn't seem current, and it seems to say that the problem is with the network manager (gconf??) rather than with Epiphany itself. This Ubuntu report is exactly what is happening. Whatever's causing the problem, I hope it gets resolved soon; I'm partial to Epiphany when using GNOME, but I've switched over to Iceweasel (aka Firefox) just to be rid of this bug.

Posted by Steven Rosenberg at 5:00 AM | Permalink | Comments (0)

I've heard of quite a few people still running Debian Sarge -- the stable version of Debian before Etch went stable in April 2007. As per Debian policy, support for what is referred to as "old stable," in this case Sarge, is slated to last for a year after the next Debian release is declared "stable" (Etch).

So now we're bumping up on March 31, 2008, and Debian is telling users about the end of updates for Sarge:

One year after the release of Debian GNU/Linux 4.0 alias 'etch' and nearly three years after the release of Debian GNU/Linux 3.1 alias 'sarge' the security support for the old distribution (3.1 alias 'sarge') is coming to an end next month. The Debian project is proud to be able to support its old distribution for such a long time and even for one year after a new version has been released.

The Debian project released Debian GNU/Linux 4.0 alias 'etch' on the 8th of April 2007. Users and Distributors have been given a one-year timeframe to upgrade their old installations to the current stable release. Hence, the security support for the old release of 3.1 is going to end in March 2008 as previously announced.

I've heard incredible stories about people running servers with Sarge and having incredible uptimes stretching into full years and beyond. And I'm as loathe to upgrade something that "just works" as much as the next lazy guy, so I understand. Three years seems like a long time ... and if you want more than three years, there's always Red Hat/CentOS/Scientific Linux and Novell's Suse (really just Red Hat Enterprise Linux clones CentOS and Scientific Linux, because what kind of cheap person like myself is going to pay year after year for updates?).

But going three years without needing to do a reinstall is a pretty great thing. And if you start with a Debian release before it goes stable -- like Debian Lenny, which is still in Testing but appears pretty darn reliable to me -- you'll probably get more than three years. At this point, I imagine that most Debian users think of Etch -- the current Stable -- as too old. That's true for desktop users, but if your hardware likes Etch, I really see no reason to move to Lenny unless you want newer versions of all of the packages.

For me, Lenny is working pretty well on the $0 Laptop (Gateway Solo 1450), and Etch is doing great on the $15 Laptop (Compaq Armada 7770dmt). And this desktop/server I just set up? I used Etch just because I know it works. And I know that getting Lenny to perform well on the Gateway means I'll be able to stick with it for what could be four years (but actually might be less because the wait between Etch and Lenny becoming stable is probably going to be much shorter than the wait between Sarge and Etch ... or at least that's what I think is going to happen).

Yeah, I probably won't be running Lenny three years from now ... but you never know. As I said recently, Lenny is looking very, very good.

Posted by Steven Rosenberg at 5:00 AM | Permalink | Comments (2)

Quick notes because I've got time for no more:

Debian Lenny: I hadn't updated Debian Lenny in about a week. Bugs are getting fixed all over the place. The latest wave of upgrades includes a couple of fixes for the Epiphany browser, which as a result is running better than ever. Most of what I noticed was cosmetic, but it just adds to the excellent functionality that Lenny already offers users. If you've been worried about running Lenny instead of Etch, I think the time is right to move to Lenny as it makes its way from Testing to Stable.

Preload in Debian: After reading about preload in Linux Journal, I finally installed it. Preload is supposed to monitor what apps you use most and automatically load them into memory, adjusting if your application habits change. Since I tend to run the same apps a lot, and since I have plenty of memory, I'm anxious to see how well preload works.

FreeBSD and the need for speed: FreeBSD 7 is now beginning its life as a stable OS. It's supposed to be up 15 percent faster than the fastest Linux kernels, up to 350 percent faster than FreeBSD 6x under normal loads, and up to 1,500 percent faster under heavy loads. I'm anxious to see how the hardware recognition performs. So far, I've had quite a bit of luck with DesktopBSD 1.6, which is based on FreeBSD 6, and I can only hope for better things with FreeBSD 7, which I plan to test soon.

OpenBSD update: I've been having a lot of fun -- and learning quite a bit -- with OpenBSD. I have the box on the local network, and I've been playing around with the ftp server, Apache Web server and with SSH. First I installed the PuTTY ssh client on my Windows XP box so I could connect from the XP box to the OpenBSD box. I could run any console program I wanted, and while it may not be a huge deal to the more experienced of you out there, it's a huge deal for me.

I wanted to run X over SSH, so I made the appropriate changes in OpenBSD to allow X11 forwarding over SSH. Ahd with the help of my friends over at LXer, I found out about Xming, an X client for Windows.

It took me awhile to figure out that I had to enable X in PuTTY to make it work. Xming runs in the background on the Windows box, and when I open an X program from the PuTTY console:

$ rox &

... A window opens on my XP desktop with the OpenBSD X program in it (which, in the case of the line above, is the Rox-filer). Pretty slick. (The & after the app name makes the process run in the background. I had one snag: I couldn't run the Dillo browser over SSH until I installed all the X fonts for Xming. There's a way to just use Xming to enable the SSH session, but that hasn't worked for me thus far. But since the PuTTY/Xming combination is working, that's what I'm going with.

I'd like to run a full X session with a full window manager running in a window on my XP box, but besides being slower than running single apps, I get the feeling that such a thing isn't exactly looked upon lovingly by the hard-core Unix geeks out there.

But being able to run any OpenBSD (or Linux) app on a network-connected box from a Windows-only PC is so totally cool that I should be sated in my dose of geekdom for the next week at least.

The $0 Laptop and its CPU fan discontents: I've been working with controlling my Gateway Solo 1450's CPU fan for months now. In Linux, I've had it controlled pretty well with a cron job, and in the case of Puppy a few added kernel modules.

But since then, I've come to realize that the cron job, which checked the CPU temperature every five minutes and turned the fan on or off depending on that temperature, is unnecessary.

All you need to do is turn the fan off at boot, and then ACPI will manage it just fine. This revelation comes after considerable work in the console, checking the temperature, running commands, running scripts and generally seeing what happens during the course of a computing session.

So I turned off my cron jobs, and now all I need to do is add the following line to /etc/rc.local:

echo 3 > /proc/acpi/fan/FAN0/state

That turns the fan off. I initially thought that only this line -- echo 0 > /proc/acpi/fan/FAN0/state -- would turn the CPU fan back on, but that is most definitely not the case. Once the fan is turned off with the "echo 3" command (which you can run from the console, just as you can the "echo 0" line), when the CPU gets warm, the fan turns on and then turns off when the CPU cools down.

So that one line added to /etc/rc.local is enough to get ACPI management of the fan working, at least in the Gateway Solo 1450.

Now there's the matter of OpenBSD, FreeBSD and NetBSD and this same CPU fan. So far nothing has worked, but I will keep trying.

Posted by Steven Rosenberg at 5:50 PM | Permalink | Comments (1)

I just read that Debian is removing Flash from its repository:

Flashplugin-nonfree has been removed (see below), as this is closed source and we don't get security support for it. For security reasons, we recommend to immediately remove any version of flashplugin-nonfree and any remaining files of the Adobe Flash Player. Tested updates will be made available via backports.org.

Since adding Flash from the repository never seemed to work for me in Debian -- I always have to get it through the browser dialogs -- it's kind of a moot point. I haven't yet investigated Gnash -- the free, open-source Flash clone -- but I'd sure like to do so. Flash is a resource hog, and I wish it would go away, but that's probably not going to happen. I just hope that Gnash or some other open-source alternative can replace it -- and quickly.

Back to Debian: The Flash news is part of Debian's main announcement that there's a new netinstall image for Etch:

The Debian project is pleased to announce the third update of its stable distribution Debian GNU/Linux 4.0 (codename etch). This update mainly adds corrections for security problems to the stable release, along with a few adjustment to serious problems.

Please note that this update does not constitute a new version of Debian GNU/Linux 4.0 but only updates some of the packages included. There is no need to throw away 4.0 CDs or DVDs but only to update against ftp.debian.org after an installation, in order to incorporate those late changes.

Those who frequently install updates from security.debian.org won't have to update many packages and most updates from security.debian.org are included in this update.

So you don't really need it, unless you don't already have it, in which case you need it.

I've been running Debian Lenny (testing) on the $0 Laptop (Gateway Solo 1450), and it's making significant progress -- it works way better than it did a month ago. I'm dual-booting with PCLinuxOS 2007 at the moment.

The older, weaker $15 Laptop (Compaq Armada 7770dmt) is still running Debian Etch (Stable), with the Xfce build's software, but now set to use Fluxbox as the window manager.

I can't decide whether or not to install Etch again on the Gateway just to see if any other bugs were fixed. For me, Lenny has resolved most of my issues, and I'll be happy to stick with it as it goes Stable.

And while I'm considering building an experimental server with OpenBSD, I might make it easy on myself and use Debian Etch instead.

My advice: If you're worried that either Debian or Slackware is too hard to figure out, don't be so worried. The not-so-hidden secret out there is that Ubuntu isn't that much easier. If you've got Ubuntu figured out even a little, you can handle Debian (and it's a bit faster, with more in the default install, besides). Slackware, you can probably figure out with a little hand-holding. Adding software and doing updates isn't as easy as in Debian/Ubuntu, but it's still fairly easy -- and you'll definitely learn something; actually quite a few somethings.

The flexibility of Debian is legendary. With one little netinstall CD, you can roll out a GNOME, KDE or Xfce desktop, a minimal console-only system (from which you can build what you want), plus any number of server configurations.

Slackware is also very flexible, but in a different way. It can't compete with Debian's 20,000+ packages, but there's a lot in the full Slack install. A full KDE desktop (with Xfce and Fluxbox, too). And if you want to spend a lot of time on the install process, you can pick and choose each individual package before committing to the final install.

Both put a lot of power in the hands of the user. And you do want power, don't you?

Flash update: Sander Marechal provided this very illuminating bug report (in this LXer thread) about the discussion in the Debian community over whether or not (and if so, then how) to include Flash in Debian.

At this point, it looks like the flashplugin-nonfree will be available to Debian users via Backports.org.

In the bug report, Ramond Wan says:

As a Debian user, but someone who isn't related to how Debian is run...I think you are correct and more importantly, what makes you think that Debian isn't political? Every time I visit a web site with Iceweasel and the server pops up an annoying message saying that Firefox is supported but not my browser, I sense only a part of the overall politics in Debian. In this case, I blame the server developers, too, for having such a message (how about if I used lynx?).

Anyway, there is a lot of politics within Debian and it stems from them
drawing a line that forms the basis of what Debian is (i.e., "free").
If they start making exceptions, then that line has no meaning.
Backports is a patch that helps make it easy for many of us. We give up
some things to be able to use Debian (rather than one of the many other
Linux distributions).

Carlo Wood says:

I'm sorry, but it doesn't seem to make much sense to let the debian users of stable and testing suffer like this. It's not like Adobe is going to be like "Oh My God!" and change their ways. They clearly don't give a damn.

I can't help but sense a political reason not to
support flash, just because it's "non-free", the
maintainers of debian WANT it to be broken, almost,
and certainly don't look hard for a way to give
their users an easy way to use flash. Just as long
as the result is that the users blame Adobe, and
not debian, it's ok - regardless of how much the
users suffer because of it.

And Timo Jyrinki says:

YouTube already works with Gnash the free Flash player, so that in particular should not be a problem. Many other sites are not yet working, but Gnash could be possibly defined as working "well enough" in time for the Lenny. At least I'm using it exclusively anyway, and I'm just using the 0.8.1 version, which lacks development for the last four months. But I don't find it problematic to skip sites that don't work with Gnash, so I'm not an average user.

In summary, Gnash works rather well for Flash 7 sites, but quite a large
portion of sites has moved to Flash 8 and 9 which are only a
work-in-progress with regards to Gnash, and most do not work properly.
Time will tell how fast Gnash will progress.

And here's what I say: I'm ambivalent about Flash. Some sites -- yes, even some that I personally help maintain -- use way too much Flash. You can barely navigate a site when you have two to four Flash apps running on a given page. The people who are all hot to use this much Flash obviously don't spend much, if any time using their own sites.

As far as video goes, Flash just seems easier than the alternatives. I know that QuickTime, for instance, runs like an old, three-legged dog on non-Apple hardware. It's just a lousy app.

So as far as video goes, I'd love to see some alternatives to Flash, especially open-source alternatives.

But as I say above, it may be a security issue, but on Debian I've always just gotten the Flash plugin straight from Mozilla through the browser itself.

Posted by Steven Rosenberg at 5:00 AM | Permalink | Comments (5)

What version of Linux has been at the top of the Distrowatch rankings for months now that I've never tried until today? PCLinuxOS.

Everybody I know who has runs PCLinuxOS has good things to say about it. Scott Ruecker of LXer and the Los Angeles Daily News' own City Hall reporter Rick Orlov are among those who have used and liked it.

I couldn't boot the CD on my test machine (VIA C3-based converted thin client), but on the $0 Laptop (Gateway Solo 1450) it's booting just fine.

To start with the live CD, I selected the "copy2ram" option because I have 1 GB to play with on this machine. It takes quite a while to copy the system files to RAM, but once that's done, the system should run very fast.

The 2007 version of PCLinuxOS has received continual updates and is a sort of rolling release -- the coders behind it don't create new ISO images on a continual basis like we get from Ubuntu, for instance. Once you install PCLinuxOS, it's easy to bring it up to day. Actually, I prefer it this way. I'd rather do a bunch of updates than continually burn new CDs.

Continue reading "Review: PCLinuxOS 2007, GNOME and MiniMe" »

Posted by Steven Rosenberg at 12:00 PM | Permalink | Comments (13)

I've taken a few days off from OpenBSD, and in the interim I ran the NetBSD live CD for the first time on the Gateway Solo 1450 (the $0 Laptop). Again, it looks great, but I'm so far from figuring out how to manage the CPU fan in any of the BSDs that I'm not optimistic about running any of them on this laptop. I wish it were different, but until the heavens open and the path forward is made much more clear, I'll stick to desktops (and my old 1999-era Compaq Armada pre-ACPI laptop) for BSD.

During that time, I booted into Debian Lenny on the Gateway and installed 141 updates. Debian Lenny is moving along very quickly. I'm ready to put an Etch install alongside it for comparison's sake during the wait for Ubuntu 8.04 ... which is two months at this writing.

The best text editor for the job: The other day, I needed to do some work at home, and I wasn't having a great time with the Gedit text editor in Lenny. I somehow thought that Gedit had a way to change the case of words, but the Lenny version (Gedit 2.20.4) didn't seem to have it. Was I imagining it, or did the Gedit in Ubuntu 7.10 have this feature? (See below for the answer.)

Anyhow, I need a better editor ... so I went into Synaptic and installed three: Geany, Bluefish and Scite. I'm going to try them all out. So far I can't seem to change the case of letters automatically in Bluefish, but there are so many features that can help with Web development that it's probably worth using. But for the level of work I'm doing, I'm relying on Geany the most at the moment. I haven't used Scite much, but I do plan to give it a try soon.

But ... GEdit does have the ability to change the case of words/letters. Under Edit -- Preferences -- Plugins, there's a Change Case plugin. I enabled it, and now I can change case via the menu with Edit -- Change Case. I prefer to use the keyboard to do this ... so I'll probably keep the other editors in contention.

Foresight Linux: The Foresight Linux booth at SCALE 6X was fairly busy. I could barely get near it during the show, and since I didn't really put 2 and 2 together and remember that Foresight is dedicated to presenting the latest in the GNOME desktop environment, I didn't linger. But I do want to give Foresight a try. It has separate install and live images, so I downloaded the live CD image and am m going to see what it's like.

I'll be your server: I've never set up a server, and all this work with OpenBSD makes me want to roll one myself. I'm going to try to do one on the local network with NFS, Samba, FTP and Apache. I'll probably try in OpenBSD and Debian as well as Damn Small Linux.

Two excellent Linux books: Since I'm not made of money, I got both of these from the library. The "Linux Administration Handbook, " by by Evi Nemeth, Garth Snyder, Trent R. Hein and an army of more recent contributiors, is a hefty tome that's long on advice, Unix/Linux history and what people like to call "best practices."

While much of the book is flying right over my head, and I don't think you could really administer a system without a secondary reference that's specific to the Linux distribution you're using, this is a very valuable book that every serious Linux user should have. Especially when it comes to servers, there's a lot of information here.

"Linux Administration Handbook" is heavy on the philosophy of how to set up and maintain a system, and amid a sea of distro-specific how-tos that expire with every six-month release, that's a good thing to have. Still, what books like "Linux Administration Handbook" make evident is that at one level, most Linux systems are more alike than they are different, and the skills you develop using one distribution are very much transferable to the others. However, there are pointers everywhere in the book to specific instructions for Red Hat/Fedora, Debian/Ubuntu and Suse.

And if you want to see how professional sysadmins (or at least the good ones) go about their work, this is the book to get. It can't be the only book on your Linux shelf, but "Linux Administration Handbook" pairs very well with a doorstop-sized distro-specific how-to (like the "Unleashed" series of books, or Mark Sobell's "Practical" guide series) to help you get a handle on making Linux work for you.

The other book I got from the library, "Linux Administrator Street Smarts: A Real-World Guide to Linux Certification Skills," by Roderick W. Smith, is a great book for anyone who wants to figure out how Linux works from the command line. The book doesn't assume a vast knowledge of Linux or Unix. It offers many tips, instructions, and again, "best practices" on how to configure and manage a Linux system. This book is also not distro-specific; instead, it's one of the best command-line-centered books I've seen when it comes to basic system administration.

I don't know how good "Linux Administrator Street Smarts: A Real-World Guide to Linux Certification Skills," in helping you get actual "certification skills," but it will definitely help with the basics of setting up and maintaining a server or desktop.

Smith's style is clear and concise -- a rarity in these kind of books, which often leave me more confused than not. I definitely recommend taking a look at this "Street Smarts" volume.

So I had two winners here. I would probably buy both of these books, but that said, I still turn to Carla Schroder's "Linux Cookbook," which I'd love to see updated, and Michael Stutz's same-name-but-different "Linux Cookbook," which could use an update even more.

If I was in a buying mood, I'd get a more recent O'Reilly book, "Linux System Administration," by Tom Adelstein and Bill Lubanovic, and I really like Chris Negus' new "Toolbox" series of distro-specific books. They're fairly cheap and filled with good, timely tips, emphasis on the "timely" part. If only all of these great books were updated every couple of years instead of five years ... or never.

Click frequency: The "publish every day at 5 a.m." thing hasn't been working out so well of late. I just haven't had all that much time to do entries in advance, but I have had an entry every day ... just not prewritten to publish at 5 a.m.

One man's FreeBSD: I admire this guy, William Denton, for chronicling eight years of personal use of FreeBSD.

Debian ... ah, Debian: In case it's not evident, I still really enjoy using Debian. While I'm a great believer in the slimmed-down application mix in the default install of Ubuntu (which is based on Debian) -- with less indeed being more, on many levels I've had a whole lot more success with Debian.

I've done the default GNOME install of Debian, the Xfce and KDE installs, a "standard" install to which I've added X, and a few "standard" installs that were console-only. The flexibility of Debian is legendary, as is its stability and usability.

Some of my hardware has been supported better by Ubuntu at times, but I keep coming back to Debian. I'd love for Debian Lenny to support the Alps touchpad as well as Ubuntu Gutsy does. I'm hoping it'll happen before Lenny is frozen, and I will be trying Ubuntu Hardy when it comes out, but I'd love for Linux in general to get everything right for my Gateway laptop.

But since fan management has gotten worse, not better, over the past six months in the Linux kernels I've used, I'm only cautiously optimistic.

Posted by Steven Rosenberg at 4:20 PM | Permalink | Comments (1)

After not succeeding in getting the Airlink 101 AWLL3028 USB wireless adapter working in Debian Lenny and Wolvix Hunter 1.1.0, my first thought was to install Ubuntu 6.06 LTS on the $0 Laptop (Gateway Solo 1450), since I had a trouble-free ndiswrapper experience on my test box in Ubuntu 6.06, but since there's no WiFi in this building, I can't really see if it works, short of hauling the converted Maxspeed Maxterm thin client home ... with all the drives haphazardly connected to it. No, not going to do that.

I'm disappointed that I couldn't get the wireless adapter working in Wolvix. I could see the network with iwconfig, but I just couldn't get DHCP running properly.

So I went back to my Linux roots: Puppy.

I've been running Puppy 3.00 on this laptop for awhile -- I have the CPU fan managed by a cron job (Gcrontab is a bitch ... I'd rather have regular crontab anyday ... and I wish the Puppy people would fix it so crontab works with the e3 console editor ... it's hard-wired somehow to vi, which isn't part of Puppy).

So I hooked up the Airlink adapter, fired up Puppy, used the network setup wizard ... navigated to the "more" part of searching for networking drivers, selected ndiswrapper, navigated to the part of the drive on which I have a copy of the Windows 98 driver for the Airlink ... and the thing lights up.

It's the clearest, easiest configuration with ndiswrapper I've tried so far. Let's see if it works. (I'm not above trying Ubuntu, and I'll probably do that at some point).

Now all I have to do is get the laptop somewhere there's a live WiFi connection to see whether or not I can actually get wireless networking flowing.

Posted by Steven Rosenberg at 4:15 PM | Permalink | Comments (2)

I've complained numerous times in the past about the Ted word processor being broken in Debian. On my many Debian installs, I could neither create a new file in Ted nor open an old one.

But on my Gateway Solo 1450 (the $0 Laptop), after doing my big Debian Lenny update yesterday -- which fixed an annoying Nautilus bug by updating to Nautilus 2.20 -- I decided to give Ted another try.

It works.

I can create new files in Ted and open old ones. I tried Ted again on my Compaq Armada 7700dmt (the $15 Laptop), now a Debian Etch machine (with Xfce and, since last night, Fluxbox) that could really benefit from Ted working. No go.

I figured that it was maybe a Lenny-only thing -- some other dependent package got updated and magically made Ted work. Here's Ted's bug status in Debian. I remember trying this "transcoded fonts" solution and having it not work.

So this morning, on my desktop Debian Lenny install, I tried Ted again, and it didn't work. I even installed the transcoded fonts. Nothing.

Yes, I have three Debian installs (two Lenny, one Etch), and Ted works on one (Lenny) of them. That's better than Ted working on none ... but.

I'm wondering if I should even be running Debian on this 233 MHz Pentium II MMX, 64 MB RAM, 3 GB hard-drive laptop. The Compaq performs OK with Puppy Linux and a bit better with Damn Small Linux. And while on my faster, 1.2 GHz laptop I detect almost no difference in response time between Xfce and Fluxbox, on the 233 MHz box, Fluxbox is much snappier, so I take back my previous assertion that Fluxbox doesn't give you much of a performance edge. When you're running really old hardware, Fluxbox can really help.

The problem: I want to have a "full" command-line system in addition to X, and that's harder to do in Puppy or DSL. And I like the fact that Debian and Slackware stay on top of security issues and frequently issue patched packages. And Debian (or Slackware, for that matter) makes it relatively easy to install any console app I want. However, I put a lot of stock in doing as little modification as possible; in my experience, things can get mucked up pretty quickly. And while both Puppy and DSL offer command-line features, neither is a full, modern, updated Debian or Slackware.

And just to provide a little background, Debian, Slackware, Puppy and Damn Small installed just fine on this old Compaq. I can't say the same for Xubuntu, which I did try.

And while I'm mentioning Xubuntu and Debian with Xfce in the same post, let me just say that of the two, Xubuntu is way more ready for prime time. Debian's default Xfce install is missing too many things; I stick by my assertion that Debian is great with the default GNOME, less so in the Xfce and KDE installs that you can do with the Xfce and KDE Debian disks (or desktop= boot parameter in the netinstaller).

Back to the Compaq. Both Puppy and DSL are way better at recognizing and configuring the hardware of this old Compaq laptop. At this point, I'm considering running both Puppy and DSL as live CDs with no OS on the puny hard drive, which would only be used for swap and storage (I could even replace the spinning hard drive with a Compact Flash chip or disk-on-module).

I hate to give up running Debian or Slackware on this laptop -- I've tried both. But when I try to build up the apps on my own, I can never do as well as Puppy and Damn Small Linux -- both of which I've used extensively over the past year and which I value very highly. The people behind Puppy and DSL really know what they're doing.

And while I'm grateful to get Ted running on my Lenny laptop (where I don't really need it), can't Debian just make Ted work everywhere, all the time? Like I've said before, there's probably a good reason that Ubuntu doesn't have Ted in its repository, and I'd say the package not working is a pretty good reason.

I haven't even complained about Ted not showing up where it should in the menus and my not being able to figure out how to put Ted where I want it in GNOME (yes, I used alacarte (here's the Debian bug situation), and no, it didn't let me add menu items (another Lenny bug, perhaps?) -- it almost makes me want to run straight toward Xfce and Fluxbox ... or Ubuntu).

Moral: Debian giveth and taketh away, but it remains damn good.

Posted by Steven Rosenberg at 6:00 PM | Permalink | Comments (0)

I half-expected today's massive Debian Lenny update to solve my Nautilus-crashes-when-I-try-to-get-the-properties-of-a-file bug. It did not, but I'm not disappointed. I went back to the original bug report, which was filed with GNOME, not Debian, but is clearly a Debian-only bug.

I saw the "solution," but didn't understand it until now. I still don't know how to actually "do" the solution, and for now I'm content to let it ride and see if Debian Testing catches up.

Briefly, users have learned that upgrading from the version of Nautilus in Lenny (2.18) to the version in unstable /Sid (2.20) fixes the problem. So all you have to do, theoretically, is switch over to the Sid repositories, reinstall Nautilus, and the bug is gone.

I don't think the package list is "frozen" for Lenny, so it's entirely possible that the Debian people don't think Nautilus 2.20 is ready yet for the Testing distribution. Perhaps there are other problems, or the app has not been checked out. Whatever the reason, and I do hope there is one, I'm eagerly awaiting Lenny to upgrade Nautilus on its own.

I would go back to Debian Etch (stable), but I like the look of the newer GNOME so much that I am reluctant to do so. And the prospect of running Lenny now, while it's still Testing, and continuing to run the same install as it becomes Stable, is an enticing one.

But ... the new Ubuntu LTS is only about three months away, and I just might want to give it an extensive try. The question: Do I replace Wolvix Hunter or Debian Lenny? I might want to run Wolvix as a live CD, freeing up its spot on the hard drive.

Posted by Steven Rosenberg at 3:30 PM | Permalink | Comments (8)

It couldn't be more than two weeks -- and probably a bit less -- since I booted Debian Lenny (the "testing" distribution) on the $0 Laptop (Gateway Solo 1450). And 100 updates await me. Everything from Fluxbox (I didn't remember that I even had Fluxbox installed) to dpkg to a bunch of GNOME packages (maybe they'll fix my Nautilus bug ... if they do, I'll write a glowing paean to all things Debian, my faith in the world will be restored, and flowers will erupt from every corner of my garden).

Posted by Steven Rosenberg at 2:45 PM | Permalink | Comments (0)

Ubuntu 6.06 LTS -- the distribution's first "long term support" release -- now has a new installer that incorporates some 600 bug and security fixes and makes installation easier, especially on servers.

It's no secret that Canonical, the company that runs Ubuntu, is making a big play both for the desktop and more-lucrative server markets, and a big part of that play is the LTS release. And even though the next Ubuntu release -- 8.04 (due 4/08 ... also known as April 2008) -- is going to be a Long Term Support release, with fixes, patches and the like for three years on the desktop, five years on the server, there's still quite a bit of time left for the current Ubuntu LTS, which will be supported until June 2009 on the desktop and June 2011 on the server.

The new installer -- you don't really need it if you can successfully use the old installer, already have a 6.06 LTS install (like I do) and have done all the updates -- underscores Canonical's commitment to the LTS concept. While the twice-yearly releases of Ubuntu get most of the light and heat in the uber-geek community, there are many who depend on the relative stability of the LTS release to keep their hardware running. That's especially true on servers, where major upgrades every six months are impractical at best and detrimential at worst -- nobody wants to break a system that's been running well.

And the LTS is vital as a counterweight to Red Hat Enterprise Linux and SUSE Linux Enterprise Server/Desktop, both of which are supported for years on end.

I'd like to say that Debian Stable (currently Etch) and Old Stable (Sarge) are equivalents, but since you can't pin down a date certain for length of their support, there is a bit of an unknown factor there, although once the Stable release goes to Old Stable, you pretty much know that the new Stable release won't give you too many problems.

Sure, many desktop users generally want something more cutting-edge, mainly something like the regular Ubuntu releases, but there are many people -- and many situations -- that warrant hanging on to a Linux installation as long as possible. Over the time I've used Ubuntu and Xubuntu (from 6.06 LTS through 6.10, 7.04 and 7.10), I've seen some parts of the installation improve dramatically, I've seen hardware work better, then worse, and occasionally not at all.

And we all know an individual or organization that hates doing major upgrades, ever. Those coming from a Windows or Macintosh background aren't all used to major OS upgrades. In the case of Windows AND Mac's OS X, major upgrades almost always cost money. $129 for an OS X upgrade might not sound like much, but paying that much every couple of years when your computer runs just fine the way it is? No thanks. That's why I'm still running OS X 10.3 on my Mac. And Windows? I have a disc for Windows 2000, and I'm not about to pay ANYTHING for the privilege of upgrading my sole Windows box (which I boot maybe twice a year) to XP.

And in Linux, just because we can change out distros 10 times a day if we wish, it doesn't mean that we have to -- or should. For