Finally the people's questions are answered! 
What is moss?
- Edited
I'm idiot at all this,I trust you guys to build it good and strong, so; one thing I'd say: Make it Rain.
Moss=Mother of Software Systems...lol
- Edited
I wonder about logouts/reboots after installation some particular packages:
- do you need reboot/logout after e.g. Firefox update?
- do you need reboot after a new kernel update?
Another question: how it would affect the boot and shutdown fast speed (the killer feature of Solus)?
Not gonna lie, it goes a bit over my head still but I think I'm slowly becoming a moss convert after rage quitting several of the immutable distros several times over mostly the reboot requirements.
Lighted this is definitely sounding in the range of "immutability done right" for me, but I wonder if a package instalation fails are we able to roll back generationally like NixOS/Silverblue?
With moss, will the format of the commands to update the system etc. change? Will it be sudo moss up instead of sudo eopkg up ? I don't want to have the commands become more complex for simple stuff, as that's one of the reasons as to why I like using Solus over other distros
- Edited
davidjharder On a system using moss, what happens if a user tries to move an executable by hand into /usr/bin? Presumably the executable gets wiped out by the next moss install?
Right now, I imagine that the binary would stay within the corresponding transaction directory in /.moss/root/${transactionID}/.
In the future, we're looking at ensuring that everything under /usr (/usr/local will be a symlink to somewhere under /var probably) will be protected (= read-only, except to moss & friends) such that you cannot write to it, even as root in "normal use".
HTH