3 ms·

> systemd is a collection of smaller tools, which is the UNIX philosophy (debunking that argument). That's not debunked. The small tools of the UNIX philosoph

> systemd is a collection of smaller tools, which is the UNIX philosophy (debunking that argument). That's not debunked. The small tools of the UNIX philosophy are supposed to compose well with others. If I want to replace systemd's init with that from daemontools (for instance) and keep the rest of systemd working, that should be possible. Or let's suppose that I want to opt in to systemd's auto-remounting and socket activation (for instance), but for whatever reason I need to keep my syslogs as text on disc, so I can't use systemd's binary logs but need my legacy syslog system. Can I do that? > I really don't get the systemd "hate" that is still floating around. It seems a lot of arguments against end up boiling down to "it's different and therefore I don't want it". The arguments I've heard boil down to "it's badly designed and therefore I don't want it."

sandGorgon 12y ago
yes you can /etc/systemd/journald.conf ForwardToSyslog=True
- e7620 12y ago
  systemd-journald is only one component, there are more than 50, and if you only want one piece of that, tough luck!
  - sandGorgon 12y ago
    that seems unfair - on one hand, there are people complaining that systemd is too monolithic... on the other hand, we have people saying there are too many components !
    - e7620 12y ago
      Come on, this horse has been beaten to death already... I'll just say, a GNU/Linux distro has many components, but they're not monolithic because they integrate well, you can do ls|grep etc, you know this. But if we want to change one component of systemd, we can't do it! You see? A lot of components, but they comprise a blob and can't be separated or used individually.
- regularfry 12y ago
  In a funny way, you've just proven my point. I'm talking about a whole class of problems caused by systemd's design, and you've provided a case-specific hack which happens to work in one instance I picked, leaving every other case where I might want to opt out of part of what systemd provides unsupported.
  - the_why_of_y 12y ago
    Have you ever noticed that it's really hard to replace the IP stack in Linux with the one from FreeBSD? Clearly that proves that Linux never followed the UNIX philosophy in the first place and we should never have switched away from MINIX.

sandGorgon 12y ago

yes you can /etc/systemd/journald.conf ForwardToSyslog=True

e7620 12y ago
systemd-journald is only one component, there are more than 50, and if you only want one piece of that, tough luck!
- sandGorgon 12y ago
  that seems unfair - on one hand, there are people complaining that systemd is too monolithic... on the other hand, we have people saying there are too many components !
  - e7620 12y ago
    Come on, this horse has been beaten to death already... I'll just say, a GNU/Linux distro has many components, but they're not monolithic because they integrate well, you can do ls|grep etc, you know this. But if we want to change one component of systemd, we can't do it! You see? A lot of components, but they comprise a blob and can't be separated or used individually.
regularfry 12y ago
In a funny way, you've just proven my point. I'm talking about a whole class of problems caused by systemd's design, and you've provided a case-specific hack which happens to work in one instance I picked, leaving every other case where I might want to opt out of part of what systemd provides unsupported.
- the_why_of_y 12y ago
  Have you ever noticed that it's really hard to replace the IP stack in Linux with the one from FreeBSD? Clearly that proves that Linux never followed the UNIX philosophy in the first place and we should never have switched away from MINIX.