[mdlug] Systemd and all of it's nonsensical BS

[Aaron Kulkis]

Brandon wrote:
> I took some time to read the debate on the Debian wiki and a few other
> articles and coming to this as a junior sysadmin I think Systemd offers
> more advantages than drawbacks. I don't like the idea of binary logs or the
> whole 'monolithic process' concept but containers, parallelization and
> on-demand services make up for that and more. Like anything in computing we
> should all be willing to bend and learn different ways to tackle problems.
> Just because something worked in the past doesn't mean it is the best
> solution for the rest of time.

Please explain why these advantages can ONLY be obtained with a huge,
bug-inviting monolithic process.

>
> On Mon, Feb 23, 2015 at 10:58 PM, Aaron Kulkis <akulkis00 at gmail.com> wrote:
>
>> Michael Corral wrote:
>>
>>> 2015-02-23, Monsieur Garry Stahl a ecrit:
>>>
>>>> On 02/23/2015 01:25 PM, Adam Tauno Williams wrote:
>>>>
>>>>>   On Mon, 2015-02-23 at 13:09 -0500, David Lee Lambert wrote:
>>>>>>   Well, depends what you mean by "consumed". Not in Debian Stable yet,
>>>>> it >  is
>>>>>>   in Debian Testing but in theory there are alternatives.  And, in my
>>>>>>   testing
>>>>>>   of Testing so far, on two fresh-installed VMs, no issues with it.
>>>>>   Running openSUSE - systemd  - on my laptop(s).  Use them all day every
>>>>>   day.  No systemd related issues.
>>>>>
>>>>>   Likewise.  openSUSE on all computers,m no issues.
>>>>
>>>
>>> I've been running systemd on Fedora for almost 4 years, when
>>> Fedora 15 became the first distro to make systemd the default
>>> init system. What problems am I supposed to be having? Because
>>> I've never had any, even on production servers running Apache,
>>> Tomcat, and PostgreSQL (yes, servers running Fedora - scary!:).
>>>
>>> At first, I didn't like systemd because it was unfamiliar to me.
>>> But once I learned how to use it, I liked it and now think it's
>>> a big improvement over the old SysV init system. In Fedora, having
>>> systemd logs forwarded to syslog is the default (it's a setting in
>>> /etc/systemd/journald.conf), so you can still have the old-style
>>> logging if you prefer that.
>>>
>>> I do think that a lot of the complaints about systemd are simply due
>>> to ignorance, though there are some crusty curmudgeons stuck in 1991
>>> who just don't want to learn anything new (or took the fictional
>>> "UNIX philosophy" about "do one thing, blah blah blah ..." a bit
>>> too seriously:).
>>>
>>
>> No, it's that 25 different areas and counting have all been
>> consumed by ONE huge monolithic program, worst of all, running
>> as PID 1.
>>
>> This means that one or two bugs can cause catastrophic consequences,
>> because this one process has its hands in EVERYTHING.
>>
>> Do you drive without either a steering wheel or brakes?
>>
>> Systemd works great when it works.
>>
>> When it's broken, it's a complete b**** to fix.
>>
>>
>> _______________________________________________
>> mdlug mailing list
>> mdlug at mdlug.org
>> http://mdlug.org/mailman/listinfo/mdlug
>>
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
>