arrgh.. build file woes..

i have two build files… one works one doesnt (machine locks up after loading image) the only difference is that i have added ls to the build image so i can do somthing useful after booting… why??

//the one that works


[virtual=x86,bios] .bootstrap = {
startup-bios
PATH=/proc/boot procnto
}

[+script] .script = {
devc-con -n9 &
reopen /dev/con1
[+session] esh
}
libc.so.1
[data=copy]
devc-con
esh
[type=link] /usr/lib/ldqnx.so.1=/proc/boot/libc.so.1






///the one that doesn’t

[virtual=x86,bios] .bootstrap = {
startup-bios
PATH=/proc/boot procnto
}

[+script] .script = {
devc-con -n9 &
reopen /dev/con1
[+session] esh
}
libc.so.1
[data=copy]
devc-con
esh
ls
[type=link] /usr/lib/ldqnx.so.1=/proc/boot/libc.so.1




vince

You will need seedres as the first statement of your script. In addition
you could try fesh rather than esh to get the els (and others) feture to
test with,

Just a segestion…


“vince” <lab-101@usa.net> wrote in message
news:Voyager.001027152819.638997A@draco…

i have two build files… one works one doesnt (machine locks up after
loading image) the only difference is that i have added ls to the build

image so i can do somthing useful after booting… why??

//the one that works