search

darthlukan / lynea

This might become an init system for Linux named after my wife. !NOTE! Don't try to run this yet.
GNU General Public License v3.0
5 stars 2 forks source link

Roadmap #8

Open darthlukan opened 9 years ago

shymega commented 8 years ago

How's this issue coming along? I'm thinking of hacking on lynea again, but I'm not quite sure of the roadmap. Thanks.

darthlukan commented 8 years ago

I've been really busy for the last year or so, so I haven't been able to do 99% of what I've wanted with regard to this issue (which is to buckle down and write one out). I do have a general idea of where I want things to go, such as to take over PID1, execute init style daemons (as in, the old initscripts which could be in whichever language the user cared to write them and PID1 could care less beyond start and exit status), and write an optional accompanying interface (such as "service" or systemctl) for simplified interaction as a separate package for convenience. Beyond that, I want to keep from making the mistakes some projects have made of swallowing every possible endpoint and feature (such as containing an http server...).

shymega commented 8 years ago

Hello,

Brian Tomlinson notifications@github.com writes:

I've been really busy for the last year or so, so I haven't been able to do 99% of what I've wanted with regard to this issue (which is to buckle down and write one out).

No problem, I'm the same right now - college has just started up for me, and all the free time I had during the summer to work on i, and slacs has suddenly disappeared beneath a plethora of 1700 word assignments..

I do have a general idea of where I want things to go, such as to take over PID1, execute init style daemons (as in, the old initscripts which could be in whichever language the user cared to write them and PID1 could care less beyond start and exit status)

Sounds cool - I like the minimal approach there.

,and write an optional accompanying interface (such as "service" or systemctl) for simplified interaction as a separate package for convenience.

How were you thinking of doing the RPC between the client <--> PID1? RPC? Just out of interest.

Beyond that, I want to keep from making the mistakes some projects have made of swallowing every possible endpoint and feature (such as containing an http server...).

Oh, definitely. Any sane init system would try to avoid that, IMHO. :)

Good luck!

Regards,

Dom Rodriguez