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

[Robert Millan]

On Wed, Oct 29, 2008 at 09:22:18AM +0100, Raphael Hertzog wrote:
> 
> Ok, if you really don't want to replace the device.map on the fly,
> let me propose yet another solution: in case of grub-probe failure, we
> regenerate a device.map in a temporary file and we try grub-probe again
> but with --device-map pointing to this temporary file. That way the
> default device.map doesn't get modified and we still have a chance to make
> it work by default. We would display a message saying that the device.map
> has to be verified if we succeed through the fallback solution.
> 
> Please find the corresponding patch attached.

I don't like that it is an ugly hack, in the sense that we're trying to stop
reliing on this sort of heuristic, and this only works around the problem.
Our long-term fix is to use only reliable identifiers like UUIDs.

But since all of this is temporary, I suppose we could live with it.  Felix,
what do you think?

-- 
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."