[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grub-devel
Subject:    Re: Grub2: add UEFI support for accessing memory address above 4GB.
From:       Michel Hermier <michel.hermier () gmail ! com>
Date:       2017-03-08 11:46:07
Message-ID: CAAZ5spCJrPDy-JMiVw=6DbDe48DGEFU8EeK5X-h3Q4fMja1xow () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Le 8 mars 2017 10:58 AM, "Brendan Trotter" <btrotter@gmail.com> a =C3=A9cri=
t :

Hi,


> Le 7 mars 2017 17:24, "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
a =C3=A9crit :
>
> I'd like to know more about the usecase. Generally you should avoid
downloading or loading too large files in bootloader. I.a. TFTP protocol
has problems with files over about 100MIB. Generally you should download
only kernel + initrd and rest of the system should be on iSCSI or NFS.

"Ancient TFTP" (with 512-byte blocks and 16-bit block numbers that aren't
allowed to roll over) has problems with files over 32 MiB. "Modern
TFTP" (with larger/negotiated block size and 16-bit block numbers that are
allowed to roll over) has no limit at all.


> On Tue, Mar 7, 2017, 09:09 Michel Hermier <michel.hermier@gmail.com>
wrote:
>
> Because I don't trust automatic detection. Even if one say it is 200%
safe, there is allways that machine that nobody heard of that will fail. So
having user being able to force some values is usually a good idea.

What do you think is more reliable: well designed auto-detection code that
was written and tested by competent developer/s that know exactly what
they're doing and why; or a random user who failed read the documentation,
thought it did something else, screwed everything up, then blames you for
their mistake, then blames you for giving them the ability to make the
mistake?


Something in the middle, have a well tuned detection, and user defined
variable (with a taint mechanism, that *blame/inform* the user that he use
a sensible option)

[Attachment #5 (text/html)]

<div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">Le  8 \
mars 2017 10:58 AM, &quot;Brendan Trotter&quot; &lt;<a \
href="mailto:btrotter@gmail.com">btrotter@gmail.com</a>&gt; a écrit  :<br \
type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div class="quoted-text"><br><br>&gt; \
Le 7 mars 2017 17:24, &quot;Vladimir &#39;phcoder&#39; Serbinenko&quot; &lt;<a \
href="mailto:phcoder@gmail.com" target="_blank">phcoder@gmail.com</a>&gt; a écrit \
:<br>&gt;</div><div><div class="quoted-text">&gt; I&#39;d like to know more about the \
usecase. Generally you should avoid downloading or loading too large files in \
bootloader. I.a. TFTP protocol has problems with files over about 100MIB. Generally \
you should download only kernel + initrd and rest of the system should be on iSCSI or \
NFS.<br></div><div><div><br></div><div>&quot;Ancient TFTP&quot; (with 512-byte blocks \
and 16-bit block numbers that aren&#39;t allowed to roll over) has problems with \
files over 32 MiB. &quot;Modern TFTP&quot;  (with larger/negotiated block size and \
16-bit block numbers that are allowed to roll over) has no limit at all.</div><div \
class="quoted-text"><div><br></div><div><br></div><div>&gt; On Tue, Mar 7, 2017, \
09:09 Michel Hermier &lt;<a href="mailto:michel.hermier@gmail.com" \
target="_blank">michel.hermier@gmail.com</a>&gt; \
wrote:<br></div><div>&gt;</div></div><div class="quoted-text"><div>&gt; Because I \
don&#39;t trust automatic detection. Even if one say it is 200% safe, there is \
allways that machine that nobody heard of that will fail. So having user being able \
to force some values is usually a good idea.<br><br><div class="gmail_extra"> \
</div></div></div></div><div>What do you think is more reliable: well designed \
auto-detection code that was written and tested by competent developer/s that know \
exactly what they&#39;re doing and why; or a random user who failed  read the \
documentation, thought it did something else, screwed everything up, then blames you \
for their mistake, then blames you for giving them the ability to make the \
mistake?</div></div></div></blockquote></div></div></div><div \
dir="auto"><br></div><div dir="auto">Something in the middle, have a well tuned \
detection, and user defined variable (with a taint mechanism, that *blame/inform* the \
user that he use a sensible option)</div></div>



_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic