Newbie,got a magic folder to work, no luck with USM RESOLVED

[tome]

Go here https://yadi.sk/d/wJFyFih_4v48w/PORTEUS ... teFix_x86/, download 020-Update&Fix-Porteus-3.0-i486-16.06.2014.xzm to your modules folder and reboot - it's for x86, you should also rename downloaded file - replace/delete & character.

[Ed_P]

Check out this thread Returnity: http://forum.porteus.org/viewtopic.php? ... =30#p25087

It will explain what you need to do.

1. Boot into Always Fresh mode.

2. Mount your save.dat file.

3. Delete "white" files from your save.dat file.

4. Unmount your save.dat file.

5. Reboot to your normal GUI mode.

6. Try USM.

Now I created a script to do steps 2 - 4 named savedatremovewhfiles.sh.

Code: Select all

#!/bin/sh 
# http://forum.porteus.org/viewtopic.php?f=81&t=3501&p=25182#p25178

# mloop requires changes= cheatcodes not be used (Always Fresh mode)

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

if [ -f  /home/guest/savedatremovewhfiles.sh ]; then
   SPACEDATDIR=/mnt/live/memory/images/changes 
else
   mloop /mnt/sda5/porteus/changes/porteussave.dat
   SPACEDATDIR=/mnt/loop
fi

echo find ${SPACEDATDIR} -name .wh.*
find ${SPACEDATDIR} -name .wh.*
echo
echo Enter to delete, Ctrl+C to exit.
read
echo "find ${SPACEDATDIR} -name .wh.* | xargs rm"
find ${SPACEDATDIR} -name ".wh.*" | xargs rm
echo
echo find ${SPACEDATDIR} -name .wh.*
find ${SPACEDATDIR} -name .wh.*

read
if [ -f /home/guest/savedatremovewhfiles.sh ]; then
   exit  
else
   uloop 
fi
exit

You need to change line 14 to match the name and location of your save.dat file. You then need to remember where and what you saved the script as so you can run it in Always Fresh mode. Something alone the lines of:

sh /mnt/sda_/porteusstuff/edsscript.sh

Do NOT save it as savedatremovewhfiles.sh in your /home/guest/ folder.

BTW I boot Porteus also as an ISO. But from my harddrive rather than a USB drive.

[Returnity]

Hi Ed-P

that seems to have worked,

ran the script rebooted and is working, I don't know what it did really, but thanks

what were the files deleted?, were they the bug?



cheers
ww

where do I put resolved??

[Ed_P]

Excellent!!

were they the bug?

They appear to be. They are a function of Linux called "white files" which are created when a file is deleted.

where do I put resolved??

You edit your opening post of the thread and add it to the title.



BTW You could have named the script the same name I gave it and saved it in your /home/guest/ folder. The test for it is to determine whether you are in Always Fresh mode and in that mode the file doesn't exist regardless what it's called.

[Returnity]

Thanks again... I'll try out razor-qt edition so probably have to work through it again. Why doesn't it happen more often. or are most just more expert with linux, doessn't every one get the error?

One last thing , I boot from usb and have save.dat container on hard drive, How can I back this up so that I can make a copy of known good (or liked) changes and then delete the changes folder if changes are not liked and put the liked folder back? I tried just delete .dat file and replacing it but it did not like it, said could not mount or something even if right clicked and asked to mount .

cheers
ww

[Ed_P]

Thanks again... I'll try out razor-qt edition so probably have to work through it again. Why doesn't it happen more often. or are most just more expert with linux, doessn't every one get the error?

It appears to be a save.dat problem, which may, or may not, be tied to non-Linux formatted drives.

One last thing , I boot from usb and have save.dat container on hard drive, How can I back this up so that I can make a copy of known good (or liked) changes and then delete the changes folder if changes are not liked and put the liked folder back? I tried just delete .dat file and replacing it but it did not like it, said could not mount or something even if right clicked and asked to mount .

I backup my save.dat file and have restored it on occasion. I have also rebuilt my save.dat file by creating a new one and copying select files from the old save.dat file to it. I can backup from Windows and from Porteus, I have restored from Windows but don't think I've done it from Porteus yet.

My backup is named as a module because I sometimes boot with it in a read only mode using the extramod= cheatcode. Useful when visitors are here and they want to use the pc.

Here's what I use in Porteus.

savedat2xzm.sh

Code: Select all

#!/bin/sh
echo Pls wait
cp /mnt/sda5/porteus/changes/porteussave.dat /mnt/sda5/porteus/modsavedat/porteussave.dat.xzm
ls -lt /mnt/sda5/porteus/modsavedat/

savedatxzm2savedat.sh

Code: Select all

#!/bin/sh
echo Pls wait
cp /mnt/sda5/porteus/modsavedat/porteussave.dat.xzm /mnt/sda5/porteus/changes/porteussave.dat 
ls -lt /mnt/sda5/porteus/changes/

The latter one would need to be done in Always fresh mode. Modify the names and paths to fit your system.

What OS is on your hard drive and what format is the hard drive?

[Returnity]

My hard drive is windows vista home (fat32 ?) I have it how I like it running and have a back up that can resore in half an hour.

I started looking to linux , not much look with them but porteus being small and quick boot gave the opportunity to mess about a bit more, and now got a basic system running ok. Thanks again.. Will be able to tinker some more later..

(p.s if you are going to get a copy of Bhagavad Gita then the recommended one is Bhagavad Gita As It Is 1972 Original Edition)

cheers

ww

[Ed_P]

My hard drive is windows vista home (fat32 ?) I have it how I like it running and have a back up that can resore in half an hour.

Excellent that you have a backup. SO many people don't do backups. Have you tested the restore function? It's a critical part of having a backup.

Does Vista have a boot.ini file on the c:/ drive or a bootmgr file?

(p.s if you are going to get a copy of Bhagavad Gita then the recommended one is Bhagavad Gita As It Is 1972 Original Edition)

You mean this one? http://www.abebooks.com/Bhagavad-Gita-P ... -PLA-_-v01

[brokenman]

rebooted and it is not working again

What exactly is not working? More info please. Since you get an output about the version I assume the program starts. It should be as simple as opening the GUI, updating USM, then close it and open it again. Then update ALL (the databases). After this you should be good to go.

[Returnity]

hi, Ed-P

I have restored from the backup a couple of times..I use paragon(free) which makes a boot cd and have the back up on a usb hdd. It has a verify function to check the file after a backup is done.

That is the book I mentioned yes , that link shows the recommended edition.

I don't know if vista has boot.ini file on the c:/ drive or a bootmgr file cant see them in root of c:



I don't understand Brokenmans question, it is like the question is from earlier in the post but posted later after stuff has been worked through..

thx

[Ed_P]

I have restored from the backup a couple of times..I use paragon(free) which makes a boot cd and have the back up on a usb hdd. It has a verify function to check the file after a backup is done.

Excellent!!

I don't know if vista has boot.ini file on the c:/ drive or a bootmgr file cant see them in root of c:

Even when you use Porteus to look at the drive? With Windows use the Command Prompt to issue a attrib command.

Code: Select all

attrib  c:\*.*

I don't understand Brokenmans question, it is like the question is from earlier in the post but posted later after stuff has been worked through.

Yes, but brokenman is the author of the USM app so he wants to be sure he understands the problem you experienced so he can try to prevent it from continuing to occur.

[Returnity]

Hi,

my Vista has got bootmgr at c:


Regarding USM I don't really understand the problem but it happened more than 3 occasions, but you seemed to understand it as your walk through's cleared it up.

cheers

[brokenman]

he wants to be sure he understands the problem you experienced so he can try to prevent it from continuing to occur

Correct. Deleting all the whiteout files (while it may solve your problem in the short term) is not recommended. They serve a purpose in the union file system and deleting them all without prejudice will probably create other problems.

Installing the slackware package should supersede the whiteout files as I understand it.

[fanthom]

Installing the slackware package should supersede the whiteout files as I understand it.

correct unless someone created xzm from changes so .wh files would always survive in xzm.
@Returnity - was it your case?

Ed_P also suggested that 'changes=EXIT:' does not handle whiteout files properly. will check that today but would be handy to have 'step by step' instruction how to recreate this bug.
@Ed_P - could you provide such instructions for me, please.

[Ed_P]

@Ed_P - could you provide such instructions for me, please.

Well one thing it's not caused by and that is the size of the save.dat file. Returnite's file is 4x the size of mine.

The problem occurs when doing a UCM update, not of a particular package but a UCM All update, and going from 3.0 to 3.1 for example. The update runs, USM works, life is good. This all done using the GUI. Then rebooting after the update, updating the save.dat file with changes=EXIT, I attempt to use UCM and nothing happens. Then I switch to terminal mode and try usm -v and I get the UCM file not found errors, ucm.conf etc, the same as Returnite.

UCM files only take about 128 MB of space in the save.dat file which is a nit in the 1 GB save.dat file Returnite uses.