[Bastian Blank] > Why lvm here, not lvm2? To avoid having to change the script currently depending on lvm. In my test setup, it is checkfs.sh, cryptdisks, mountall.sh and resize_lvm. I have no idea which other scripts also depend on lvm and not lvm2. I can update checkfs.sh, mountall.sh and resize_lvm, but cryptdisks is out of reach.
It might be a good idea to provide lvm2, instead but it need to be coordinated with other packages. It might be a good idea to provide 'lvm2 lvm' in the transition period. I'm not quite sure what the effect of multiple provides is, but it seem to work in most cases. >> +# Required-Start: mountdevsubfs >> +# Required-Stop: >> +# Should-Start: udev devfsd raid2 mdadm cryptdisks-early > > devfsd and raid2 is old. Yeah. I suspect I added them when I started working on this for Sarge. If the packages no longer exist in unstable, it might be a good idea to drop them. Or drop them anyway, and tell the maintainers of the devfs and raid packages to reverse depend on lvm instead. Reverse dependencies started working a few days ago, and it will make it easier for maintainers to put their init.d script in the right place. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
