Re: Fwd: Re: [gentoo-soc] Weekly Report: Portage Powered Android

[Benda Xu]

Hi Gunwant,

Gunwant Jain <therealgunwant@×××××.com> writes:

>> Could you please remind me why we need a bootstrap-init?  Can we just
>> exec the Android init when the lxc-guest starts?
>
> Yeah sure. Apparently, Android needs to parse its device tree for early
> mounting partitions, before exec'ing `init`. Plus even before dealing
> with the dt, we need to mount `/system` and switch root to it.
> I could create the environment for "using /system as root" w/o the help
> of `bootstrap-init` but I couldn't deal with the device tree easily.
>
> `bootstrap-init` creates the entire environment for android to boot from
> scratch and then finally exec's `init`. So I proposed to use it instead
> of manually setting up the LXC container for system-as-root devices.
> That way the setup is clean as we only need a /dev directory and a static
> `bootstrap-init` binary inside of the LXC rootfs.

In principle you can choose your way of achieving things.  But
considering you got stuck in making a functional 'bootstrap-init', I
have 2 questions.

1. If you need to prepare a proper environment for Android to boot
   inside the LXC guest, please check out LXC container hooks in
   lxc.container.conf(5) manpage.  Another init seems an overkill for
   me.

2. Why bootstrap-init needs to be written in C++?  Would a shell script
   enough?

Benda