When I add:
as a cheatcode in porteus,cfg, all hell breaks loose.
It complains about a bad "changes" or "from" cheatcode, not finding my disk by label (or something like that) and enters "debug mode".
Only by booting into always fresh could I fix porteus.cfg by removing this cheatcode.
..works fine but:
Code: Select all
APPEND initrd=initrd.xz noswap from=LABEL:150405u1p1pB changes=LABEL:150405u1p2pD/porteussave.dat ramsize=10% volume=20%
.. blows up.
Code: Select all
APPEND initrd=initrd.xz noswap from=LABEL:150405u1p1pB changes=LABEL:150405u1p2pD/porteussave.dat mopt=commit=1 ramsize=10% volume=20%
I see several possibilities:
1) Somehow I'm failing to properly quote all or part of this cheatcode. Maybe:
or something like that would work better.
2) It won't work because I'm asking too much of the cheatcodes mechanism to properly pass the commit=1 argument intact regardless
as to my syntax.
3) I screwed up my file edit and should try it again.
4) The commit option is not compatible with one or more of my file system types (I think I use 3 or 4 different types on a single USB stick)
and Porteus/Linux bombs out with error messages are a bit misleading when it tries to apply the commit option to a FS that doesn't support it.
Sooooo... if i can't fix this problem in porteus.cfg, what is the path to the persistent version of fstab (or its precursor, or its modern day replacement) where I can add the commit=1 option on a FS by FS or otherwise explicit basis?
Recommended or example line entry? Esp. if the file is not self-documenting or is empty by default in Porteus.
Of course I may be missing some third possibility entirely. I'm all ears!