Page 3 of 3

Re: ISO - save changes

Posted: 25 Feb 2013, 10:30
by fanthom
@EdP

when you are booting with 'changes=EXIT:/mnt/sdb1/porteussave.dat' (or without EXIT:) cheatcode then save.dat container is mounted by initrd (read: "is being used") and you can't mount it from porteus session. this is done to avoid 2 independent "bodies" writing to the same file.
that's why you are are getting:

Code: Select all

[   79.043234] XFS (loop10): Filesystem has duplicate UUID 86bf39ee-fa3f-4de5-a068-a17da83834a6 - can't mount
if you want to resize .dat or check it's content then you must boot without 'changes=' cheatcode.

Re: ISO - save changes

Posted: 25 Feb 2013, 16:55
by Ed_P
Thank you Image fanthom.

Code: Select all

root@porteus:~# mloop /mnt/sdb1/porteussave.dat
using /dev/loop9

Please wait while i gather some info ....



#################################
Your data file has been mounted at:
/mnt/loop

You can unmount it by typing uloop

Here is a list of the files:
etc  opt  root	var

root@porteus:~# ls /mnt/loop
etc/  opt/  root/  var/
root@porteus:~# ls /mnt/loop/etc
NetworkManager/  adjtime  fstab  random-seed  udev/
X11/             cups/    mtab   resolv.conf
root@porteus:~# ls /mnt/loop/opt
porteus-scripts/
root@porteus:~# ls /mnt/loop/opt/porteus-scripts
uloop*
root@porteus:~# ls /mnt/loop/etc/networkmanager
/bin/ls: cannot access /mnt/loop/etc/networkmanager: No such file or directory
root@porteus:~# ls /mnt/loop/etc/NetworkManager
system-connections/
root@porteus:~# ls /mnt/loop/etc/NetworkManager/system-connections
QuickMoose
root@porteus:~# cat /mnt/loop/etc/NetworkManager/system-connections/QuickMoose
[connection]
id=QuickMoose
uuid=3cefcb8c-b823-462d-8e0a-f57f3bdaffb3
type=802-11-wireless

[802-11-wireless]
ssid=QuickMoose
mode=infrastructure
mac-address=60:D8:19:1A:A1:FC
security=802-11-wireless-security

[802-11-wireless-security]
key-mgmt=wpa-psk
auth-alg=open
psk=mtFGg6Lem2

[ipv4]
method=auto

[ipv6]
method=auto
root@porteus:~# du -sh mnt/loop
du: cannot access ‘mnt/loop’: No such file or directory
root@porteus:~# du -sh /mnt/loop
20M	/mnt/loop
root@porteus:~# uloop

/mnt/loop has been unmounted

root@porteus:~#
I don't suppose there is a way to dynamically invoke the save file function when booted without the changes= option without rebooting is there?

My changes seem to be quite modular. I may start looking into converting them to extramods.

Thanks again. :beer:

Re: ISO - save changes

Posted: 26 Feb 2013, 13:59
by brokenman
and I know it has my changes in it since I just booted and they are here.
It should have clicked for me after reading this that you were trying to open the boat you were floating in. Sorry.

You can use the 'save session' function in the Porteus Settings Centre which can create a module from your current session changes. For the record i ALWAYS boot in fresh mode and just save a session when i am happy with it. The resulting module goes into the porteus/modules folder and when they accumulate (and i am happy all is well) i merge all the modules into one single module.

Re: ISO - save changes

Posted: 08 Apr 2013, 04:06
by Ed_P
FYI I have my Porteus 2.0 ISO running now on a USB flash drive formatted with NTFS and it and the save.dat file work fine.