public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alon Bar-Lev <alon.barlev@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	SYSLINUX@zytor.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
Date: Wed, 31 Aug 2005 14:29:44 -0700	[thread overview]
Message-ID: <43162148.9040604@zytor.com> (raw)
In-Reply-To: <4315B668.6030603@gmail.com>

Alon Bar-Lev wrote:
> 
> Hello Peter,
> 
> I am sorry that I am contacting you directly... Please refer me to 
> correct contact if you are not the one.
> 
> Lately, I've found that 256 bytes long kernel parameters are not enough 
> for my configuration. 
> 
> I've found the place where the kernel defines the length, I've actually 
> found it in two places... I cannot understand why...
> 
> include/asm-i386/param.h: #define COMMAND_LINE_SIZE 256
> include/asm-i386/setup.h: #define COMMAND_LINE_SIZE 256
> 
> Now... I've added an entry in the kernel configuration menu so that I 
> can define these constants using menuconfig. 
> 
> I was quite happy...
> 
> But then I've got into a discussion with grub's development team...
> 
> From what I've read in the Documentation/i386/boot.txt I understood 
> that if I use boot protocol 2.02+ there should be no reason for 256 byte 
> limitation on the string pointed by the cmd_line_ptr, so I guessed they 
> will deliver the command-line twice once for the old protocol truncated, 
> and once for the new protocol not truncated.
> 
> Grub and Lilo approach is to point  the cmd_line_ptr to the old 
> protocol's command line, thus truncating it to 256.
> 
> I'm just wondering... Can the 256 limit be broken, without modifying the 
> boot protocol?
> 
> I think it can... But I need a formal answer so I can push it forward.
> 

Yes, it can.  Several people on the SYSLINUX mailing list have tried 
this, and it works just fine.  The current version of SYSLINUX has a 
limit of 511 characters (because of memory management reasons inside 
SYSLINUX) instead of 255 (plus null).

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.

	-hpa


       reply	other threads:[~2005-08-31 21:30 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 ` H. Peter Anvin [this message]
2005-08-31 21:57   ` THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit 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
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=43162148.9040604@zytor.com \
    --to=hpa@zytor.com \
    --cc=SYSLINUX@zytor.com \
    --cc=akpm@osdl.org \
    --cc=alon.barlev@gmail.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