From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: how to increase commandline size (patch + changelog)
Date: Fri, 13 Oct 2006 20:53:09 +0200 [thread overview]
Message-ID: <200610132053.09465.okuji@enbug.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0610110109360.8238@boston.corp.fedex.com>
On Tuesday 10 October 2006 19:17, Jeff Chua wrote:
> On Tue, 10 Oct 2006, Marco Gerards wrote:
> > Hollis Blanchard <hollis@penguinppc.org> writes:
> >> 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.
>
> Is it possible to "calculate" the needed offset for the exact cmdline
> length user pass in to grub and set this in grub2/kern/i386/pc/startup.S,
> then we don't need to worry about what the user pass in.
I do not like it very much. Linux specifies how it is loaded precisely, so we
should follow it carefully. Even if loadlin passes anything and it is useful
for you, it is a bug feature, and I don't appreciate that way.
BTW this is a kind of FAQ. I have answered the same question several times
until now. All I have been saying is that you should improve Linux before
changing GRUB. I thought someone took an action for this, but the
specification hasn't changed AFAIK.
Okuji
prev parent reply other threads:[~2006-10-13 18:53 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
2006-10-10 17:17 ` Jeff Chua
2006-10-13 18:53 ` Yoshinori K. Okuji [this message]
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=200610132053.09465.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.org \
/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.