From: "Ro0tSiEgE" <ro0tsiege@bjstuff.com>
To: <linux-kernel@vger.kernel.org>
Subject: Booting Issue
Date: Sat, 2 Feb 2002 17:27:42 -0600 [thread overview]
Message-ID: <002901c1ac41$361daa10$ed00000a@citrix.bjstuff.com> (raw)
I have a big booting issue. Apparently, it's something in my config file,
that makes my kernel panic saying no init found. Now even though I have some
external patches applied, I know that can't be the issue because I've tried
the same config without the patches. If somebody could PLEASE look at my
config and tell me what I'm doing wrong, I've been fighting with this
problem for over a month, every kernel I've tried to make, no matter what
version, with or without any patches, says I have no init found. But kernels
I've made in the past work fine, so I'm thinking it's gotta be something
with my config. Please look at my config (this is 2.4.18-pre7-ac2), its
posted at: http://www.bjstuff.com/config
Thanks very much,
Brad Parker
next reply other threads:[~2002-02-02 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-02 23:27 Ro0tSiEgE [this message]
[not found] <000001c1ac7e$07899b40$0200a8c0@mainframe>
2002-02-03 20:08 ` Booting Issue Ro0tSiEgE
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='002901c1ac41$361daa10$ed00000a@citrix.bjstuff.com' \
--to=ro0tsiege@bjstuff.com \
--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