From owner-freebsd-current Sun Dec 12 7:34:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id F076F14CE1 for ; Sun, 12 Dec 1999 07:34:15 -0800 (PST) (envelope-from street@iname.com) Received: from mired.eh.local ([24.64.136.188]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991212153415.SYIZ9271.mail.rdc2.on.home.com@mired.eh.local>; Sun, 12 Dec 1999 07:34:15 -0800 Received: (from kws@localhost) by mired.eh.local (8.9.3/8.9.3) id KAA34145; Sun, 12 Dec 1999 10:34:15 -0500 (EST) (envelope-from kws) To: "Jordan K. Hubbard" Cc: FUJISHIMA Satsuki , Greg Lehey , current@FreeBSD.ORG Subject: Re: vinum start needs block device References: <6104.944978331@zippy.cdrom.com> From: Kevin Street Date: 12 Dec 1999 10:34:14 -0500 In-Reply-To: "Jordan K. Hubbard"'s message of "Sat, 11 Dec 1999 21:58:51 -0800" Message-ID: <879030896x.fsf@mired.eh.local> Lines: 18 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Biscayne" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > > Since the recent block device vanishment, MAKEDEV all and my vinum > > volumes have failed to start. > > Please read /usr/src/UPDATING if you're going to track -current > these days. The reason for this is clearly documented at the > top of that file and won't be a problem in -release since the > correct device nodes will be created initially. Jordan, I don't understand your answer. Using the new MAKEDEV is what causes vinum to fail. Won't -release be using the new MAKEDEV? Greg, is there a mechanism to transition an existing vinum installation to the new device nodes? -- Kevin Street street@iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message