submitted 2 years ago* (last edited 2 years ago) by to c/linux@lemmy.ml
 

When I just see my TV taking Linux updates it makes me feel so cozy. For context sake I have a veroV running osmc.

you are viewing a single comment's thread
view the rest of the comments
[+] -28 points 2 years ago (16 children)

Ew I don't want my TV running systemd

  • source
  • hideshow 16 child comments
  • [–] 7 points 2 years ago* (last edited 2 years ago) (11 children)

    I have actually seen some people with this kind of opinion regarding systemd, but I still do not get the hate about it.

    Can you elaborate what is so terrible about systemd?

    EDIT: typos

  • source
  • parent
  • hideshow 11 child comments
  • [–] 14 points 2 years ago (3 children)

    Ah no, please don't start another thread like this. We've had our experiences, that's it.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 6 points 2 years ago (2 children)

    It may have been a thing discussed ad nauseum on certain threads. I just wanted to understand if there are facts that make systemd bad in general

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 2 years ago* (1 child)

    Well, my experience was

    1. why a service misbehaved, can't get smart from that log dump
    2. configuring DNS, got annoyed that it was yet again something Systemd does itself and in a poor mans way, despite there being tools and standards for tens of years.
    3. Then found out about their security track record and that it all runs as PID 1 (more power than even root)

    All in all, it works very contrary to my experience that layers upon layers leads to unmanageable complexity and inefficinecy and it's all implemented in a poor way, functionally (some will likely disagree to this).

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 2 years ago

    Thanks for the response. Right now I do not have enough knowledge to judge for myself if systemd is effectively great or not. Once I have the time I will check closer kernel architecture (theoretical wise), then in how the Linux kernel is effectively organized and only after that understand the theory behind systemd. I've seen several threads where 2 very different camps exists, but I was not entirely sure of the information I was getting.

    Cannot say I will get around this, but for sure peeks my curiosity

  • source
  • parent
  • [–] 7 points 2 years ago* (last edited 2 years ago) (6 children)

    The unix philosophy is that a piece of software should do one thing, and do it well. Systemd does a dozen things, all of them poorly. It's an especially poor choice for an embedded or appliance system.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 1 point 2 years ago (5 children)

    Systemd is not a singular thing, it's a collection of a lot of things.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 2 years ago (4 children)
  • [–] 1 point 2 years ago (2 children)

    Linux is not a singular thing, it's a collection of a lot of things.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago (1 child)

    Linux is a kernel. The kernel modules, services, userland, etc. are all modular and can be used independently. Not so with systemd (at least how it's implemented in most distros).

  • source
  • parent
  • hideshow 1 child comment