From owner-freebsd-hackers  Tue Oct  1 01:33:14 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA06521
          for hackers-outgoing; Tue, 1 Oct 1996 01:33:14 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA06508
          for <FreeBSD-hackers@FreeBSD.org>; Tue, 1 Oct 1996 01:33:04 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id SAA19477; Tue, 1 Oct 1996 18:26:45 +1000
Date: Tue, 1 Oct 1996 18:26:45 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199610010826.SAA19477@godzilla.zeta.org.au>
To: bde@zeta.org.au, jkh@time.cdrom.com
Subject: Re: disklabeling a vn device
Cc: FreeBSD-hackers@FreeBSD.org, guido@gvr.win.tue.nl, phk@critter.tfs.com
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

I wrote:
>...
>To avoid this problem, you have to create a valid BSD slice of the
>correct size or the special invalid slice table that says that the
>disk is "dedicated".  Copies of the special table are kept in
>bootstraps.  The simplest way to put one on `vnfile' is:
>
>	dd if=/usr/mdec/boot1 of=vnfile conv=notrunc
>
>It should also be possible to use `fdisk -i vnfile', but device
>independence of fdisk is currently broken - it mungs the pathname.

This is still too hard.  It should be possible to just newfs /dev/rvn0.
Device independence of newfs seems to have always been broken.

Bruce