From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Jeff Chua <jchua@fedex.com>
Subject: Re: how to increase commandline size (patch + changelog)
Date: Tue, 10 Oct 2006 18:08:12 +0200 [thread overview]
Message-ID: <871wpg17df.fsf@xs4all.nl> (raw)
In-Reply-To: <1160494821.1123.17.camel@basalt.austin.ibm.com> (Hollis Blanchard's message of "Tue, 10 Oct 2006 10:40:21 -0500")
Hollis Blanchard <hollis@penguinppc.org> writes:
> On Tue, 2006-10-10 at 16:38 +0200, Marco Gerards wrote:
>>
>> - Add some run-time argument to the loader to override the command
>> line length. But I do not like this either because it allows
>> breaking the Linux boot protocol.
>
> What exactly happens if we give the kernel a longer cmdline than it
> supports? Does it just truncate, or fail to boot?
It truncates.
> Why not allow users to pass as much as they want, and just warn them if
> it's >255?
I am not sure what the impact is. Linux has a memory map and I assume
the memory after the commandline is used for other things, or might be
overwritten.
--
Marco
next prev parent reply other threads:[~2006-10-10 16:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 0:45 how to increase commandline size (fwd) Jeff Chua
2006-10-10 1:03 ` how to increase commandline size (patch + changelog) Jeff Chua
2006-10-10 2:27 ` Hollis Blanchard
2006-10-10 3:08 ` Jeff Chua
2006-10-10 4:32 ` Hollis Blanchard
2006-10-10 4:59 ` Jeff Chua
2006-10-10 6:54 ` Marco Gerards
2006-10-10 6:52 ` Marco Gerards
2006-10-10 8:01 ` Jeff Chua
2006-10-10 12:35 ` Markus Laire
2006-10-10 14:38 ` Marco Gerards
2006-10-10 15:40 ` Hollis Blanchard
2006-10-10 16:08 ` Marco Gerards [this message]
2006-10-10 17:17 ` Jeff Chua
2006-10-13 18:53 ` Yoshinori K. Okuji
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871wpg17df.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@gnu.org \
--cc=jchua@fedex.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.