3 ms·

I'm repeating myself, but the best way to use systemd is as an init system only, and then staying away from those fancy features like dynamic users (wtf) or soc

I'm repeating myself, but the best way to use systemd is as an init system only, and then staying away from those fancy features like dynamic users (wtf) or socket activation. Especially avoid all that bolted on crap like timesyncd, resolved, etc. Yes they integrate a bit better with systemd, but no you don't need this better integration, especially since these tools are usually less configurable than their bigger brothers and are often more buggy just because they are not that battle tested yet. > systemd will tell me to reproduce on the latest version, Ubuntu will ignore it as always Amen to that. Distro bug reporting/handling is a pretty sad story on its own, and so far dealing with Ubuntu has been the worst. The most insane instance was when I reported a bug in their ati x11 driver. It was about two weeks after a new non-LTS came out, I even tracked down the bug and found that it was already fixed upstream only 2 commits after the one they shipped. So they didn't need to do anything but apply that single patch. No response ever. 6 months later the next release just shipped newer drivers and the problem was gone, but hadn't I recompiled the fixed driver myself I wouldn't have been able to switch vt for half a year without crashing X. I really like open source and all and make an effort to produce usable bug reports to help improve things for everyone, but instances like this make me wonder what the f*ck is wrong with people maintaining such projects. <end unrelated rant>

majewsky 8y ago
> Especially avoid all that bolted on crap like timesyncd, resolved, etc. You're pretty much stuck with systemd-resolved when you use systemd-networkd. And systemd-networkd is a godsend. It's the first network setup tool that I've found that is: - full-featured - simple to set up for the 99% usecases like "just do DHCP whenever a physical interfaces goes UP" - available and works the same on all major distros - not a Lovecraftian monstrosity like network-manager
- fps_doug 8y ago
  Agree, this is the only thing that's almost as well-designed as the init part of systemd. Unfortunately, you still have some weird edge-case every now and then with it that's just not possible to set up, and then you're screwed because you cannot just plug in in a little shell snippet somewhere.
muxator 8y ago
In that case Ubuntu was a middleman whose interests were completely disaligned with their customers', which probably means they in reality felt obliged to someone else. You tried to voice. Depending on your loyalty, you may think of exiting [0]. [0] https://en.wikipedia.org/wiki/Exit,_Voice,_and_Loyalty https://en.wikipedia.org/wiki/Exit,_Voice,_and_Loyalty

majewsky 8y ago

> Especially avoid all that bolted on crap like timesyncd, resolved, etc. You're pretty much stuck with systemd-resolved when you use systemd-networkd. And systemd-networkd is a godsend. It's the first network setup tool that I've found that is: - full-featured - simple to set up for the 99% usecases like "just do DHCP whenever a physical interfaces goes UP" - available and works the same on all major distros - not a Lovecraftian monstrosity like network-manager

fps_doug 8y ago
Agree, this is the only thing that's almost as well-designed as the init part of systemd. Unfortunately, you still have some weird edge-case every now and then with it that's just not possible to set up, and then you're screwed because you cannot just plug in in a little shell snippet somewhere.

muxator 8y ago

In that case Ubuntu was a middleman whose interests were completely disaligned with their customers', which probably means they in reality felt obliged to someone else. You tried to voice. Depending on your loyalty, you may think of exiting [0]. [0] https://en.wikipedia.org/wiki/Exit,_Voice,_and_Loyalty https://en.wikipedia.org/wiki/Exit,_Voice,_and_Loyalty