Recently in Geany Category

As an experiment, I decided to bring my Evolutionary Computing presentation on making the journey into free, open-source software — a slide show originally created in OpenOffice Impress 2.4 — into Google Docs, which happens to have a presentation app in addition to the better-known Docs and Spreadsheets components.

I revised the presentation — taking some things out, adding others and providing some updates on what I'm doing — and output it as a PDF.

Download that PDF for your reading pleasure by clicking on the image above or the link below:

Evolutionary Computing (revised July 2009)

Interesting note: I believe that no previous entry on this blog has been filed under so many categories. (And I've been considering dumping Categories entirely and just using tags ...)

/usr/local/share/xfce4/README.OpenBSD

I tried quite a few OpenBSD ports during my last run on the Sparcstation 20. None of them would build (Firefox, Seamonkey, Geany).

Curiously, when I ran NetBSD on the Sparc, the Firefox PACKAGE wouldn't install. Not a port that needed to be compiled, but a precompiled package built for the 32-bit Sparc architecture. That didn't give me a whole lot of hope for pkgsrc, which theoretically can be used to bring NetBSD packages into OpenBSD and other OSes. (DragonFlyBSD uses NetBSD packages, and that's a great way for the FreeBSD-derived DragonFly to have a huge package repository, and it makes me want to try it on my i386 hardware).

I spent the past few days installing Solaris 9 on the Sparc 20. (I got the OS super-cheap — $1 plus shipping — from eBay, unopened in the box).

Solaris is quite a bit different from OpenBSD and Linux. I'm still getting the hang of it. A lot of the trouble I'm having is due to my near-total unfamiliarity with it. I do have "The Complete Idiot's Guide to Solaris 9," which I found remaindered at Fry's for a few bucks, and it's a good resource. It's somewhat short — not "complete," but for the "complete idiot," which I am in this regard. There are quite a few other Solaris 9 books out there, including a "Dummies" book by Dave Taylor, who wrote a general Unix book I quite liked (here's everything Amazon has that he wrote).

Back to the Sparcstation 20 after the Solaris 9 installation: With 50 MHz of CPU and 128 MB of RAM, it's far from ideal. GNOME &mddash; which ships with Solaris 9 — is almost unusable, but the CDE desktop is pretty responsive. It reminds me quite a bit of Fvwm in OpenBSD.

StarOffice 6 is included among the many discs in the Solaris box. When I installed it as root, only root could run it, so I started over again in my user account. The answer to this mystery is probably somewhere in my "Complete Idiots" book.

I found a Firefox 2.0.0.20 package built for Solaris 8 at the great SunFreeware site. Again, installing as root meant only root could use it. Even after installing it through the user account with su didn't work all the way. I can still run Firefox as root, but I get errors relating to patches that I need to do when I try to run it as my user. I'll have to read up on Solaris admin and eventually find and install all the Solaris patches.

But I did get Firefox to run, and it's WAY faster than Netscape 4.7, which shipped with Solaris. Yes, I did just type the words "Netscape 4.7."

I could very well keep Solaris on the box, but one idea is to run OpenBSD and then try to use the Solaris binary packages for Firefox and OpenOffice (since none of the OpenBSD ports of Firefox or Seamonkey will install on the Sparc 20).

Running Solaris binaries in OpenBSD is supposed to work. And yes, OpenBSD is a better, faster OS, for my use anyway, than Solaris on this platform.

Sun Sparcstation 5 image from the OSIAH: Online Sun Information ArcHive.

This post began its life as a comment on the previous Sparcstation 20 entry, and true to the way I overwrite even a comment, it works well enough as a standalone entry.

And thus, here it is in that form:

I've discovered that NetBSD doesn't run so well on the Sparcstation 20 (50 MHz processor, 128 MB RAM). The install went fine, but the X configuration was less than optimal. Console messages continued to appear on the X screen, and I could tell that, among other things perhaps, the horizontal sync and/or vertical refresh might have been just a bit off. I imagine that if I take the xorg.conf information from OpenBSD and use it for NetBSD, all issues will be solved.

But when NetBSD's 32-bit Sparc packages for Firefox and Seamonkey (precompiled packages, NOT ports) wouldn't install, and then the Geany package did install but ran so slowly as to be unusable, I decided to go in a different direction.

Thus far, that direction is a reinstall of OpenBSD. I haven't tried any ports yet, but all the packages I have installed — a few GUI editors (nedit, which I quite like, and another I can't remember), plus the Dillo browser, which in all fairness ran great in NetBSD, too — did work.

Now that I'm running not the box's original, jet-plane-noisy 2 GB Seagate hard drive but a super-cheap-on-eBay 35 GB Hitachi SCSI drive that's pleasantly quiet, maybe the installation of an OpenBSD port of a "modern" Web browser will work. Maybe not. I'll also try to roll Abiword onto the box, as well as Geany (for comparison's sake, if anything else).

And there's always Solaris.

I know there are Solaris-compatible packages for just about everything, so if I can't manage to get Seamonkey or Firefox installed from OpenBSD's ports with the extra disk space, my next move will be installing Solaris 9 (I got an unopened box of the software for $1 — yep, that little, plus shipping — on eBay) and see how that OS runs on the box.

One thing: Sound on the 32-bit Sparc platform doesn't work in OpenBSD. It does in NetBSD. Of course it does in Solaris, since Sun's OS was written with the Sparc in mind.

It may be that Solaris is the best OS for desktop use on the Sparc 20. Probably the best thing to do is get a CPU module faster then the current 50 MHz processor I'm now running, and also upping the memory to the max of 512 MB (right now I have the 128 MB the box had when I got it).

But make no mistake, for sheer out-of-the-box configuration on a Sparcstation 20 (sound nothwithstanding), OpenBSD is way ahead of NetBSD.

My next line of attack is trying a few (or more) OpenBSD ports. Even if this experiment goes well, I'll have to roll Solaris 9 onto the Sparc 20 before I decide on any long-term OS for the box.

Before I finish this entry, it's worth pointing out that Debian Etch for Sparc boots but won't install. It hangs when trying to load the CD driver. I don't know if the Sparc port of Debian is broken for EVERY 32-bit Sparc model, but it sure doesn't work for the Sparcstation 20.

Image above right: This isn't my Sparc; it's a Sparcstation 5 from http://www.computermuseum.org.uk. They look exactly alike (and in many ways are).

When I first installed OpenBSD 4.4 on my Toshiba 1101-S101 laptop (Celeron 1.3 GHz), I kept the stock 256 MB of RAM.

Everything was running so well that I didn't hurry to add RAM.

But since I do have spare PC133 SODIMMs, I could've bumped it up to 512 MB, 768 MB or 1 GB.

I decided to go with 768 MB for now, which meant adding a 512 MB SODIMM.

Opening up the bottom of the Toshiba, installing the module, closing it up and booting all went fine.

And now I'm starting to look at how the system is using memory. Right now I'm running the Opera and Firefox Web browsers, the Geany text editor, the GIMP image editor and an xterm window. This is all in fvwm, OpenBSD's default window manager.

The top utility reports that I still have 289 MB of free memory, and I'm not using any swap at all.

I then opened a spreadsheet and document in OpenOffice (which happens mighty slowly, by the way). Free memory dropped to 190 MB. I realized that while I had the GIMP running, I didn't have any files opened. I cranked up one of the .jpgs I worked on earlier in the day, and free memory was now at 186 MB.

I still could pull the 256 MB module and replace it with another 512 MB SODIMM, but for now this is pretty good performance. I can imagine things going to hell if I started streaming video (on the sites that Opera's Flash plugin support), but in terms of getting work done on this laptop, OpenBSD and 768 MB of memory are doing very well.

(Yes, I do have the OpenBSD T-shirt with this design. It doesn't get more geeky.)

I'm getting ready to give the $0 Laptop (Gateway Solo 1450) to our daughter to run her educational games (Childsplay, Gcompris, TuxPaint) on Ubuntu Hardy with the non-crashing Xfce window manager instead of the crashy version of GNOME in this Ubuntu build.

To replace that machine for me, I pulled a Toshiba Satellite 1101-S101 laptop from the boneyard.

With a 1.3 GHz Celeron processor, 248 MB RAM (how it has this amount, I don't know) and a 20 GB hard drive, the specs are pretty similar to the Gateway, except for the Gateway's 1 GB of memory, which I'll probably split between the two machines.

The Toshiba came to me with Windows XP, and this time I wanted to preserve Windows and dual-boot it with a FOSS OS. The CD/DVD drive is extremely flaky. I think it's dying. It does better with "commercial" CDs, and I did get it to boot Partition Magic so I could shrink the NTFS Windows partition and set it up for Linux.

The only Linux CD I could boot was Debian's Etch and a Half. Something was squirrely on our network, and I couldn't get DNS working in the installer. I could've done a minimal install, fixed /etc/resolv.conf and then brought the rest of Debian into the box, but I took this opportunity to go in a different direction.

With all the CPU fan issue on the Gateway, I could never run OpenBSD (or NetBSD or even FreeBSD after the first boot) because I couldn't get the noisy CPU fan under control.

I powered up the Toshiba, which couldn't get networking in Windows either. Since I don't yet have the administrator password, I couldn't update the DNS settings.

I went to an OpenBSD mirror and downloaded a floppy image plus a DOS/Windows utility that helped me create a bootable OpenBSD install floppy. (Before anybody mentions this, I know I could've just as easily created a Debian boot floppy.)

The Toshiba successfully booted off the OpenBSD floppy, and I was able to plug in a mirror and do a full install over the network.

This was my first dual-boot install of OpenBSD, and after the install was done, the machine wouldn't boot at all. I hadn't installed a bootloader and thought the box would boot into Windows, where I planned to modify that bootloader to choose between Windows XP and OpenBSD. Instead I got a "no operating system" message.

And I don't have a Windows XP disc from which to "repair" the master boot record.

So I rebooted with the OpenBSD floppy, dropped down to a shell and added the OpenBSD bootloader at the prompt:

# fdisk -u wd0

Then I rebooted and was in OpenBSD. There is a GRUB package for OpenBSD, and I'll probably install that so I can easily dual-boot either Windows and OpenBSD or eventually Linux and OpenBSD. There are other alternatives as far as bootloaders go, but my familiarity with GRUB is what is governing my decision in this case.

I'm also going to add rsync as well. I have no skills when it comes to OpenBSD's dump and restore utilities, so having rsync is another plateful of Linux-like comfort food that will help me get along in OpenBSD.

Other packages I've installed thus far: nano, mc (the Midnight Commander file manager), Rox-filer (my favorite X file manager), Geany (X text editor) and the Firefox (I probably should've gotten the version with Java, but I'm going to try to add the Java developer's kit and get the Java runtime that way) and Opera Web browsers.

Opera came via a port and not a precompiled package, and it took a lot longer to install this time than the last time I installed it in OpenBSD (on the Compaq Armada 7770dmt), if I recall correctly.

When you download the ports tree and install from there, everything is fetched for you and compiled when needed. Looking at all the output in the terminal, it looks like these ports could never work, but in my experience with OpenBSD they always do. This time was no different. It took maybe 45 minutes to get all the dependencies plus Opera, but after that it worked immediately.

I've grown accustomed to OpenBSD's default window manager, Fvwm2, and I'll probably stick with it for at least awhile before adding any others. Unlike Debian, Ubuntu, Slackware, etc., installing an app in OpenBSD doesn't automatically update the menus, so you have to manage this yourself. Getting into the guts of the .fvwmrc file is more instructive than not, and once I figured out how to do it, it got less arduous.

I still don't like waiting for ports to download, compile and install, so having 4000+ precompiled packages for i386 is a very good thing.

After a year of strugging with and complaining about the Gateway fan blasting away under OpenBSD, I couldn't believe that I was running OpenBSD 4.4 on the Toshiba with no CPU fan problem whatsoever. Everything from autoconfiguration of my two network interfaces (one Realtek 8189 wired Ethernet, the other an Orinoco WaveLAN PCMCIA wireless) to a perfect xorg.conf made this OpenBSD install go .

I haven't checked audio yet, but I've never had OpenBSD fail to configure the sound card.

I've always read that most OpenBSD developers use laptops to code in the OS, and now that I have this Toshiba running OpenBSD better than anything I've tried before, I'm amazed at how well it installs and runs on this specific platform.

I've probably written a half-dozen posts about exactly why I'm running OpenBSD, and I'll probably write another one as time allows in the week ahead.

And I'll be either ordering a CD set or contributing directly to the OpenBSD project in the days ahead.

I decided to start adding apps to the Self-Reliant Thin Client, which is running Debian Etch from an 8GB CF card as the boot drive with a 1 GHz VIA CPU that insists at running at 500 MHz, plus 256 MB of RAM.

I used aptitude to add the Geany text editor and the Fluxbox window manager.

Fluxbox runs great, as usual, but I really don't see any app-speed improvement with Iceweasel, OpenOffice, Geany or Gedit.

In previous tests, I saw a real advantage to using Fluxbox or Xfce over GNOME, but here in Debian, GNOME is running well enough that I'll probably use it quite a bit. I'll continue testing Fluxbox, but I imagine that GNOME will continue to be my main window manager on this box (as it has been when running off of a traditional hard drive).

It definitely depends on the specific box, and especially on the available RAM. I guess that 256 MB of RAM is enough for good GNOME performance. With 128 MB of RAM, Xfce, Fluxbox, Fvwm or other lightweight window managers might dramatically improve performance vs. GNOME.

One thing I have to do is run top when running the same apps in both GNOME and Fluxbox. If the same amount of swap, relatively speaking, is being used in both window managers, that tells me why my GNOME performance is so relatively good. But if there was a lot more swap used in GNOME vs. Fluxbox, then I'd know that the lighter-weight window managers are really making a difference.

Not that anything approaching brain-surgery-level thinking was in any way involved here, but I figured out why and how it's easy to get paragraphs to automatically indent when writing in the Geany text editor.

First of all, it's not called automatic tabbing or paragraph inentation. The correct term for what I'm enjoying so much is auto-indentation and it can be turned on and off under the Document menu in Geany. The defaults for auto-indentation can also be set in the Edit menu under Preferences--Editor.

When writing for print, where I don't need — and can't stand — having two returns between paragraphs. After transferring the file from this laptop to my newspaper's print publishing system, those double-returns demand that I delete one of them. That's because in most non-Web publishing, indented first lines make paragraphs distinct from one another, not extra linefeeds.

So having the indents on the first line of every paragraph helps me seen where each paragraph begins.

I know that programmers use indents to help structure their code. But when something so right for coding in C also helps hacks like me, making traditional word processing applications less needed, everybody wins.

(This post was originally written on May 22, 2008; since that time, I've added the RAM, and it does indeed make a difference. It's still not easy to live with 144 MB of RAM and 233 MHz of CPU, but it's easier than having less than half of that M. What I can say is that 500 MHz of CPU and 256 MB of RAM is positively picnic-ish. Also, I finally did the OpenBSD 4.2-to-4.3 upgrade on the VIA box. It wasn't easy, but I did get it done.)

If the question is "how low can you go" in terms of computer memory, it's all about applications.

If you stayed in the Linux console and never ran X, just about anybody could be happy with 32 MB of RAM. It might be hard to actually run Linux or a BSD in 16 MB, but I've heard of Linux distributions that will do it, Damn Small Linux, Tom's RtBt (is that the right spelling?) and DeLi Linux among them.

But as much as the hard-core users talk about how they stay at the command line all the time, it's hard to get much done strictly in a console when you're a regular person. Sure you can use Lynx for text-only Web browsing, you can set up Mutt (and Postfix/Sendmail/msmtp/esmtp, Procmail and whatever other helper apps are needed) with highly customized configuration files designed to handle and filter multiple mail accounts, use Vi or Emacs for text editing and all that.

But the bottom line for me is that I need a Web browser. A "real" Web browser, something that works with Movable Type and Google Docs, and that pretty much means Firefox or some Iceweaselish derivative.

I don't tend to use OpenOffice very much (although it runs better in Debian with 64 MB that you'd think), I barely even use AbiWord these days. I'm not saying that I won't need OpenOffice in the future, but at present I'm most comfortable using various X text editors, including Geany in most Linuxes and BSDs, Gedit when I'm in GNOME, and Google Docs half the time just for the easy portability of my copy.

And while Geany doesn't load super quickly from a "traditionally" installed distribution (but is quite quick when loaded into memory as it is in Puppy Linux, once it's loaded it runs very well indeed.

And the Dillo Web browser -- which looks better in its OpenBSD incarnation than it does anywhere else -- performs quite well in 64 MB of RAM. The only problem is that Dillo can't do everything I need to do on the Web. At least the Dillo in Puppy and DSL has https support. That's not turned on in OpenBSD, and the app needs to be recompiled to add it. I can manage to turn on cookies in OpenBSD, which helps me with some sites, but for anything remotely complicated, Firefox is essential.

And while Firefox will run in 64 MB of RAM, it does so very poorly. There just isn't enough memory to keep the program from swapping to the drive incessantly whenever doing just about anything.

In this very 64 MB, I've run just about everything that will load on this Compaq laptop: Puppy, DSL, Debian (the Xfce install, plus a "standard" install with Fluxbox), Slackware (without KDE) and OpenBSD.

Truth be told, Almost all of these OSes run just about the same. Damn Small Linux has a bit of an edge, and if DSL 4.3 ran as well as 4.0, its inclusion of Firefox 2 would put it over the top. As it is, I've lost my desktop wallpaper, and I can't figure out how to display the menu in Fluxbox (even though I prefer to run JWM).

Puppy definitely needs more memory, especially to run the Mozilla-derived Seamonkey Web suite.

Debian Etch was OK. While the Xfce install is odd in many ways, as I say, I was surprised to see OpenOffice run at all -- and not too badly at that. Iceweasel was, again, an exercise in frustration. But Debian remains a distinct possibility for this machine.

It's main OS for awhile has been OpenBSD, with a partition set aside for the Linux files generated by the Puppy and DSL live CDs.

OpenBSD runs pretty well, but as I said, Firefox remains an issue.

The question: Will things improve with the boost of RAM from 64 MB to the Compaq Armada 7770dmt's maximum 144 MB? From my past experience, I know that Puppy can run in 128 MB if you have swap space, and DSL is certainly comfortable with 128 MB.

To answer the question, I could reduce the memory in my Via test box from 256 MB to 128 MB and see how OpenBSD (now version 4.3) runs in that configuration. But I'd have to pull the cover from my converted thin client and find a 128 MB SIMM. I've probably got one ... somewhere.

Better to just wait for my Compaq memory to come in the mail (luckily it's cheap).

I've know for awhile that 256 MB is a significant sweet spot for Linux, but I'd love for 144 MB to be just sweet enough to give this laptop a new lease on open-source life.

And while I managed to upgrade my VIA box from OpenBSD 4.2 to 4.3, it takes a lot more work than a simple apt-get, and I'm reluctant to do it

(This post was originally written on April 24, 2008; since then, I've bumped the system up to 144 MB. This entry should set the scene for how much better things are working with the additional memory).

When you're not running X, 64 MB of RAM is plenty. In OpenBSD, or just about any version of Linux for that matter, you just don't need a lot of memory to use the console. Of course, you can't do a whole lot either.

I know, I KNOW, that real geeks use the command line as much as possible. E-mail with Mutt or Pine (and fetchmail, procmail, sendmail, procmail ... did I miss anything (maybe msmtp, which I prefer, or esmtp, exim, postfix ...), text entry with vi (or nano, joe, emacs), text-only Web browsing with Lynx or Elinks.

OK, I do all this stuff, though I did give up on Mutt; it just didn't work for me as well as I needed, and while I put in plenty of time on the configuration, I needed to be way more of an expert than I'll probably ever be). But I really prefer to run X. I get the apps I want, real Web browsing, and a whole lot more overall productivity.

But X takes memory, and while OpenBSD with the Fvwm window manager can run in 64 MB, things take forever and a day due to all the swapping. Unfortunately, my 1999-era laptop -- a Compaq Armada 7770dmt -- maxes out at 144 MB. That's 16 MB on the motherboard, plus two 64 MB EDO SODIMMs.

The memory is on the way (I hope). Right now I have two smaller SODIMMs, a 16 MB and a 32 MB, in the laptop. And yes, I had to do the Compaq memory fix from the OpenBSD FAQ to make the OS recognize the "extra" memory. But it does work.

Anyway, I'm hopeful that OpenBSD will perform dramatically better in X with 144 MB. Since this is a pre-ACPI laptop, I don't have the problems that plague me with my Gateway Solo 1450, on which only Linux, it seems, will turn the fan on and off in response to CPU temperature. In OpenBSD, it's all on. In FreeBSD, it works for a day, and then that's the end of it. Can't figure out that one.

But I'd love to have a laptop devoted to OpenBSD (I'm using vi now ... but I miss Geany, Firefox and the rest of the junk I've got loaded on here). And if OpenBSD can work well on the desktop with only 144 MB, that will be a significant achievement for all of us with hardware in the 10-year-old range.

I'd love to roll OpenBSD onto my 10-year old PC that now runs Windows 2000. It would Do OK with Linux, for sure, but getting OpenBSD on there would be really great. And I have a full 256 MB of RAM on that box. I'm already running that much memory on my test box in the office, and I have no complaints there when it comes to running X apps in OpenBSD.

I started X to finish this post. First I ran Firefox, even though this laptop has only wireless 802.11b networking (and no wired Ethernet, although I've been meaning to get a PCMCIA Ethernet card). Yep, still takes a dog's age to start Firefox, and it's not all that responsive when it's running.

Again, I would love for that NOT to be the case after the memory upgrade.

I started Geany to continue writing. Geany runs pretty well with this 233 MHz processor and 64 MB of RAM.

So does the Dillo browser. And everytime I write about Dillo in OpenBSD, I like to mention that, for some reason, the Dillo menus and buttons look way better in the OpenBSD version of the app (I'm using the package, not the port) than they do in any other operating system in which I've tried it. And I've tried many.