News for hackers. Stuff that matters.
Re:Avoiding systemd isn't hard by sandGorgon on Tuesday October 21, 2014 @01:40PM (#8488563)
yes you can

/etc/systemd/journald.conf ForwardToSyslog=True

Re:Avoiding systemd isn't hard by regularfry on Wednesday October 22, 2014 @03:24AM (#8491746)
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.
Re:Avoiding systemd isn't hard by the_why_of_y on Wednesday October 22, 2014 @01:12PM (#8493703)
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.
Re:Avoiding systemd isn't hard by e7620 on Tuesday October 21, 2014 @02:01PM (#8488730)
systemd-journald is only one component, there are more than 50, and if you only want one piece of that, tough luck!
Re:Avoiding systemd isn't hard by sandGorgon on Tuesday October 21, 2014 @02:13PM (#8488826)
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 !
Re:Avoiding systemd isn't hard by e7620 on Tuesday October 21, 2014 @02:34PM (#8488949)
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.