Kevin,
this must have been a very painful decision. I publically applaud you for
making it.
The great benefit from EVMS is the unified toolset for the administrator. It
is impressive that you are willing to rework this on top of a "Not Invented
Here" framework. I'm not sure whether my ego would have allowed the same
decision ;-)
The Device-Mapper seems to appeal more to the kernel community (and I'll agree
it is quite impressively neat code), and the EVMS management aspect appeals to
users. I hope that merging these will appeal to all. (It certainly does to
me).
I'm most certainly looking forward to seeing the clustering support comeing
;-)
Now, an interesting question is whether the md modules etc will simply be
continued to be used or whether they'll make use of the DM engine too? Can
they be made "plugins" to DM or the EVMS framework? Or even, could EVMS (in
theory) parse the meta-data from a legacy md device and just setup a DM
mapping for it? That would appeal to me quite a bit. I really need to start
reading up on it...
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
-- Principal Squirrel SuSE Labs - Research & Development, SuSE Linux AG "If anything can go wrong, it will." "Chance favors the prepared (mind)." -- Capt. Edward A. Murphy -- Louis Pasteur - 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/