Yes I also prefer to boot with changes=RAM since I don't always want to save what I'm doing (in fact I often don't). So that for me is the mode I'd use for saving out the, in that case, RAM-based upper_changes. I've been too busy myself on the core build script functionality to try saving out these changes. But I have glanced at the various mechanisms rufwoof has been using, and they all look good to me. So thus far that includes a general utility for simply merging together numbered upper_changes layers, or a simple compressed tar archive which gets untarred back in again (different, but a bit like tinycore Linux save archive), or rufwoof's latest .bak file idea, which is quite novel by the look of it.rufwoof wrote:I boot with changes=RAM, so upper_changes is mounted to /mnt/layers/RAM/upper_changes.
Sorry, half asleep just now and typing on android phone so probably typos or autocorrect errors.
wiak