3 ms·
> If you're not solving problems in the real world, you're not really solving problems; you are just being smug and 'clever'. systemd is a project that wants t
by geofft 10y ago
> If you're not solving problems in the real world, you're not really solving problems; you are just being smug and 'clever'.
systemd is a project that wants to change what the real world is. It makes no secret of this. See, for instance, the very small /etc/os-release file: http://0pointer.de/blog/projects/os-release.html http://0pointer.de/blog/projects/os-release.html
"It's our hope that by dropping support for non-compliant distributions we gently put some pressure on the remaining hold-outs to adopt this scheme as well."
Sometimes they aim too high and it just doesn't work (see, e.g., the stateless systems stuff that assumes that everyone is bought in completely and also loves btrfs). When that happens, they don't start dropping support for everyone, they just quietly give up. But I don't think that support for SysV init scripts or /etc/fstab is evidence of a changed view on pragmatism. The way to change the world was to start with compatibility the world as it is, and push steadily for improvements. Device naming is unambiguously a place where the world needs to get better, and systemd is right to push for improvements (although I may disagree quite a bit with what specific improvements they're pushing for and how!).
Also note that Poettering is quite specifically is okay with /etc/fstab because he doesn't see anything he wants to change with them: the format is expressive enough for everything he envisions. https://github.com/systemd/systemd/issues/4961 https://github.com/systemd/systemd/issues/4961
- Touche 10y agoThe FAQ of that article is quintessential NIH, which I think summarizes the systemd project well.
- yjftsjthsd-h 10y agoNot just NIH; the condescension and strawmanning are well demonstrated as well. But yes, a wonderful example of the project's attitudes.
- geofft 10y agoCan you explain why you think it's NIH? As someone who's written a lot of code to parse lsb_release (including an installer script that starts with "apt-get install lsb-release", because you can't even depend on lsb-release being installed on Debian/Ubuntu), I certainly agree with just about all of the FAQ in substance, if not in tone.
- yjftsjthsd-h 10y agoBoth LSB and whatever Fedora was doing before were one small patch away from working for their purposes... so they created an entirely new format instead of trying to cooperate with anybody else.
- geofft 10y agoWhat would the small patch look like? As a consumer, the requirements I have are 1. always available, 2. machine-parseable without running a script, and 3. cross-distro (like lsb_release already is). I think any patch that gets you that causes you to end up with /etc/os-release, although possibly under a different name, no?
- orf 10y agoA single format in a well defined place is better than /etc/redhat-release, /etc/SuSE-release, /etc/debian_version, /etc/arch-release, /etc/gentoo-release, /etc/slackware-version, /etc/frugalware-release, /etc/altlinux-release, /etc/mandriva-release, /etc/meego-release, /etc/angstrom-version, /etc/mageia-release all possibly being present. Lot's of historical crud to clean up in *nix land, this is one of them.
- teddyh 10y agoIt’s called “Pacing and leading”.