public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "jens m. noedler" <noedler@web.de>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] [resend] update Documentation/kernel-parameters.txt
Date: Mon, 14 Aug 2006 18:49:17 +0200	[thread overview]
Message-ID: <44E0A98D.9040203@web.de> (raw)

Hi,

This is just a little documentation update which applies to 2.6.18-rc4.
The patch was first send on 27. July 2006 to the LKML but nobody picked
it up, so here is the second chance. :-)

By the way: Does anybody know _why_ COMMAND_LINE_SIZE depends
on the architecture? Wouldn't it make sense to generalize it
for all platforms to e.g. 2048 characters?

Kind regards, Jens


Signed-off-by: jens m. noedler <noedler@web.de>

---

--- linux/Documentation/kernel-parameters.txt.orig	2006-08-13 23:40:31.000000000 +0200
+++ linux/Documentation/kernel-parameters.txt	2006-08-13 23:40:55.000000000 +0200
@@ -110,6 +110,13 @@ be entered as an environment variable, w
 it will appear as a kernel argument readable via /proc/cmdline by programs
 running once the system is up.
 
+The number of kernel parameters is not limited, but the length of the
+complete command line (parameters including spaces etc.) is limited to
+a fixed number of characters. This limit depends on the architecture
+and is between 256 and 4096 characters. It is defined in the file
+./include/asm/setup.h as COMMAND_LINE_SIZE.
+
+
 	53c7xx=		[HW,SCSI] Amiga SCSI controllers
 			See header of drivers/scsi/53c7xx.c.
 			See also Documentation/scsi/ncr53c7xx.txt.


-- 
jens m. noedler
  noedler@web.de
  pgp: 0x9f0920bb
  http://noedler.de




                 reply	other threads:[~2006-08-14 16:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=44E0A98D.9040203@web.de \
    --to=noedler@web.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox