Re: Launch of L4Linux
Adam Lackorzynski <[email protected]>
| Newsgroups | gmane.comp.micro-kernel.l4.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu Jul 25, 2013 at 14:52:49 +0200, Maximin Coste wrote: > 2013/7/22 Adam Lackorzynski <[email protected]>: > > Principally you can take whatever ramdisk you like to use. > > Concerning the provided ramdisk, it contains a busybox and also a proper > > /bin/sh link/binary. I'm not sure what's the difference to your previous > > run. Maybe you could copy the relevant output here to have a look. > > Here is my output: > > l4linux | RAMDISK: ext2 filesystem found at block 0 > l4linux | RAMDISK: Loading 16384KiB [1 disk] into ram disk... done. > l4linux | VFS: Mounted root (ext2 filesystem) readonly on device 1:0. > l4linux | Freeing init memory: 112K > l4linux | request_module: runaway loop modprobe binfmt-464c > l4linux | Failed to execute /bin/sh. Attempting defaults... > l4linux | request_module: runaway loop modprobe binfmt-464c > l4linux | request_module: runaway loop modprobe binfmt-464c > l4linux | Kernel panic - not syncing: No init found. Try passing > init= option to kernel. See Linux Documentation/init.txt for guidance. That binfmt-464c error typically happens when the Linux cannot execute init/sh for some reason. Is it maybe a different ramdisk or so? Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/