On Fri, 2017-03-03 at 00:59 -0500, Anton Aylward wrote:
On Tuesday, nicholas
wrote a rather good parody of these kinds of denunciations of 'new technology; on the main forum. Message-ID: <1689789.g315aOOmSE@asus> https://lists.opensuse.org/opensuse/2017-02/msg00946.html That sums up this thread well.
Just that this sort of ridicule will not bring us any closer to a
solution. On the contrary, it will likely cause the other side to
harden its position. It's true that not all arguments in discussions
like this are technically well-founded. There's way too much emotion in
these discussions, but that's hard to settle once it started, and
postings like the one you referenced are rather not the right way to
reconcile the dispute.
Like it or not, Unix traditionalists represent a substantial part of
the Linux user community. Most of these people are neither ignorant nor
generally opposed to new technology. You just need very good arguments
to force them to fundamentally change their way of working.
Despite the vocal opposition, systemd has successfully taken over a lot
of functionality from traditional daemons already, in openSUSE as well
as elsewhere, so I can hardly understand the heat on the pro-systemd
side. Why not sit back and enjoy what you already achieved?
systemd timers are simply not a fully functional replacement of cron
yet. Even if they were, to achieve full user acceptance, some sort of
"compatibility UI" similar to systemd's sysvinit support might be in
order [*]. Creating new timer units in $HOME/.config/systemd/user is
just not as user-friendly as "crontab -e", not in general, and
specifically not for seasoned unix users. Call me stupid, I've been
working with systemd for I-dont-know-how-many years now, and I still
need to open several man pages every time I create a new unit file.
Regards
Martin
[*] See other thread - "init 3" is indeed easier to type and memorize
than "systemctl isolate multi-user.target", and therefore systemd's
legacy support is a good thing.
--
Dr. Martin Wilck