From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Jeff Chua <jeffchua@silk.corp.fedex.com>
Cc: lkml <linux-kernel@vger.kernel.org>, torvalds@transmeta.com
Subject: Re: [bug] 2.6.0 COMMAND_LINE_SIZE <160???
Date: Wed, 24 Dec 2003 10:04:46 -0800 [thread overview]
Message-ID: <20031224100446.229721fe.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0312241804470.21411@silk.corp.fedex.com>
On Wed, 24 Dec 2003 18:11:54 +0800 (SGT) Jeff Chua <jeffchua@silk.corp.fedex.com> wrote:
|
| On Tue, 23 Dec 2003, Randy.Dunlap wrote:
|
| > On Tue, 23 Dec 2003 21:07:45 +0800 (SGT) Jeff Chua <jeffchua@silk.corp.fedex.com> wrote:
| >
| > Same processor arch. type in both .config files?
| > Same compiler version building them?
|
| Same for both.
|
| gcc 2.95.3 20010315
| glibc-2.2.5-34
|
| perhaps, it's loadlin or linld problem, or fat32 problem. The difference
| is lilo doesn't need _dos_ to boot.
Just curious, what kind of disk/OS config do you have where
using loadlin (or linld) is useful? Does it have anything to do
with not writing (updating) the MBR on disk?
Are there some booting alternatives for you?
Is Linux on the same hard disk as Windows (or DOS)?
| I tried to replace ./arch/i386/boot/setup.S with the one from 2.4.24-pre1
| and it seems to go further before it breaks.
Yes, not much difference in those source files.
| What's next to debug this?
Good question. I'm not sure. Anyone else have suggestions?
--
~Randy
prev parent reply other threads:[~2003-12-24 18:06 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
2003-12-24 10:11 ` Jeff Chua
2003-12-24 18:04 ` Randy.Dunlap [this message]
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=20031224100446.229721fe.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®