Date: 12 Dec 1999 10:34:14 -0500 From: Kevin Street <street@iname.com> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: FUJISHIMA Satsuki <k5@cheerful.com>, Greg Lehey <grog@lemis.com>, current@FreeBSD.ORG Subject: Re: vinum start needs block device Message-ID: <879030896x.fsf@mired.eh.local> In-Reply-To: "Jordan K. Hubbard"'s message of "Sat, 11 Dec 1999 21:58:51 -0800" References: <6104.944978331@zippy.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Jordan K. Hubbard" <jkh@zippy.cdrom.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?879030896x.fsf>