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>,
	"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 22:01:21 +0300	[thread overview]
Message-ID: <443FF181.6000004@gmail.com> (raw)
In-Reply-To: <443FEDF9.6050203@zytor.com>

H. Peter Anvin wrote:
> 
> Well, obviously, since apparently LILO doesn't properly null-terminate 
> long command line.
> 
> Thinking about it a bit, the way to deal with the LILO problem is 
> probably to actually *usw* the boot loader ID byte we've had in there 
> since the 2.00 protocol.  In other words, if the boot loader ID is 0x1X 
> where X <= current version (I don't know how LILO manages this ID) then 
> truncate the command line to 255 bytes; when this is fixed in LILO then 
> LILO gets to bump its boot loader ID version number.
> 
>     -hpa

I don't understand...

If LILO worked until now, it should continue to work after 
applying this patch, since nothing was changed from its 
perspective. It will continue to provide 255 characters + 
null command line, so even if you have 1024 max 
command-line, then you will still receive truncated to 255 
chars.

What I think is that the boot.txt should be clearer... But 
if you think that this patch can be applied without making 
any change to the documentation that's will also be great! I 
will try to deal with boot loaders developers afterwards...

Best Regards,
Alon Bar-Lev.

  reply	other threads:[~2006-04-14 18:59 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
2006-04-14 18:09   ` Alon Bar-Lev
2006-04-14 18:46     ` H. Peter Anvin
2006-04-14 19:01       ` Alon Bar-Lev [this message]
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=443FF181.6000004@gmail.com \
    --to=alon.barlev@gmail.com \
    --cc=barryn@pobox.com \
    --cc=bunk@fs.tum.de \
    --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