Porteus

brokenman wrote:I should add that when saving the changes as a module you can NOT create the module within the live system (E.g /home/guest/module.xzm or /tmp/module.xzm) because you would be caught in a loop where the changes are always changing because you are creating a module there.

Whoa!! OK, thanks for the clarification. I think I will continue doing it my way.

This thread might contribute to this topic. A Firefox question

For me, the result of following that instruction was:
-- no changes saved
i guess you never meet required condition:
While you are running a session with changes=EXIT, you can use the 'dump-session' command

To clarify/expand what I posted earlier, here's the scenario

file successfully created:
/mnt/sdb1/boot/syslinux/porteus.cfg

boot line reads:
APPEND initrd=initrd.xz changes=EXIT:/porteussave.dat ramsize=42% timezone=America/New_York login=root

The result of calling dump-session:
-- savefile is NOT modified
-- AUFS layer (or whatever) is blanked, and system state is apparently "fresh, as of the beginning of this current xsession"

despite repeated requests, pleas, suggestions... there's still a user/dev disconnect.
i'm getting annoyed by all these people coming here and trying to convert porteus to puppy with all the popups/wizards/etc...
from my point of view such system is a pain to use and i would probably have to abandon it.

Seriously?!?

Okay, I'll go stand in the too-f'ing-stupid-to-use-Porteus corner

Seriously, and sincerely, I'm apologizing for however I've contributed to your annoyance.
Goodbye.

ok - tomorrow i'll double check if 'dump-session' script still does the job correctly.

Okay, I'll go stand in the too-f'ing-stupid-to-use-Porteus corner
Porteus is different than everything many users have come across so far (i mean other distros). it gives you a lot of power but that power requires a knowledge which can only be gained by reading the docs

EDIT:
seems that you were right and i have pushed fixed 'dump-session' script to porteus updates:
http://dl.porteus.org/x86_64/testing/up ... ngeLog.txt

thanks a lot for reporting.