:photos
:papers
:tutorials
:drm
:nmicrocoder
:daes
:dhex
:deadline
:dettuxx
:circdraw
:systemc
:xf86config
:qdslconfig
:bootfloppy
:6502
:alienware

:math

winscp.exe
putty.exe

:impressum
I always liked the thought of haveing OpenBSD running on my webserver. And I liked the fact that OpenBSD can be installed with a single floopy-image.
However, the bootfloppy OpenBSD provides is designed to work on a computer with a monitor and a keyboard only. And it is a toughie to customize.

So look at my collection I got so far:

Standard:

floppy37.fs.gzmd5=75a48f00c0cfad3fa9bf74a71c2c70c1The default OpenBSD 3.7 bootfloppy

With a serial console:

Those bootfloppys are the standard OpenBSD-floppies, but instead of using the graphics adapter as stdout, it uses the serial output. This makes an OpenBSD-Installation on a root-/dedicated-/(whatever) server much easier! (As long as your server is connected to a serial console server, of course...)
Look at my howto to see how you can customize them to your needs.
floppy35_seriell.fs.gzmd5=86a9797122a343e764d667177b1534a9OpenBSD 3.5, with the output redirected to the serial console
floppy36_seriell.fs.gzmd5=93e436bc48c2aaccf736acad7d3778f0OpenBSD 3.6, with the output redirected to the serial console
floppy36_seriell_com1.fs.gzmd5=bae0dfde76ea1899791865179e8469adI am not sure what this one was...
floppy36_seriell_stty.fs.gzmd5=e97ab0d4d566a63aada720cde797fed2... or this one... anyhow...
floppy37_serial.fs.gzmd5=9b35e1cfbde8dfc8b39238a3c660ca31OpenBSD 3.7, with the output redirected to the serial console
floppy37_seriell.fs.gzmd5=c9b6ade342ad6043ab21401c24828fccOpenBSD 3.7, with the output redirected to the serial console
floppy38_amd64_seriell.fs.gzmd5=49623d645bea956e0748e9c95b330647OpenBSD 3.8, for amd64, with the output redirected to the serial console

(all floppies use 57600,8N1 as serial parameters)

Custom start script:

Those are my latest ones: I tampered a bit with /usr/src/distrib/miniroot/dot.profile, and tried to add an startup-script, which is easier to access than the ones on the bootfloppy. It is just a quick-and-dirty hack at the moment, so don't bother about all the warnings at boot-time...
When you mount them on your local computer, like I have written in my howto, you will probably notice a file called "autoexec.ksh"
Because there are some providers out there, who won't give you the luxury of a serial console, you can see wether computer boots or not. Just set the correct networking parameters, and try to ping it. Great for a testdrive too!

My goal is to come up with an auto-installer. So please download those floppies and check them out, IF you are planning to "depenguinate" a box.
floppy37_autoexec.ksh.fs.gzmd5=e0957d2c0ca0ef9279c5ed00cfd3bd0bMount it, and edit the autoexec.ksh for your needs!
floppy37_autoexec.ksh_serial.fs.gzmd5=2bd947968a0aa1aa05e39d7ebf4728a9Same as above, but with a 57600 baud serial console.
(See how I have done them in howto_pimp_my_openbsd_bootfloppy.txt)
Btw: All floppys are i386 only. Sorry.