I am well aware that I can deliver mails to another dir but the home dir. It is in fact the prerequisite for virtual users.
But, users usually have scripts in their home dir e.g. ~/bin, they can’t just write to persistent storage outside their home (unless setup separately). Thus cron jobs are a bust, and there are also other services that might need access. I am not saying that this isn’t possible, but rather just a hassle I’d like to avoid.
Their scripts can read from outside the home directory when the user is logged in.
Potentially the mail could be in /var/spool/mail and when the user logs in the script could retrieve the mail for them.
Indeed, this is true. It’s also true for autofs as well. It’s also true for script environments that live in the user’s home folder. It’s important and useful to grok the limitations of such things and if it doesn’t fit your use case, then maybe systemd-homed isn’t the right fit for that environment or you might need to use an alternative path for those scripts to love.
I use scripts and systemd user services to manage my portable home directory.
I use timers as a substitute for cron processes
I use paths to monitor files and/or directories for creation, deletion or modifications.
I use services to start and stop my podman containers
I install my flatpaks from flathub in user mode
You should be able to accomplish normal user interactions when you are mounted, logged in and have the correct label context for the home directory. When the user’s and system’s Group permissions match, those permissions are also available.
There were more errors, mostly I/O. As I upgraded Fedora while I was logged in with my homed user, maybe upgrade process has interrupted some I/O, which in turn resulted into damaged loop file. I deleted my homed user (it was created for experimenting with homed) and tried to create new using exactly same command, but now I get new error:
21:47:28 systemd-homed: Operation on failed: Invalid argument
21:47:28 kernel: I/O error, dev loop0, sector 0 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 2
21:47:28 systemd-homewor: Failed to set up LUKS password for slot 0: Invalid argument
21:47:23 systemd-homed: Operation on failed: Wrong medium type
On F37 same command created fully functional homed-managed user
Apologies, I was stupid and impatient - deleted my homed user with the hope to re-create it without errors, but got new ones instead. This means I cannot check avc denials on old user (deleted) and on new as well (cannot create it yet).