[Aboriginal] confused about control-Images

prasanna balan prazzb at gmail.com
Fri Jul 8 11:37:54 PDT 2011

Hello again

The "native-build.sh" script in each system image launches qemu with a
> build control image as the third drive (/dev/hdc).  The init scripts
> attempt to mount /dev/hdc on /mnt, and then run /mnt/init.  If that
> works, it runs the build control image.  If that doesn't work, it falls
> back to a shell prompt.

Workin exactly as u said....(Bcoz u wrote it 2 behave that way :D)

> This lets you plug a separate, device-independent filesystem into your
> system image and have it automaticaly take over when the emulator
> finishes booting.

What i felt the best is the same image runs for all the targets

The images I made mostly use this to build more
> software in an automated fashion, but really they could do anything.

Know your boundaries...let it be a native compiler testing image

(The busybox one runs the busybox test suite, although that hasnt' been
> fully converted to build in a separate tree yet.)

Keep it going....will help wen i understand the scripts completely
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.landley.net/pipermail/aboriginal-landley.net/attachments/20110709/4b732ed3/attachment-0002.htm>

More information about the Aboriginal mailing list