On 13/06/16 15:29, KatolaZ wrote:

> If I can provide my 2 cents to the discusion, before writing a new
> init you should have studied and understood very well one of the
> existing ones, and what should happen behind the scenes from the
> moment your kernel is decompressed to the appearance of a login
> terminal. I would recommend to start with sysvinit or the standard
> rc-based init of *BSD. By studying I mean looking into the code of the
> process that is called "init" and into the code of all the processes
> directly started by init (e.g., /etc/init.d/rc, in the case of
> sysvinit, getty/agetty, etc...), and being sure to have understood
> what is in there.

Concur. If you wanted a simple and easy to follow example, grab the
busybox init source. It does everything you need and is small enough
that you can digest it relatively easily.

Most other init systems tend to rapidly devolve into a nest of vipers
and are therefore harder to follow.

Regards,
Brad