From: Alon Bar-Lev <alon.barlev@gmail.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit - Resubmit
Date: Mon, 6 Feb 2006 09:38:40 +0200 [thread overview]
Message-ID: <9e0cf0bf0602052338p127918f4l1f50b9583ce8d31@mail.gmail.com> (raw)
In-Reply-To: <20060205201844.447efd20.rdunlap@xenotime.net>
Hello,
Since I removed this from the main text:
>-The kernel command line is a null-terminated string currently up to
>-255 characters long, plus the final null. A string that is too long
>-will be automatically truncated by the kernel, a boot loader may allow
>-a longer command line to be passed to permit future kernels to extend
>-this limit.
>+The kernel command line is a null-terminated string. A string that is too
>+long will be automatically truncated by the kernel.
I thought it would be appropriate to add it to the older (<2.02) boot
protocols specific notes.
>+ The kernel command line *must* be 256 bytes including the
>+ final null.
I've removed the 256 limit from the 2.02 boot protocol since grub and
lilo guys did not understand the comment: "a boot loader may allow a
longer command line to be passed to permit future kernels to extend
this limit.", they both truncate the command-line to 256 (hard coded).
I thought that it best to make clear that the limit on the
command-line length is determined by the kernel and not by the boot
loader.
I can remove the addition.
Best Regards,
Alon Bar-Lev
On 2/6/06, Randy.Dunlap <rdunlap@xenotime.net> wrote:
> On Fri, 03 Feb 2006 22:32:29 +0200 Alon Bar-Lev wrote:
>
> >
> > Extending the kernel parameters to a size of 1024 on boot
> > protocol >=2.02 for i386 and x86_64 architectures.
> >
> > Signed-off-by: Alon Bar-Lev <alon.barlev@gmail.com>
> >
> > ---
> >
> > Hello,
> >
> > This patch was submitted a long ago, but did not find its
> > way into the kernel, but was not rejected as well.
> >
> > Current implementation allows the kernel to receive up to
> > 255 characters from the bootloader.
> >
> > In current environment, the command-line is used in order to
> > specify many values, including suspend/resume, module
> > arguments, splash, initramfs and more.
> >
> > 255 characters are not enough anymore.
> >
> > Please consider to merge.
>
> Please explain this comment and why it is being added:
>
> + The kernel command line *must* be 256 bytes including the
> + final null.
> +
>
> thanks,
> ---
> ~Randy
>
next prev parent reply other threads:[~2006-02-06 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 20:32 Alon Bar-Lev
2006-02-06 4:18 ` Randy.Dunlap
2006-02-06 7:38 ` Alon Bar-Lev [this message]
2006-02-06 8:43 ` Barry K. Nathan
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=9e0cf0bf0602052338p127918f4l1f50b9583ce8d31@mail.gmail.com \
--to=alon.barlev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®