From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Jeff Chua <jeffchua@silk.corp.fedex.com>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [bug] 2.6.0 COMMAND_LINE_SIZE <160???
Date: Tue, 23 Dec 2003 09:21:04 -0800 [thread overview]
Message-ID: <20031223092104.6bc9f634.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0312232102340.5732@silk.corp.fedex.com>
On Tue, 23 Dec 2003 21:07:45 +0800 (SGT) Jeff Chua <jeffchua@silk.corp.fedex.com> wrote:
|
| I can't seems to pass more than 160 bytes on command line when booting
| linux-2.6.0. 2.4.24 is ok.
|
| Booting via loadlin, but I've tried linld, still the same problem.
|
| It hangs after "Ok, booting the kernel".
So 2.4.24-pre works OK for you.
2.6.0 works OK for me with a command line length of 219 bytes
(about half of it doesn't matter for booting, but it's all
there in /proc/cmdline). Using lilo.
Same processor arch. type in both .config files?
Same compiler version building them?
--
~Randy
MOTD: Always include version info.
next prev parent reply other threads:[~2003-12-23 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 13:07 Jeff Chua
2003-12-23 17:21 ` Randy.Dunlap [this message]
2003-12-24 10:11 ` Jeff Chua
2003-12-24 18:04 ` Randy.Dunlap
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=20031223092104.6bc9f634.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=jeffchua@silk.corp.fedex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®