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)

Yesterday I went on about the man page for fvwm, the default X window manager in OpenBSD.

It clearly says that, in the absence of a .fvwmrc file in the user's home directory, fvwm will look in /usr/X11R6/lib/X11/fvwm/ for a file called system.fvwmrc:

During initialization, fvwm will search for a configuration file which describes key and button bindings, and a few other things. The format of these files will be described later. First, fvwm will search for a file named .fvwmrc in the user's home directory, then in ${sysconfdir} (typically /usr/X11R6/lib/X11/fvwm). Failing that, it will look for system.fvwmrc in ${sysconfdir} for system-wide defaults. If that file is not found, fvwm will be basically useless.

There's a file called system.fvwm2rc in that directory, but it doesn't control fvwm. I know this because I added a line to it, stopped X and restarted it. No change.

Since fvwm looks for the .fvwmrc file in the user's home directory, I decided to create one with the help of the system.fvwm2rc file mentioned in the man page.

I used the Geany editor, but substitute any text editor you wish (I'm just more comfortable in a GUI editor when it comes to things like copying and pasting. I don't use vi enough to be all that proficient).

Here's how to do it:

Log on with your user account, open an xterm window and do the following (again, substitute your favorite editor for geany, or install the geany package on your OpenBSD system with $ sudo pkg_add -i geany):

$ geany /usr/X11R6/lib/X11/fvwm/system.fvwm2rc

Under the File menu in Geany, choose Save As, then navigate to your home directory and save the file as .fvwmrc (in other words, create /home/~/.fvwmrc, substituting the name of your user's home file for ~)

Now you should have a .fvwmrc file in your home directory that is editable by the user account. Modifying the menus is pretty easy. I've already added a category for applications and added all the apps I've installed thus far to it.

I'd still love to find out where the systemwide fvwm configuration file really lives. I don't have enough Unix or OpenBSD knowledge to do so at this point.

I've stuck with fvwm because it's the default window manager in OpenBSD, and it's pretty nice once you learn about it. I've got a long way to go, that's for sure.

Fvwm note: Changes in your .fvwmrc aren't implemented until you quit X and restart it.

Applications I've added to my OpenBSD box thus far:

Geany (text editor)
Dillo (lightweight GUI browser)
Firefox (heavyweight GUI browser)
Nano (console text editor; I just "get it" more than vi)
MC (console file manager)
Rox (the ROX-filer GUI file manager)
Abiword (relatively lightweight word processor)
Ted (even lighter RTF-format word processor)

I haven't added a mail client, and I might add Sylpheed or Thunderbird. I might also add mutt, fetchmail and msmtp and try POP mail from the command line for one account. Generally, though, the whole console e-mail thing baffles me -- and yes, I have done it before. I generally find a GUI mail client or Web mail interface so much easier that I don't need to spend days and days fiddling with mutt.

Essential OpenBSD reading: The OpenBSD Journal. I just found out about this, although I'm sure I've been here before.

Also: OpenBSD 101.

Ted on OpenBSD: I installed the Ted word processor -- an exceedingly light application that reads and produces files in rich text format -- which can be read and edited by most word-processing applications, including Microsoft Word.

Ted on OpenBSD ... how to actually run it:

This doesn't work:

$ ted

But this does:

$ Ted

Remember, Unix-like OSes are case sensitive, and in the case of Ted, it's really capital T, small e, small d.

I've been grumbling about Ted not working in Debian for an age, but Ted works fine in OpenBSD. I'll probably use Geany for most of my work, though. I got used to Geany by using it in Puppy Linux, and while I'm not crazy about its Windows implementation, in Linux/Unix, I still really like it.

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

So I think I'm "discovering" the NetBSD live CD, but I learn that Distrowatch announced the damn thing in 2006. All I can say is that I'm very, very impressed.

It's NetBSD, it boots on my temperamental test box, and not only does it have X, it has a full KDE desktop with tons of applications -- the full KOffice, Konqueror, Firefox, Abiword, K3b, Krita, the GIMP, Inkscape, JuK, XMMS, -- hell, just say it's got a full KDE 3.5.4 setup and then some, and NetBSD autoconfigured for my monitor (with the VESA option) and looks absolutely gorgeous.

If the NetBSD people could someday, someway, make this an installable live CD, they'd really have something here. So far, this looks and works better on my computer than DesktopBSD and PC-BSD. I guess the one thing this version of NetBSD is missing when compared to DesktopBSD and PC-BSD is graphical package managment, but the rest of it looks and works so well ...

While the NetBSD live CD attempts to configure a static IP address for you (ignore this if you use DHCP), it didn't work. To configure a static IP in NetBSD at a terminal -- and it is slightly different than doing the same thing in Linux -- here's how to do it (adapted from my similar tutorial for the FreeBSD-based FreeSBIE live CD):

My Ethernet interface, usually eth0 in Linux, is called rtk0 in NetBSD. If you're unsure, run this command:

$ ifconfig -a

That should output the name of your Ethernet interface.

To set the static IP in NetBSD I either used the same terminal window or opened a terminal window (Konsole in the KDE menu works fine) and became root:

$ su
(When prompted, for a password, the root password is root. If you signed on as root, you don't have to su, since you're already root).

At the # prompt, do the following (substituting your own networking numbers, of course):

# ifconfig rtk0 192.9.200.20 netmask 255.255.255.0 broadcast 192.9.200.255

# route add default 192.9.200.254
(Note: don’t use route add default gw, like in Linux — gw is not needed. As above, enter your own router/gateway address)

I also set up my name servers in /etc/resolv.conf (I used vi because I knew it would be there. You can also use any of the other KDE text editors in the live CD environment. Use any text editor you wish in its place:

# vi /etc/resolv.conf

once in the file, I added these lines:

domain yourdomain.com
nameserver 192.9.200.4
nameserver 192.9.200.2

(as always, add your own search domain and name server IPs, then save and close the file; you should now be ready to start Firefox and begin browsing the Web. Note: my connection doesn't require use of a domain in /etc/resolv.conf)

And again, if you have a dynamic connection, ignore this completely.

Additional info: Look at this PDF, which looks like a PowerPoint presentation for some background on BSD live CDs.

Posted by Steven Rosenberg at 5:10 PM | Permalink | Comments (2)

Notepad++ is working out pretty well so far. The latest Windows text editor in my quest for a better, freer text-editing experience, Notepad++ is under the GPL license, so it's free and open-source. It's also not a port of a Linux/Unix editor like Geany, and the annoying Geany bug -- in which extra linefeeds (or carriage returns?) are inserted in Windows (CR/LF) formatted text files -- is thankfully not present in Notepad++.

In fact, Notepad++ allows you to set whether you want your text files to be in Windows (CR/LF), Unix (LF) or Mac (CR???) format. Since the files look the way I want (and cut/paste that way) in the default Windows format, I'm pretty happy. I like the way you can change the case of letters -- ctrl-U for lower-case, ctrl-shift-U for upper. I'll have to get used to it, because every other program I use does it a different way.

The search/replace function in Notepad++ is very good. It even keeps your previous search/replace words in a drop down so you can use them again in the session. I haven't yet figured out how to search for text and replace it with a carriage return/linefeed, but if I figure that one out, Notepad++ will become a must-have editor on my Windows box.

Notepad++ seems to remember the last directory I saved to, and all newly created files default to that directory. But I don't think it remembers the directory from the last time the program ran. EditPad Lite does remember, and it's a great help. I wouldn't be opposed to setting my "home" directory manually, but I'm not sure this can be done. If using the Notepad++ directory for files causes it to open to the same directory every time, that's a small sacrifice for me to make; I generally store all of my text files in one place, and it doesn't matter where that place is (though it's nice to be able to choose it in advance, though navigating to my text-file directory once per day isn't an insurmountable hardship).

Notepad++ remembers the last eight files I've opened, and they're available for reopening in the File menu. I think I can set it to remember more. For me, the more the better.

Why a text editor? I remember Jerry Pournelle, prolific science-fiction writer and long-winded columnist for Byte magazine way, way back in the day talking about the pre-IBM-PC machines he had set up for word processing in what he called (and still calls) Chaos Manor, and all the technical specs, trials and tribulations he went through. He's definitely an inspiration for this blog and its style, although I've never quite thought of it that way until now. (I used to love Byte back in the '80s.) Pournelle always talked about text editors, and at the time, I had no idea what a "text editor" was. I knew what a word processor was, but it took awhile for the concept of a text editor and what it can do to sink in.

And then came vi. Vi's great when it's the only game in town, as it was on the UC Santa Cruz timeshare Unix box I had an account on in the late '80s. Today I can fake it in vi, but I'm no master.

I still use word processors occasionally -- usually AbiWord, sometimes OpenOffice, occasionally MS Word on the Mac. But more and more -- with all the Web work I do -- text editors are quicker, more flexible, faster -- and most importantly, they give you clean ASCII output that isn't mucked up with extra crap.

End note: I Googled Jerry Pournelle to see if I was spelling his name right. I'm glad to see his Web site, which I'm going to explore at greater length at my earliest opportunity.

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

I've been changing text editors in Windows like some people change underwear -- clean people that is.

And every time I try a new one, I open a text file and choose the new application. Windows remembers what I chose the last time, and that is presented as the first choice when I open a new text file. I've gone from EdiPad Lite to Geany to Notepad++, and I appreciate Windows remembering the last text editor I've used. I get the same treatment with .doc files, which I sometimes open with OpenOffice but usually go quick-and-dirty with AbiWord.

Anyhow, it's a nice feature in Windows, this remembering the last app I used in a given category. Nice to hear me say something nice about Windows, don't you think?

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

In search of more Windows text editors, I started here, which led me to PSPad, which I will try next week. There's more info at PSPad's English-language site. I've just learned that PSPad was created by Jan Fiala of the Czech Republic.

While Notepad++ is under the GNU GPL license, I think PSPad is distributed as "freeware," with a request for donations. You don't have to pay, but I don't think you get the source code, either. I can't argue with "free."

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

Notepad++ is doing pretty well. But I have two problems: First, I don't see a function for renaming files. I prefer not to "save as" sometimes and instead change a file's name. Two, when creating a file, I had a little trouble naming it. I wanted the .txt extension to be added automatically, and for some reason my file had .txt in the name and the extension. The latter could be operator error, the former ... well, I'll have to work on it.

However, lack of a "rename" function is not a deal-breaker.

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

Since Geany in Windows can't manage to get the spacing between lines right without we selecting the LF mode (as opposed to the CR/LF mode) for every file I open, I decided to look elsewhere for my Windows text editor solution. (Note: this "setting" doesn't seem to make a difference in EditPad Lite -- things come out OK no matter which kind of line endings I choose.)

Next up: Notepad++, which unlike my former favorite EditPad Lite, is under the GNU license, meaning it's free and open-source -- a requirement for my new Windows text editor.

So far, Notepad++ is looking very good. I can open multiple files in tabs, I can wrap lines without the wrapping screwing up the file (the biggest detriment -- to me, specifically -- in Linux/Unix console editors -- is when word-wrapping inserts line-feeds everywhere they wrap; I just want to see the wrap, not have the wrap be permanent -- sorry, vi).

Confession: I opened up GVim for Windows, which I've had installed for a while. There's no way that would ever work. I'm just being realistic.

So I'll see how Notepad++ goes and report back.

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

I'm not saying I'm gonna stick with Geany in Windows, even though I've had nothing but praise for it as a Linux application. I'm not crazy about the paragraph I'm working on going from a white background to gray (and I haven't figured out how to turn this "feature" off), nor am I crazy about the cursor disappearing at times when I scroll down and it's a the far left of the screen ...

But I did figure out the solution to one of my problems:

When I copied and pasted my text from Geany into whatever Web program I'm prepping it for, I ended up with extra lines. I fixed it by going under Document -- Set Line Endings and switching from Convert and Set to CR/LF (Win) to Convert and set to LF (Unix).

(Note: Having to do this for EVERY file is a pain in the ass. Why can't I just set it and forget it?)

I also noticed that Geany -- mainly a text editor for programmers -- has a couple of features that might be useful: Under Tools -- Export, you can choose to output text as HTML or LaTex (the latter being useful for Linux/Unix typesetting but the former being useful for just about everything I do).

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

After yesterday's post on sharware vs. freeware vs. free, open-source software, I decided to install Geany on my Windows box. I've always liked Geany in Puppy Linux, and when I learned from the Geany Web site that the full-featured text editor was available for Windows, I had to try it.

To run in Windows, Geany needs the GTK 2 runtime libraries. Since I already have the GIMP image editor installed on this XP box, I already had GTK 2, so I was able to choose a version that didn't include the libraries.

I just started using Geany in Windows. I opened all the files I was working on last night in EditPad Lite, and now I'm not violating the EditPad license by using the program for "commercial" purposes.

So not only do I feel wrong about using pirated copies of commercial software, I'm not even comfortable running shareware or restricted freeware without paying. And with great FOSS alternatives like Geany, I don't have to.

As I say above, I first used Geany in Puppy Linux, where it is the default GUI text editor. And besides the Windows version, Geany is offered in source code as well as in packages for Gentoo, Fedora, Debian, Ubuntu, Suse, Slackware, Mandriva, ArchLinux, AltLinux, FreeBSD, NetBSD and Solaris.

And it looks like Geany can run in OS X (if you have the GTK libraries, I presume).

I have plenty of text editors on my Linux boxes, but I just can't work with Microsoft's Notepad. I'm no fan of Apple's text editor in OS X, either -- I'd rather open a shell and use Nano (or is it Pico that's included ... I can't remember).

I've barely begun to scratch the surface when it comes to text editors. There are dozens out there, and Wikipedia does a fairly good job of attempting to categorize and compare them.

Posted by Steven Rosenberg at 11:15 AM | Permalink | Comments (0)

Back in the BBS days, I actually did pay for a shareware program. I used a couple of related programs that allowed for the reading of and writing to QWK packets, which enabled me to download my Internet mail and USENET messages, read them offline, do my replies, new messages and the like, and assemble them for upload. I can't remember the name of the programs, but I actually paid something like $15 for their use, for which I actually received a couple of 5 1/4-inch floppies in the mail.

Now I prefer FOSS -- free, open-source software -- for everything, and in Linux it's easy to get a distribution with thousands of packages -- all free to use and modify as any of us sees fit.

But back in the worlds of Windows and OS X, there are quite a few FOSS programs, but more that are released under the old terms of "shareware" and "freeware." Not being entirely free at all. Some ask for donations, others say that for "commercial" use, you should pay X amount.

The two I use most in Windows:

IrfanView, which is free for personal use, with a donation requested for businesses. I think the amount requested is $10.

EditPadLite can be used "only for private purposes that do not generate any income and by registered not-for-profit organizations ..." There is the non-free program EditPad Pro for "profitable" usage, which costs "only $49.95."

I'll make my confession now: I use both programs for "business use," though I'm never quite sure if such use is, indeed, generating any profit (even though that is way beside the point).

As I say, even though I prefer FOSS, I'm inclined to pay the $10 toll for Irfanview. It's worth way more, seeing as I can't find even one application that can do what it does as well and as fast.

The $49.95 for EditPad Pro? That's too rich for my blood.

Sure I could get my frugal employer to pay, but as they say, I've got other fish to fry ... I should probably just find a FOSS editor that works with Windows and be on my merry-friggin-way.

I do have Gvim installed ... but that seems like too much trouble.

I like using Geany in Linux, and there's a build of that for PC. Maybe I'll give that a try.

But again, I ask: Have you ever paid for shareware?

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

I knew that Wolvix Hunter 1.1.0 had Gslapt -- the graphical front end to the get-slapt package manager for Slackware -- but for some reason I had no idea that it would be useful for updates.

But commenter Morten Juhl-Johansen Zölde-Fejér gently told me that Wolvix's get-slapt/Gslapt indeed points to a Slackware 11 mirror, as well as Wolvix's own repository.

So I opened up Gslapt, updated and upgraded. I didn't add anything, so I can't vouch for get-slapt/Gslapt's ability to satisfy dependencies, but the upgrade went perfectly, and now I've got a fully up-to-date Wolvix distribution.

Already I've said that Wolvix (and perhaps by extension Slackware 11 -- not 12) is the best-performing Slackware-derived distribution I've tried. I've had no configuration problems whatsoever. And a look in Gslapt shows me that there's a huge number of Slackware packages that I could potentially install.

But one of the great things about Wolvix Hunter is that it pretty much has everything I want. It looks great, now has the latest Firefox browser, OpenOffice, MtPaint, the GIMP, AbiWord, a ton of multimedia apps, just as many networking apps, even a bunch of text editors (I'm currently exploring what Bluefish has to offer, but there's also Mousepad, KompoZer, SciTE, medit, vi, GNU nano and JOE). Mail clients? Hunter has Claws Mail and Thunderbird in the GUI, plus mutt at the console.

And the Wolvix Control Panel is one of the best configuration GUIs I've seen.

Never mind that the current versions of Zenwalk and Vector won't run (they'll install, but they won't even give me a shell login; it's probably something having to do with a hardware hangup).

The more I use it, the more I like Wolvix.

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

Wolvix Hunter 1.1.0 image from Wolvix.org.

After dual-booting Ubuntu (at times 7.04 and 7.10) and Debian (first Etch, then Lenny, then a couple of Lennies for a couple of days) on the $0 Laptop (Gateway Solo 1450), I've said goodbye to Ubuntu for the time being and decided to install the dependable Wolvix Hunter 1.1.0 (the bigger of the two Wolvix distros) and keep Debian (still Lenny). After "losing" two Ubuntu 7.10 installs to unknown causes -- both times processes began slowing to a crawl -- I thought rolling back to Ubuntu 7.04 would give me something stable.

But the boot process for 7.04 began stalling at something having to do with the CD drive (I turned off "quiet spash" in GRUB so I could see where it was dying). I'm thinking that either my laptop or Ubuntu itself must be somehow cursed. One of the reasons I had Ubuntu installed, besides the fact that it works pretty well (when it does work) with this laptop, is that I can easily get Internet Explorer (via IEs4Linux) on the box. There's one Web site I work on that absolutely requires IE, and my need for such access could grow from minimal to critical at just about any time. That hasn't happened yet. What I'd like to see is updated instructions at IEs4Linux to get it set up on Debian. (As far as Debian goes, IEs4Linux remains stuck in the Sarge era).

But suffering through three dead Ubuntu installs in a row has made me weary. For one thing, I'm going back to separate partitions for /home. That's how I have Wolvix set up. Wolvix can be run as a live CD, a frugal install or a full install. I believe the frugal install saves files in the same way as Knoppix and Damn Small Linux, and I want to be able to access the partition when booting Debian, so I opted for the full install. I don't think Wolvix provides updates in the way Debian, Ubuntu and other "established" distros do. No matter. It runs even better on this laptop than it did on the Maxspeed Maxterm thin client (where Wolvix was tested along with another crop of distros in my gOS comparison).

And Wolvix has another thing going for it: It's a Slackware-based distro that actually installs and runs with no trouble. Slackware 12 runs ... but I just can't get the X configuration right (and just about any other Slack-based distro offers a better Xfce experience in terms of applications and tools than Slackware itself, which remains a KDE-focused distro, albeit a faster KDE distro than any other). Both Zenwalk and Vector have been problematic; I can install, but something funky happens during booting and I can't even get to a console. I suppose I could turn off ACPI, AGP, IRQs and the like ... but if Wolvix can just run, why not the others? I probably will try to put Slackware 11 on the box at some point just to see if it's Slackware 12 that's screwing me over (Wolvix is based on Slack 11).

Anyhow, besides the fact that it runs and installs seamlessly, I really like the look of Wolvix, as well as the software mix in Wolvix Hunter (which features heavier apps like Open Office and the GIMP, along with lighter ones such as MtPaint, AbiWord and Dillo). Wolvix ships with Xfce and Fluxbox as window managers. In my recent tests, I've determined that Fluxbox doesn't provide much of a speed advantage over Xfce, and since Xfce has many more features, I'm pretty much running it exclusively, even on the aged $15 Laptop (a 1999 Compaq Armada 7770dmt with a 233 MHz processor and 64 MB of RAM). And while the spread between Xfce and Fluxbox isn't as wide as one would think, Xfce does provide significant speed advantages over GNOME and KDE

The Wolvix Control Panel app is excellent. For everything from configuration to installation, Wolvix is way ahead of most of the distributions I've used. While the network-configuration portion of the control panel can be somewhat confusing (it reminds me of Zenwalk), it does work. Before I figured it out, I tried using Slackware's netconfig utility in Wolvix. It doesn't seem to work, though you can go through the paces. At least Wolvix offers a utility that does work. With a distro like the highly touted gOS offering NO network configuration utility (they think everybody has DHCP), I'm thankful for any kind of help. Yes, I can hack the text files that hold Linux's network configuration, but I'd prefer not to. It's just the way I am.

Since I'm constantly switching between a static IP at the office and dynamic IP at home, it's taking me a few extra steps (I love being able to easily switch between network settings in Debian and Ubuntu), but the trade-off is worth if since Wolvix otherwise performs so well.

And the Debian Lenny honeymoon is way, way over for me. I've considered rolling it back to Etch. My Alps touchpad issues are coming back (it's not as perfect as it is in Wolvix, Ubuntu 7.04 or 7.10), and the fact that the new Lenny kernel seemed able to manage the noisy Gateway CPU fan for a day but not thereafter is very troubling. I can continue to use the Etch kernel with Lenny, and I just might do that, but I'm left wondering what's going on and whether or not there's an easier fix.

What I did do, for both Wolvix AND Debian Lenny, was put my fan-managing cron job to work. It basically checks CPU temp every five minutes and, if it goes above 60C, turns the fan on, then turns it off when it goes below 50C. Rather than a shell script and a cron job, I'd just like a single line of code that I could stick in some config file to make this work. I've seen things similar to what I need, but I haven't yet nailed it down for the Gateway Solo 1450.

I did, however, get the fan to stop in Debian from boot (using @reboot as the time element for the entry in crontab for the first instance of the cron job, then following with */5 * * * * to run it every five minutes thereafter. Again, I will detail the Gateway Solo 1450 fan-control solution, step by step, in a future entry.

And while I think a cron job is a sloppy, hackish way to deal with a CPU fan, I've done it now in Puppy, Wolvix and Debian, so I'm pretty much getting used to it. It's notable that in Ubuntu 6.06 LTS, I couldn't get the system to allow me to turn the CPU fan on and off, even when sudoing the command. I guess I needed to write to root's crontab, and sudoing can't quite qet you there. At least that's my six-second analysis of the situation. I would've loved to put Ubuntu 6.06 LTS on the laptop -- perhaps it could stick around without self-destructing like 7.10 and 7.04. I seem to remember Ubuntu, at least in the alternate install, offering to create a root account. Maybe if I install with the alternate CD, I can get control of the fan. But do I really want to run Ubuntu 6.06 LTS?

Briefly, here is where Ubuntu is falling down:

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

yields the following:

bash: /proc/acpi/fan/FAN0/state: Permission denied

In every other distro on which I've used this line in my cron job, I need to su to root to run it (Puppy logs you on as root, so it's no problem there). But I can't seem to get it to work in Ubuntu. As it is, 6.06 LTS only has five months of support remaining still has a year and five months of support remaining (I'm no math whiz). Might as well wait until 8.04 comes out as the next LTS (or just stick with CentOS 5). ... Then again, Ubuntu 6.06 is from the Debian Sarge era. I smell another install of MepisLite 3.3 .. or maybe the recently updated -- even though I thought it was dead -- Sarge itself. I could always try to solve my Alps touchpad problems and stop my whining (if only ...).

UPDATE: I figured out how to shut the fan on and off in Ubuntu. Details tomorrow morning.

I did keep Debian Lenny (upgraded from Etch). And I know this is the testing distribution and not stable, but I was alarmed by a bug I discovered in the Nautilus file manager. When in a Nautilus window, if you right-click on a file and try to get its properties, Nautilus crashes, a bug report screen comes up, and then Nautilus relaunches. I filled out the bug report and went to the Web page for the bug. While there are about 500 reports of the same bug, it looks like the bug itself has been "closed." Well, it's not fixed, but the report is closed. It says that the bug goes away in Gnome 2.20.1. I have 2.20.2, and it hasn't gone away. I'm hoping that it will, but if the problem with the Ted word processor being catastrophically broken in both Etch and Lenny is any indication, I won't hold my breath. I guess I don't quite understand how bugs are dealt with.

As I said, I'm considering rolling it back to Etch. I'm also considering an installation of CentOS 5.0, which manages the CPU fan fine. Pros: CentOS, a copy of Red Hat Enterprise Linux, will be supporting this distro for YEARS; if it works now, it'll get security patches for a long, long time. Cons: it's harder -- at least for me -- to find as much variety in software as there is for Debian, Ubuntu, even Slackware. I'm sure there's plenty of software out there -- and there's nothing stopping me from compiling my own -- but I just couldn't get the hang of adding repositories and GPG keys. Just finding and installing AbiWord was beyond my capabilities. Perhaps a RHEL 5 book would hel