I am not comfortable with the feature creep that systemd is slowing bringing in. binfmt mount executing files based on a lookup, similar to windows assoc, intercepting gethostbyname(), this really feels like an attempt to shim old vulnerable windows concepts into linux. I am concerned that linux will not be recognizable in the near future and will be subject to bloat and obfuscation. What would it take to make this stop?<p>There are some things brought in that I like, but I don't believe systemd is required for them. Cgroups, LXC, to name a couple. Those make functional and operational sense to me.
I'm going to pass on this one. How is /etc not 'extensible'? You just add a new file to the directory. Reinventing the windows registry, but this time in JSON, is a lateral move that is only going to complicate maintaining systems.<p>For user level configuration, you already have too many competing mechanisms for doing this already, and this one requires systemd level integration making it much more coupled to the operating system and system in general.
talk / context: <a href="https://streaming.media.ccc.de/asg2019/relive/164" rel="nofollow">https://streaming.media.ccc.de/asg2019/relive/164</a><p>edit: I think the most important part of the talk was an answer to question about why .ssh/authorized_keys won't be possible with this scheme (42:00):<p>> this is about protecting your data from the system as much as possible, so that when you are not logged in it's really cut off<p>This looks like, among other things, an ecryptfs replacement.
Some of Lennart's inventions that he presents at conferences seem to lose momentum soon after. A while ago he talked about casync and mkosi. Both of these seemed more interesting to me than this but progress seem slow or stalled. We will see what becomes of this, but I don't think it is a slam dunk and what everyone has always needed but never realized. I think by ruling out remote /server use cases he will limit the interest in it.