From owner-freebsd-current Sun Dec 12 7:38: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B318314E48 for ; Sun, 12 Dec 1999 07:37:57 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id QAA17570; Sun, 12 Dec 1999 16:37:30 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kevin Street Cc: "Jordan K. Hubbard" , FUJISHIMA Satsuki , Greg Lehey , current@FreeBSD.ORG Subject: Re: vinum start needs block device In-reply-to: Your message of "12 Dec 1999 10:34:14 EST." <879030896x.fsf@mired.eh.local> Date: Sun, 12 Dec 1999 16:37:29 +0100 Message-ID: <17568.945013049@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <879030896x.fsf@mired.eh.local>, Kevin Street writes: >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? I think that between the two of us, Greg and I have lost a oneline patch on the floor, try this: Index: vinumio.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinumio.c,v retrieving revision 1.45 diff -u -r1.45 vinumio.c --- vinumio.c 1999/10/13 03:17:59 1.45 +++ vinumio.c 1999/12/12 11:00:12 @@ -76,7 +76,7 @@ drive->devicename, drive->vp->v_usecount); } - if (drive->vp->v_type != VBLK) { /* only consider block devices */ + if (!vn_isdisk(drive->vp)) { /* only consider block devices */ VOP_UNLOCK(drive->vp, 0, drive->p); close_drive(drive); drive->lasterror = ENOTBLK; -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message