[Aboriginal] confused about control-Images

Rob Landley rob at landley.net
Fri Jul 8 14:40:38 PDT 2011

On 07/08/2011 01:37 PM, prasanna balan wrote:
> 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

It was intentional. :)

I made an image to build LILO once (x86 only), and Gentoo From Scratch
needs more host tuple information than I can easily probe (alas "$(uname
-m`-unknown-linux)" won't work on armv5l with eabi, portage wants to
know "armv5l-uclibc-gnueabi" or some such.).  But in general, the images
just do native stuff and "native" is externally provided. :)

>     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

Yes, but my boundaries are "I have no idea what you're going to run on
the target". :)

>     (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
> Thanks
> prazzb

Cool.  I look forward to it.

Right now I'm redoing LFS to be based on the 6.8 release, and I need to
automate some chunks of BLFS too.

Gentoo From Scratch is maybe 1/3 finished.

I haven't started debian from scratch or fedora or ubuntu or Arch Linux.
 Heck, OpenEmbedded has its own package management system with a package
repository, no reason we can't bootstrap the environment to the point
where it can natively build openembedded packages...

Lots to do here.



More information about the Aboriginal mailing list