On Tue, 6 Jun 2006, Jonas Smedegaard wrote: > It is wrong to assume a purely no-older-than-etch system: Imagine the > process of upgrading from sarge to etch...
aha... now i understand :) what you really need is some sort of weak dependency which implies that if the package is already installed then it must be a specific rev. > Can someone come up with a test command that does not mess with actual > devices, and returns true for versions of mdadm that properly supports > "-Ac partitions"? Or even better, a complete patch for yaird? ok cool... well according to the mdadm changelog the -Ac partitions bug was fixed in 1.10.0 ... so we'd want to stick something like this into Templates.cfg !case "`mdadm --version 2>&1`" in ! mdadm\ -\ v1.[1-9][^0-9]*) ! mdadm --assemble <TMPL_VAR NAME=target> --uuid <TMPL_VAR NAME=uuid> \ ! <TMPL_LOOP NAME=components> <TMPL_VAR NAME=dev></TMPL_LOOP> ! ;; ! *) ! mdadm -Ac partitions <TMPL_VAR NAME=target> --uuid <TMPL_VAR NAME=uuid> ! ;; !esac hmm well i need to handle mdadm v0.x too i guess... i'm trying to avoid added grep to the initrd. let me know if the above is generally what you're looking for -- an alternative is to test the mdadm version at mkinitrd time but i didn't see a way to do that without mucking in the perl (which i don't mind doing either). i probably won't be able to test a patch for a week or two though. thanks -dean -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
