Christian Weeks wrote: > Hmm, I've regenerated a working one now... When I was examining it, it > did have vgchange contained within it, and also another vgchange under > /lib/lvm-200/ (or something similar)... I figured that one of the > scripts was somehow choking when it tried to execute the vgchange > executable in the initrd environment.
the new lvm-common looks for vgchange in the preferred /lib/lvm-XXX directory (200 for lvm2, 10 for lvm10) to determine which LVM usertools are installed, then looks in that directory for the command you wanted (in this case also vgchange, judging by the message!). Previously it just looked for the requested command which caused problems when LVM1 and LVM2 were both installed and you wanted a command that only existed for one version (e2fsadm was the actual culprit at the time). So, provided there is a vgscan in /lib/lvm-200, things /should/ work fine. ahem. > After I finish work this evening (about 10 hours from now) I'll build > and test that it's broken a broken one, for your perusal.. Is that OK? > That's fine by me. I'll look at it tomorrow morning my (UK) time. -- patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
