From: "Dean McEwan" <dean.mcewan@eudoramail.com>
To: "John Bradford" <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: I compiled the kernel but it doesn't do any thing, its a bit like typing "halt
Date: Thu, 03 Apr 2003 16:49:58 0000 [thread overview]
Message-ID: <LKIAPKGOJEIOACAA@whowhere.com> (raw)
On Tue, 1 Apr 2003 11:38:47 John Bradford wrote:
> init=/bin/sh is already defined in init/main.c isn't
> it?
>
>Once the kernel has booted, it usually passed control to init. The
>kernel usually looks for init in /sbin /etc and /bin, but if there is
>no init in those locations, /bin/sh is looked for as a last resort.
>I am assuming that you have an init on your system, but something is
>wrong.
Perhaps. It may be the kernel.
Using init=/bin/sh will allow you to use the shell as the init
>process, which proves it's an init problem.
I did it but to no avail... Alas Mandrake sucks :-)
>
>> I accidentally compiled initrd in, but ive got it off
>> with "noinitrd".
>
>I don't really understand what you're trying to do.
Ok John, I'll put it simply, Im trying to compile a 2.5.* kernel. ;-)
Once ive got a 2.5.* series kernel to work on my machine, I've
decided to download .66 when I can get the one Ive got now to compile.
>>
Ok John, calm down you seem a bit agitated :-)
Maybe you've been talking to Andre ;-)
---
Cheers, Dean.
No Warrantee for incorrectness, political or otherwise,
after all, Dubya doesn't have one...
One of 4 members of the board of DM. TECH.
a.k.a. Everybody at DM. TECH's Boss.
Member of ATI Open Source development project.
NDA's signed to date = 29.
Number of people who've blocked me = priceless.
Need a new email address that people can remember
Check out the new EudoraMail at
http://www.eudoramail.com
next reply other threads:[~2003-04-03 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 16:49 Dean McEwan [this message]
2003-04-03 17:25 ` I compiled the kernel but it doesn't do any thing, its a bit like typing "halt root
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=LKIAPKGOJEIOACAA@whowhere.com \
--to=dean.mcewan@eudoramail.com \
--cc=john@grabjohn.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