3 ms·
The answer to "why not standardize it" isn't to make a brand new and still-incomplete implementation part of init. At most there could have been justification f
by wtallis 12y ago
The answer to "why not standardize it" isn't to make a brand new and still-incomplete implementation part of init. At most there could have been justification for further standardizing the interface through which dnsmasq, unbound, et al. can act as the default system resolver. But it's not like they didn't all already have a way to do so.
- takeda 12y agoWhile current setup works well in server environment where ideally you want to have full control over services so you can set up your system by running only services that you actually need. But in case of desktop system such approach becomes very problematic. There are tons of services you need for it to function and simply there too many moving parts. From my limited experience Ubuntu shows it best. Because there's so much interaction required between many simple services it is full of race conditions with things working mostly ok but once in a while behave in an odd way.
- bitwize 12y agoThe answer to "why not standardize it" isn't to make a brand new and still-incomplete implementation part of init. Yes it is because unless you make it a required component of the core OS, balky sysadmins will never embrace it and Linux will keep doing the wrong thing. That's the ultimate goal of systemd: to enforce consistent, correct behavior across distributions.