Damian Ivanov wrote:
wow, you kinda get stuck on whatever you can. multi-seat is an example. no real arguments againts systemd, let's hate what it does well, everything.
Not at all -- I am just taking the things touted as features and "must haves" and and examining them 1-by-1 as I have done before. Just as when I asked -- why move things to /usr/bin, when you could have put things in /bin and had the same effect (all in one place) but no risk of having /usr not mounted? That one wasn't easy to make a case for. Since if you want to hold it's state separate, you either subject it to snapshots that can be rolled back or make it read-only during normal use. If you wanted to share it, mount it on /usr/share/bin, then use rbind to mount it on /usr/share/bin and export that. There was no reason to cause the breakage that occurred, it was *unthinking* and bad design -- yet such moving of binaries and libs is ongoing (many packages need to go against the normal defaults of a package to put things in /usr with links in /bin). I.e. the decision could be made to roll it back. Same with providing for boot-from-disk. Vendors did it for years allowing customers to run a script generating a kernel for their system -- took no technical knowledge -- but did allow boot optimizing. Yet suse and linux can't do that... too 'compricated'... Rational arguments are ignored in the end. There is a breakdown in logic here somewhere (maybe I just didn't drink the koolaid?) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org