In message <[EMAIL PROTECTED]>, 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
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
