Recently in Free, open-source software Category

In addition to his first e-mail to me, David Gurvich adds more about his experiences with Intel i830m video in Linux and PC-BSD/FreeBSD:

I did think the problems with FreeBSD were due to using PC-BSD and installing a lightweight desktop on top. After testing with a bare install that turns out to not be the case and the issue is with FreeBSD and has nothing to do with the scripts that PC-BSD uses.

I have not tested OpenBSD but most of the wireless drivers on FreeBSD have been ported from there. I suspect there is a difference between the two that causes these drivers to crash the system on FreeBSD. The primary reason that I was interested in FreeBSD was ZFS support and wanted to setup a file server. The network issue stopped that in it's tracks.

There is a graphical network tool in the FreeBSD ports that seems to work ok but most of my settings were with wpa_supplicant and rc.conf. I believe that PC-BSD has it's own graphical network configuration tool but didn't use that.

Flash does have issues on FreeBSD and I don't recommend installing the linux compatibility to use flash. Instead, use wine with a windows browser. There is a memory leak in the linux flashplugin on FreeBSD that will eventually cause your system to freeze until you kill nspluginwrapper. The same technique may work on OpenBSD.

I have tried Fedora 12 on this laptop and that worked somewhat after tweaking a number of parameters. By somewhat I mean that I had random Xorg crashes and the tweaks simply mitigated the frequency. I gave F12 about 2 months but just could not take the crashes. Fedora 12 is working well on the other systems that I've installed it on but there was a problem with one that had ATI video which required building an xorg module from git.

I am currently using Arch linux on the X30 and, since configuring the boot parameters with 'nomodeset' and locking the xf86-video-intel driver to 2.9.1, have not had any issues with video. The main problem has been with the networking scripts and I am still not sure what the issue is there but installing wicd-1.7 seems to have worked around that. I am impressed with the speed vs Fedora 12. The reason I am impressed is that, prior to Arch, Fedora 12 had been among the fastest distributions on the X30 with a useable firefox in under 2 minutes. The X30 from startup to a working firefox connection takes 45 seconds in Arch.

The main issue I will have with Arch is likely the very reason Arch is so responsive. Rolling releases don't keep old packages around and new versions can cause random failures on working systems. That means that I will need to maintain a list of packages that should not be upraded and be careful on upgrades. Nothing new to anyone who has used Gentoo.

I've currently had Arch installed on the X30 for a month and have had no issues to deal with since the video and networking were fixed. The livecd boots to a text console and I recommend looking at the arch installation guide. Pretty much everything needs to be configured but the wiki makes that simple.

David Gurvich

David, you hit on a number of important points. I will definitely try Fedora 12 to see how it works with i830m, and I agree with you that Arch is an excellent choice. I've written many times about how the Arch community has been a great resource for me in solving my X issues with i830m all the way from Debian Lenny through now.

I neglected to mention ZFS in FreeBSD. That certainly is something to recommend in its favor. There's also a project bringing journaling to soft updates in FreeBSD's UFS filesystem that I heard about in this BSD Talk episode.

I'm not terribly happy about Flash being so problematic in FreeBSD. I forget all the trouble I had with the Opera browser in OpenBSD. That browser and its Flash plugin uses OpenBSD's Linux compatibility layer, and I was eventually able to stop most crashes by changing a parameter in Opera.

Here's what I'm hoping for:

• People smarter than me will figure this out and either make allowances in the kernel and xorg, or will create some other kind of mechanism that doesn't leave users of Intel 830m video chips out in the cold
• HTML 5 will sooner than later take hold with an open video codec and return Flash to what it's good at, which is little applications that I can safely ignore, and stop doing what it's bad at, which is delivering video that can better be handled by a plethora of other formats. The easiest way for this to happen would be for Google to open-source the on2 video codec it recently acquired. (Except that Google already converted the entire YouTube library to the loved-by-Apple patent-encumbered H.264.)

  I've run BSD before, and if Linux/Xorg throws Intel 830m under the bus, I'll be an enthusiastic user of any system that doesn't follow along.

The OMG!Ubuntu blog reports on the decision, however preliminary, at the Ubuntu Developer Summit in Dallas to remove the GIMP image editor from the 10.04 Lucid LTS release of the wildly popular Linux distribution.

Read the well-wrought entry linked above for the drawn-out reasoning behind moving the "professional"-quality Photoshop killer GIMP from the Ubuntu base (it'll be available in the Ubuntu Software Center, or your other favorite package-management tool).

Those assembled seem to think that GIMP is not used enough and is not consumery enough. And that the F-Spot photo manager can do basic photo editing and is much better for the average user.

Oh, do I have bones — plural — to pick over this one. I still haven't made my decision on whether I'm for Mono (using the Microsoft-compatible open-source tools) apps or against them (and F-Spot, along with Tomboy notes and, if you've added it, the Banshee music player seem in my mind anyway to be the highest-profile Mono apps in the GNOME world).

All I can say is that with the geek-political climate these days, more Mono rather than the same or less will just give more users a reason to jump off of GNOME (and Ubuntu) in order to keep one's collective hands, if not clean, than at least Microsoft-free.

Again, I haven't made a personal decision about Mono as yet, but I'm far from happy with F-Spot.

And yes, I've been using it somewhat regularly. For my purposes, I'm not crazy about having to import images into F-Spot. digiKam can deal with images in any directory structure, and I'd like my photo-organizing program to do the same. I understand that F-Spot is more iPhoto-like in this aspect. I still don't like it. It's OK for my personal images, but I can't keep my businessy images separate. Everything's in one big pile in F-Spot, except when you dig into the actual directory structure the app creates. Yep, just like iPhoto.

In F-Spot I can add a caption in the "comments" area. Unfortunately that data does not come up in any other applications I use to edit or view photos. I can't edit the IPTC data that 100 percent of professional photojournalists use (and those are the guys whose images I handle day in and out).

F-Spot will sharpen and adjust the color of images. It will crop them. But it won't resize them. Huge, huge deal-breaker for my "professional" use of this application. (And why would I use something for my "home" images that won't do the job with my real work if I don't have to?)

Truth be told, I don't require all that Photoshop offers. On the PC I use IrfanView. And basically my "quest" for a Linux/Unix image viewing/editing program runs along the lines of "give me something that does what IrfanView can do."

Even the GIMP (and Krita, too, O fans of KDE) can't deal with the IPTC data in JPEG images, which I absolutely need.

The digiKam image manager in KDE, through the great Kipi Plugins, CAN deal with this data, and pretty well, too (although the limit on the length of the IPTC credit line is a bit grating and seemingly unnecessary).

So I've been using digiKam for the past few weeks somewhat regularly. (Truth be told, I tend to work in IrfanView on my Windows box at the office about 80 percent of the time when editing photos; it's the environment I know, and that does what I want it to do.)

digiKam is a bit unwieldly. Like many KDE apps, there are menus for days, along with choices to match. It resizes. Good. It sharpens (although the results aren't as good, seemingly, as in every other app that sharpens images; there are, again, lots of choices, and I barely understand — and can't get a great result — from them. digiKam can crop, but you can't enter the exact dimensions of your crop in pixels and then drag the box around to make the perfect crop like I do in IrfanView. Not a deal-breaker, but not good either.

And did I say digiKam is unwieldy. Why are there separate "edit" modes for the metadata and the image data?

I've had little ol' gThumb on this Ubuntu machine for awhile. And hearing that the UDS suggested and then rejected it as a "replacement" for either GIMP and/or F-Spot prompted me to try it out. Sure I had opened a few images, but I hadn't yet done any heavy lifting with gThumb.

It was time.

Gthumb, little ol' gThumb (that's what I'll call it for the purposes of this entry), does almost everything I need:

-- Deals with images in their current directory structure
-- Resizes images to exact pixel dimensions
-- Crops images to exact pixel dimensions
-- Can edit/add IPTC caption info (to the main caption area only) with the "comments" feature
-- Allows for easy save-as of images

The only thing gThumb doesn't seem to do (and I could be missing it, though I don't think I am) is sharpen images. I can live without that, especially if gThumb can create and won't destroy existing IPTC data in JPEGs.

(Note: Besides Krita and GIMP, my previous favorite light image editor for Linux, MtPaint, is also an IPTC-data-destroyer and therefore can't be used for my "real" work.)

So thanks UDS people, for mentioning gThumb. And if you're asking my advice, and I know for damn sure that you're not, keep the GIMP or don't. I'll install it anyway.

But look deep into your geeky, geeky hearts and find it within them to replace F-Spot with gThumb. Or at very least make gThumb part of the Ubuntu base, make it the default image-organizing app, and let the rest of the free, open-source software-using world discover this most worthy of applications that for the most part can free me from the purgatory of Windows-based photo editing applications for good.

(And while I'm on the well-trod soapbox, let me mention that I wrote this entire entry using the newish Webkit-based Epiphany Web browser, another lovely bit of GNOME that I liked in its Gecko days but like even more now.)

(And sorry [really] about all those parentheses, within which I'm thinking all too often these days.)

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 ...)

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).

Come to the Jan. 27 meeting of TUGNET — The User's Group Network — and hear me speak to whoever shows up.

My topic: Evolutionary computing: Making the leap to free, open-source
applications and operating systems.

What I'll be trying to do is bring the worlds of this blog, which explores the inner reaches of my own geekiness, with that of my print column, Tech Talk, which is aimed at a more general audience.

Both the blog and column draw heavily on my own experience, and I wouldn't have gotten wherever it is I am now if I worried about what I didn't know. I've said on many an occasion that I'm hear to learn and to demystify the process of wading into the technological waters.

Enough of that. What I'll be talking about is my own journey from a garden-variety user of proprietary software to one who aims to use free and open-source solutions wherever possible.

While I burned and ran my first Linux live CD in January 2007, I first got my feet wet in the world of Unix way back in the 1980s through a free on-campus account at UC Santa Cruz, where average (read: non-technically inclined) students were encouraged to use Unix to write and print out (on a bona fide networked laser printer ... and this was right around the time Apple released its original LaserWriter at a cost of $6,995) our essays and anything else we did for our classes.

At TUGNET, I'll talk about the advantages of using free, open-source applications in proprietary environments like Windows and Mac OS and how that makes it all the easier to make the transition to FOSS operating systems that include a few hundred active Linux distributions and four key BSD projects.

I'll be providing tech tips, as well as book and Web-site recommendations on how to learn more about free software, and I'll talk about why I'm using OpenBSD these days more than Linux (and why that could always change because I'm a major proponent of choosing and freely changing both hardware and software to best do the task at hand).

I'd like to thank TUGNET president Marian Radcliffe for inviting me.

And dear reader (as I weakly invoke Jane Austen), I hope to see you there.