Mailing List Archive: Init error on boot up

Gday,

I believe you'll find that your device nodes haven't been created.
Even running devfs, you need some basic nodes (AFAIK).
The way I've overcome this in the past is to copy the /dev entries
from my host system to the mounted root either before or after
a chroot install.
For me, this approach had worked best with DFS (Debian From Scratch)
chroot installs and systemimager installs.
I image it should be a similar situation with debootstrap and cdebootstrap.

Just creating /dev/console, /dev/tty0 etc will not be enough, however
I'm not sure what the minimal requirement is.

Marcus.

Shahzad Chohan wrote:

>Hi I've kind of made progress on getting rhel 3 running on fc4.
>
>Now I'm getting the following. Any ideas about this?
>
>Freeing unused kernel memory: 156k freed
>Warning: unable to open an initial console.
>Kernel panic - not syncing: No init found. Try passing init= option to kernel.
> [<c011d2a3>] panic+0x53/0x230
> [<c01051ba>] init+0x14a/0x1c0
>
>
>config file:
>
>kernel ="/boot/vmlinuz-2.6.11-1.1369_FC4xenU"
>memory = 400
>name = "rhel-3-es"
>#nics = 1
>disk = ['phy:cciss/c0d0p2,sda1,w']
>root = "/dev/sda1 ro
>
>Many Thanks
>Shaz
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@lists.xensource.com
>http://lists.xensource.com/xen-users
>
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users