cvs -d :pserver:anoncvs@yaifo.cvs.sourceforge.net:/cvsroot/yaifo co -P yaifo

I’m still testing and tweaking sgi and sparc64.

Yaifo 4.5 has several new features and a new architecture. You can download Yaifo 4.5 from SourceForge. Below is a summary of some of the changes in this release:

• Support for sgi added
• Add ‘get-files’ target to copy authorized_keys and ssh_host*_key files
• Add SNAPSHOT=yes|no to default to snapshots directory
• Add install target (requires REALLY=YES environment variable)
• Start adding landisk support – not complete

There are no new features in Yaifo 4.4 besides bringing Yaifo in sync with OpenBSD 4.4. Thanks to Seth for helping me test and finding some problems.

You can download Yaifo 4.4 from SourceForge.

For the yaifo release accompanying OpenBSD 4.3, I decided to match OpenBSD’s version number. From this point forward, only one version of yaifo will be active. I will not backport updates for older versions of OpenBSD… who is “upgrading” to older versions anyway? So the current OpenBSD release and some recent version of -current will be supported.

You can download Yaifo 4.3 from SourceForge.

The OpenBSD installer with a terrible name has a new update to coincide with the release of OpenBSD 4.2. New in Yaifo 0.5:

• amd64 has been tested and is working (it worked with version 0.4, but I didn’t have a way to test).
• macppc added.
• cleanall make target actually does clean all now.
• I started to take more ownership of the project (not just functionality) including updating the readme, copyrights and cvs $Id$ tags.
• Added boot.conf to build a kernel with console redirection (to make yaifo + soekris work properly).
• Changed the message at the end of an upgrade/install to recommend reboot over halt (because halting a server 1000 miles away would be just plain stupid).
• Update to OpenBSD 4.2.
• Use a standard sshd_config and customize sshd through command line options in net.sh.

Download yaifo-0.5 for OpenBSD 4.2.

I wrote about how I went about setting up my new Soekris net5501:

I recently purchased a new Soekris net5501 to replace my beige box firewall. I had previously set up a net4501 but I wasn’t happy with it and sold it to a friend. Large file transfers would grind it to a halt and the performance wasn’t as good as my beige box. The net5501 has increased horsepower (faster processor, more memory) and a better network chipset (vr(4)). And, most of all, because there are 4 network ports! At my house I have 3 network + my FiOS connection. I have my internal LAN (wired with full access to everything), my wireless network (requires authentication and has limited access to the LAN) and my DMZ (for my web server; no access to the LAN or wireless networks).

For my installation, I use Yaifo so I don’t have to deal with a serial console or setting up pxeboot. (I actually did hook up a serial console to update the bios, which I’ll discuss later). Also, I use a custom rc and a flashdist-like system so I can mount my CF read-only. My “fdlite” script doesn’t rely on a customized install like flashdist. It does use some of the device modifications Chris uses to make the read-only / work properly, though.

Read more at The OpenBSD Journal.

I just bought a Soekris Net5501. I was hoping that Yaifo would provide a convenient method for installing OpenBSD on the CompactFlash card I’ll be using in my new Soekris firewall. After a few tweaks, it does!

It seemed reasonable that I should be able to plug my CF card into a CF reader and connect it to my OpenBSD laptop and copy the yaifo.fs image to the CF using dd if=yaifo.fs of=/dev/rsd0c. So, that was exactly what I did. Then I popped the CF card into my Soekris and it wouldn’t boot. I dug around and found a serial cable (actually, I already had one ready for this, but you might not have one) and saw that the boot process really doesn’t get passed loading the kernel.

After some trial and error, I modified Yaifo to include an /etc/boot.conf file in the yaifo.fs (and yaifo.rd) image. The default boot.conf file only contains comments and does not change the way Yaifo works. You can modify this file to redirect boot messages to your serial console (set tty com0) and modify the speed of the connection (stty com0 19200 for my Soekris).

This, in my opinion, makes installing OpenBSD on a CF card (especially in a Soekris) very easy:

1. Buy an OpenBSD CD to support the cause.
2. Buy a device that uses CF for storage (like a Soekris Net5501).
3. Buy a CompactFlash storage device.
4. Pop the CF card into another OpenBSD system where you’ve built your yaifo.fs image with proper network settings and appropriate boot.conf settings. Copy the yaifo.fs image to your CF: dd if=yaifo.fs of=/dev/rsd0c
5. Pop the CF card into your Soekris and power it up.
6. When your Soekris responds to pings, SSH to it and set it up to fit your needs.

I plan to put up more detailed Soekris + Yaifo instructions either here or on The OpenBSD Journal.

I also set up a new category on my website for Yaifo so that it has its own page. I haven’t decided yet, but I think I’ll just have the SourceForge Project Homepage redirect to the page here.

I will still generate tarballs for downloads, but you can get the latest and greatest from CVS:

cvs -d:pserver:anonymous@yaifo.cvs.sourceforge.net:/cvsroot/yaifo login
cvs -z3 -d:pserver:anonymous@yaifo.cvs.sourceforge.net:/cvsroot/yaifo co -P yaifo

Besides updating Yaifo for OpenBSD 4.2, I also made the install complete message warn users to use the reboot command instead of typing halt (which could be disastrous if you don’t have console access):

CONGRATULATIONS! Your OpenBSD upgrade has been successfully completed!
To boot the new system, enter reboot at the command prompt. Once the
system has rebooted, you will be able to use your system.

Note: Using the halt command at this point may render your installation
unreachable.  Make sure to use the reboot command instead.

I would like to come up with a different name that more expresses that Yaifo is not a different installer, but an enhanced version of bsd.rd (with sshd). I’d also like to come up with a logo. After I get a new name and logo, I’m going to set up a SourceForge project.

If you have name and logo suggestions, leave a comment (or send me an email).