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

[Raphael Hertzog]

On Tue, 28 Oct 2008, Robert Millan wrote:
> 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.
>
> > 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.

Sorry but I don't understand how you concile the two sentences that you
gave:
- on one side you say that "-t drive" only fails when device.map is wrong
  and you accept that we invite the user to regenerate it
- on the other side you tell me that trying to regenerate it only when "-t
  drive" fails has been tried and was worse than the problem

What do I miss ?

I could understand that always regenerating device.map would be worse and
wrong (and it's possibly this that got tried). But I only suggested to
regenerate it when we have serious suspicion that device.map is wrong
and _not_ always.

Cheers,
-- 
Raphaël Hertzog

Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/