Writing my own init with Go

Re:Writing my own init with Go by lmm on Tuesday February 09, 2016 @10:43AM (#11065986)

Even at this 3-line stage, the stateful log.SetOutput construct is ugly and error-prone. So I'd say a functional/immutable language would already be adding value, and that would only increase as the amount of code grows. At a minimum an init is going to involve parsing config and something similar to a state machine, both good use cases for functional languages.

[ Parent | on HN ]

Re:Writing my own init with Go by groovy2shoes on Tuesday February 09, 2016 @12:18PM (#11066902)

Init's job is to start the init scripts and then hang around to foster orphan processes. Ideally, it should not be parsing configs, but should spawn another process to do that sort of work. A good PID 1 is very, very minimal.

[ Parent | on HN ]

Re:Writing my own init with Go by lmm on Wednesday February 10, 2016 @03:46AM (#11071460)

This project isn't just a PID1 though, it's a full system. (Well at the moment it's a hello world, but that's the intent)

[ Parent | on HN ]