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 help me; they've got to be out there. Another con: RHEL -- and, by extension , CentOS -- doesn't play MP3s or even Ogg audio files. I'm sure the codecs are out there, but I like the fact that most Linux distros -- whatever philosophy of freedom they espouse -- at least play an MP3. Hell -- I even can play Oggs in Windows Media Player on my XP box.

But what I did do with Lenny today was pack a bunch of software onto it. I threw all the kids' educational stuff I could find, the GIMP (I can't believe Debian doesn't ship with the GIMP), plus digiKam, which the esteemed Carla Schroder recommended to me as the best Linux image editor -- one that also deals with the IPTC caption info that I need to both preserve and edit. (Both the GIMP, as well as Krita and MtPaint not only won't edit the IPTC text embedded in a JPEG by Photoshop, they completely erase the info; NOT NICE.)

By the way, I thought about doing a frugal install of Puppy Linux, but what I did was preserve my pup_save on the Debian partition so I can continue running Puppy from CD (I'm still on 3.00; I've had no problems, so I haven't tried the 3.01 CD yet, although I do have it).

I wish Damn Small Linux would run better on the Gateway, but I'm still running DSL 4.0 on the older $15 Laptop (Compaq Armada 7770dmt). There are new releases of DSL in the 4 series and also in the 3 series. I have to say that I like both of them. I did a lot of work with DSL 3.2 and 3.3, and I'm glad the developers are keeping both going. I am disappointed, however, that the version of Firefox (it's 1.0.something) in DSL does not work with Google Docs. I was hoping to run DSL instead of Debian Etch (the main distro on the Compaq's puny 3 GB hard drive) and gain some speed in Google Docs, but it is not to be. For better or worse, it's another point in Puppy's favor -- Puppy's Seamonkey browser/e-mail/HTML-generator app can handle Google Docs. But now that both Puppy and DSL feature MtPaint, at least they're equal in terms of image editing; for me, MtPaint is the best lightweight image editor for Linux. If it edited the IPTC info, I'd be in geek heaven. Since it doesn't, I remain on geek terra firma.

And I continue to prefer Geany as a text editor over DSL's Beaver (and over Xfce's Mousepad, GNOME's Gedit, anything that comes with KDE ... should I go on?).

I'm having one problem with Puppy: One of the Web sites I work on -- LA.com -- has an obscene amount of Flash animation, and it crashes Seamonkey every time I try to access it. I thought that Firefox might make a difference, so I installed the PET package. But the site crashes Firefox, too. I don't have this problem in any other Linux distro or in Windows or Mac, so something fishy is going on. Yeah, the amount of Flash is obnoxious, but it's not my call.

This entry is way too long, and I didn't even mention my re-flirtation with PC-BSD. After I deleted Ubuntu and before I put Wolvix on the laptop, I decided to do another PC-BSD install. The install itself went fine. I still had that weird graphic blob below the cursor. And I downloaded three PBI files to update my 1.4 release (I didn't feel like burning a new CD, since's I've only got two left in my formerly 100-CD stack). One PBI took it from 1.4 to 1.4.1, the next to 1.4.1.1, and the last to 1.4.1.2. They couldn't do this in a regular software update? Anyway, I couldn't go from 1.4.1.1 to 1.4.1.2 -- it said something about only updating from 1.4.1. And BSD is different enough from Linux that the prospect of adapting my fan-quieting cron job to BSD is and will remain way beyond my capabilities.

So PC-BSD met the same fate as it did the last few times I installed it; it came down quickly. I'm enjoying Wolvix Hunter right now.

So here's where I stand this week with the $0 Laptop: Wolvix Hunter 1.1.0 and Debian Lenny on the hard drive (Wolvix with its own /home, so I can roll a new distro over it without killing out my files) and Puppy 3.00 as a live CD. But I'm thisclose to slapping Ubuntu 6.06 LTS or CentOS 5.0 in there.

Like many of you, I'm stuck between changing Linux and BSD distributions like underwear and finding something that can serve me for years without it either falling apart or me yearning for something better.

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

I'm not a programmer, but I use text editors just about every day. Especially for Web work, text editors are must-have tools for writers and editors.

And for me, a text editor needs to do a few things -- and do them well.

Here is my list:

It needs to start up quickly.

It must open ALL files, not just those with .txt suffixes.

It must have word wrap but NOT actually wrap the lines in the text file itself (i.e. wrap for display purposes only).

It must have a search/replace function.

It must have word count.

It must change upper-case to lower-case ... and lower-case to upper-case.

Not an extensive list, but many, many text editors cannot do these simple tasks. Mousepad in Xfce can't (though it is fast), Gedit in GNOME can't. Beaver in Damn Small Linux also doesn't do all of these things.

What I use in Windows: The free EditPad Lite -- a great text editor.

Mac OS X: the default GUI text editor in OS X (I think it's called TextEdit, or something like that) is pathetic. Sorry Mac people. I'd love to have someting better for when I use the Mac, which is often.

Do I use command-line editors? Yes, I do, but it's just much easier to use a GUI editor when I'm working in a GUI. Half of the time, I'm cutting and pasting type from Web pages, e-mails and the like, and it's just too hard to do with console editors. I tend to stick to Nano (Pico in the OS X console) because I just don't use vi enough to keep my skills fresh. And I don't want to get anywhere near Emacs -- I just don't have the desire or the time. Give me Nano, and I'm happy at the console.

Again, I don't program -- I just write, so my requirements for a good text editor are probably very different than the usual crowd at which text editors are named, meaning coders.

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

I'm writing this review on Google Docs in Firefox while running gOS 1.0.1, the Ubuntu-based distribution that steers users toward Web-based applications whenever possible -- mostly those under the auspices of Google -- and which powers the Everex Linux PC being sold for $199 by the truckful at Wal-Mart.

I'm getting more comfortable with Google Docs all the time, but there are times when you need a traditional text editor. Yet there is no GUI text editor to be found in the gOS distro. There is the entire OpenOffice suite and the GIMP image editor, a smattering of games, Rhythmbox for music and Xine for video, but no stand-alone mail client (you're encouraged by the iconography on the gOS desktop to use Gmail ...). Luckily there is a terminal program, which is named UXterm but looks suspiciously like plain ol' xterm, and with that you can bring up Vim or Nano, but that's pretty much it. Come to think of it, without a terminal in the GUI, and a console text editor, gOS would be in a heap of trouble, so it's good that they included one. But every gOS user's life would be a whole lot easier with a GUI text editor. Since you can add anything in the Ubuntu repositories, holes in gOS are easily filled.

But the more I used the new, green OS, the more I wondered whether the Everex (and everybody else) would be be better off with Ubuntu, Xubuntu, Debian ... or just about anything. While the Everex, with its 1.5 GHz VIA processor and 512 MB of RAM is underpowered when compared to most modern desktops, I regularly run Debian and Ubuntu -- both with GNOME -- and even Slackware with GNOME and Xfce on a machine with similar power but half the memory. And as I found out, the speed and lightness on resources that the Enlightenment window manager promises are just not there.

One thing I do like about gOS -- and this may be a feature of Ubuntu 7.10 for all I know -- is that when you're in a terminal and try to run an application you don't have installed, the terminal outputs what you do need to do to get it.

For instance, I tried to run the Joe editor:

$ joe

and I got the following:

The program 'Joe' is currently not installed. You can install it by typing:
sudo apt-get install joe
bash: joe: command not found

Whenever that message comes from, it's a very nice touch and is more than enough to get even a novice user going with apt.

But sheesh, at least give me Leafpad, Mousepad, Gedit ... whatever. Normally I would just add the editor I want, but for this evaluation of gOS, I pledged to stay with Google Docs; that's what they want you to use, so I'll use it. In the past, I've even gone as far as automatically posting a Google Docs item to one of my Blogger blogs, but that feature, in my opinion, is pretty much useless. Why not just write directly in Blogger? And since you can only auto-post from Google Docs to a single blog, the write-to-blog feature won't work for me. However, the post-to-blog feature does work with WordPress and LiveJournal blogs, plus a few others I've never heard of. That makes it more useful, but what I need is for Google Docs to act as more of a "dashboard" app for my various blogs -- I'd like to be able to publish from here to more than one blog (actually about six, and therein lies my sickness).

Update: I was all set to complain about Google Docs' browser-printing problem, but I just printed a document from Docs on my Windows PC, and what Docs did was turn my document into a great-looking PDF, which opened in Adobe Reader and was easily printed on paper. I'm not sure how seamless this integration is in Linux systems, but I plan to find out soon. Printing on actual paper seemed like the weak link in the whole Google Docs scheme, but it looks like they have that problem solved very well -- I may never use a traditional word processor again (especially if the promised offline extension of Docs is ever released).

Google Docs is a whole lot better than many people let on. I never need to insert tables or pictures into my documents. I write stuff. Stuff with words, and if I need to insert photos, I'm generally already in a blog post or on a printed page that I'm dealing with in a publishing program that is a whole lot bigger and more complicated than Google Docs. But Docs CAN insert images, tables, links and more. And it's not a bad HTML generator either. You can look at the HTML source at any time and copy/paste it into your Web content.

For the everyday writer of articles for publication, Google Docs is pretty kick-ass. When not connected to the Internet, or for those who don't want Google to see their documents, there's always the option of using OpenOffice, though I think AbiWord and Gnumeric are more in keeping with the lightness touted by gOS.

Getting back to gOS ... almost: Even though this is supposed to be about gOS, the bare-bones Linux distro relies heavily on the Firefox browser and links to various Web tools like GMail, Google Docs, Wikipedia (see, they're not all Google), Facebook, Blogger, YouTube, Google Maps and Picasa. So any review of gOS must take heavily into account the browser experience.

Since I work on four or five separate computers a day, working with docs online and using Web-based (or IMAP-delivered) e-mail is a must for me. I could add a standalone mail client to gOS as easily as I can with any Ubuntu or Debian system, but for now I won't. Even so, a user with gOS can pretty much make it do anything they could do on Ubuntu. Or they could wipe gOS from the drive and replace it ... or perhaps dual-boot.

One of the most attractive things about gOS and the Everex PC is that the combination promises full power management, making for a more green PC than most anything else out there on the desktop, so if you have the Everex PC, making gOS work the way you want it becomes a more attractive option. Hopefully Linux, as it matures even further, will include better power management for all motherboards.

More mail: I'm divided about the use of mail clients anyway. Most of the time, a Web portal is fine for me, especially if the entire session takes place in a secure connection (thanks, DSL Extreme). And I suspect that the vast majority of computer users have never heard of a mail client -- they barely know what Outlook is -- and have been accessing e-mail through the browser as long as they've had e-mail access, so gOS is going in the right direction there.

Gmail tip: To keep your Gmail session secure throughout, start out in your browser with the following:

https://mail.google.com

Note the "s" for a secure connection. You can also type https://gmail.com. Unsecure e-mail, particularly over unencrypted wireless connections, is a real problem, and it makes me reluctant to use Yahoo Mail because only the password is sent over a secure connection. The rest of your e-mail is right out there for others to intercept and use for ill.

Speaking about the greenish gOS desktop, the Enlightenment window manager isn't that bad. I think gOS could've been done just as well with Xfce -- maybe even better -- but I know that some Enlightenment developers are behind the project, and I'm always happy to see any desktop environment taken to the next level. At least it sets gOS apart from the dozen or so Xfce-based distros out there. But speedy, it's not.

One of the first things I did in gOS was add some virtual desktops; it's one of the best features that Windows doesn't offer, and I think the gOS people should ship the OS with more than a single desktop showing. I like the traditional four, so I left-clicked on the mouse and went to Desktop -- Virtual -- Configure Virtual Desktops. I could've added more than four, but I didn't. Switching between desktops is done with the usual ctrl-alt-arrow keys. You can't tell in gOS which desktop you're on, but at least they're there.

One feature I turned on in Enlightenment that I've never seen before in any other window manager (although I'm pretty sure it's there in most window managers) is the ability to switch or "flip" screens by moving the mouse pointer to the left or right edge of the screen, effectively scrolling to the next desktop. It's kind of neat. I don't know if I need it (I discovered it by accident after forgetting that I set it), but it may just be something that gOS users will grow to like. I had to turn the feature off because I kept triggering it by accident -- I like my Firefox windows to fill up the screen, and more than once I found myself on the next desktop when I didn't want to be there just yet. Ctrl-alt-arrow is good enough for me. But if you like the "flip screen" feature, you can make it look even more groovy with "animated flip."

One successful install, one less so: Both my regular test box (the VIA C3 Samuel-based Maxspeed Maxterm converted thin client) and the $0 Laptop (Gateway Solo 1450) are very Ubuntu friendly, meaning installs of Ubuntu-based distros generally go well on both. gOS installed like a champ on the thin client, but it won't install at all on the Gateway. On the latter, the live CD environment comes up fine (and the graphics are much snappier than on the Maxspeed), but when I do the install, I enter all the relevant information, and about six seconds into the actual install, the program crashes -- and that's it. Since I recently did an install of Ubuntu 7.10 on this very same laptop, it's curious, indeed, that gOS will not install. It's regretful, but at least I got gOS on one box. Hopefully the bug, whatever it is, will be squashed in future editions of gOS.

Potential problem: I'm running top in a terminal window on one of my four desktops, and it consistently shows Enlightenment using 9 percent to 12 percent of my CPU and 12 percent of my 256 MB of memory ... at idle. That's not exactly light. I'll have to go back to Ubuntu and Xubuntu and see how much CPU and memory GNOME and Xfce take up. I don't think it's this much. That said, gOS seems to be running as well as anything else, but not radically better. I'm able to switch windows in Firefox fairly quickly and do the same with my virtual desktops. Again, I'd have a better feel for how gOS compares if I could install it on my Gateway laptop.

So I decided to install the next distro I'm testing -- Wolvix Hunter 1.1.0. In case you haven't heard of Wolvix, it's a live CD based on Slackware that runs the Xfce and Fluxbox window managers. It can be used as a live CD, or put on the hard drive as a frugal install or traditional hard drive install. I opted for the traditional hard drive install.

The Wolvix installation process is excellent. I already had partitions set up, but the Wolvix installer offered to start up Gparted and make some or modify those I have. I also had the option of designating separate partitions for /home and other directories (I declined but would have configured a separate /home if I planned to use Wolvix long-term). The installer also gave me the option of booting Wolvix at the console or in a GUI (I chose the GUI), and it offered to put GRUB on the master boot record (I accepted). It also detected gOS, which allowed me to dual-boot. If whatever I install on the remaining partition messes up GRUB, I can easily reinstall it from Wolvix without having to geek out too much. (Note: Wolvix didn't do so well on GRUB, I instead used the gOS install disk to reinstall GRUB, and it recognized gOS perfectly).

I ran top in a terminal in Wolvix Hunter running Xfce, and at idle, with the Firefox window open on another screen (just like in gOS), the top running process was X at between 2 and 4.6 percent CPU and 7.6 percent memory. In short, a whole lot lighter than Enlightenment.

Maybe Wolvix isn't the best distro with which to compare gOS, but the Xfce vs. Enlightenment comparison is more than valid. Is it possible that the Everex PC could perform better with Xubuntu instead of gOS? (The answer is yes.)

Anyway, since Wolvix includes Fluxbox, I decided to go further and check top again. I opened Firefox, opened this document, switched to another window, opened a terminal and ran top. X was still the top running process and veered between 0.3 percent and 1.7 percent of CPU, and 6.1 percent of memory. Again, much better than Enlightenment in gOS.

To provide an even clearer picture of the performance of gOS and Enlightenment, I tested the load times of Firefox and OpenOffice Writer in a variety of Linux distributions and window managers. (Note: Slackware 12 doesn't include OpenOffice, and I haven't bothered to add it, so times are provided for KOffice's KWord -- which is generally quicker to load than OO). Load times were checked twice for each setup, since the second load of each of these two applications often happens much more quickly than the first.

Other variables that may have affected the times: Ubuntu 6.06 uses Firefox 1.5. All others used variants of Firefox 2.0. OpenOffice versions ranged from 2.0 in Ubuntu 6.06 to 2.3 in gOS.

The distros and window managers tested on the Maxspeed converted thin client (1 GHz VIA C3 processor, ECS eveM motherboard, 256 MB RAM) were:

gOS 1.0.1 (Enlightenment)
Ubuntu 6.0.6 LTS (GNOME)
Wolvix Hunter 1.1.0 (Xfce and Fluxbox)
Slackware 12 (KDE, Xfce and Fluxbox)
Ubuntu 7.04 (GNOME)
Xubuntu 7.04 (Xfce)
Debian 4.0 Etch (Xfce)

To sum up before the results are given, gOS was the slowest of the bunch -- even slower than Slackware under KDE -- and also slower than Ubuntu. It may be surprising, but Ubuntu with GNOME compares somewhat favorably to other distros running Xfce; you don't lose much speed by running GNOME as opposed to Xfce. Slackware and Debian with Xfce were another story; both were extremely fast when it came to loading applications. I didn't include Debian Etch with GNOME in the test because I didn't have it installed on one of the thin client's drives. But Debian compared very well to Slackware when both used the Xfce desktop environment. Curiously, Xubuntu -- Ubuntu's Xfce variant -- was slower than Debian with Xfce; in fact (as I already mentioned), Xubuntu didn't provide much of a speed advantage over regular Ubuntu.

I expected Wolvix to be the fastest, or at least as fast as Slackware. but it was buried by Slack. Not surprisingly, when Xfce was chosen for the window manager instead of KDE, Slackware was the undisputed winner, with a first-load time for Firefox of 8 seconds. That said, Ubuntu was slower, but not overly much, so if you prefer Ubuntu and GNOME to Slackware and Xfce, it's not like night and day in terms of application load time; it's more like noon and 2:30 p.m. -- a difference, but not so much as to make the slower of the two unusable.

The reason I even did this test was that from a "desktop feel" standpoint on my underpowered test box, gOS lacked the quickness of most of the other distros, including the Dapper and Feisty versions of Ubuntu.

And while Ubuntu has made some performance gains between 6.06 and 7.04, compatibility with hardware and desire for (or lack of interest in) more up-to-date apps should govern users' choice of the LTS vs. regular releases of the distro. For instance, on the converted thin client, hardware recognition is great in both versions, but on my Gateway laptop, ACPI and touchpad configuration work better in 7.10, and almost as well in 7.04. But ACPI management of the CPU fan only works with the kernel provided in 7.04.

Another aside: I saw practically no difference in application load times between Xfce and Fluxbox. So if you prefer Fluxbox, go ahead and use it, but you won't be gaining any performance over Xfce, at least in 256 MB of RAM. On the $15 Laptop (Compaq Armada 7770dmt), which only has 64 MB of RAM, I ran Debian with Fluxbox for months, and it runs just as well now that I have Xfce on it. And the superior tools included in Xfce put it ahead of Fluxbox when it comes to usability on the desktop.

The Slackware KDE vs. Slackware Xfce numbers are the most startling; using Slack with Xfce will save considerable load time on slower systems.

On "modern" PCs, however, much of this is moot. With a dual-core processor and 512 MB to 1 GB of RAM, everything loads so quickly that for desktop use, personal preference for one window manager or another holds more sway than load times, which will be acceptably short in just about any desktop environment. And for those who like all the bells and widgets of KDE, if you have enough power to enjoy them, it's probably worth it. Just Konqueror alone, with its ability to function as a Web browser, file manager, file viewer, FTP client and configuration portal, makes KDE very attractive. If only I could get X configured properly in Slackware on my Gateway Solo 1450 laptop.

Here are the test results:

gOS 1.0.1 (Enlightenment)
Firefox 2.0.0.10 1st load: 30 sec.
                 2nd load: 15 sec.
OpenOffice 2.3   1st load: 56 sec.
                 2nd load: 21 sec.  

Ubuntu 6.06 (GNOME)
Firefox 1.5.0.13 1st load: 21 sec.
                 2nd load: 10 sec.
Open Office 2.0  1st load: 44 sec.
                 2nd load: 26 sec.

Wolvix Hunter 1.1.0 (Xfce)
Firefox 2.0.0.6 1st load: 19 sec.
                2nd load: 12 sec.
OpenOffice 2.2  1st load: 37 sec.
                2nd load: 23 sec.

Wolvix Hunter 1.1.0 (Fluxbox)
Firefox 2.0.0.6 1st load: 22 sec.
                2nd load: 12 sec.
OpenOffice 2.2  1st load: 42 sec.
                2nd load: 23 sec.

Slackware 12 (KDE)
Firefox 2.0.0.8 1st load: 24 sec.
                2nd load: 14 sec.
KOffice         1st load: 19 sec.
                2nd load: 16 sec.

Slackware 12 (Xfce)
Firefox 2.0.0.8 1st load:  8 sec.
                2nd load:  8 sec.
KOffice         1st load: 15 sec.
                2nd load: 13 sec.

Slackware 12 (Fluxbox)
Firefox 2.0.0.8  1st load: 9 sec.
                 2nd load: 9 sec.
Koffice         1st load: 15 sec.
                2nd load: 13 sec.

Xubuntu 7.04 (Xfce)
Firefox 2.0.0.10 1st load: 18 sec.
                 2nd load:  9 sec.
OpenOffice 2.2   1st load: 36 sec.
                 2nd load: 22 sec.

Ubuntu 7.04 (GNOME)
Firefox 2.0.0.10 1st load: 17 sec.
                 2nd load: 10 sec.
OpenOffice 2.2   1st load: 40 sec.
                 2nd load: 18 sec.

Debian 4.0 Etch (Xfce)
Firefox 2.0.0.8  1st load: 10 sec.
                 2nd load: 10 sec.
Open Office 2.0  1st load: 17 sec.
                 2nd load: 17 sec.

As I say above the biggest thing to emerge is the speed advantage of Slackware and Debian, especially with Xfce. The relative slowness of Slackware 11-based Wolvix was puzzling. And while I didn't have OpenOffice installed in Slackware, and KOffice is pretty much a quicker program, I included its load numbers for comparison's sake. I did first and second loads of all apps because the second load is often -- but not always -- much quicker. Times for office suites were the number of seconds it took to open up a new OO Writer or KWord document.

While I didn't expect Debian to be slow, I also didn't expect it to be so comparable to Slackware. That's good news for Debian users.

But the biggest thing to come out of this test is that standard Ubuntu pretty much crushes gOS. The new, hot distro may be green in color, but it's incomplete and slow.

That said, the idea of doing most work in the browser and drawing on Web-based portals for not just e-mail and "social networking" purposes, but also document creation, photo editing and storage is becoming more attractive and viable all the time. In this realm, gOS is making a big "idea" contribution to the OS game, but in terms of sheer performance, polish and basic tools, it has a long way to go.

The average user -- even newbies -- would be better off with Ubuntu or Xubuntu on the Everex. And as these tests show, the Xfce desktop environment, in most instances, provides more bang for your MHz.

I wanted gOS to be great, but when it comes to Linux and BSD distros, greatness only comes with time and painstaking effort. After all the hype over the gOS-Everex-Wal-Mart effort -- some of it even generated by yours truly -- I didn't expect to see gOS beaten by every single established distro I threw at it. I don't usually do extensive time tests, but the sludginess of gOS drove me to it.

And while I expected Slackware and Debian to acquit themselves well, I wasn't prepared for out-of-the-box Ubuntu to best gOS. It wouldn't make as great a story -- "Wal-Mart chooses Ubuntu" -- but it would be way better for those buying the $199 box from the world's largest retailer.

Posted by Steven Rosenberg at 4:00 PM | Permalink | Comments (18)

I can't believe I didn't think of this before. When the GUI text
editor Geany wouldn't cooperate with the X setup on my Debian 4.0
laptop, I took the advice of all the users of self-described "crap
computers" at ubuntuforums.org and went for the smaller, faster Leafpad
editor. Problem solved. Many of those posting listed all the apps they
user on their low-end systems, many running Xubuntu, some Fluxbuntu but
quite a few Debian with Fluxbox, just like this laptop.

I already knew that the Ubuntu community can be a great help not just
for users of the various 'Buntu Linux distros but also Debian, Mepis,
Mint, and just about every other distribution of the operating system.
Remember, when you get down to the kernel, Linux is pretty much the
same, and a humongous, growing community with lots of newbies is bound
to be helpful.

Back to the low-spec app list. I'm already on board with Sylpheed as the
quickest GUI mail client, AbiWord as the best light word processor,
Dillo as a great GUI browser in addition to the Elinks, Lynx and W3m
text-only browsers, with Lynx my current favorite. (Note: I've been warming up to the e-mail component of Seamonkey when I use Puppy and Vector.)

One thing to remember with a true low-spec computer -- you need to plan
for both GUI (the X Window system) and CLI (command-line interface, in
this case the bash shell) environments. All CLI programs will work in a
GUI environment -- just open a terminal window (generally Xterm, but
there are more than a dozen others) and type in the program's name. But
GUI apps will not run in a console (i.e. the shell).

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

I spent the day upgrading my new Xubuntu 6.10 (Edgy) installation to Xubuntu 7.04 (Feisty), and since Xubuntu is derived from Ubuntu, far and away the most popular Linux distribution for the desktop, I expected -- and still expect -- a lot more from it.

During my nearly month-long Thin Puppy Torture Test (chronicled extensively in this blog), I managed to get quite a bit of work done with my Maxspeed Maxterm thin client (1 GHz VIA processor, 256 MB RAM, no disk drives at all), most of it related to producing this and other Daily News blogs. From extensive Web surfing to light photo editing, heavy writing and use of Movable Type for Web publishing, Puppy Linux 2.14 performed admirably, even if, along the way, I lost the ability to mount external drives and couldn't really deal with large audio files due to the lack of available memory. But for the basics, Puppy did the job, day in and day out.

With Xubuntu, I hooked up a 14.4 GB hard drive and a 32x CD-RW drive. And by the time I installed Xubuntu, I expected to get even more real work done. This time I seek to up the ante, doing work for Dailynews.com, which entails working with larger photo files (downloaded from services such as GettyImages.com and WireImage.com, although the latter offers a choice of smaller images to begin with).

And eventually, it means, installing some version of Wine (allowing use of Windows programs without the Windows OS installed), with Internet Explorer 6 running, because the Daily News Web publishing system requires IE. (And for the love of God, WHY??)

As far as text editors go, I can use just about anything. Even the anemic Mousepad editor that comes with Xubuntu would be OK, even though I prefer Geany, and even EditPad for Windows. And since Xubuntu's word processor, AbiWord is so light on resources and quick-loading, that could really serve as a text editor for my purposes.

And when it came to image editing, Xubuntu offers the GIMP, which though part of the GNOME office suite (featuring the loosely tied-together AbiWord, Gnumeric for spreadsheets and the GIMP), is a true resource hog, taking a full minute to load in Xubuntu on my 1 GHz box. For my purposes at least, I'm very familiar with the GIMP, as I've been using the Windows version for at least a year (and never having used Photoshop, had nothing to "unlearn"). So already the GIMP is a mismatch for Xubuntu, if indeed one is running it on "low-spec" hardware. I missed mtPaint from Puppy (which I just might install for Xubuntu, if I can figure it out), but I didn't miss the paint program that comes with Damn Small Linux, which doesn't do nearly what I need.

Long story short, I did work on about five photos for Dailynews.com, but the times required to save them in the GIMP really had me thinking about whether or not Xubuntu on this platform could handle this level of work. But I had to stop myself. I don't recall working with original images this big in Puppy 2.14. I mostly took images already sized for the Web and then made them even smaller. Even the GIMP in Xubuntu could make relatively quick work of that. And as far as general Web work with Firefox in Xubuntu, it went smoothly. I was even able to add the Flash plug-in for Firefox without working up a geekish sweat (translation: no command line needed, no Synaptic Package Manager, just clicking in the bar on Firefox to get the needed plug-in -- it was positively Windows-like).

When I write my full-length review of Xubuntu, I'll recount my odyssey of getting network printing working. Yes, it did take me most of the day, and yes, I'm surprised at how unintuitive Xubuntu's printer-configuration utility actually is (I gave up and used the CUPS interface), and I'm shocked that I got printing working much, much easier in both Puppy and DSL (and MepisLite ... and Slax and Knoppix and even standard Ubuntu Dapper). But that's another battle to recount on another day.

Suffice it to say that my first full day with Xubuntu Feisty was maybe a bit less bumpy than expected, especially given the high expectations I have for something that's billed as a speedier version of the hottest desktop Linux distribution on the planet -- however dubious such a distinction may be.

But in my search for answers on whether or not Xubuntu and its Xfce desktop interface is truly ready for real work (or at least for what it is that I do to put out Web pages and newspapers), I'm going to have to compare it to Zenwalk 4.4.1, which features the same interface but is built upon Slackware, as opposed to Ubuntu/Xubuntu's base of Debian. And I'll have to do a traditional hard-drive install of Puppy to see how it performs in that kind of traditional install (and whether that kind of setup allows me to deal with the kinds of large files that I do, in fact, have to process during the course of my day).

And last ... and only least if you think of it that way ... I will do a standard Windows 2000 install on the 1 GHz thin client (because I've got a 2000 disc and not one with XP on it) ... load it up with the requisite open-source apps (Open Office, AbiWord, the GIMP, Avast antivirus, Firefox, even SeaMonkey) to have a truly well-played field on the same hardware before drawing any definite conclusions in the battle for OS supremacy on my low-spec desktop. And honestly, as I work on this entry at home on an iBook G4 1 GHz/384MB laptop with OS X 10.3.9, and seeing how well it runs, I can't leave Apple and its BSD-derived operating system out of the equation.

Posted by Steven Rosenberg at 9:02 PM | Permalink | Comments (18)

Given how similar Puppy 2.14 was to 2.13, I was wholly unprepared for how different the latest Puppy release, 2.15CE (community edition), is from its predecessors.

First of all, it looks completely different. That's because IceWM is the default window manager for Puppy 2.15, although the old standby JWM (Joe's Window Manager) is still available. And aside from the radical change in GUI, the desktop background is darker (and less "puppy" themed) than in distros past. Still, the Menu key on the bottom left does have a paw print.

Under Settings-Themes in the main Puppy menu (accessible, as always, by right-clicking anywhere on the screen), you can alter the look of your desktop very easily.

Under IceWM, Puppy remains lightning-fast -- it sure was on my Dell 3 GHz Optiplex GX520 with 512 MB RAM.

All my configuration information from the previous Puppy version was picked up from my pup_save.2fs file when I booted 2.15 for the first time, so my networking, screen resolution and printing were already set up.

When I brought up a Web page, the fonts in the SeaMonkey browser looked "funny," or at least different. The change was due to SeaMonkey being configured to use a serif font instead of the usual sans-serif. Pages looked strange to me, but everything is displaying normally enough. It's nothing that can't be fixed, though, because it's easy to change to sans-serif under the SeaMonkey Edit menu (go to Preferences, then Appearance, then Fonts, then pick sans-serif for whatever seems appropriate. I did just that, and everything then looked like it was "supposed to."

Despite the SeaMonkey change, other apps in the new Puppy, like AbiWord, look terrific with the new window manager. The fonts appear crisper, and as I said, it's just as quick in IceWM as in JWM.

But here's the big "secret" in Puppy 2.15: Restart with JWM (from the Shutdown manager) and you are back in the old Puppy window manager -- and when you do, it looks like you have about TWICE AS MANY APPS in the menus. Open Office, yep. Scribus, yes; the Gimp, Blender ... but none of these apps actually run until you download the proper packages (I haven't gotten to that yet). I assume that they will be accessible from both window managers at that point. (Note: these apps are characteristic of the GrafPup package.)

The Puppy Software Installer (a new utility) is where these packages seem to be, and it looks easy to use. The PETget package manager is still there, and it appears to duplicate the work of the PSI, albeit with fewer apps. I think the PETget packages are more "official," while the PSI contains the old "dotpup" applications. I've heard about apps availabe as .SFS "squash files," especially the ones that crop up in the JWM menus so that's something else I'll have to look into.

When you first load the SeaMonkey Web browser, it tells you all about 2.15CE's downloadable Expansion Packs -- just click on what you want (from Open Office to the GIMP, Opera, Audacity, even KDE, and follow the instructions (or at least that's what I'm led to believe).

Also new -- and on the Seamonkey home page -- are "online applications" -- things you can do via the browser for word processing, presentation, spreadsheets, image editing, office suite, chess and more. I plan to check these out, sinc I have a great insterest in apps delivered over the Web.

There is also 3DCC (under System) to "install drm-modules to enable accelleration for your kernel," Open GL for 3d apps, and the Nvidia drivers for those who have monitors that require them.

The many configuration Wizards under the Setup menu are one of the best parts of Puppy. They make setting up a system easier than any other Linux distribution I've tried. A new Wizard -- the Defaults Wizard -- enables you to see the "default" program that will run for 15 separate tasks, from Web browsing to word processing, drawing, spreadsheet, contacts and more. And it makes it easy to change those apps. For instance, if you want your "write" icon on the desktop to load AbiWord, that's the default, but if you have installed Ted or even Open Office Write, you can make those the go-to app when you click that "write" icon. A great tool.

For some reason, the "free ram" counter did not show up in JWM, as it does in previous Puppies. But it's there in the default IceWM desktop environment.

Another new thing in Puppy 2.15: When you're in ROX-Filer, photo-file icons now feature minature images (like in Windows XP) -- a very welcome addition.

The Shutdown menu from 2.13/2.14 is missing in the IceWM version of Puppy 2.15. In the new GUI, i can quit X from the menu (or ctrl-alt-backspace from the keyboard), go down to a shell prompt and then poweroff or reboot (text instructions are on the screen), but I miss the elegance of directly rebooting and shutting down from the GUI. I know itn's not Unix-geeky enolug, but I like the way it worked before.

Luckily when running JWM, the old Shutdown menu is right there. It all boils down to what you're used to -- and I'm the kind of peroson who doesn't like to change things unless there's a good reason ... call me conservative, but hey, I'm running Linux, not Windows 2000 or XP, so I've got a little daredevil in me, right?

Curiously -- at the prompt, xwin or startx will start IceWM. Some systems will only start a window manager with startx, and it's nice to see Puppy allow for both commands.

Flash video still works great -- Puppy being one of the select distros to provide Macromedia Flash right out of the box. Sure, it's not open source, but Macromedia Flash has pretty much crushed Java and all the other streaming-video technologies in its YouTube-propelled wake. At least it's better than Windows Media, right? (YES, right.)

At one point, I tried the "Change window manager" command in the menu, but instead of going from JWM to IceWM, I got a blank screen. Ctrl-alt-backspace wouldn't kill X at this point, but ctrl-alt-del did shut it down. I didn't do a whole lot of "change window manager" type stuff in 2.13 and 2.14, being a big JWM fan, so this could've been a problem in previous Puppies -- I'll have to look into it further.

Another thing that seemed to change in Puppy 2.15CE is the location of my SATA hard drive in the directory tree. In previous versions, it used to be under /mnt, but in 2.15 it is under /initrd/mnt and is called dev_save instead of sda1. It also was auto-mounted -- something that didn't happen in previous Puppies, in which you have to mount drives you're not booting from. It's an interesting change. Some people don't like drives to be auto-mounted, but I'm on the fence with this one. Still, Puppy's Mounting Utility Tool (a.k.a. MUT) remains easy to use if you want to check and change the status of other drives in your system.

And despite the different look, all the apps I've grown accustomed to using in Puppy are there: the AbiWord word processor, the Geany text editor, the SeaMonkey browser/e-mail/html editor suite, the light Dillo browser, the Gaim instant-messaging program, the ROX-Filer and the mtPaint image editor.

My overall impression of Puppy 2.15CE is a good one. But I wish all the packages I see on the JWM menus were included on the CD, along with clear instructions on how to either install or enable them. And from a quick perusal, it appears that adding the packages while using Puppy 2.15 as a live CD is one thing, but adding them to a hard-disk install is another. If it hasn't been worked out already, I expect it will at some time soon. In Puppy, problems tend to get solved quickly, and the online community at the Puppy Forums is second to none in its ability to help users.

Still, I'm not prepared to give up Puppy 2.14, which I've been running for 22 days straight now on the Thin Puppy (a Maxspeed Maxterm 1 GHz thin client with 256 MB RAM and, since it died, no Compact Flash storage, nor a hard drive or CD drive). I'm used to it. And that's the beauty of Puppy and other distros that are designed primarily to be used as live CDs. You can have a stack of them, with the option of booting any version that works for you -- for your hardware and the work you're trying to do.

The Puppy developers have been issuing new versions at a very quick pace. Looking at Distrowatch, between Sept. 14, 2006 (Puppy 2.10) and April 6, 2007 (Puppy 2.15), there have been six Puppy releases in under eight months -- quite a pace.

One of the neatest features of Puppy is the pup_save.2fs file. When you are running from the live CD, you have the option of creating such a file when you shut down the system. I think it's limited to 512 MB in size, but contained in that file are your downloaded applications and files. And when running from CD, you can keep the pup_save.2fs file on a USB flash drive. Or it can live on your system's main hard drive, even if you're not using that drive as a boot device. As for me, I like to keep a separate pup_save file on each box I run Puppy on. That way I have the settings unique to that computing environment saved.

As far as files go, I prefer to keep them on a USB flash drive so I can take them wherever I need them -- and since Puppy plays well with both NTFS and FAT file systems, I generally format the drives as FAT so they can be read on a Windows system (and so I can work in any environment). The other advantage of keeping files on an external drive is that Puppy's own file system, after booting, is contained entirely in RAM. That's great for speed, but when you download anything large (like giant audio or video files), it all eats away at your free RAM and can really affect the system. But if you store your files on any other drive, be it flash or traditional hard disk, your memory stays fairly intact (except for things such as browser cache) and the whole computing experience under Puppy goes much better.

And if you do run Puppy with a traditional hard-drive install, it's probably a good idea to either partition your drive and save your files on the partition, or use an external flash drive to keep those files portable. That's because even when booting from hard disk, Puppy still keeps its file system in RAM. Again, it's fast, but you run the risk of losing some of your work if you put the available RAM under too much stress. It's not as much of a problem on machines with 512 MB or even 1 GB of RAM, but with 256 MB it's essential, with 128 MB mandatory.

That said, if you've got some free memory left, saving standard text and image files (which is what I do generally) doesn't even dent the free memory, and it's OK to keep those in the RAM-based file system -- Puppy even has a "My Documents" folder to make Windows types feel better. It's probably a good idea, since in Puppy you're always logged on as root, and there are no "user" files characteristic of a "normal" Linux system. There's a bit of a debate about this on the Puppy forums, but those who program the system generally have a reason for it, and if I knew more about it, I'd delve further. As it is, I'm content to use the system as is.

And while many people do install Puppy to their hard drives, the majority probably run it from live CD with a pup_save file on the hard drive or an external USB flash drive. That's probably the best-case use of Puppy. Your file system is easily backed up (just copy the pup_save.2fs file to another drive). And one of the benefits of Puppy running its file system in RAM is that writes to your flash media are kept to an absolute minimum, extending the life of your flash memory indefinitely.

But remember, if you want to download a 600 MB ISO file, you're gonna have to put it on another drive or partition, or you'll soon be in memory trouble. As long as you keep this in mind, Puppy is ultra-stable and is just so plain usable and fun, it remains my go-to distro.

Posted by Steven Rosenberg at 4:08 PM | Permalink | Comments (16)

Here's a plug for Geany, the primary text editor in Puppy Linux.

I've been using Geany for a few weeks now, and it's really a nice piece of software. For one thing, it's not foreign to someone who primarily uses full-fledged word processors -- and Windows ones, at that.

I'm not using Geany to write code. I use it to get stuff written fast -- and all the things I want to do, including changing stuff to upper case, to lower case, get word counts, it does it with ease. And there are plenty of keyboard shortcuts to make this and other stuff happen.

Geany uses the GTK+ toolkit, meaning you don't need KDE or GNOME to use it. There are even versions for Mac OS and Windows, if you want to keep things consistent across platforms.

On Windows, I've been partial to EditPad, but with Geany, I don't miss it.

Posted by Steven Rosenberg at 4:58 PM | Permalink | Comments (0)