3 ms·

Systemd should have never made it into desktop operating systems. It's clearly designed and tuned (and bugs are prioritized) for servers. But unfortunately, the

Systemd should have never made it into desktop operating systems. It's clearly designed and tuned (and bugs are prioritized) for servers. But unfortunately, there's no such thing as a "desktop Linux". Every "desktop" distro is just a server distro with maybe LibreOffice thrown in (if you're lucky). The issues the author are experiencing with split-DNS configuration (a purely desktop concern, nobody in a server farm will have split-DNS) are hardly unusual.

jeppesen-io 5y ago
It's not ideal, but slit DNS is run on servers. For example running consul. Or a very large company where your team can't update the company wide delegation. Both I've seen in the real world It's easy with systemd or just use dnsmasq
dmacvicar 5y ago
I disagree with systemd being designed purely for servers. We got systemd --user and session awareness which eliminated all kind of hacks of running daemons (eg. a sync app, sound) as a non system user.
- jeppesen-io 5y ago
  Agreed - having user services is such a nice tool to have Makes sense as systemd took several ideas from MacOS launchd
- phendrenad2 5y ago
  ...Hacks that worked around security features that were in place because Linux is, and always will be, a high-security server-first OS, with the desktop as an afterthought.
deknos 5y ago
it makes even more sense for the desktop than for servers. servers do not often un/mount stuff, often services are just a few and long running, and certainly no usb stuff which is running around. but the desktop is and will be a sprawling mess of components, look also too windows and mac. because nothing is totally certain, and something has to take care of it. what is your argument that systemd is not made for the desktop? and split dns can also occur in server systems which are public but have a virtual "inner" network. and my split dns works, so.. perhaps either your configuration sucks or the software is just not working at the desktop that seemlessly, but that will come. but it takes time.
hammyhavoc 5y ago
Since when have server distros shipped with Pipewire et al? Let's not conflate bundled programs with actual operating system functionality.

jeppesen-io 5y ago

It's not ideal, but slit DNS is run on servers. For example running consul. Or a very large company where your team can't update the company wide delegation. Both I've seen in the real world It's easy with systemd or just use dnsmasq

dmacvicar 5y ago

I disagree with systemd being designed purely for servers. We got systemd --user and session awareness which eliminated all kind of hacks of running daemons (eg. a sync app, sound) as a non system user.

jeppesen-io 5y ago
Agreed - having user services is such a nice tool to have Makes sense as systemd took several ideas from MacOS launchd
phendrenad2 5y ago
...Hacks that worked around security features that were in place because Linux is, and always will be, a high-security server-first OS, with the desktop as an afterthought.

deknos 5y ago

it makes even more sense for the desktop than for servers. servers do not often un/mount stuff, often services are just a few and long running, and certainly no usb stuff which is running around. but the desktop is and will be a sprawling mess of components, look also too windows and mac. because nothing is totally certain, and something has to take care of it. what is your argument that systemd is not made for the desktop? and split dns can also occur in server systems which are public but have a virtual "inner" network. and my split dns works, so.. perhaps either your configuration sucks or the software is just not working at the desktop that seemlessly, but that will come. but it takes time.

hammyhavoc 5y ago

Since when have server distros shipped with Pipewire et al? Let's not conflate bundled programs with actual operating system functionality.