public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alon Bar-Lev <alon.barlev@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
Date: Tue, 06 Sep 2005 23:19:53 +0300	[thread overview]
Message-ID: <431DF9E9.5050102@gmail.com> (raw)
In-Reply-To: <431628D5.1040709@zytor.com>

H. Peter Anvin wrote:
> Chris Wedgwood wrote:
> 
>> On Wed, Aug 31, 2005 at 02:29:44PM -0700, H. Peter Anvin wrote:
>>
>>> I think someone on the SYSLINUX mailing list already sent a patch to
>>> akpm to make 512 the default; making it configurable would be a
>>> better idea.  Feel free to send your patch through me.
>>
>>
>> So we really need this to be a configuration option?  We have too many
>> of those already.
> 
> 
> Maybe not.  Another option would simply be to bump it up significantly 
> (2x isn't really that much.)   4096, maybe.
> 
>     -hpa
> 

Hello Peter, I've written a reply before but got no response...

The idea of putting arguments in initramfs is not practical, 
since the whole idea is to have the same image of system and 
affecting its behavior using the boot loader...

I would like to push forward the idea to extend the 
command-line size...

All we need for start is an updated version of the "THE 
LINUX/I386 BOOT PROTOCOL" document that states that in the 
2.02+  protocol the boot loader should set cmd_line_ptr to a 
pointer to a null terminated string without any size 
restriction, specifying that the kernel will read as much as 
it can.

After I get this update, I will try to work with GRUB and LILO 
so that they will fix their implementation. Currently they 
claim that they understand that they should truncate the 
string to 256.

After that I will provide my simple  patch for setting the 
maximum size the kernel allocates in the configuration.

BTW: Do you know why the COMMAND_LINE_SIZE constant is located 
in two separate include files?

Best Regards,
Alon Bar-Lev.

  parent reply	other threads:[~2005-09-06 20:23 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4315B668.6030603@gmail.com>
2005-08-31 21:29 ` THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit H. Peter Anvin
2005-08-31 21:57   ` Chris Wedgwood
2005-08-31 22:01     ` H. Peter Anvin
2005-08-31 22:07       ` Chris Wedgwood
2005-08-31 22:12         ` Jesper Juhl
2005-08-31 22:14           ` Chris Wedgwood
2005-08-31 22:17             ` H. Peter Anvin
2005-08-31 22:18             ` Jesper Juhl
2005-08-31 22:24               ` H. Peter Anvin
2005-09-01  8:54                 ` Alon Bar-Lev
2005-08-31 22:12         ` H. Peter Anvin
2005-08-31 22:15           ` Chris Wedgwood
2005-09-01 20:48         ` [syslinux] " Peter Jones
2005-09-06 20:19       ` Alon Bar-Lev [this message]
2005-09-06 20:40         ` H. Peter Anvin
2005-09-06 20:49           ` Alon Bar-Lev
2005-10-06 22:49             ` Georg Lippold
2005-10-10 12:44               ` [PATCH] " Georg Lippold
2005-10-10 13:21                 ` Jesper Juhl
2005-10-10 13:32                   ` Alon Bar-Lev
2005-10-10 13:57                     ` Georg Lippold
2005-10-10 14:07                       ` Alon Bar-Lev
2005-10-10 14:53                   ` H. Peter Anvin
2005-10-10 14:59                     ` Alon Bar-Lev
2005-10-10 15:03                       ` H. Peter Anvin
2005-10-10 16:23                         ` Alon Bar-Lev
2005-10-10 17:02                           ` Bernd Petrovitsch
2005-10-10 15:46                     ` Georg Lippold
2005-10-10 15:49                       ` H. Peter Anvin
2005-10-10 17:16                         ` [PATCH 1/1] 2.6.14-rc3 x86: COMMAND_LINE_SIZE Georg Lippold
2005-10-10 18:24                           ` Alon Bar-Lev
2005-10-10 20:36                             ` Georg Lippold
2005-10-11  8:32                               ` Alon Bar-Lev
2005-10-11 16:50                                 ` Georg Lippold
2005-10-11 17:44                                   ` Alon Bar-Lev
2005-10-11 19:21                                     ` Andi Kleen
2005-10-11 19:24                                       ` Alon Bar-Lev
2005-10-11 20:21                                         ` Andi Kleen
2005-10-11 20:04                                           ` Alon Bar-Lev
2005-10-13 20:18                                             ` Georg Lippold
2005-10-11  1:48           ` THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit Coywolf Qi Hunt
2005-10-11  1:49             ` H. Peter Anvin

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=431DF9E9.5050102@gmail.com \
    --to=alon.barlev@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox