LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: Alon Bar-Lev <alon.barlev@gmail.com>,
Matt Domsch <Matt_Domsch@dell.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, johninsd@san.rr.com,
davej@codemonkey.org.uk, Riley@williams.name,
trini@kernel.crashing.org, davem@davemloft.net, ecd@brainaid.de,
jj@sunsite.ms.mff.cuni.cz, anton@samba.org, wli@holomorphy.com,
lethal@linux-sh.org, rc@rc0.org.uk, spyro@f2s.com,
rth@twiddle.net, avr32@atmel.com, hskinnemoen@atmel.com,
starvik@axis.com, ralf@linux-mips.org, matthew@wil.cx,
grundler@parisc-linux.org, geert@linux-m68k.org,
zippel@linux-m68k.org, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com, uclinux-v850@lsi.nec.co.jp,
chris@zankel.net
Subject: Re: [PATCH 00/26] Dynamic kernel command-line
Date: Mon, 4 Sep 2006 08:12:42 +0200 [thread overview]
Message-ID: <200609040812.43553.ak@suse.de> (raw)
In-Reply-To: <17659.26177.846522.226410@cargo.ozlabs.ibm.com>
> Under what circumstances do we actually need a command line of more
> than 256 bytes?
A common case is auto-installation of distributions. The auto installers
tends to get a lot of information passed using the kernel command line.
> It seems to me that if 256 bytes isn't enough, we should take a deep
> breath, step back, and think about whether there might be a better way
> to pass whatever information it is that's using up so much of the
> command line.
See it as the kernel's environment and it starts making more sense.
In theory another environment could be added, but then the command like
does the job already, except that it is a bit short sometimes.
-Andi
--
VGER BF report: H 0
next prev parent reply other threads:[~2006-09-04 6:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 21:50 [PATCH 00/26] Dynamic kernel command-line Alon Bar-Lev
2006-09-03 21:52 ` [PATCH 01/26] Dynamic kernel command-line - common Alon Bar-Lev
2006-09-03 22:10 ` Matthew Wilcox
2006-09-03 22:12 ` Alon Bar-Lev
2006-09-05 23:52 ` Bill Davidsen
2006-09-03 21:52 ` [PATCH 02/26] Dynamic kernel command-line - alpha Alon Bar-Lev
2006-09-03 21:53 ` [PATCH 03/26] Dynamic kernel command-line - arm Alon Bar-Lev
2006-09-03 21:54 ` [PATCH 04/26] Dynamic kernel command-line - arm26 Alon Bar-Lev
2006-09-03 21:54 ` [PATCH 05/26] Dynamic kernel command-line - avr32 Alon Bar-Lev
2006-09-03 21:55 ` [PATCH 06/26] Dynamic kernel command-line - cris Alon Bar-Lev
2006-09-03 21:55 ` [PATCH 07/26] Dynamic kernel command-line - frv Alon Bar-Lev
2006-09-03 21:56 ` [PATCH 08/26] Dynamic kernel command-line - h8300 Alon Bar-Lev
2006-09-03 21:56 ` [PATCH 09/26] Dynamic kernel command-line - i386 Alon Bar-Lev
2006-09-03 21:56 ` [PATCH 10/26] Dynamic kernel command-line - ia64 Alon Bar-Lev
2006-09-03 21:57 ` [PATCH 11/26] Dynamic kernel command-line - m32r Alon Bar-Lev
2006-09-03 21:57 ` [PATCH 12/26] Dynamic kernel command-line - m68k Alon Bar-Lev
2006-09-03 21:58 ` [PATCH 13/26] Dynamic kernel command-line - m68knommu Alon Bar-Lev
2006-09-03 21:58 ` [PATCH 14/26] Dynamic kernel command-line - mips Alon Bar-Lev
2006-09-03 21:59 ` [PATCH 15/26] Dynamic kernel command-line - parisc Alon Bar-Lev
2006-09-03 21:59 ` [PATCH 16/26] Dynamic kernel command-line - powerpc Alon Bar-Lev
2006-09-03 22:00 ` [PATCH 17/26] Dynamic kernel command-line - ppc Alon Bar-Lev
2006-09-03 22:00 ` [PATCH 18/26] Dynamic kernel command-line - s390 Alon Bar-Lev
2006-09-03 22:01 ` [PATCH 19/26] Dynamic kernel command-line - sh Alon Bar-Lev
2006-09-03 22:01 ` [PATCH 20/26] Dynamic kernel command-line - sh64 Alon Bar-Lev
2006-09-03 22:01 ` [PATCH 21/26] Dynamic kernel command-line - sparc Alon Bar-Lev
2006-09-03 22:02 ` [PATCH 22/26] Dynamic kernel command-line - sparc64 Alon Bar-Lev
2006-09-03 22:02 ` [PATCH 23/26] Dynamic kernel command-line - um Alon Bar-Lev
2006-09-03 22:03 ` [PATCH 24/26] Dynamic kernel command-line - v850 Alon Bar-Lev
2006-09-03 22:03 ` [PATCH 25/26] Dynamic kernel command-line - x86_64 Alon Bar-Lev
2006-09-03 22:03 ` [PATCH 26/26] Dynamic kernel command-line - xtensa Alon Bar-Lev
2006-09-03 23:33 ` [PATCH 00/26] Dynamic kernel command-line Paul Mackerras
2006-09-04 2:50 ` Nigel Cunningham
2006-09-04 8:32 ` Martin Schwidefsky
2006-09-04 8:42 ` Alon Bar-Lev
2006-09-04 5:05 ` Alon Bar-Lev
2006-09-04 6:12 ` Andi Kleen [this message]
2006-09-04 17:09 ` Luca
2006-09-04 1:01 ` Josh Boyer
2006-09-04 5:07 ` Alon Bar-Lev
2006-09-04 19:59 ` Josh Boyer
2006-12-02 10:47 Alon Bar-Lev
2007-01-18 12:58 [patch " 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=200609040812.43553.ak@suse.de \
--to=ak@suse.de \
--cc=Matt_Domsch@dell.com \
--cc=Riley@williams.name \
--cc=akpm@osdl.org \
--cc=alon.barlev@gmail.com \
--cc=anton@samba.org \
--cc=avr32@atmel.com \
--cc=chris@zankel.net \
--cc=davej@codemonkey.org.uk \
--cc=davem@davemloft.net \
--cc=ecd@brainaid.de \
--cc=geert@linux-m68k.org \
--cc=grundler@parisc-linux.org \
--cc=heiko.carstens@de.ibm.com \
--cc=hskinnemoen@atmel.com \
--cc=jj@sunsite.ms.mff.cuni.cz \
--cc=johninsd@san.rr.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rc@rc0.org.uk \
--cc=rth@twiddle.net \
--cc=schwidefsky@de.ibm.com \
--cc=spyro@f2s.com \
--cc=starvik@axis.com \
--cc=trini@kernel.crashing.org \
--cc=uclinux-v850@lsi.nec.co.jp \
--cc=wli@holomorphy.com \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).