From owner-freebsd-current  Sun Apr 30 05:46:52 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id FAA20960
          for current-outgoing; Sun, 30 Apr 1995 05:46:52 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA20953
          for <freebsd-current@FreeBSD.org>; Sun, 30 Apr 1995 05:46:39 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA26064; Sun, 30 Apr 1995 22:42:36 +1000
Date: Sun, 30 Apr 1995 22:42:36 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199504301242.WAA26064@godzilla.zeta.org.au>
To: freebsd-current@FreeBSD.org, root@io.cts.com
Subject: Re: How to write -current bootcode to disk?
Sender: current-owner@FreeBSD.org
Precedence: bulk

>> I'm not sure if the boot code is your only problem, but you can
>> rewrite it with
>> 
>> 	disklabel -B [-b /usr/mdec/sdboot] [-s /usr/mdec/bootsd] sd0
>> 
>> (The bracketed terms show the defaults.)
>> 
>> For a wd-style disk:  s/sd/wd/g

>Does this look good to you?

>io[511]# disklabel -B wd0
>Warning, revolutions/minute 0
>super block size 0
>io[512]# _

Not te right.  `disklabel -B' only writes the boot blocks, not the label.
I think there has to be a label before the boot blocks can be written.
The zero values are because there are bogus values in the label.  The
slice code makes it a bit easier to get a bogus label because it
constructs a dummy label with too many zero values.  Ideally you
should be able to say `disklabel /dev/wd0 >foo' to get a prototype label
and then `disklabel -R -r wd0 foo' to apply it.

Bruce