Strange save.dat behavior [Solved ]

Post here if you are a new Porteus member and you're looking for some help.
User avatar
Ed_P
Contributor
Contributor
Posts: 8343
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Strange save.dat behavior [Solved ]

Post#1 by Ed_P » 22 May 2014, 15:20

fanthom wrote:btw: please start new thread if there is no 'single post' answer as this bug does not belong to USM.
No problem. How's this?
fanthom wrote:i see only two options:
- 'changes=EXIT:' cheatcode does not dump your savings (i checked yesterday and it was ok). could you confirm that anything (like new wallpaper or random file on the desktop) gets saved?
Stuff gets saved all the time. Firefox bookmarks, network files, /home/guest files, /home/guest/. folder files, etc.
- one of your custom startup/shutdown scripts messes up the changes (remember that they are stored in RAM until the shutdown)
I don't believe I have any other than one for my mouse pad.

syndaemon.desktop

Code: Select all

[Desktop Entry]
Exec=syndaemon -i 1 -d
Name=syndaemon
Icon=/usr/share/pixmaps/porteus/error.png
Type=Application
Version=1.0
in /home/guest/.config/autostart. Refer to this posting for details: http://forum.porteus.org/viewtopic.php? ... =45#p13596
brokenman wrote:changes=EXIT:/porteus/changes/porteussave.dat is in your boot line. This means that whatever is in the root of this file gets loaded into the root of your live file system.
Yes.
brokenman wrote:/mnt/sda5//porteus/changes/porteussave.dat/changes is a module that was loaded. This looks weird to me. Do you have the folder: /changes (check with: ls /changes)
That looks weird to me also. /mnt/sda5/porteus/changes/porteussave.dat is a file not a directory. Where are you seeing that?

Code: Select all

guest@porteus:~$ ls /mnt/sda5/porteus/changes
porteussave-Base.dat*  porteussave-old-Bkup.dat*  porteussave.dat*
porteussave-b4.dat*    porteussave-old.dat*
guest@porteus:~$ ls /mnt/sda5//porteus/changes/porteussave.dat/changes
/bin/ls: cannot access /mnt/sda5//porteus/changes/porteussave.dat/changes: Not a directory
guest@porteus:~$ 
Don't let the multiple .dat files scare you. They are used for my testing of this problem.
Also what scripts automatically start when you boot? (the contents of /etc/rc.d/rc.local for example)
rc.local

Code: Select all

#!/bin/sh
#
# /etc/rc.d/rc.local:  Local system initialization script.
#
# Put any local startup commands in here.  Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.



- update -

My basic NTFS directory structure for porteus is:

/mnt/sda5/ISOs - for .iso and related support files.

/mnt/sda5/porteus - for porteus directories and related Windows support files.
/mnt/sda5/porteus/changes - for the save.dat file plus currently several backups.
/mnt/sda5/porteus /modules - for .xzm files
/mnt/sda5/porteus/modsavedat - for a renamed copy of my save.dat file. Used when I don't use the changes= cheatcode.
/mnt/sda5/porteus/Guest - for a backup of my /home/guest files
Last edited by Ed_P on 01 Jun 2014, 05:52, edited 3 times in total.
Ed

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Strange save.dat behavior.

Post#2 by fanthom » 23 May 2014, 05:33

"Stuff gets saved all the time. Firefox bookmarks, network files, /home/guest files, /home/guest/. folder files, etc."
so everything gets saved except for USM files - is it? and you say that nothing is excluded in /etc/changes-exit.conf.
really weird - please upload your setup or at least gzipped save.dat.
Please add [Solved] to your thread title if the solution was found.

User avatar
Ed_P
Contributor
Contributor
Posts: 8343
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: Strange save.dat behavior.

Post#3 by Ed_P » 23 May 2014, 13:04

fanthom wrote:so everything gets saved except for USM files - is it?
Not all of them but certainly some of them.

Code: Select all

guest@porteus:~$ ls /usr/bin/usm*
/usr/bin/usm*  /usr/bin/usmgui*

guest@porteus:~$ ls /etc/usm*

guest@porteus:~$ ls /usr/share/usm

guest@porteus:~$ ls /usr/man/man8/usm.8*
/usr/man/man8/usm.8.gz

guest@porteus:~$ ls /var/usm
alien/  local/  ponce/  salix/  slackware/  slacky/

guest@porteus:~$ 
really weird
Definitely.
- please upload your setup or at least gzipped save.dat.
I PMed it to you.
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 8343
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: Strange save.dat behavior.

Post#4 by Ed_P » 23 May 2014, 20:26

The really weird part, the usm files are saved in the save.dat file. They just aren't being reloaded when booting.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# mloop  /mnt/sda5/porteus/changes/porteussave.dat
using /dev/loop6

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  home  opt	root  usr  var

root@porteus:/home/guest# ls /mnt/loop/etc/usm
files.conf         mirrors-salix.txt       mirrors-slackware.txt         suppliment-libs.txt
mirrors-alien.txt  mirrors-sbo.txt         mirrors-slackwarepatches.txt  suppliment-optifest.txt
mirrors-ponce.txt  mirrors-slackverse.txt  mirrors-slacky.txt            usm.conf
root@porteus:/home/guest# 
The above done in Always fresh mode.

And in changes=EXIT mode we have:

Code: Select all

guest@porteus:~$ ls /etc/usm

guest@porteus:~$ ls /mnt/live/memory/images/changes/etc/usm
files.conf         mirrors-sbo.txt               mirrors-slacky.txt
mirrors-alien.txt  mirrors-slackverse.txt        suppliment-libs.txt
mirrors-ponce.txt  mirrors-slackware.txt         suppliment-optifest.txt
mirrors-salix.txt  mirrors-slackwarepatches.txt  usm.conf
guest@porteus:~$ 
and

Code: Select all

root@porteus:/home/guest# ls /mnt/live/memory/images/changes/usr/share/usm
README           funccli*            funcpackageInfo*    funcsystemSetup*
funcchangelogs*  funcelementCreate*  funcpackageSearch*  functxtStatic*
funcchecks*      funcgtkDialogs*     funcslackbuilds*    funcupdateDatabase*
funccleanup*     funcpackageGet*     funcsystemDeps*     funcworkhorse*

root@porteus:/home/guest# ls /usr/share/usm
root@porteus:/home/guest# 
If I manually restore the usm files I can get to here:

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# cp /mnt/live/memory/images/changes/etc/usm/* /etc/usm
root@porteus:/home/guest# ls /etc/usm
files.conf         mirrors-sbo.txt               mirrors-slacky.txt
mirrors-alien.txt  mirrors-slackverse.txt        suppliment-libs.txt
mirrors-ponce.txt  mirrors-slackware.txt         suppliment-optifest.txt
mirrors-salix.txt  mirrors-slackwarepatches.txt  usm.conf

root@porteus:/home/guest# usm -v
/usr/bin/usm: line 55: /usr/share/usm/funcelementCreate: No such file or directory
/usr/bin/usm: line 56: /usr/share/usm/funccleanup: No such file or directory
/usr/bin/usm: line 57: /usr/share/usm/funcsystemSetup: No such file or directory
/usr/bin/usm: line 58: /usr/share/usm/funccli: No such file or directory
/usr/bin/usm: line 59: /usr/share/usm/funcgtkDialogs: No such file or directory
/usr/bin/usm: line 60: /usr/share/usm/functxtStatic: No such file or directory
/usr/bin/usm: line 61: /usr/share/usm/funcpackageSearch: No such file or directory
/usr/bin/usm: line 62: /usr/share/usm/funcpackageInfo: No such file or directory
/usr/bin/usm: line 63: /usr/share/usm/funcchecks: No such file or directory
/usr/bin/usm: line 64: /usr/share/usm/funcpackageGet: No such file or directory
/usr/bin/usm: line 65: /usr/share/usm/funcupdateDatabase: No such file or directory
/usr/bin/usm: line 66: /usr/share/usm/funcchangelogs: No such file or directory
/usr/bin/usm: line 67: /usr/share/usm/funcslackbuilds: No such file or directory
/usr/bin/usm: line 68: /usr/share/usm/funcsystemDeps: No such file or directory
/usr/bin/usm: line 128: help_check: command not found
/usr/bin/usm: line 134: system_setup: command not found

You are using USM version: 3.1.1
/usr/bin/usm: line 240: cleanup: command not found
/usr/bin/usm: line 587: cleanup: command not found

root@porteus:/home/guest# ls /mnt/live/memory/images/changes/usr/share/usm
README           funccli*            funcpackageInfo*    funcsystemSetup*
funcchangelogs*  funcelementCreate*  funcpackageSearch*  functxtStatic*
funcchecks*      funcgtkDialogs*     funcslackbuilds*    funcupdateDatabase*
funccleanup*     funcpackageGet*     funcsystemDeps*     funcworkhorse*

root@porteus:/home/guest# ls /usr/share/usm

root@porteus:/home/guest# cp /mnt/live/memory/images/changes/usr/share/usm/* /usr/share/usm/

root@porteus:/home/guest# ls /usr/share/usm
README           funccli*            funcpackageInfo*    funcsystemSetup*
funcchangelogs*  funcelementCreate*  funcpackageSearch*  functxtStatic*
funcchecks*      funcgtkDialogs*     funcslackbuilds*    funcupdateDatabase*
funccleanup*     funcpackageGet*     funcsystemDeps*     funcworkhorse*

root@porteus:/home/guest# usm -v

 You are missing required database files! 
 Please run: usm -u all

root@porteus:/home/guest# 
I'm not sure what to do at this point. Basically I need a script to restore all the usm files and folders then usm should work again.
Ed

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Strange save.dat behavior.

Post#5 by fanthom » 23 May 2014, 21:33

so we are getting closer.
now i think that .wh. files could get somehow to the module and blanks usm files in /union.

please show me output of this command:

Code: Select all

find /mnt/live/memory -name .wh.* 
thanks
Please add [Solved] to your thread title if the solution was found.

User avatar
Ed_P
Contributor
Contributor
Posts: 8343
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: Strange save.dat behavior.

Post#6 by Ed_P » 23 May 2014, 21:42

fanthom wrote:please show me output of this command:

Code: Select all

find /mnt/live/memory -name .wh.* 
Yes sir.

Code: Select all

root@porteus:/home/guest# find /mnt/live/memory -name .wh.*
/mnt/live/memory/changes/.wh..wh.orph
/mnt/live/memory/changes/.wh..wh.plnk
/mnt/live/memory/changes/.wh..wh.aufs
/mnt/live/memory/changes/var/log/packages/.wh.usm-3.1.0-noarch-2
/mnt/live/memory/changes/var/usm/alien/.wh..wh..opq
/mnt/live/memory/changes/var/usm/slacky/.wh..wh..opq
/mnt/live/memory/changes/var/usm/slackware/.wh..wh..opq
/mnt/live/memory/changes/var/usm/salix/.wh..wh..opq
/mnt/live/memory/changes/var/usm/ponce/.wh..wh..opq
/mnt/live/memory/changes/var/usm/local/.wh..wh..opq
/mnt/live/memory/changes/var/usm/.wh..wh..opq
/mnt/live/memory/changes/usr/lib/.wh.libxml.so.1
/mnt/live/memory/changes/usr/lib/.wh.libpng.so.2
/mnt/live/memory/changes/usr/share/usm/.wh..wh..opq
/mnt/live/memory/changes/usr/lib64/.wh.libapm.so.1
/mnt/live/memory/changes/usr/man/man8/.wh.usm.8
/mnt/live/memory/changes/home/guest/.macromedia/Flash_Player/macromedia.com/support/flashplayer/sys/.wh..wh..opq
/mnt/live/memory/changes/home/guest/Backups/FireFox/.wh.bookmarks-2014-05-04.json
/mnt/live/memory/changes/home/guest/Backups/FireFox/.wh.bookmarks-2014-05-18.json
/mnt/live/memory/changes/home/guest/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/.wh.bookmarks-2014-05-17.json
/mnt/live/memory/changes/home/guest/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/.wh.bookmarks-2014-05-16.json
/mnt/live/memory/changes/home/guest/.cache/mozilla/firefox/c3pp43bg.default/safebrowsing/.wh..wh..opq
/mnt/live/memory/changes/home/guest/.wh.Use
/mnt/live/memory/changes/home/guest/.wh.Preferences
/mnt/live/memory/changes/home/guest/.wh.Privacy
/mnt/live/memory/changes/home/guest/.wh.History
/mnt/live/memory/changes/home/guest/.wh.Java
/mnt/live/memory/changes/etc/usm/.wh..wh..opq
/mnt/live/memory/images/changes/etc/usm/.wh..wh..opq
/mnt/live/memory/images/changes/home/guest/.macromedia/Flash_Player/macromedia.com/support/flashplayer/sys/.wh..wh..opq
/mnt/live/memory/images/changes/home/guest/Backups/FireFox/.wh.bookmarks-2014-05-04.json
/mnt/live/memory/images/changes/home/guest/Backups/FireFox/.wh.bookmarks-2014-05-18.json
/mnt/live/memory/images/changes/home/guest/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/.wh.bookmarks-2014-05-17.json
/mnt/live/memory/images/changes/home/guest/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/.wh.bookmarks-2014-05-16.json
/mnt/live/memory/images/changes/home/guest/.cache/mozilla/firefox/c3pp43bg.default/safebrowsing/.wh..wh..opq
/mnt/live/memory/images/changes/home/guest/.wh.Use
/mnt/live/memory/images/changes/home/guest/.wh.Preferences
/mnt/live/memory/images/changes/home/guest/.wh.Privacy
/mnt/live/memory/images/changes/home/guest/.wh.History
/mnt/live/memory/images/changes/home/guest/.wh.Java
/mnt/live/memory/images/changes/usr/lib/.wh.libxml.so.1
/mnt/live/memory/images/changes/usr/lib/.wh.libpng.so.2
/mnt/live/memory/images/changes/usr/share/usm/.wh..wh..opq
/mnt/live/memory/images/changes/usr/lib64/.wh.libapm.so.1
/mnt/live/memory/images/changes/usr/man/man8/.wh.usm.8
/mnt/live/memory/images/changes/var/log/packages/.wh.usm-3.1.0-noarch-2
/mnt/live/memory/images/changes/var/usm/alien/.wh..wh..opq
/mnt/live/memory/images/changes/var/usm/slacky/.wh..wh..opq
/mnt/live/memory/images/changes/var/usm/slackware/.wh..wh..opq
/mnt/live/memory/images/changes/var/usm/salix/.wh..wh..opq
/mnt/live/memory/images/changes/var/usm/ponce/.wh..wh..opq
/mnt/live/memory/images/changes/var/usm/local/.wh..wh..opq
/mnt/live/memory/images/changes/var/usm/.wh..wh..opq
root@porteus:/home/guest# 
Ed

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Strange save.dat behavior.

Post#7 by fanthom » 23 May 2014, 22:01

they should never be present in /mnt/live/memory/images/changes/ and i'm wondering how they could get there.
probably it's when you boot with 'changes=' and then with 'changes=EXIT:' on the same container. this should not be allowed....

could you check when they were created (today, last week, last month)?
once you find this please boot to always fresh, mount your save.dat and remove all '.wh.' files from the files you want to see back in union ('/') like e.g. USM files.
after reboot everything should be ok.

also - please stick to either 'changes=' or 'changes=EXIT:' for certain container to avoid similar troubles in the future.
Please add [Solved] to your thread title if the solution was found.

User avatar
Ed_P
Contributor
Contributor
Posts: 8343
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: Strange save.dat behavior.

Post#8 by Ed_P » 23 May 2014, 22:19

fanthom wrote:they should never be present in /mnt/live/memory/images/changes/ and i'm wondering how they could get there.
probably it's when you boot with 'changes=' and then with 'changes=EXIT:' on the same container. this should not be allowed....
I never boot with changes=, always changes=EXIT.
could you check when they were created (today, last week, last month)?
You got a command for that? The save.dat file is only a couple of weeks old at most. I've been recreating and rebuilding it periodically in testing this situation.
once you find this please boot to always fresh, mount your save.dat and remove all '.wh.' files from the files you want to see back in union ('/') like e.g. USM files.
Well I expect all my save.dat files to be back every time I reboot. :evil: Is this going to effect other files periodically? Do I have to do this '.wh' file cleanup regularly? You got a script to do this?
also - please stick to either 'changes=' or 'changes=EXIT:' for certain container to avoid similar troubles in the future.

As noted previously I never use 'changes=' although with these problems I was thinking of trying it.
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 8343
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: Strange save.dat behavior.

Post#9 by Ed_P » 23 May 2014, 22:26

fanthom wrote:could you check when they were created (today, last week, last month)?
05/17, 05/19, 05/23 for the few I saw with spaceFM.
Ed

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Strange save.dat behavior.

Post#10 by fanthom » 23 May 2014, 22:28

"You got a command for that?"
c'mon - it's an easy task. you can figure this out yourself.
i believe in you.

"Well I expect all my save.dat files to be back every time I reboot. :evil: Is this going to effect other files periodically? Do I have to do this '.wh' file cleanup regularly?"
this is the first report i got about incorrect handling of the '.wh.' files by the 'changes=EXIT' cheatcode. we are trying to find a root of this.
for now the answer is - "i dont know".

will have to look at the code first, then try to recreate bug, then fix it.
probably within 2 weeks i'll give you an answer.
Please add [Solved] to your thread title if the solution was found.

User avatar
Ed_P
Contributor
Contributor
Posts: 8343
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: Strange save.dat behavior.

Post#11 by Ed_P » 23 May 2014, 22:49

This is the plan at this point.

removedumbwhfiles.sh

Code: Select all

#!/bin/sh

#  Requires changes= cheatcode not used (Always Fresh mode)

if [ `whoami` != "root" ]; then
  ktsuss "$0"
  exit
fi

mloop  /mnt/sda5/porteus/changes/porteussave.dat

echo find /mnt/loop -name .wh.*
find /mnt/loop -name .wh.*

echo rm -f /mnt/loop/.wh.*
rm -f /mnt/loop/.wh.*

echo find /mnt/loop -name .wh.*
find /mnt/loop -name .wh.*

read
Don't know how to show file dates.
root@porteus:/home/guest# ls -al /mnt/live/memory .wh.*
/bin/ls: cannot access .wh.*: Operation not permitted
/mnt/live/memory:
total 0
drwxr-xr-x 6 root root 120 Mar 1 18:20 ./
drwxr-xr-x 18 root root 440 May 23 16:36 ../
drwxr-xr-x 12 root root 260 May 23 16:36 changes/
drwxr-xr-x 2 root root 40 Mar 1 18:20 copy2ram/
drwxr-xr-x 16 root root 320 May 23 16:36 images/
drwxr-xr-x 2 root root 40 May 23 16:36 xino/
Crash and burned.

Code: Select all

guest@porteus:~$ ls /mnt/loop/home/guest/remove*
/mnt/loop/home/guest/removedumbwhfiles.sh

guest@porteus:~$ sh /mnt/loop/home/guest/removedumbwhfiles.sh
sudo: /mnt/loop/home/guest/removedumbwhfiles.sh: command not found

guest@porteus:~$ find /mnt/loop -name .wh.*
find: `/mnt/loop/etc/cups/ssl': Permission denied
/mnt/loop/etc/usm/.wh..wh..opq
/mnt/loop/home/guest/.macromedia/Flash_Player/macromedia.com/support/flashplayer/sys/.wh..wh..opq
/mnt/loop/home/guest/Backups/FireFox/.wh.bookmarks-2014-05-04.json
/mnt/loop/home/guest/Backups/FireFox/.wh.bookmarks-2014-05-18.json
/mnt/loop/home/guest/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/.wh.bookmarks-2014-05-17.json
/mnt/loop/home/guest/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/.wh.bookmarks-2014-05-16.json
/mnt/loop/home/guest/.cache/mozilla/firefox/c3pp43bg.default/safebrowsing/.wh..wh..opq
/mnt/loop/home/guest/.wh.Use
/mnt/loop/home/guest/.wh.Preferences
/mnt/loop/home/guest/.wh.Privacy
/mnt/loop/home/guest/.wh.History
/mnt/loop/home/guest/.wh.Java
find: `/mnt/loop/root': Permission denied
/mnt/loop/usr/lib/.wh.libxml.so.1
/mnt/loop/usr/lib/.wh.libpng.so.2
/mnt/loop/usr/share/usm/.wh..wh..opq
/mnt/loop/usr/lib64/.wh.libapm.so.1
/mnt/loop/usr/man/man8/.wh.usm.8
find: `/mnt/loop/var/db/sudo': Permission denied
find: `/mnt/loop/var/cache/ldconfig': Permission denied
find: `/mnt/loop/var/spool/cups': Permission denied
/mnt/loop/var/log/packages/.wh.usm-3.1.0-noarch-2
find: `/mnt/loop/var/log/setup/tmp': Permission denied
/mnt/loop/var/usm/alien/.wh..wh..opq
/mnt/loop/var/usm/slacky/.wh..wh..opq
/mnt/loop/var/usm/slackware/.wh..wh..opq
/mnt/loop/var/usm/salix/.wh..wh..opq
/mnt/loop/var/usm/ponce/.wh..wh..opq
/mnt/loop/var/usm/local/.wh..wh..opq
/mnt/loop/var/usm/.wh..wh..opq

guest@porteus:~$ rm -f /mnt/loop/.wh.*

guest@porteus:~$ find /mnt/loop -name .wh.*
find: `/mnt/loop/etc/cups/ssl': Permission denied
/mnt/loop/etc/usm/.wh..wh..opq
/mnt/loop/home/guest/.macromedia/Flash_Player/macromedia.com/support/flashplayer/sys/.wh..wh..opq
/mnt/loop/home/guest/Backups/FireFox/.wh.bookmarks-2014-05-04.json
/mnt/loop/home/guest/Backups/FireFox/.wh.bookmarks-2014-05-18.json
/mnt/loop/home/guest/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/.wh.bookmarks-2014-05-17.json
/mnt/loop/home/guest/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/.wh.bookmarks-2014-05-16.json
/mnt/loop/home/guest/.cache/mozilla/firefox/c3pp43bg.default/safebrowsing/.wh..wh..opq
/mnt/loop/home/guest/.wh.Use
/mnt/loop/home/guest/.wh.Preferences
/mnt/loop/home/guest/.wh.Privacy
/mnt/loop/home/guest/.wh.History
/mnt/loop/home/guest/.wh.Java
find: `/mnt/loop/root': Permission denied
/mnt/loop/usr/lib/.wh.libxml.so.1
/mnt/loop/usr/lib/.wh.libpng.so.2
/mnt/loop/usr/share/usm/.wh..wh..opq
/mnt/loop/usr/lib64/.wh.libapm.so.1
/mnt/loop/usr/man/man8/.wh.usm.8
find: `/mnt/loop/var/db/sudo': Permission denied
find: `/mnt/loop/var/cache/ldconfig': Permission denied
find: `/mnt/loop/var/spool/cups': Permission denied
/mnt/loop/var/log/packages/.wh.usm-3.1.0-noarch-2
find: `/mnt/loop/var/log/setup/tmp': Permission denied
/mnt/loop/var/usm/alien/.wh..wh..opq
/mnt/loop/var/usm/slacky/.wh..wh..opq
/mnt/loop/var/usm/slackware/.wh..wh..opq
/mnt/loop/var/usm/salix/.wh..wh..opq
/mnt/loop/var/usm/ponce/.wh..wh..opq
/mnt/loop/var/usm/local/.wh..wh..opq
/mnt/loop/var/usm/.wh..wh..opq
Ed

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Strange save.dat behavior.

Post#12 by fanthom » 24 May 2014, 01:06

ever heard about permissions in Linux?
this is my last answer to you till you learn about linux basics.

run this command as root:

Code: Select all

find /mnt/loop -name ".wh.*" | xargs rm
Please add [Solved] to your thread title if the solution was found.

User avatar
Ed_P
Contributor
Contributor
Posts: 8343
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: Strange save.dat behavior.

Post#13 by Ed_P » 24 May 2014, 04:45

I was using root, that's how I did the mloop to mount the save.dat file. I also used root mode for spaceFM unfortunately it's search results wouldn't let me delete the files it found. I don't remember what happened but I closed the terminal window and when I reopened it I didn't switch back to root mode. The find command ran ok with or without root mode. And the rm command ran without displaying anything indicating that it needed root priviledges. I'm not a mind reader.

Are you saying the rm command would have worked if I was in root mode again?

Thank you for the command. I've modified my script and will reboot to Always Fresh and run it, then reboot and try usm.
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 8343
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: Strange save.dat behavior.

Post#14 by Ed_P » 24 May 2014, 05:15

"rm: invalid option -- 'n'"

Do you see an "n"?

Code: Select all

guest@porteus:~$ sh /mnt/sda5/porteus/Guest/removedumbwhfiles.sh
using /dev/loop6

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  home  opt	root  usr  var

find /mnt/loop -name .wh.*
/mnt/loop/etc/usm/.wh..wh..opq
/mnt/loop/home/guest/.macromedia/Flash_Player/macromedia.com/support/flashplayer/sys/.wh..wh..opq
/mnt/loop/home/guest/Backups/FireFox/.wh.bookmarks-2014-05-04.json
/mnt/loop/home/guest/Backups/FireFox/.wh.bookmarks-2014-05-18.json
/mnt/loop/home/guest/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/.wh.bookmarks-2014-05-17.json
/mnt/loop/home/guest/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/.wh.bookmarks-2014-05-16.json
/mnt/loop/home/guest/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/.wh.bookmarks-2014-05-19.json
/mnt/loop/home/guest/.mozilla/firefox/c3pp43bg.default/bookmarkbackups/.wh.bookmarks-2014-05-18.json
/mnt/loop/home/guest/.cache/mozilla/firefox/c3pp43bg.default/safebrowsing/.wh..wh..opq
/mnt/loop/home/guest/.wh.Use
/mnt/loop/home/guest/.wh.Preferences
/mnt/loop/home/guest/.wh.Privacy
/mnt/loop/home/guest/.wh.History
/mnt/loop/home/guest/.wh.Java
/mnt/loop/usr/lib/.wh.libxml.so.1
/mnt/loop/usr/lib/.wh.libpng.so.2
/mnt/loop/usr/share/usm/.wh..wh..opq
/mnt/loop/usr/lib64/.wh.libapm.so.1
/mnt/loop/usr/man/man8/.wh.usm.8
/mnt/loop/var/log/packages/.wh.usm-3.1.0-noarch-2
/mnt/loop/var/usm/alien/.wh..wh..opq
/mnt/loop/var/usm/slacky/.wh..wh..opq
/mnt/loop/var/usm/slackware/.wh..wh..opq
/mnt/loop/var/usm/salix/.wh..wh..opq
/mnt/loop/var/usm/ponce/.wh..wh..opq
/mnt/loop/var/usm/local/.wh..wh..opq
/mnt/loop/var/usm/.wh..wh..opq
rm: invalid option -- 'n'
Try 'rm --help' for more information.
find /mnt/loop -name .wh.*

guest@porteus:~$ find /mnt/loop -name .wh.*
find: `/mnt/loop/etc/cups/ssl': Permission denied
find: `/mnt/loop/root': Permission denied
find: `/mnt/loop/var/db/sudo': Permission denied
find: `/mnt/loop/var/cache/ldconfig': Permission denied
find: `/mnt/loop/var/spool/cups': Permission denied
find: `/mnt/loop/var/log/setup/tmp': Permission denied
guest@porteus:~$ su 
Password: 
root@porteus:/home/guest# find /mnt/loop -name .wh.*
root@porteus:/home/guest# find /mnt/loop -name *.wh.*
root@porteus:/home/guest# cat /mnt/loop/home/guest/removedumbwhfiles.sh
#!/bin/sh

if [ `whoami` != "root" ]; then
  ktsuss "$0"
  exit
fi

mloop  /mnt/sda5/porteus/changes/porteussave.dat

echo find /mnt/loop -name .wh.*
find /mnt/loop -name .wh.*

echo find /mnt/loop -name ".wh.*" | xargs rm
find /mnt/loop -name ".wh.*" | xargs rm

echo find /mnt/loop -name .wh.*
find /mnt/loop -name .wh.*

readroot@porteus:/home/guest# uloop

/mnt/loop has been unmounted

root@porteus:/home/guest# 
??? There were more .wh. files before I thought,
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 8343
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Re: Strange save.dat behavior.

Post#15 by Ed_P » 24 May 2014, 05:26

And the answer is....



Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -v

 You are using USM version:  3.1.1

root@porteus:/home/guest#



and




The usm panel icon works again.

:Yahoo!:
Ed

Post Reply