Re: RFC: poky-tiny: init procedure

[Darren Hart <dvhart@linux.intel.com>]

On 06/15/2012 12:05 AM, Thomas Petazzoni wrote:
> Le Fri, 15 Jun 2012 07:31:45 +0100,
> Tomas Frydrych <tf+lists.yocto@r-finger.com> a écrit :
> 
>> Hi Darren,
>>
>> On 14/06/12 22:09, Darren Hart wrote:
>>> This solution improves the kick-the-tires
>>> experience with poky-tiny, without pulling in all of init, 
>>
>> I think you really should quantify what 'all of init' means, without
>> this you are addressing a problem that is merely perceived. Just a
>> quick look shows that the sysvinit package is about 120KB unpacked,
>> for that you get a solution that is tested, robust, and supported
>> across Yocto.
> 
> FWIW, Busybox comes with its own implementation of a very simple and
> basic init, which only takes a few KB of space inside the Busybox
> binary. That's what we use by default in Buildroot, and it works just
> fine. It's a really good trade-off between no init at all, and a
> full-blown sysvinit system.
> 

Good point on this. I had a look. Enabling the basics here, including
the ability to give the controlling console to commands starting with a
dash in inittab results in a 5664 byte delta (compared with 2560 bytes
for enabling setsid and cttyhack). Note that the help in busybox
suggests the cttyhack may be more reliable than the init support for
handing over the controlling terminal.

So the difference between the two options is about 3k, but enabling
setsid and cttyhack may enable others to things besides what I am
looking to do.

I have sent a patch to oe-core to enable SETSID and CTTYHACK in the
default defconfig.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel