Patrick, does it make sense to limit live mode for increased isolation in user-sysmaint-split, given that disk writing is limited? Live mode is very convenient for testing packages, new programs before installing in PERSISTENT mode. Often I try to install some program, but during installation, I encounter dependency problems, library version issues… as a result, package either doesn’t work or can disappoint me. And then it is very convenient to reboot. Rather than deleting everything I just installed + no traces of such experiments are left on disk
Root access in live mode is, for all intents and purposes, equivalent to root access in persistent mode from a security standpoint. It’s not at all difficult to mount the root filesystem read/write in one location even while it’s mounted read-only somewhere else (unless overlayfs somehow prevents that, which I highly doubt). Live mode shouldn’t be trusted to enhance one’s security (at least not by much), it’s a privacy enhancer only.
That being said, maybe this is a legitimate use for LIVE mode SYSMAINT? Currently that feature isn’t planned, but it would be pretty easy to implement.
1 Like
Yes. Documented here:
Remount Disk as Read-Write after booting into Live Mode
Yes.
Сould look like - LIVE mode SYSMAINT (for testing new packages before installed on disk). Admin’s laboratory
1 Like
I am implementing this.
Space is limited. Can only be 3 or 4 words.
LIVE Mode - SYSMAINT Session (For maintenance testing.)
1 Like
A post was split to a new topic: How to use zulucrypt in USER boot mode?