Yes, please give more details, so it is reproducible, b/c "... and it didn't go well" doesn't tell muchtrawglodyte wrote: ↑Fri Feb 16, 2024 10:09 pm 1. When I do the frugal install I wind up as user "demo", and I probably should have just left that alone. But I tried using MX User Manager to Rename User Account, and it didn't go well. I eventually got it sorted, my user is mxl now, but I'd be happy to do another install and try it again, perhaps give better info on what exactly happened if someone thinks this is important.
The tool is using this command:trawglodyte wrote: ↑Fri Feb 16, 2024 10:09 pm 2. It seems that when I use the startup and shutdown screens for loading and saving rootfs (I'm doing semi-automatic mode) everything is fine, but when I try to use RemasterCC to Save root persistence things go wrong.
Code: Select all
pkexec persist-save
Code: Select all
sudo persist-save --cli
Yes, any "frugal" options given would trigger a frugal detection live-process.trawglodyte wrote: ↑Fri Feb 16, 2024 10:09 pm 3. Despite choosing frugal_root on install, the boot paramater created was persist_root. Which (I think) is doing what I want it to do, and when I tried changing it to frugal_root I think maybe it didn't do what I wanted. So, anyway, leaving it persist_root is cool with me. Just wanted to document that here.
The boot parameter frugal_root is a shortcut for "frugal persist_root"
The frugal process would try first to find an available frugal-install and boot into,
and if not found offers to create / make a frugal install.
The generated grub.entry is meant to boot into the existing frugal install.
When using frugal_root instead of "persist_root" the frugal detection
would start to search for an existing frugal install,
by using the default frugal partition label flab="antiX-Frugal"
and the default frugal boot-dir fdir="/antiX-$(uname -r)"
So yes, you can trigger another frugal installation when attempting to boot into an existing
frugal installation.