"I also believe the implementation is poor."
Systemd goes against the fundamental Linux/UNIX philosophy of "files first"
/ "everything is a file" and "do only one thing but do that thing right".
You come across binary logs and it does waaay too many things. From a
security perspective it's a ticking time bomb (which already went off
several many with critical exploits but the general public doesn't care).
It's extremely unfortunate that the Debian core maintainers didn't opt for
more explicit help or support for alternative init systems. That will fuse
the current trend that all major distributions (Debian based, Ubuntu
derivatives, and of course all RedHat related distributions) will be based
on systemd and there's no supported alternative. Very very sad.

On Sat, Oct 31, 2020 at 9:47 AM 'Michael Chaney' via NLUG <
[email protected]> wrote:

> On Sat, Oct 31, 2020 at 10:51 AM Howard White <[email protected]> wrote:
>
>> Like some other "veteran" admins, I'm a little slow coming around to the
>> full impact of systemd - specifically the migration away from scripts in
>> /etc/init.d.
>>
>> DAMMIT!  I used to know where to go look for things!
>
>
>
> I share the sentiment, but I believe the concept of systemd is good.  I
> also believe the implementation is poor. Unfortunately, like a lot of
> things in UNIX, it will be the de facto standard now because no one will
> take the initiative to create something better. Even if they did, it’s
> difficult to overcome the momentum that systemd has.  I expect it’ll be
> another 20 years before it’s replaced.  A long 20 years.
>
> At the same time, if you learn how to work with it it is useful for some
> things such as running background jobs as a particular user. And yes, that
> is possible with the old init scripts, but systemd does actually make it
> better if for no other reason than your background programs being
> automatically monitored and all that.
>
>> --
> Michael Darrin Chaney, Sr.
> [email protected]
> http://www.michaelchaney.com/
>
> --
> --
> You received this message because you are subscribed to the Google Groups
> "NLUG" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nlug-talk?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "NLUG" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nlug-talk/CAAtfUtHDvy-z88UHV8m3qQtfvqCWXjPcWQxCHF1vbvNXBcZKoQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/nlug-talk/CAAtfUtHDvy-z88UHV8m3qQtfvqCWXjPcWQxCHF1vbvNXBcZKoQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
-- 
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nlug-talk?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nlug-talk/CA%2BKhHxKwONn7MdxfnH%2BHR1-dVYiMm4WNuSc_4LkUmwRc1SsVXg%40mail.gmail.com.

Reply via email to