Kevin> However, the drawback to making this switch is losing
Kevin> automatic boot-time volume discovery. Activating EVMS volumes
Kevin> will now require a call to a user-space utility, which will
Kevin> need to be added to the system's init scripts in order to
Kevin> activate the volumes on each boot.
Kevin> In addition, this switch complicates having the root filesystem
Kevin> on an EVMS volume.
Actually, this isn't as much of an issue with 2.5-as-it-will-soon-be.
The initramfs stuff solves the problem for booting, and is exactly
where boot-time discovery should be.
You will need to ensure sufficient integration with hotplug to deal
properly with such things as external devices (usb, 1394, cardbus/
pcmcia, iscsi, docking stations, etc) and media bays. But this should
be relatively easy, yes?
Without initramfs, I find current evms' in-kernel discovery to be very
beneficial from the end-user standpoint, but early userpsace is clearly
the proper place for boot-time volume discovery just as it is for eg
nfsroot or similar (gfs root, root on iscsi or usb or 1394).
In short, your new plans are the way to go, but do be sure to take
advantage of all the kernel offers or will offer.
-JimC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/