Am Dienstag, den 13.10.2009, 17:20 +0000 schrieb Jim Bailey:
>
> What I really need to see is someone from the grub2 team to triage this
> bug but with 137 and counting open bugs against grub2 and 2 weeks to
> release I am quite worried.
I know the problem since a few months and even sent a first patch in
June for my nvidia dmraid devices to upstream.
But the problem is that the internal design used by grub-probe to map
Linux devices to GRUB devices doestn't work with any non real harddisk
devices like dmraid and multipath.
For LVM/mdraid we don't need to do this as we have native support for
them.
Am Dienstag, den 13.10.2009, 17:20 +0000 schrieb Jim Bailey:
>
> What I really need to see is someone from the grub2 team to triage this
> bug but with 137 and counting open bugs against grub2 and 2 weeks to
> release I am quite worried.
I know the problem since a few months and even sent a first patch in
June for my nvidia dmraid devices to upstream.
But the problem is that the internal design used by grub-probe to map
Linux devices to GRUB devices doestn't work with any non real harddisk
devices like dmraid and multipath.
For LVM/mdraid we don't need to do this as we have native support for
them.
That discussion is here: lists.gnu. org/archive/ html/grub- devel/2009- 07/msg00509. html lists.gnu. org/archive/ html/grub- devel/2009- 08/msg00065. html
http://
http://
For me this is just not a high priority.
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer