Thin Puppy: December 2007 Archives

The Thin Puppy ran all the way through Christmas Day (mercifully, I wasn't here), but today something happened, and the power momentarily went out. I might've kicked the power cord, or something else nefarious happened, but the Maxspeed Maxterm converted thin client rebooted, and since there was no CD in the drive, I just shut it down. I'm sure it could've gone much longer than 13 days, but I have accepted that 30 days without a reboot won't be happening.

Anyway, I booted Puppy 3.00 on the $0 Laptop (I haven't done the upgrade to 3.01 on the Gateway yet).

One of the bigger changes recently in Puppy Linux has been the dropping of the lightweight Dillo browser in favor of NetSurf, which looks like a similarly lightweight browser based on Mozilla. I can't be sure of its origins, but it seems to work pretty well, is just as fast as Dillo, and -- most importantly -- seems to be currently in development. Work on Dillo has pretty much stalled, or so it appears. So I think of this as a good choice for Puppy Linux -- the lightweight browser is needed, especially for the lower-spec computers than many of us use to run Puppy.

I thought Puppy also had a text-only browser, but I don't see it in the Puppy 3.00 menu. I'd like to see Lynx or Elinks in the Puppy base. If you must have a text Web browser, Elinks is available as an easy-to-add PET package in the Puppy Package Manager. Even Dillo can be restored via a PET package.

The main browser in Puppy continues to be Seamonkey, which also functions as a mail client and HTML editor. I've always liked Seamonkey, and I continue to see it as an application that fits Puppy very well.

I have one nagging problem: One of the Web sites I work on: LA.com has way too much Flash on it for its own good, and while that may or may not be the cause, the home page crashes Seamonkey every time. I'm generally anti-Flash -- it hogs resources and should only be used when you need to show an actual video (and then only after a link is clicked), but I've accepted that today's Web designers have gone Flash-crazy.

Most of these developers also think that everybody runs browsers with Flash and that they have Flash enabled. I suppose it's true for 95 percent of users, but I don't have Flash activated on this very laptop's Debian partition. In Ubuntu, I do have it, and Puppy ships with Flash implemented in Seamonkey, but the ability to easily turn Flash on and off in Firefox would be welcomed by me. More welcome is the new Gnash open-source clone of Flash. I haven't tried it yet, but it's definitely on my to-do list.

$0 Laptop-and-Puppy update: Puppy runs so well on this Gateway Solo 1450, it should be noted. Since I got the fan under control via a cron job (long explanation of this STILL forthcoming -- I promise), Puppy 3.00 has performed very, very well. I've been running it from the live CD (all the better for impending and frequent upgrades, as well as ease in booting) and have a 1.2 GB pup_save in my Debian Etch partition. I've also had good luck with Knoppix 5.1.1 on this laptop, but not so much with Damn Small Linux, which has problems with the X configuration. And with 256 MB of RAM, Puppy is a much better fit than Knoppix.

I continue to warn against dual- and triple-booting, even as I continue to do it with this laptop (still, avoid pain and DON'T dual-boot -- I'm telling you). But I encourage the use of live CDs on computers with existing Linux (and even Windows) installs. It gives you a nice option and is not likely to screw anything up.

I haven't updated much in the past few days because I haven't used the Puppy box much in that time. I finished up my long gOS review -- and come to think of it, Puppy would be perfect for the Everex Linux PC. You could keep gOS on there but boot Puppy from the CD/DVD drive and have a super-fast system that blows the standard gOS install out of the proverbial water.

But back to the second Thin Puppy Torture Test. The box has been chugging along, no problem.

Today I had somebody ask me to grab a bunch of photos off of two SD Flash memory cards. I plugged my card reader into the remaining USB port, used the Puppy Drive Mounter to mount and open it, and then I dragged a bunch of images to the My-Documents folder, which if you've used Puppy before, is owned by root.

And in Puppy, you run as root, not in a normal user account. There have been all kinds of arguments about the wisdom of running as root -- and it's many people's main complaint about Puppy, that running as root is not safe. Damn Small Linux creates a user account when you boot the live CD, and you can go multiuser and create named accounts if you want. I believe the GrafPup spin of Puppy also allows the use of user accounts. ... And Puppy allows you to create any number of pup_save files, booting into whichever one you wish (and also encrypting and password-protecting them if you want), allowing for multiple users on the same computer (but still running as root).

I'm not really qualified to comment on the root vs. user debate, but I've never had any problems, and I understand that especially in the live CD environment, it doesn't matter as much. Again, I leave it to the experts.

But back to the photos. There were quite a few of them, and I only have a 256 MB Flash drive connected to the Thin Puppy box, so I didn't/couldn't transfer them all to Puppy's filesystem.

Still, after I transferred some and then later deleted them, my Puppy "free RAM" indicator dropped from 111 MB to 89.9 MB and stayed there. I've been told that this indicator is not a true picture of free RAM on the system, but it's curious that it drops and, at this point at least, doesn't rebound after files are deleted.

I pulled the card reader before unmounting the Flash card, and I got a warning message from Puppy. Remember to unmount your media!! The message suggested that I reboot, but since this is the Thin Puppy Torture Test II, I ignored that warning.

The system is still running fine, and I got the chance to use MtPaint and GTKSee as image viewers. MtPaint isn't really designed to look at images in a "slide show" fashion, but one good thing is that you can open an image in a directory, use ctrl-mouse wheel to shrink it so it fits in the window, and then retain that image size when viewing all the other images in the directory, opening them up as needed.

But GTKSee is better for doing a slide show. Just open the application (under Graphics), navigate to the proper directory, and start the slide show under the Tools menu (or by typing ctrl-S).

P.S. Since I didn't have enough memory in the Thin Puppy to burn a CD with all those images, I started up Puppy 2.17 (it was the first Puppy CD I found) on my Windows box, mounted the SD chip and threw everything into a directory on the Windows drive. I got the usual warnings about writing to NTFS partitions, but I ignored them. I got a warning the next time I booted into Windows, but everything was there, and everything was fine. (I burned my CD in Windows, not Puppy because I had work to do with the proprietary publishing software that I need for my "real" job).

I'll have to experiment with Puppy's CD burning applications later.

But one thing I always forget is that Puppy runs GREAT on my 3 GHz Pentium 4 Dell. I'm not used to running Linux of any kind on such a "powerful" machine. I'd love to run all my Linux distros on something so "good" (its 512 MB RAM is twice what I have on any other box).

One thing about low-spec Linux distros like Puppy. As well as they run on old, old hardware, if you can get everything configured, they really fly on "modern" PCs.

Pup_save thoughts: The pup_save in Puppy Linux has a predetermined size. Usually the largest you can make is 1.25 GB. There is a warning message that crops up (I can't remember where) that says you can make a pup_save up to 1.83 GB, but that is the largest tested configuration. I don't know if there is a limit on the size of a "save" file in Damn Small Linux or Knoppix (both of which use the same "save" technology, I think -- but don't quote me), and having a limit on how big the pup_save can be is somewhat of a limitation in Puppy. I suggest having additional storage space outside of the pup_save on which to store large files -- and large amounts of files, for that matter.

On this Thin Puppy, unless I add another Flash drive, I'm stuck with the 256 MB on the primary USB Flash drive.

Nothing much to report today, except that the monitor does go into power-saving mode when idle. It just takes awhile.

Everything is running great. I almost forgot how much I like using Seamonkey as a Web browser. I haven't yet set up the mail-client portion yet, but I do plan to.

I still think Geany is one of the best text editors out there. And despite it's lack of typographical, "smart" quotes, AbiWord is a model of how light yet powerful a word-processing application can and should be. And MtPaint continues to get the job done when it comes to preparing images for the Web (although I'd just about kill for a Linux-compatible photo editor that didn't obliterate and even allowed editing of the Photoshop-implanted IPTC info embedded in JPEG images).

Today's "free memory" in the Puppy Memory Applet: 113 MB.

As I look back on the past year's worth of Click entries, I see my adoption of Linux play out. The pace of free, open-source software development is so fast that it makes the year seem very long indeed.

The most fun I had writing these entries was during the month of the original Thin Puppy Torture Test, in which the converted Maxspeed Maxterm thin client ran on Puppy Linux (I think I was using 2.14 at the time) for a month with no hard drive -- in fact, no storage at all except the onboard RAM.

Since then, I've been able to create and access a pup_save file on an attached USB flash drive, and I thought it would be a good time for a second Thin Puppy Torture Test. This time, I burned a fresh Puppy Linux 3.01 CD, booted the thin client, and "upgraded" an existing pup_save file on the flash drive.

I've been planning to get a 2 GB or 4 GB Compact Flash module on which I can dual-boot Puppy and Damn Small Linux with frugal installs (copying the few and huge CD files over to the flash drive and making it bootable) and no spinning drives of any kind attached whatsoever, but in the interim, I'm doing this new rendition of the torture test.

One of the reasons I'm going back to a long-term Puppy test is the nagging feeling that running Puppy and/or Damn Small Linux from live CDs -- or going all-out and doing the same with Knoppix or Wolvix on a 1 GB RAM box -- is a very viable alternative to traditionally installed Linuxes for desktop computer users.

Having a recent Ubuntu Gutsy install go bad on me (twice!) didn't exactly endear me to traditional Linux installs, and from my use of all the live CDs mentioned -- all of which are designed to be used as live CDs rather than as sludgy demos of what a traditionally installed system will do much quicker -- running a live CD completely in RAM, with no spinning hard drives or whirring CD drives, is a refreshing change.

I originally wanted to do a Damn Small Linux Torture test, but I couldn't get DSL 4.0 (or any previous version; I have CDs for 3.2 and 3.3) to boot from CD without a hard drive connected.

So before I begin the torture, I'll give DSL another try with the USB flash drive connected ... but even as I close out this entry, I know that Puppy, out of the box, has more of the apps I want (AbiWord, MtPaint) even while DSL seems lighter on overall resources. (Note: since the original writing, Damn Small Linux has added MtPaint).

Final thought: The mere fact that you can run Linux in a traditional install, frugal install, as a live CD, and make it even quicker by running completely in RAM, illustrates the wonderful freedom of choice we have with a fully open and modifiable operating system.