6 ms·

No, it is saying "don't build systemd from source unconfigured and then run it in production", which is an entirely reasonable point to make. systemd is meant t

No, it is saying "don't build systemd from source unconfigured and then run it in production", which is an entirely reasonable point to make. systemd is meant to be, by self-description, "a toolbox to build an operating system", not "something you install and expect it to work". Distributions are expected to configure reasonable defaults amongst other configuration.

LoSboccacc 11y ago
and where does it say that I have to configure it? and I'm quoting the man page here [1]: "NTP This setting defaults to an empty list" "FallbackNTP If this option is not given, a compiled-in list of NTP servers is used instead" "Files in /etc/ are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages" sorry but no: I'm not supposed to magically guess that the default setting is going to violate some term of services of a corporation, especially as: " this list is combined with any per-interface NTP servers acquired from systemd-networkd.service(8)" so all it say is it works trough discovery, be happy and configure the networkd service and all will be fine. [1] http://www.freedesktop.org/software/systemd/man/timesyncd.conf.html http://www.freedesktop.org/software/systemd/man/timesyncd.co...
- bkor 11y ago
  Your distribution will already have set different defaults. Various of the major distributions have done so. Lennart also said he'd accept a patch to add a big warning in configure if you fail to provide these defaults. Linking to a bugreport with an ongoing discussion is a bit pointless IMO. It's still being discussed!
  - Sanddancer 11y ago
    Any binary default is wrong and broken, period. It's especially wrong and broken to set that binary default to a server you have no control over. It's triply wrong and broken to set that binary default to a server you have no control over whose maintainer has asked that you not use in this way. At the very least, the systemd team should have the decency to document what this default is so that administrators trying to hunt down suspicious and/or unusual activity have some starting point to go from.
- Merovius 11y ago
  "configured" as in "./configure". If you build systemd yourself, configure it. If you don't it will come with sensible defaults.
  - LoSboccacc 11y ago
    except default aren't anywhere close to sensible, which is the whole point really
    - Merovius 11y ago
      The defaults on my installation are *.debian.pool.ntp.org. Can you give me an example of an installation with less sensible defaults? edit: Ah, I think I now know where the misunderstanding lies. My "if you don't" refers to "if you don't build it from source", not to "if you don't ./configure it".
  - Aloha 11y ago
    Why would this stuff be baked into the binary for the software?
digi_owl 11y ago
And this seems to be a plague on Linux as of late. I recall a few years back someone involved with a minor distro reached out to the X.org people for some assistance getting the thing to build. The response was something akin to "Why would you do that?! Go install a big name distro already!". There is something rotten in Linux userland...

LoSboccacc 11y ago

and where does it say that I have to configure it? and I'm quoting the man page here [1]: "NTP This setting defaults to an empty list" "FallbackNTP If this option is not given, a compiled-in list of NTP servers is used instead" "Files in /etc/ are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages" sorry but no: I'm not supposed to magically guess that the default setting is going to violate some term of services of a corporation, especially as: " this list is combined with any per-interface NTP servers acquired from systemd-networkd.service(8)" so all it say is it works trough discovery, be happy and configure the networkd service and all will be fine. [1] http://www.freedesktop.org/software/systemd/man/timesyncd.conf.html http://www.freedesktop.org/software/systemd/man/timesyncd.co...

bkor 11y ago
Your distribution will already have set different defaults. Various of the major distributions have done so. Lennart also said he'd accept a patch to add a big warning in configure if you fail to provide these defaults. Linking to a bugreport with an ongoing discussion is a bit pointless IMO. It's still being discussed!
- Sanddancer 11y ago
  Any binary default is wrong and broken, period. It's especially wrong and broken to set that binary default to a server you have no control over. It's triply wrong and broken to set that binary default to a server you have no control over whose maintainer has asked that you not use in this way. At the very least, the systemd team should have the decency to document what this default is so that administrators trying to hunt down suspicious and/or unusual activity have some starting point to go from.
Merovius 11y ago
"configured" as in "./configure". If you build systemd yourself, configure it. If you don't it will come with sensible defaults.
- LoSboccacc 11y ago
  except default aren't anywhere close to sensible, which is the whole point really
  - Merovius 11y ago
    The defaults on my installation are *.debian.pool.ntp.org. Can you give me an example of an installation with less sensible defaults? edit: Ah, I think I now know where the misunderstanding lies. My "if you don't" refers to "if you don't build it from source", not to "if you don't ./configure it".
- Aloha 11y ago
  Why would this stuff be baked into the binary for the software?

digi_owl 11y ago

And this seems to be a plague on Linux as of late. I recall a few years back someone involved with a minor distro reached out to the X.org people for some assistance getting the thing to build. The response was something akin to "Why would you do that?! Go install a big name distro already!". There is something rotten in Linux userland...