I compiled the kernel but it doesn't do any thing, its a bit like typing "halt".
init=/bin/sh is already defined in init/main.c isn't it?
I accidentally compiled initrd in, but ive got it off with "noinitrd".
---
Cheers, Dean.
Quoted 3 lines
Quoted 1 line
whats system.map actually for
Decoding numerical addresses in to function names.
Does it need to be put in /boot after compilation from the root linux source folder, 'coz the mandrake one for 2.4.19-16mdk is in there.
Quoted 3 lines
John.
Need a new email address that people can remember Check out the new EudoraMail at
http://www.eudoramail.com
Quoted 2 lines
init=/bin/sh is already defined in
init/main.cisn'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. Using init=/bin/sh will allow you to use the shell as the init process, which proves it's an init problem.
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.
Quoted 7 lines
Quoted 3 lines
Quoted 1 line
whats system.map actually for
Decoding numerical addresses in to function names.
Does it need to be put in /boot after compilation from the root linux source folder, 'coz the mandrake one for 2.4.19-16mdk is in there.
No.
John.