> 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. Using init=/bin/sh will allow you to use the shell as the init
process, which proves it's an init problem.
> I accidentally compiled initrd in, but ive got it off
> with "noinitrd".
I don't really understand what you're trying to do.
> >> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 07 2003 - 22:00:13 EST