Bug#554790: This breaks device.map on upgrade

2010-07-20 Thread Vladimir 'φ-coder/phcoder' Serbinenko
On 07/12/2010 12:38 PM, Colin Watson wrote: [Re-sending with full quoting and from my @ubuntu.com account so that it doesn't get stuck in the grub-devel moderation queue.] On Mon, Jul 12, 2010 at 12:26:21AM +0100, Colin Watson wrote: On Fri, Jul 09, 2010 at 08:01:12AM +0400, Vadim Solomin

Bug#554790: This breaks device.map on upgrade

2010-07-20 Thread Colin Watson
On Tue, Jul 20, 2010 at 03:02:47PM +0200, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 07/12/2010 12:38 PM, Colin Watson wrote: Vladimir, would this patch need a copyright assignment? Most of it seems pretty straightforward; in fact I doubt that it would come out very much different if

Bug#554790: This breaks device.map on upgrade

2010-07-12 Thread Colin Watson
[Re-sending with full quoting and from my @ubuntu.com account so that it doesn't get stuck in the grub-devel moderation queue.] On Mon, Jul 12, 2010 at 12:26:21AM +0100, Colin Watson wrote: On Fri, Jul 09, 2010 at 08:01:12AM +0400, Vadim Solomin wrote: This fix, at least in its current form,

Bug#554790: This breaks device.map on upgrade

2010-07-11 Thread Colin Watson
On Fri, Jul 09, 2010 at 08:01:12AM +0400, Vadim Solomin wrote: This fix, at least in its current form, has a potential to break grub for users having more than one drive, unless they are careful enough to check and fix their device.map after upgrade. Old mkdevicemaps assigned grub device

Bug#554790: This breaks device.map on upgrade

2010-07-08 Thread Vadim Solomin
This fix, at least in its current form, has a potential to break grub for users having more than one drive, unless they are careful enough to check and fix their device.map after upgrade. Old mkdevicemaps assigned grub device numbers in the sort order of kernel device names, which was right