> No-one suggested 2.6.0 shipping without /something/, but having a dead
> LVM1 in _2.5_ doesn't help anyone.
Has the cabal (which does not exist) reached a verdict on the preferred
solution for 2.6 yet, so that we can sort of see where things are going?
Who has the hat "Volume Manager" on his gullible head? ;-)
I'll again pipe in for the radical solution: EVMS(powerful) on top of
device-mapper(elegant).
EVMS also shows promise as they are working on _open_ cluster support, which I
think will be one of the big things to happen in 2.7.
Rip out the compatibility cruft (LVM1, md and maybe others), as EVMS can do
everything they can as promised.
I'd understand if the compatibility "cruft" was still left in for 2.6 so
people could use the 2.6 timeframe to migrate and then finally kick it out
first thing in 2.7.
But then, I have a strong, explosive allergy to duplicated chunks of code.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
-- Principal Squirrel Research and Development, SuSE Linux AG ``Immortality is an adequate definition of high availability for me.'' --- Gregory F. Pfister- 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/