From: Dave Jones <davej@redhat.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
alon.barlev@gmail.com, ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86_64, i386: Add command line length to boot protocol
Date: Mon, 12 Mar 2007 19:39:46 -0400 [thread overview]
Message-ID: <20070312233946.GE21835@redhat.com> (raw)
In-Reply-To: <20070312231220.GC9749@elf.ucw.cz>
On Tue, Mar 13, 2007 at 12:12:20AM +0100, Pavel Machek wrote:
> > 65535 characters? Are you for real?
> > Stop and think about just how big that is. If you have to create
> > a boot command line that long, you have serious, serious issues.
>
> Well, it is about the same size as my .config...
So? That has *nothing* to do with the boot command line
> I agree we are unlikely to hit it any time soon... I could imagine
> some (ab)uses, like fixed_acpi_bios=<lots of hex digits>, but those
> are ugly.
That's beyond ugly, and rapidly heading towards 'loony'.
> I could also imagine some uses where entire embedded machine
> is described at kernel commandline.
There are far better ways to get configuration into the kernel
than the boot command line.
Anyways, I'm tired of arguing for the sake of arguing.
I really could care less.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-03-12 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 18:14 [PATCH] x86_64, i386: Add command line length to boot protocol Bernhard Walle
2007-03-06 18:21 ` Dave Jones
2007-03-12 10:43 ` Pavel Machek
2007-03-12 20:55 ` Dave Jones
2007-03-12 23:12 ` Pavel Machek
2007-03-12 23:39 ` Dave Jones [this message]
2007-03-06 21:46 ` Alon Bar-Lev
2007-03-07 10:05 ` Vivek Goyal
-- strict thread matches above, loose matches on Subject: below --
2007-02-13 16:49 Bernhard Walle
2007-02-04 18:05 Bernhard Walle
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=20070312233946.GE21835@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alon.barlev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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