Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 19 submissions in the queue.

systemd: Harbinger of the Linux Apocalypse.

posted by janrinok on Tuesday August 19 2014, @12:04PM   Printer-friendly
from the you-either-love-it-or-hate-it dept.

Subsentient writes:

The good people over at Infoworld have published a story outlining why they feel systemd is a disaster.

Excerpt from Infoworld:

While systemd has succeeded in its original goals, it's not stopping there. systemd is becoming the Svchost of Linux—which I don't think most Linux folks want. You see, systemd is growing, like wildfire, well outside the bounds of enhancing the Linux boot experience. systemd wants to control most, if not all, of the fundamental functional aspects of a Linux system—from authentication to mounting shares to network configuration to syslog to cron. It wants to do so as essentially a monolithic entity that obscures what's happening behind the scenes.

 
This discussion has been archived. No new comments can be posted.
systemd: Harbinger of the Linux Apocalypse. | Log In/Create an Account | Top | 98 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 0) by Anonymous Coward on Tuesday August 19 2014, @09:56PM

    by Anonymous Coward on Tuesday August 19 2014, @09:56PM (#83264)

    Yes I've seen this smartass argument too. Problem is, log forwarding was nothing like this and all things considered was less robust due to it being both an ad-hoc protocol [...] deserialized format like json [..] when have facts like this stopped people from claiming that the journal gateway is somehow reinventing syslog's forwarder despite being nothing like it whatsoever and intended to be more than just forwarding to another daemon.

    Right, let's make this easy. I was debunking the quoted section and specifically your claim that the webserver is "a potentially useful method of sending journal records to another system".

    As for json, yes it's much cleaner and more expressive than ini files -- consider...

    smptd = {
      name: 'postfix',
      bin: '/usr/bin/postfix',
      /* Ensure dovecot is running for SASL auth */
      depends: [ 'syslog', 'dovecot']
    };

    ... because systemd authors didn't. And it may also make sense as a serialisation format for logging, along with a new RFC for remote logging. And basic log tampering on the local machine could be prevented with checksumming just as effectively as it is prevented by a binary log format. Only the json for configuration stuff has anything to do with a pid 1 replacement though!