On Fri, 15 Aug 2008 18:36:49 +0200 Felix Zielcke <[EMAIL PROTECTED]> wrote:
>>>> -- why does adding an "fd0" entry to "device.map" not resolve this >>>> error? >> >> If (fd0) is an "unknown device", then why doesn't "(fd0) /dev/fd0" >> make it known? > > Because the file is called device.map > Which means map linux devices to grub devices. -- which was my point. I appreciate that English is a second language for you, but perhaps if you were to review the distinction between "does" and "does not", these questions would seem more sensible. >>> I assume you don't know enough C to understand the whole sourcecode. >> >> You assume wrong. > > I still assume that, because you even failed to choose the right > severity of this report. The Debian documentation about this is very > clear. Yes, it says "failure to boot" == "critical". That seems clear enough. But perhaps you have a different interpretation? > Honourly I don't have still any motivation at all for this report. > > Luckly I have already forwarded this to grub-devel and somebody had an > idea. Forget it, I'll fix it myself, and send the patch to upstream. > So now you can proof how much your C knowledge is and your understanding > of GRUB sourcecode. > > please add to disk/lvm.c to the mod_init function: > grub_errno = GRUB_ERR_NONE; This does nothing to explain why grub is worried about (fd0), when none of its inputs mention any such device, as I pointed out several times already. But I suppose that your lofty arrogance prohibits you from addressing such mundane questions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
