Re: Bug#727708: tech-ctte: Decide which init system to default to in Debian.
previously on this list Theodore Ts'o contributed:
> So hopefully that is something the technical committee will take into
> account --- how well things are documented, both in terms of a
> comprehensive reference manual, and a tutorial that helps people with
> common things that system administrators might want to do. The
> docuementation you pointed to at http://upstart.ubuntu.com/cookbook/
> is something I wish I had access to when I first was forced to use
> Upstart; maybe if Upstart was as polished back then, I might not have
> given up on Ubuntu in disgust.
I would like to have seen that, I think the man page found via
apropos upstart should point to that doc in /usr/share as well as the
http for offline use at the very least, even if a pdf/html has to be
copied off to be read on a server. I don't use Linux for any servers
that I currently deploy but I can see that being very annoying in
I have had my time wasted with almost every init system except
OpenRC which is pretty much intuitive but still not so intuitive as
OpenBSD's being my favourite where you have around 6 files (few for
lockdownability but actually simplicity too) ALL in /etc and with rc in
the name and one directory called rc.d all of which have very good man
pages including giving reasons for why things are done in as few files
as possible even though you could work it out yourself rather quickly.
Of course good man pages is one of OpenBSD's watch words or primary
goals and security and minimal defaults comes before speed and ease
of average user use so it shouldn't be that surprising.
rc.conf has the defaults and the line
rc.conf.local can have overrides such as
sshd_flags=NO for off
sshd_flags="" for default
sshd_flags="-4" for ipv4 only
'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
In Other Words - Don't design like polkit or systemd