Known Issues (Release 4.1)

Project Status
Please note that this project is no longer active.

If you are interested in taking over the code base please let me know.

Overview

The most likely place for a failure is running release.sh. Here are some tips to help out.

First check the OpenBSD website: http://www.openbsd.org/faq/current.html http://www.openbsd.org/faq/faq5.html

release.sh, RAMDISKC - Disk is full

Symptoms: The output to stdout will look like this. The general error to look for is: /dev/svnd0a on /mnt/ was full 1.4M It is possible that when there are kernel updates, that the disk image will not fit on the floppy disk.

E.g. this could happen if it has been a few weeks after the stable release has been made and there were additions to the kernel.

Fix: Edit the RAMDISKC down to a smaller size, use the changes made to the RAMDISKC. http://www.openbsd.org/cgi-bin/cvsweb/src/sys/arch/i386/conf/RAMDISKC

For example, based on changes from the 3.7 release (version 1.53 of the file) and the current version (version 1.62 of the file) here are the changes made to 'shrink' the kernel and allow the release to complete:
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/arch/i386/conf/RAMDISKC.diff?r1=1.62&r2=1.53&f=h

Reference: Please see this thread: http://archives.neohapsis.com/archives/openbsd/2005-07/thread.html#701

Warning messages during image.sh

Symptoms: Get 'Device not configured' messages when trying to create new drive image. disklabel: Can't get bios geometry: Device not configured

...

fdisk -c 980 -h 8 -s 32 -f /usr/mdec/mbr -e svnd0
fdisk: sysctl(machdep.bios.diskinfo): Device not configured
Does not appear to impact successfull completion and is harmless.

Fix: None.

Reference: None.