Can you (easily) update a BSD system between releases? Or am I barking up the wrong (ports) tree?

Note: I originally wrote this post on 2/15/08. Today is 4/24/08. Since that time, I’ve looked into updating in the BSDs a bit further. In FreeBSD, it’s certainly possible to update both ports and packages.

In OpenBSD, the Errata for a give release shows you what needs to be fixed in the base system. The updates are easily available, but they do need to be compiled from source. What the OpenBSD team really wants you to do, it seems, is run the -current release, on which all ports can be updated from source. Sounds like a lot of compiling. Still, I might try it at some point.

Anyway, here is the “original” 2/15/08 entry:

While it’s pretty easy to install software from precompiled packages or from ports in OpenBSD, FreeBSD and NetBSD, I’ve hit a bit of a wall when it comes to keeping any of these systems up to date with periodic security and bug patches.

I don’t know if such updates are either not as necessary in the BSDs, even though my Linux boxes have a dozen or so of them every week, or that it’s just to hard to do for the average BSD user.

I see plenty of Web help on how to upgrade from one version of a BSD to another, but I don’t see anything that covers searching for periodically updated packages and updating an installation on, lets say, a weekly basis as security and bug problems arise and are presumably updated in the repositories of packages and ports.

O, BSD users, correct me if I’m wrong — and I do hope that I am wrong. But with apt/Aptitude/Synaptic in Debian-based Linux distributions, rpm/Yum in Red Hat- and Suse-style systems, and upgradepkg (and slapt-get/Gslapt) in Slackware (with security announcements going to the mailing list and the http://www.slackware.com/security page) … need I go on?

The point is that almost all Linux installations are easily upgraded with precompiled binary packages. Gentoo … well, I won’t go there because I know it has its own BSD-like ports system, but I’ve never used it and don’t know how it works.

Again, the point is that all of these Linux distributions have me conditioned to expect — and to install — updates on a regular basis.

But what do I do with BSD? In OpenBSD, for instance, I’ve never even downloaded the ports tree. Everything I’ve installed has been a precompiled binary package for the i386 architecture. It’s very slick, works perfectly … but am I exposing myself to undue risk by running Firefox 2.0.0.6 instead of the newer 2.0.0.12? Is all that extra OpenBSD security for nought if I’m running applications rife with security holes?

I’m being completely serious. Is there something I’m missing here? Since OpenBSD, at least, updates the whole system every six months, am I OK to keep the same packages running until the next release? What does this say about BSD vs. Linux when it comes to security and bugs?

But wait. I did run DesktopBSD for awhile, and I remember that system having a GUI package manager that not only fetched new packages but upgraded those already installed.

So that’s what Matt Olander was talking about when he said that PC-BSD and DesktopBSD were working together to share technology when it came to package management.

As far as I’m concerned, I don’t need to do my updates in a GUI app. I’m perfectly OK with using the console. Just being able to do that updating is enough. That is, unless someone out there can convince me that Linux has conditioned me to think I need something that I really don’t.

Those on all sides of this issue, please enlighten me — and quickly.

DesktopBSD’s brief, shining moment

I’ve been shuttling CDs in and out of my Gateway Solo 1450 laptop, just seeing what works and how well.

I’ve also been fiddling around with the BIOS settings, trying to get the CPU fan under control in both Linux and the various BSDs. A select few Linux kernels do this automatically … most don’t. I can control the fan with a cron job, but I’ve never, ever been able to do this with any version of BSD.

Until today. For some reason, I ran DesktopBSD 1.6 as a live CD, and the fan fell silent, turning on at various intervals, then off.

Like it’s supposed to do.

I rebooted.

It worked again.

A couple of boots later, it stopped working. I changed nothing between boots. It could’ve had something to do with going from Debian Lenny to DesktopBSD …

So while ACPI fan control is possible with FreeBSD — upon which DesktopBSD is based — I’ve got nothing in the bag. And it may never work again.

I tried PC-BSD 1.4 and FreeBSD 6.3 (just booting, not installing) … and the fan roared as always. I thought I could control it from a console, but that didn’t work.

But for two brief, shining moments, I had a FreeBSD-based system running with CPU fan management working perfectly.

If only it would happen again.

SCALE 6x: BSD all over it

The “L” in SCALE may stand for Linux, but each of the three major BSD projects has a table at the Southern California Linux Expo. While the FreeBSD booth was giving away PC-BSD CDs (they still have about 500 left, so have at it, people), the OpenBSD booth was selling Version 4.2 CD sets for $45, and the NetBSD people were selling T-shirts for $15.

But it’s not all about stuff.

I spent a lot of time talking to Kevin Lahey, a developer for NetBSD who is also a programmer for the Information Sciences Institute under the auspices of the University of Southern California. His organization does work for the Department of Homeland Security, and in the past Kevin has worked for the NASA Ames Research Center, and he told me that NetBSD has a lot of uptake in both government and university settings.

The NetBSD project began in May 1993, and is edging closer to its 15th birthday. It was nice to see Kevin’s IBM Thinkpad running NetBSD with a GUI desktop. I’ve been impressed by the way NetBSD both looked and performed in the 2006-era live CD I tried on Friday, and while NetBSD is increasingly aimed at embedded applications, I think it’s a great candidate for desktop use.

Kevin told me that NetBSD has over 200 active developers, most of whom do IT-related work for companies, many of which use NetBSD as part of their business.

As far as the desktop goes, NetBSD is getting better all the time at supporting the ACPI standard for power management — something that will also see considerable improvement in the forthcoming OpenBSD release, as I learned at that booth. The NetBSD kernel also supports gigabit and even 10GB Ethernet, so it plays very well in many networked environments.

While OpenBSD encourages users to use the precompiled packages for the various architectures, NetBSD users rely on ports for adding applications. Also at the NetBSD booth was David Maxwell, and he told me that thera are about 16,000 ports for NetBSD. It always amazes me that there is so many applications available for the BSD operating systems.

I didn’t quite get how NetBSD handles software updates, and Kevin tried to explain it to me, but there is some mechanism at work that can bring the needed updates down to your box as needed. It’s something I’ll have to look into more. Luckily, every one of the three BSD projects includes excellent, comprehensive documentation on their Web site.

As far as that documentation goes, David told me that NetBSD takes extra care to make sure its man pages are up to date.

Again, it’s great to see a worthy project and the very smart people behind it.

On a BSD roll — DesktopBSD boots and runs where it has never boot and run before

After whining over a dozen or so entries about how my VIA C3 Samuel-based test box would boot and install OpenBSD but not NetBSD, FreeBSD, DesktopBSD or PC-BSD, I’ve had a great time working in OpenBSD, and I was surprised to learn that the NetBSD 4-based live CD boots into a KDE desktop, looks great and runs pretty well, too.

I recently burned the latest DesktopBSD CD, which in its latest version boots as a live CD and will install the system. On my Gateway Solo 1450 laptop, besides the power management not working, there’s an unattractive blob that follows the cursor everywhere it goes (it’s a cute little program-dependent icon otherwise). But on a fanless desktop (there is a CPU fan, but it doesn’t run and hasn’t killed the CPU yet)

But my desktop test box has never been able to boot a FreeBSD-based CD until today, when I figured I’d give DesktopBSD 1.6 a try. It booted, configured the monitor for 1280 x 1024 (I prefer 1024 x 768 and will try it that way later) and is now up and running. If I had more time, I’d do a full install on one of my three drives that I rotate in and out of use (they sit atop a CD-RW drive, all outside the main box and connected with extra-long power and IDE cables).

The DesktopBSD KDE environment doesn’t look as nice as the one in the NetBSD live CD, and I’m not a big fan of KDE mostly because my old hardware can use all the help and speed it can get, but running both of these live CDs gives me hope that I can do some work with all NetBSD and FreeBSD in addition to OpenBSD to see what fits my hardware and goals for a desktop system.

The NetBSD live CD — why haven’t I heard of this before?

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.

OpenBSD on the desktop: Why?

Why a desktop installation of OpenBSD?

It’s a legitimate question. According to Distrowatch, among the three main BSD projects (they don’t like to be called “distros”), FreeBSD is way out in front — and is the base for PC-BSD and DesktopBSD — followed by OpenBSD and NetBSD.

And even though there are two desktop-focused versions of FreeBSD, and it’s possible to turn all three of the major BSD projects into a desktop-worthy system, the question remains: Why not just stick with Linux, with its usually superior hardware detection, vastly larger community of users (who in theory and often in practice can provide all the help you need to get a system up and running) and much larger choice of distributions?

For one thing, Linux isn’t alone on the desktop, nor should it be. Apple has a hugely popular desktop operating system based in part on code from BSD. And another operating system derived from Unix — OpenSolaris — is also inching onto the desktop with its Indiana project.

I think the competition is enormously healthy for free, open-source software, and I support that competition and choice wholeheartedly.

And using OpenBSD to build up a desktop system is just plain fun. It’s more of a challenge, and all the configuration that I’ve done and am doing just teaches me more about what makes operating systems tick, even in my technologically feeble state.

I’m no coder. I’ve never programmed anything. I just mess around with hardware and software and then write about it.

I’m pretty much compelled to do all the things I’ve done over the past year and a half. It hasn’t gotten boring.

And while I’m not going to move away from Linux, if the hardware and software cooperate — as they have on this test machine — I see no reason not to spend some considerable time running OpenBSD and seeing what I can do with it.

Again, my thanks go to all the people behind OpenBSD as well as the bloggers whose experience has paved the way for me to consider running the operating system and then to install and begin configuring it.

Going forward, I hope all of the major BSD projects — FreeBSD, OpenBSD and NetBSD — will continue to grow, keeping their documentation of the same ultra-high quality and enabling users to get more and more hardware working to the point where both server and desktop users have a greater number of choices than ever with which to get things done.

$0 Laptop shakeup: Ubuntu 7.04 is gone, Wolvix Hunter 1.1.0 takes its place

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.