burninbush wrote:I appreciate your indulgence on my issue, understand it's not the intended usage. I have had good success booting other slack-like livecds in this poor man's manner, though none using your system.
Actually it is intended usage just not documented. Anyway I suspect the poor man's install is not the issue here.
burninbush wrote: And after asking 2x I still have no idea what enables persistence.
I can't seem to find those. Apart, I thought you already found out yourself that it's enabled by default. There's also a savefile cheatcode which allows you to change the basename (i.e. the last component of the path --> salixlive.save). The actual path used is $basedir/salix/persistence/$savefile
burninbush wrote:OK, I tried that, made no difference at all to the panic. One thing that did make a difference, allowed me to boot one time, was to run a mkfs.reiserfs on the container file, after which it booted in what looks like normal fashion. Changed a couple things, but then a reboot evoked the same panic. Tried that again to be sure; it boots fine when that file is empty, panics when it has anything inside it. And after asking 2x I still have no idea what enables persistence.
You seem to be deleting /bin/chroot from the live environment. As this change is saved with the persistence file you can't boot anymore. At least by doing that I'm getting exactly the same error message as you.
So that makes me wondering what those couple things are or whatever else you did to trigger such a change. Maybe you should try first with small changes. Adding a file to my home directory was e.g. no problem.
burninbush wrote:Giving up here, good luck with your distro, and thanks again for the effort you put into my issue.
That's unfortunate. It would have been interesting to know how you triggered that removal of /bin/chroot.