Bug#501306: update-grub fails silently with wrong device.map

[Robert Millan]

On Tue, Oct 28, 2008 at 10:27:29AM +0100, Raphael Hertzog wrote:
> 
> I have two concerns with this:
> - grub-probe can possibly fail in other circumstances and we will display
>   a misleading error message in those cases

grub-probe's messages aren't always appropiate for grub legacy's update-grub
(see #495909).  Besides, when "-t drive" fails it always means that device.map
is wrong.

> - the installation will still fail and most users have no idea what
>   device.map really is. If you go that route, you should at least give
>   them the command-line to execute to regenerate the device.map

Seems fine.

> But in the mean time for Grub 1, wouldn't the best solution simply be
> to regenerate the device.map in case of errors and try again ?

We tried this, and the solution was worse than the problem.  In the end it
had to be reverted.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."