after some hacking, downloading and patching (and some good advice), i believe i've built and installed (almost) all of the LVM2 and device mapper stuff for 2.6.0. there's only one last issue. the LVM2 source builds a whole new set of lvm commands but, rather than installing them into /sbin as the current lvm commands are, it appears to install a single executable, "lvm", and symlinks everything else to it (also in the /sbin directory). the only drawback is that the current lvm RPM already has commands with those names in /sbin and, since i have no interest in LVM1 support, the obvious approach is to remove the current lvm rpm, then "make install" to add the new ones (which i built without LVM1 support). at the moment, this causes a dependency error since the new mkinitrd depends on the current lvm rpm, so my plan is just to force removal of the current lvm rpm (dependencies be damned), then "make install" the new command and symlinks. are there any obvious drawbacks to this plan? rday -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
