From owner-freebsd-current  Tue Jan 30 19:43:29 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA07818
          for current-outgoing; Tue, 30 Jan 1996 19:43:29 -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 TAA07806
          for <freebsd-current@FreeBSD.org>; Tue, 30 Jan 1996 19:43:13 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA11342; Wed, 31 Jan 1996 14:38:58 +1100
Date: Wed, 31 Jan 1996 14:38:58 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199601310338.OAA11342@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

>Couldn't we find a way to stop this?

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

>It's starting to get annoying.  Not only that any /dev/zero-created
>empty file that we are about to disklabel during the release process
>causes this bogus warning (until it's disklabeled -B), but fooimage
>above was an cd9660 image, so the warning is not of much use.

>Since the warning is not of interest for ``ordinary people'' anyway,
>i'd vote for hiding it behind some debugging option (perhaps enabled
>via sysconfig).

It is an error for disks that should have a partition table, but
since there is no way of telling which disks those are, it is hard
to tell when to suppress the warning.

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

Bruce