Comment # 17 on bug 907457 from Michael Chang

(In reply to Martin Pluskal from comment #16)
> (In reply to Michael Chang from comment #15)

> > And how to correct such errors via maintenance update ?
> Who is talking/requesting maintenance update here?

No one. Just to clarify the request here.

> > User has to correct
> > the device.map manually to reflect their (setup) changes anyway, so in this
> > regard it looks like "won't fix" or invalid.
> 
> It is my understanding that device.map containing kernel device name should
> not be created at all - but apparently this has happened, and since system
> was installed about two weeks ago, it is not unreasonable to expect that
> whatever caused it is still present.

I'm now looking into this as this is not what I expected also.

Meanwhile, a better fix for me is to think a better solution to not creating
device.map for knowing mbr device. Can we replace current approach with a
mbrdisk=/dev/disk-by-id/ ... in /etc/default/grub_installdevice ? Grub2 doesn't
require (hdX) names as root device, as it searches file system uuid and bios
disk order really doesn't matter for it. It only affects device to embed
bootloader images (that is the device to be used in grub2-install) and also
reinstall mbr or such.