Root filesystem overlay. Symbolic links.

Hi,

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!

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?

Ciao, MM
--
Marian Aldenhövel, Rosenhain 23, 53123 Bonn
http://www.marian-aldenhoevel.de
"I ran some quick calculations on it. He's about 80% on the right
 track.  That leaves him only 20% dead when he crashes." Bob C

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
lists@xxxxxxxxxxxxxx with a subject of: unsubscribe t2