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

[Michael ORourke]

I've got the solution to the systemd complexities...
What if it had a unified hierarchical configuration database, which stored thousands of key-pairs and grouped them by functional categories, perhaps call them "nests".  Also, we will need some low-level utilities that can edit the entries in the nests, but if you edit the wrong thing, them the system will refuse to run and you will most likely have to reload the OS.  Sounds like a good solution to me.  ;-)

-Mike

-----Original Message-----
>From: Aaron Kulkis <akulkis00 at gmail.com>
>Sent: Feb 26, 2015 2:44 AM
>To: awilliam at whitemice.org, MDLUG's Main discussion list <mdlug at mdlug.org>
>Subject: Re: [mdlug] Systemd and all of it's nonsensical BS
>
>Adam Tauno Williams wrote:
>> On Wed, 2015-02-25 at 01:51 -0500, Aaron Kulkis wrote:
>>> 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.
>>
>> How are you going to implement IPC in a shell script?
>
>The same way any other characters are passed between processes in a shell script.
>_______________________________________________
>mdlug mailing list
>mdlug at mdlug.org
>http://mdlug.org/mailman/listinfo/mdlug