3 ms·
Actually, the article is about working around problems encountered integrating nfs with systemd. They were charitable enough to not use that kind of phrasing, b
by falcolas 10y ago
Actually, the article is about working around problems encountered integrating nfs with systemd. They were charitable enough to not use that kind of phrasing, but everything they talked about had to do with fixing new problems brought forth by using systemd at the upstream layer, so those downstream don't have to worry about it (but admitting that there are still some steps which have to be undertaken by the end user to avoid unnecessarily starting the rpcbind service).
They could have easily written this same article when nfs first came out and they were working through their default sysvinit scripts.
- kbenson 10y agoI'm pretty sure they were being charitable because that's a somewhat biased interpretation of what was being discussed. It would be trivial to make NFS start exactly as it did prior to systemd. I would characterize this as fixing the problems brought forth by trying to use NFS with the new capabilities systemd offers, and the unforseen consequences of doing so without knowing/considering how everything interconnects with it.
- lobster_johnson 10y agoNFS is an old (some would say legacy), idiosynchratic piece of software with multiple revisions that affect how you run it, depending on what kind of backwards compatibility you want. As the article points out, some of the problems could be eliminated by only enabling NFSv4 support, for example. If anything, the article is a good example of adapting new tech to work around the many odd behaviours of old tech.