We are seeing grub network errors ("couldn't send network packet")
with UEFI PXE over an Emulex CNA. Debugging turned out that the
TX code path was running in a timeout waiting for the "recycle
buffer" to be returned. Time had an influence on this effect:
the menu and all required modules loaded us
installer doesn't support any more, and the major argument from the
Fedora devs for this (apart from sparing dev and QA resources) was the
warning emitted by GRUB when users try to install using block lists.
I am still convinced that the risk of boot loader corruption in that
scenario is extrem
bugzilla. Apologies to everyone that the
discussion went off-topic for this list.
Martin
--
Dr. Martin Wilck
PRIMERGY System Software Engineer
x86 Server Engineering
FUJITSU
Fujitsu Technology Solutions GmbH
Heinz-Nixdorf-Ring 1
33106 Paderborn, Germany
Phone: ++49 5251
l, this scenario requires the user to make a serious mistake
as root, and we all know that this can have all kinds of really bad
consequences.
AFAICS, for extX/Linux at least, there is no risk scenario that doesn't
involve this kind of serious user mistake.
Martin
--
Dr. Martin Wilck
PRIMERG
ly that the user mistake you describe must be
some manipulation of "core.img" itself (e.g. running grub2-mkimage but
now grub2-setup, which would classify as "mistake" in a blocklist setup)?
Martin
--
Dr. Martin Wilck
PRIMERGY System Software Engineer
x86 Server Engineering
It just wants you to do it
> consciously :)
Good :)
Martin
--
Dr. Martin Wilck
PRIMERGY System Software Engineer
x86 Server Engineering
FUJITSU
Fujitsu Technology Solutions GmbH
Heinz-Nixdorf-Ring 1
33106 Paderborn, Germany
Phone: ++49 5251 525 2796
Fax:
th bothering the
GRUB developers with. The validity of my use case should be discussed
elsewhere.
Martin
--
Dr. Martin Wilck
PRIMERGY System Software Engineer
x86 Server Engineering
FUJITSU
Fujitsu Technology Solutions GmbH
Heinz-Nixdorf-Ring 1
33106 Paderborn, Germany
Phone: +
ther Fedora's grub.cfg, or core.img instead of
> depending on a blocklist?
>
> https://bugzilla.redhat.com/show_bug.cgi?id=886502
As long as I install F18 on extX, yes. But as explained above, it
wouldn't be my preferred solution.
Martin
--
Dr. Martin Wilck
PRIMERGY System Software Engine
; Embedding enough of grub in the first track or a boot partition (as EFI
> systems support, as do a number of non x86 architectures) gives a much
> more reliable system since it can read anything else it needs using the
> filesystem and hence doesn't break if files are changed.
I understand
velopers didn't
seem to have a big issue with stage1_5 being loaded via block lists).
Recent GRUB2-based distributions like Fedora have removed this option,
and some users are dissatisfied with that. I would like to understand
what the actual risk is. So I'd appreciate examples for the &
> herefore I asked a similar question on ext4-devel.
The ext4 developers have made some interesting comments on the subject:
http://thread.gmane.org/gmane.comp.file-systems.ext4/36911On 02/07/2013
Regards
Martin
--
Dr. Martin Wilck
PRIMERGY System Software Engineer
x86 Server Engineer
corruption by setting the IMMUTABLE flag on core.img,
and I'd like to ask for the GRUB experts' opinion about that.
Finally I'd like to know if it's true that the GRUB team plans to drop
block list support altogether in a future version.
Regards
Martin Wilck
PS: It has been s
12 matches
Mail list logo
