[Toybox] toybox initd
Rob Landley
rob at landley.net
Mon Feb 4 18:20:18 PST 2013
And I got permission! (Second attempt. If balsa eats this one, I'm
taking a hex editor to it.)
Rob
On 01/24/2013 11:36:48 AM, Rob Landley wrote:
> On 01/17/2013 02:50:38 PM, Ilya Kuzmich wrote:
>> Hi Rob.
>>
>> Can you please share with me your vision on what exactly toybox
>> initd should
>> look like?
>
> Sorry for the delay, started a new job on monday and got behind on my
> email. (I checked the webmail for the toybox archive, but you sent
> this to my personal email. I've just now caught up to the 17th. :)
>
>> The thing is, for the last couple of months i'm doing embedded linux
>> on my
>> dayjob and our sysv scripts is not very fast, robust, concise,
>> flexible or
>> pretty much anything. After poking around i did not found init that
>> would be
>> small, well-written, maintained, and provide any significant
>> advantage over
>> busybox initd
>> Which made me thinking about writing my own, which is a bad idea
>> prob.
>> I would really like to know what are your plans for the toybox
>> initd, and/or
>> your thoughts on desing of pid1 in general for that matter.
>
> Well, I did "oneit" already, which runs a single program. That way
> you can launch a shell script as your init to bring the system up,
> and designate one master program that will reboot the system if it
> ever exits.
>
> My next init will probably be something sysvinit-like, just because
> so many people are used to it. I have a todo item to look at:
>
> A) busybox init
> B) android core init
> C) klibc init
> D) the old sysvinit man page
> E) LSB 4.1 chapter 20, "System Initialization"
>
> And see if I can come up with some common characteristics. I dunno if
> this will wind up being an extension of oneit or a separate command.
>
> Finally, I need to study upstart and systemd and see what that's all
> about. But I haven't even started looking at that yet.
>
> Ideally I'd like an init that could read an inittab, or the android
> init data format, or the upstart/systemd formats, and behave
> appropriately in each case without too much code duplication. But I
> dunno yet how much actual code sharing that would involve and whether
> or not it would be worth it. I haven't done the research or design
> work yet.
>
> Mind if I forward this response to the toybox mailing list?
>
> Thanks,
>
> Rob
1360030818.0
More information about the Toybox
mailing list