From owner-freebsd-current  Wed Jan 31 15:37:57 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA24648
          for current-outgoing; Wed, 31 Jan 1996 15:37:57 -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 PAA24608
          for <freebsd-current@FreeBSD.ORG>; Wed, 31 Jan 1996 15:37:36 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id KAA29774; Thu, 1 Feb 1996 10:35:55 +1100
Date: Thu, 1 Feb 1996 10:35:55 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199601312335.KAA29774@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

>> >uriah # vnconfig -c /dev/rvn0 fooimage 
>> >uriah # Jan 30 23:51:48 uriah /kernel: vn0: invalid primary partition table: no magic

>> For emulating physical disks that don't have partition tables or labels,
>> don't use the `-s labels' option to vnconfig.

>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.

>And why is it printed in the cited case, with an cd9660 image?  I
>haven't used -s labels.

Because -s labels was set previously.  I think all the options have to
live across opens so that they don't go away after you have vnconfig'ed
them, but perhaps they should go away when the device is unconfigured.

>I think it should at least go away for vn devices.  Anybody playing
>with vn is expected to know what (s)he's doing.  It's annoying enough

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.

Bruce