All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alon Bar-Lev <alon.barlev@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Barry K. Nathan" <barryn@pobox.com>,
	Adrian Bunk <bunk@fs.tum.de>
Subject: Re: [PATCH][TAKE 3] THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
Date: Fri, 14 Apr 2006 10:53:51 -0700	[thread overview]
Message-ID: <443FE1AF.8050507@zytor.com> (raw)
In-Reply-To: <443EE4C3.5040409@gmail.com>

Alon Bar-Lev wrote:
> diff -urNp linux-2.6.16/Documentation/i386/boot.txt linux-2.6.16.new/Documentation/i386/boot.txt
> --- linux-2.6.16/Documentation/i386/boot.txt	2006-03-20 07:53:29.000000000 +0200
> +++ linux-2.6.16.new/Documentation/i386/boot.txt	2006-04-14 01:55:47.000000000 +0300
> @@ -235,11 +235,8 @@ loader to communicate with the kernel.  
>  relevant to the boot loader itself, see "special command line options"
>  below.
>  
> -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.
>  
>  If the boot protocol version is 2.02 or later, the address of the
>  kernel command line is given by the header field cmd_line_ptr (see
> @@ -260,6 +257,9 @@ command line is entered using the follow
>  	covered by setup_move_size, so you may need to adjust this
>  	field.
>  
> +       The kernel command line *must* be 256 bytes including the
> +       final null.
> +
>  
>  **** SAMPLE BOOT CONFIGURATION
>  

This chunk is confusing at the very best.

	-hpa

  parent reply	other threads:[~2006-04-14 17:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 23:54 [PATCH][TAKE 3] THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit Alon Bar-Lev
2006-04-14  0:38 ` Joshua Hudson
2006-04-14 17:53 ` H. Peter Anvin [this message]
2006-04-14 18:09   ` Alon Bar-Lev
2006-04-14 18:46     ` H. Peter Anvin
2006-04-14 19:01       ` Alon Bar-Lev
2006-04-14 19:04         ` H. Peter Anvin
2006-04-14 19:05         ` 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=443FE1AF.8050507@zytor.com \
    --to=hpa@zytor.com \
    --cc=alon.barlev@gmail.com \
    --cc=barryn@pobox.com \
    --cc=bunk@fs.tum.de \
    --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 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.