Thanks for elaborating! > Whereas on Haiku with packagefs, the package_daemon gives the packagefs the new state description, and it can update all of its inter

Thanks for elaborating! > Whereas on Haiku with packagefs, the package_daemon gives the packagefs the new state description, and it can update all of its internal states and re-bind everything internally with a lot less overhead, because both ends of the system know exactly what is going on. That sounds reasonable. Thus far, my implementation is quick enough for the number of packages I’m dealing with, but perhaps I run into similar limitations down the road :) > because the bootloader itself speaks "packagefs", and can load the kernel out of a package. Understood, cool. I haven’t actually explored how to revert to older systems in the most user-friendly way in distri. Currently, in the rare cases where I actually brick my system, I just boot distri from a USB stick (takes 20s to write), mount my disk and run “distri reset /var/log/distri/update/<latest>/before.txt”. I’m thinking retaining old kernel/initrd combinations and mounting an older set of packages from the initrd might be a viable path. > people who complain that Linux is unsuitable for $average_user will remain correct Possibly, but that’s not what my project is trying to achieve :)