Cheatcode mopt=commit=1 blows up Porteus. Suggestions?

Post here if you are a new Porteus member and you're looking for some help.
Post Reply
mysterylectricity
White ninja
White ninja
Posts: 17
Joined: 18 Feb 2015, 07:52
Distribution: 3.1
Location: San Francisco

Cheatcode mopt=commit=1 blows up Porteus. Suggestions?

Post#1 by mysterylectricity » 26 Apr 2015, 14:40

Hi,

When I add:

mopt=commit=1

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.

IE:

Code: Select all

 APPEND initrd=initrd.xz noswap from=LABEL:150405u1p1pB changes=LABEL:150405u1p2pD/porteussave.dat ramsize=10% volume=20% 
..works fine but:

Code: Select all

 APPEND initrd=initrd.xz noswap from=LABEL:150405u1p1pB changes=LABEL:150405u1p2pD/porteussave.dat mopt=commit=1 ramsize=10% volume=20% 
.. blows up.

I see several possibilities:

1) Somehow I'm failing to properly quote all or part of this cheatcode. Maybe:

mopt='commit=1'

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!

Thank you!

-Jeff

User avatar
Ed_P
Contributor
Contributor
Posts: 3156
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Cheatcode mopt=commit=1 blows up Porteus. Suggestions?

Post#2 by Ed_P » 26 Apr 2015, 16:58

Have you checked the format of the mopt cheatcode?
http://www.porteus.org/component/content/article/26-tutorials/general-info-tutorials/117-cheatcodes-what-they-are-and-how-to-use-them.html wrote:
mopt

... This cheatcode will allow you to customize your filesystem
mount options. By default, the mount options for all
filesystems in Porteus are: "noatime,nodiratime,suid,dev,exec,async".
Each option must be separated wtih a comma "," with no spaces
between any characters.
Example: 'mopt=realtime,sync,users,nosuid,noexec'
See 'man mount' for more information on specific mount options.
I don't see commit as an option.
Ed

User avatar
fanthom
Site Admin
Site Admin
Posts: 4566
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Cheatcode mopt=commit=1 blows up Porteus. Suggestions?

Post#3 by fanthom » 26 Apr 2015, 21:18

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.

i guess this is the case as seems that 'commit=' flag is supported only by ext3/4

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?
you have to edit linuxrc in initrd.xz and add specific rules to your filesystem
Please add [Solved] to your thread title if the solution was found.

Post Reply