4 ms·
Its not a part of systemd, its a part of ifupdown that was added to aide Debian's transition from SysV to systemd. Seems unfair to me to count this against syst
by gcommer 8y ago
Its not a part of systemd, its a part of ifupdown that was added to aide Debian's transition from SysV to systemd. Seems unfair to me to count this against systemd; there are other less intrusive ways this could've been done, and "allow reading configuration from env vars" is probably a good thing anyways.
https://github.com/wido/ifupdown/commit/c29820f370a4905b836660ee4cf0162cdafdac66 https://github.com/wido/ifupdown/commit/c29820f370a4905b8366...
- riobard 8y agoIs there any detailed roadmap of Debian's transition from SysV to systemd? Currently it's a mess in Debian 9 where some packages come with traditional init scripts and some with systemd unit files, and some even with upstart scripts.
- zwischenzug 8y agoAuthor here. It may be unfair, I didn't mean to imply any kind of judgement. 'This kind of thing' was vague, but was intended to get over the fact that systemd is taking over more and more of the OS, and people don't like this. Whether this is good or bad I'm fairly agnostic on. At least it's managed and a standard.
- aargh_aargh 8y agoI'm not one to flame on systemd but I have to correct you there - it's not a standard, it's a single implementation.