On Sat, 2009-02-21 at 18:26 +0000, Steve Langasek wrote:
> Ok, I can confirm the behavior reported by the latest follow-ups.
> Rebooting after upgrade, the system hangs while starting udev and never
> advances. Downgrading to udev 1.37-2 and dmsetup 2:1.02.27-4ubuntu3
> corrects this problem (while using an older initramfs that doesn't
> contain udev 1.38).
>
> If this is specific to systems using devmapper for / then I suppose it
> makes sense to continue using this same bug for tracking the issue.
>
> ** Changed in: udev (Ubuntu Jaunty)
> Status: Fix Released => Confirmed
>
Uh,
Surely you're confusing two entirely separate bugs here?
You've just unmarked *this* bug, caused by the failure to
name /dev/mapper devices properly, because of the existance of bug
#332270?
Are you saying you can prove that this bug is not fixed?
Scott
--
Scott James Remnant
<email address hidden>
On Sat, 2009-02-21 at 18:26 +0000, Steve Langasek wrote:
> Ok, I can confirm the behavior reported by the latest follow-ups.
> Rebooting after upgrade, the system hangs while starting udev and never
> advances. Downgrading to udev 1.37-2 and dmsetup 2:1.02.27-4ubuntu3
> corrects this problem (while using an older initramfs that doesn't
> contain udev 1.38).
>
> If this is specific to systems using devmapper for / then I suppose it
> makes sense to continue using this same bug for tracking the issue.
>
> ** Changed in: udev (Ubuntu Jaunty)
> Status: Fix Released => Confirmed
>
Uh,
Surely you're confusing two entirely separate bugs here?
You've just unmarked *this* bug, caused by the failure to
name /dev/mapper devices properly, because of the existance of bug
#332270?
Are you saying you can prove that this bug is not fixed?
Scott
--
Scott James Remnant
<email address hidden>