All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Alon Bar-Lev <alon.barlev@gmail.com>,
	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: Thu, 1 Sep 2005 00:12:00 +0200	[thread overview]
Message-ID: <9a874849050831151230d68d64@mail.gmail.com> (raw)
In-Reply-To: <20050831220717.GA14625@taniwha.stupidest.org>

On 9/1/05, Chris Wedgwood <cw@f00f.org> wrote:
> On Wed, Aug 31, 2005 at 03:01:57PM -0700, H. Peter Anvin wrote:
> 
> > Maybe not.  Another option would simply be to bump it up
> > significantly (2x isn't really that much.)  4096, maybe.
> 
> I wonder if we're not at the point where we need something different
> to what we have now.  The concept of a command-line works for passing
> simple state but for more complex things it's too cumbersome.

How about

a) bump the limit on the cmd line - it's still useful, and 256 really
is quite small for some things.

b) add a new boot option telling the kernel the name of some file in
initrd or similar from which to load additional options.

I don't know if b is feasible at all. It would mean that the kernel
would need to get a hold of the initrd or whatever quite early to be
able to process options from it, but if it's doable somehow it would
be a really neat thing.


-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2005-08-31 22:12 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 [this message]
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=9a874849050831151230d68d64@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=SYSLINUX@zytor.com \
    --cc=akpm@osdl.org \
    --cc=alon.barlev@gmail.com \
    --cc=cw@f00f.org \
    --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 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.