From owner-freebsd-current  Wed Jan 31 20:34:02 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA20923
          for current-outgoing; Wed, 31 Jan 1996 20:34:02 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA20871
          for <freebsd-current@freebsd.org>; Wed, 31 Jan 1996 20:32:51 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA10717; Thu, 1 Feb 1996 15:28:51 +1100
Date: Thu, 1 Feb 1996 15:28:51 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199602010428.PAA10717@godzilla.zeta.org.au>
To: freebsd-current@freebsd.org, j@uriah.heep.sax.de
Subject: Re: invalid primary partition table: no magic
Sender: owner-current@freebsd.org
Precedence: bulk

>> >Well, what about those that are about to get a label the next second?
>> >New vn devices are often created by dd'ing the appropriate amount of
>> >data out of /dev/zero.
>> 
>> You can ignore the problem or dd an MBR or dd just an 0xAA55 signature.

>Hmm, but the first access does always cause this message.

You can edit the file before vnconfig'ing it.  You can also run fdisk -u
on the file to partition it.  This is a good way to learn how to use
fdisk (start with an MBR with random garbage on it and fix it).

>> That's right, they are expected to know enough to ignore the problem
>> or to use a binary editor to avoid it :-).  I get it all the time
>> for floppies and have been ignoring it.

>:-)

>(Run a ``make release''.  The doFS.sh tries to optimize the file
>system usage.  Be as nitpicking as i am about kernel messages, so i'm
>getting all of them logged onto any xterms where i'm logged in.  Now
>you know why i'm complaining... :)

Complain to the author of doFS.sh :-).

Bruce