News for hackers. Stuff that matters.
Re:Writing my own init with Go by jabagonuts on Tuesday February 09, 2016 @10:17AM (#11065796)
> The reason that I wrote sleep 3 seconds is that I want to see how the kernel reacts when init dies.

That was my favorite line in the entire post. I love seeing this kind of fearless experimentation.

When I first learned to program, I desperately wanted everything to work and would try very hard not to break things. As I've matured into senior roles, I spend of a lot of effort creating "safe" development and testing environments like the author did here, just so that I can break things and make observations and then throw the environment away when I've learned what I needed to learn. Tools like vagrant and cheap cloud computing have made this easier to do than ever.

Re:Writing my own init with Go by agumonkey on Tuesday February 09, 2016 @11:18AM (#11066284)
it should be called acquiring information, not 'breaking' things :D
Re:Writing my own init with Go by kough on Tuesday February 09, 2016 @11:20AM (#11066316)
"Actively exploring modes of failure"
Re:Writing my own init with Go by slantview on Tuesday February 09, 2016 @12:18PM (#11066899)
Or maybe hacking ;)
Re:Writing my own init with Go by gravypod on Tuesday February 09, 2016 @06:25PM (#11069643)
I'll be using this in future conversations, thanks!