Hi,
On 14.04.2008, at 15:20, Marian Aldenhövel wrote:
My custom T2-built target now boots a kernel in QEMU (and on the
real device
as well, but I'm playing with the emulator for now), loads an
initramfs -
which is all it ever will get - and then goes haywire with loads of
messages,
most propably from processes started via minit.
I have statically compiled a "hello world" program and put that as /
init onto
my root-fs and it runs that fine. So there is hope. I mean, any
hello world
is a major achievement, right?
Hooray!
Yes, congratulations!
Next it has been suggested to me to boot right into a shell as /
init. To use
that to look around the system from the inside and find out what
it's missing
instead of scrolling down an endless list of init-booboos.
I tried to achieve that via the root filesystem overlay by
instructing it
to create a symlink to /bin/bash.
I created a file $target/rootfs/init with a single line:
#!ln -s ./bin/bash
As suggested by the handbook I stole that from another target.
Unfortunately ./scripts/Build-Target just copies that file as-is to
$build/TOOLCHAIN/rootfs instead of creating a symlink in the target.
What am I doing wrong this time?
Syntax-wise the line should work, do you get any diagnostic scrolling
by whiel the Build-Target is processing the overlay?
For a test you can also pass init=/bin/bash via the "kernel arguments".
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
Geschäftsführer: Susanne Klaus, René Rebe
Sitz: Berlin, Amtsgericht Charlottenburg HRB 105 123 B
USt-IdNr.: DE251602478
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of: unsubscribe t2
