Skip to contentSkip to conversation

I compiled the kernel but it doesn't do any thing, its a bit like typing "halt

DISCUSSION Dean McEwan 2 participants 2 messages Apr 3, 2003

lore
Share & tools
lore
#0 lore raw
Quoted 10 lines · 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

Quoted 1 line

process, which proves it's an init problem.

I did it but to no avail... Alas Mandrake sucks :-)

Quoted 5 lines
Quoted 3 lines

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.

Quoted 1 line
Quoted 1 line

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

#1 lore raw
Quoted 11 lines
Quoted 10 lines

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.

Quoted 6 lines

Perhaps. It may be the kernel.

Using init=/bin/sh will allow you to use the shell as the init

Quoted 1 line

process, which proves it's an init problem.

I did it but to no avail... Alas Mandrake sucks :-)

So, does the shell run successfully, or does the kernel still hang?

If the shell runs successfully, it's an init problem. If the kernel hangs, it's probably a kernel problem.

Quoted 6 lines
Quoted 4 lines
Quoted 2 lines

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. ;-)

OK...

Quoted 2 lines

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.

So, if your init works fine with 2.4.x, why are you assuming that it's likely to be an init problem when a 2.5.x kernel doesn't boot? I thought maybe you were having specific problems that suggested that init might be to blame.

Quoted 1 line

Ok John, calm down you seem a bit agitated :-)

Eh? What are you basing that on!? I'm not agitated at all.

Quoted 1 line

Maybe you've been talking to Andre ;-)

Errr, no.

John.