Don't be facetious. The point that is being made is:
F U C K system v init. F U C K anyone who relies on it,
uses it, likes it, we will not help you, we will not
continue on with it, F U C K U N I X, F U C K old sys
You say it in many clever ways, but don't think we don't
get the message.
As was said before:
SystemD feels like an invasion, because it and its priests
are spearheading just that.
I now know to 1/100th of a degree what the pagans of europe felt.
Debian provides all manners of different languages and support for them
Debian provides various different kernels to run,
and different versions of different kernels aswell as
build systems should you choose to run some other kernel.
Debian should continue to provide the simple sysvinit
(for most daemons) scripts
that it always has. It is usually not hard to start up a
daemon. The standard debian init scripts are usually fine,
just change which binary it runs etc.
Not much support is needed: keep your hands off the init
scripts and they'll keep working as they have for most
daemons. So stop being facetious and telling us to
go and fk ourselves while claiming you arent.
And respect your elders please too, they use, like,
would like to continue to use system V init, and
not be goaded into being corralled into your
new cattle pen.
From: James Rhodes <email@example.com>
To: Thilos Rich <firstname.lastname@example.org>; 727708 <email@example.com>
Sent: Mon, Feb 3, 2014 2:00 am
Subject: Re: Bug#727708: multiple init systems - formal resolution proposal
The point that is being made is not "you can't run software with shell scripts if you want", it's "don't expect developers to write or maintain them for you".