USM bug reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: USM bug reports

Post#31 by Ed_P » 14 May 2014, 00:23

brokenman wrote:Follow these instructions exactly as they appear. Do not add or remove any extra steps. Do not run any scripts or commands between steps.

1) Boot to fresh mode
2) Open a console
3) elevate to root (su)
4) Download usm-latest-0.0-noarch.txz (See wget line in your post about update-usm.sh)
5) Install usm-latest-0.0-noarch.txz
6) In root terminal run: usm -u all
7) In root terminal run: usm -v (check it is the right version 3.1.1)

Do this and only this and report back if it works ok.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# wget --no-check-certificate --trust-server-names  http://sourceforge.net/projects/usm/files/$LATEST/download -P /tmp
--2014-05-13 19:43:25--  http://sourceforge.net/projects/usm/files//download
Resolving sourceforge.net (sourceforge.net)... 216.34.181.60
Connecting to sourceforge.net (sourceforge.net)|216.34.181.60|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2014-05-13 19:43:25 ERROR 404: Not Found.

root@porteus:/home/guest# wget --no-check-certificate --trust-server-names  http://sourceforge.net/projects/usm/files/usm-latest-0.0-noarch-1.txz/download -P /tmp
--2014-05-13 20:18:35--  http://sourceforge.net/projects/usm/files/usm-latest-0.0-noarch-1.txz/download
Resolving sourceforge.net (sourceforge.net)... 216.34.181.60
Connecting to sourceforge.net (sourceforge.net)|216.34.181.60|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://downloads.sourceforge.net/project/usm/usm-latest-0.0-noarch-1.txz?r=&ts=1400026715&use_mirror=iweb [following]
--2014-05-13 20:18:35--  http://downloads.sourceforge.net/project/usm/usm-latest-0.0-noarch-1.txz?r=&ts=1400026715&use_mirror=iweb
Resolving downloads.sourceforge.net (downloads.sourceforge.net)... 216.34.181.59
Connecting to downloads.sourceforge.net (downloads.sourceforge.net)|216.34.181.59|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://iweb.dl.sourceforge.net/project/usm/usm-latest-0.0-noarch-1.txz [following]
--2014-05-13 20:18:36--  http://iweb.dl.sourceforge.net/project/usm/usm-latest-0.0-noarch-1.txz
Resolving iweb.dl.sourceforge.net (iweb.dl.sourceforge.net)... 70.38.0.134, 2607:f748:10:12::5f:2
Connecting to iweb.dl.sourceforge.net (iweb.dl.sourceforge.net)|70.38.0.134|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 52516 (51K) [application/octet-stream]
Saving to: ‘/tmp/usm-latest-0.0-noarch-1.txz’

100%[======================================>] 52,516       172KB/s   in 0.3s   

2014-05-13 20:18:36 (172 KB/s) - ‘/tmp/usm-latest-0.0-noarch-1.txz’ saved [52516/52516]

root@porteus:/home/guest# installpkg /tmp/usm-latest-0.0-noarch-1.txzVerifying package usm-latest-0.0-noarch-1.txz.
Installing package usm-latest-0.0-noarch-1.txz:
PACKAGE DESCRIPTION:
Package usm-latest-0.0-noarch-1.txz installed.

root@porteus:/home/guest# usm -u all
 Starting alien database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 alien  database updated. 

 Starting salix database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
Downloading: OPTIFEST.gz  DONE
Downloading: MANIFEST.bz2  DONE
 salix  database updated. 

 Starting slacky database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slacky  database updated. 

 Starting ponce database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
Optimizing manifest
 ponce  database updated. 

 Starting slackware database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackware  database updated. 

 Starting slackwarepatches database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackwarepatches  database updated. 

 Starting sbo database update 
Downloading: vercheck.txt  DONE
SLACKBUILDS.TXT.gz
Downloading: SLACKBUILDS.TXT.gz  DONE
 sbo  database updated. 


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

 You are using USM version:  3.1.1

root@porteus:/home/guest# 

Ok, now what?
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5436
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM bug reports

Post#32 by brokenman » 14 May 2014, 11:31

Great. Everything is working nicely.

Now you can use the GUI or in the terminal search for something and download it.

usm -s fbreader
usm -g fbreader
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: USM bug reports

Post#33 by Ed_P » 14 May 2014, 14:38

Ok, I exited Always Fresh mode, rebooted to my normal changes=EXIT mode, reran the exact same steps plus your -s step:

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# wget --no-check-certificate --trust-server-names  http://sourceforge.net/projects/usm/files/usm-latest-0.0-noarch-1.txz/download -P /tmp
--2014-05-14 10:13:58--  http://sourceforge.net/projects/usm/files/usm-latest-0.0-noarch-1.txz/download
Resolving sourceforge.net (sourceforge.net)... 216.34.181.60
Connecting to sourceforge.net (sourceforge.net)|216.34.181.60|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://downloads.sourceforge.net/project/usm/usm-latest-0.0-noarch-1.txz?r=&ts=1400076838&use_mirror=superb-dca2 [following]
--2014-05-14 10:13:58--  http://downloads.sourceforge.net/project/usm/usm-latest-0.0-noarch-1.txz?r=&ts=1400076838&use_mirror=superb-dca2
Resolving downloads.sourceforge.net (downloads.sourceforge.net)... 216.34.181.59
Connecting to downloads.sourceforge.net (downloads.sourceforge.net)|216.34.181.59|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://superb-dca2.dl.sourceforge.net/project/usm/usm-latest-0.0-noarch-1.txz [following]
--2014-05-14 10:13:59--  http://superb-dca2.dl.sourceforge.net/project/usm/usm-latest-0.0-noarch-1.txz
Resolving superb-dca2.dl.sourceforge.net (superb-dca2.dl.sourceforge.net)... 209.61.193.20
Connecting to superb-dca2.dl.sourceforge.net (superb-dca2.dl.sourceforge.net)|209.61.193.20|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 52516 (51K) [application/octet-stream]
Saving to: ‘/tmp/usm-latest-0.0-noarch-1.txz’

100%[======================================>] 52,516      53.9KB/s   in 1.0s   

2014-05-14 10:14:01 (53.9 KB/s) - ‘/tmp/usm-latest-0.0-noarch-1.txz’ saved [52516/52516]

root@porteus:/home/guest# installpkg /tmp/usm-latest-0.0-noarch-1.txzVerifying package usm-latest-0.0-noarch-1.txz
Cannot install /tmp/usm-latest-0.0-noarch-1.txzVerifying:  file not found
Cannot install package:  file not found
Cannot install usm-latest-0.0-noarch-1.txz:  file not found
root@porteus:/home/guest# installpkg /tmp/usm-latest-0.0-noarch-1.txz
Verifying package usm-latest-0.0-noarch-1.txz.
Installing package usm-latest-0.0-noarch-1.txz:
PACKAGE DESCRIPTION:
Package usm-latest-0.0-noarch-1.txz installed.

root@porteus:/home/guest# usm -u all
 Starting alien database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 alien  database updated. 

 Starting salix database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
Downloading: OPTIFEST.gz  DONE
Downloading: MANIFEST.bz2  DONE
 salix  database updated. 

 Starting slacky database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slacky  database updated. 

 Starting ponce database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
Optimizing manifest
 ponce  database updated. 

 Starting slackware database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackware  database updated. 

 Starting slackwarepatches database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackwarepatches  database updated. 

 Starting sbo database update 
Downloading: vercheck.txt  DONE
SLACKBUILDS.TXT.gz
Downloading: SLACKBUILDS.TXT.gz  DONE
 sbo  database updated. 


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

 You are using USM version:  3.1.1

root@porteus:/home/guest# usm -s fbreader

fbreader-0.99.4-x86_64-1alien.tgz was found in alien
fbreader-0.99.4-x86_64-1dj.txz was found in salix
fbreader-0.12.10-x86_64-2ponce.txz was found in ponce
Packages found:   3 

Use:   usm -i <package>  for more info
Use:   usm -g <package>  to download

root@porteus:/home/guest# 
I was also able to open USM via the taskbar icon and do the same search.

I now plan to reboot to Always Fresh mode, check the space usage of my save.dat file, and report it here, reboot to my normal mode and try USM again.

Always Fresh mode, save.dat space usage:

Code: Select all

guest@porteus:~$ sh /mnt/sda5/porteus/Guest/savedatspaceused.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

193M	/mnt/loop
Filesystem      Size  Used Avail Use% Mounted on
/dev/loop6      252M  207M   46M  83% /mnt/loop

328K	/mnt/loop/etc
30M	/mnt/loop/home
4.0K	/mnt/loop/opt
15M	/mnt/loop/root
3.7M	/mnt/loop/usr
145M	/mnt/loop/var

2.2M	/mnt/loop/var/log
128M	/mnt/loop/var/usm

424K	/mnt/loop/home/guest/Downloads
16K	/mnt/loop/home/guest/Desktop
11M	/mnt/loop/home/guest/Backups
ls /mnt/loop/home/guest/Backups
FireFox  NetworkManager  spaceFM  wmWeather
ls /mnt/loop/home/guest/Backups/FireFox
bookmarks-2014-05-04.json  bookmarks.html  places.sqlite  prefs.js
11M	/mnt/loop/home/guest/Backups/FireFox
And now back to my changes=EXIT mode we have:

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -v
awk: fatal: cannot open file `/etc/usm/usm.conf' for reading (No such file or directory)
/usr/bin/usm: line 54: /etc/usm/usm.conf: No such file or directory
/usr/bin/usm: line 55: /share/usm/funcelementCreate: No such file or directory
/usr/bin/usm: line 56: /share/usm/funccleanup: No such file or directory
/usr/bin/usm: line 57: /share/usm/funcsystemSetup: No such file or directory
/usr/bin/usm: line 58: /share/usm/funccli: No such file or directory
/usr/bin/usm: line 59: /share/usm/funcgtkDialogs: No such file or directory
/usr/bin/usm: line 60: /share/usm/functxtStatic: No such file or directory
/usr/bin/usm: line 61: /share/usm/funcpackageSearch: No such file or directory
/usr/bin/usm: line 62: /share/usm/funcpackageInfo: No such file or directory
/usr/bin/usm: line 63: /share/usm/funcchecks: No such file or directory
/usr/bin/usm: line 64: /share/usm/funcpackageGet: No such file or directory
/usr/bin/usm: line 65: /share/usm/funcupdateDatabase: No such file or directory
/usr/bin/usm: line 66: /share/usm/funcchangelogs: No such file or directory
/usr/bin/usm: line 67: /share/usm/funcslackbuilds: No such file or directory
/usr/bin/usm: line 68: /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: 
/usr/bin/usm: line 240: cleanup: command not found
/usr/bin/usm: line 587: cleanup: command not found
root@porteus:/home/guest# 
Ed

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

Re: USM bug reports

Post#34 by Ed_P » 18 May 2014, 04:19

Ok, one last test. I start with a rebuilt 256 MB 3.0 save.dat file, check my folder usage, do a USM update, check my folder usage again, reboot to Always Fresh to check my save.dat usage before and after the USM update, then reboot to my normal GUI changes=EXIT system and check USM again.

Code: Select all

guest@porteus:~$ ./test.sh

========== live system Before ==========

7.4M	/etc
27M	/home
18M	/opt
139K	/root
1.1G	/usr
7.0M	/var

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

du -sh /etc/usm
42K	/etc/usm


du -sh /var/log
4.9M	/var/log
du -sh /var/usm
1.9M	/var/usm


========== usm update ==========

usm -u all
 Starting alien database update 
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 alien  database updated. 

 Starting salix database update 
Downloading: CHECKSUMS.md5  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
Downloading: OPTIFEST.gz  DONE
Downloading: MANIFEST.bz2  DONE
 salix  database updated. 

 Starting slackware database update 
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackware  database updated. 

 Starting slacky database update 
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slacky  database updated. 

 Starting ponce database update 
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
Optimizing manifest
 ponce  database updated. 




 You are using USM version:  3.1.0



========== live system After ==========

7.4M	/etc
27M	/home
18M	/opt
139K	/root
1.1G	/usr
82M	/var

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

du -sh /etc/usm
42K	/etc/usm


du -sh /var/log
4.9M	/var/log
du -sh /va[s][/s]r/usm
77M	/var/usm


========== Next step ==========

Now to exit Porteus, save changes, reboot to
Always Fresh and check save.dat space used,
then reboot to changes=EXIT and see if usm works.

guest@porteus:~$ 
Note the /var folder goes from 7 MB to 82MB, certainly not a show stopper.

Code: Select all

guest@porteus:~$ sh /mnt/sda5/porteus/Guest/testdats.sh

========== save.dat Before ==========

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


du -sh
97M	/mnt/loop
df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/loop6      252M  111M  142M  44% /mnt/loop

48K	/mnt/loop/etc
26M	/mnt/loop/home
4.0K	/mnt/loop/opt
72K	/mnt/loop/root
3.0M	/mnt/loop/usr
68M	/mnt/loop/var

ls /mnt/loop/etc/usm
ls: cannot access /mnt/loop/etc/usm: No such file or directory
du: cannot access ‘/mnt/loop/etc/usm’: No such file or directory

596K	/mnt/loop/var/log
68M	/mnt/loop/var/usm


/mnt/loop has been unmounted



========== save.dat After ==========

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


du -sh
108M	/mnt/loop
df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/loop6      252M  121M  132M  48% /mnt/loop

48K	/mnt/loop/etc
27M	/mnt/loop/home
4.0K	/mnt/loop/opt
72K	/mnt/loop/root
3.0M	/mnt/loop/usr
78M	/mnt/loop/var

ls /mnt/loop/etc/usm
ls: cannot access /mnt/loop/etc/usm: No such file or directory
du: cannot access ‘/mnt/loop/etc/usm’: No such file or directory

700K	/mnt/loop/var/log
77M	/mnt/loop/var/usm


/mnt/loop has been unmounted


guest@porteus:~$ 
Note the usage of the save.dat file goes from 44% before the USM update to 48% after.

Then we reboot and:

Code: Select all

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

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

root@porteus:/home/guest#
Something isn't working and I don't think it's save.dat space related. I think the changes= cheatcode isn't saving a change that the USM system is making.
Ed

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

Re: USM bug reports

Post#35 by fanthom » 18 May 2014, 08:47

"I think the changes= cheatcode isn't saving a change that the USM system is making."
please have a look on /etc/changes-exit.conf to make sure that directory where USM files are saved is not excluded. please also test with normal 'changes=' to confirm that it's changes=EXIT:' fault.

thanks
Please add [Solved] to your thread title if the solution was found.

tome
Contributor
Contributor
Posts: 561
Joined: 26 Jun 2013, 14:03
Distribution: x64 Openbox
Location: Poland
Contact:

Re: USM bug reports

Post#36 by tome » 18 May 2014, 20:02

another bug - usm, alien or me? - calibre-1.37 vs calibre-1.35

Code: Select all

root@me:/# usm -s calibre

calibre-1.11.0-i486-1alien.txz was found in salix
calibre-1.37.0-i486-1alien.txz was found in alien
Packages found:   2 

Use:   usm -i <package>  for more info
Use:   usm -g <package>  to download

root@me:/# usm -g calibre

 The following items were found.
 Choose an number to confirm. 
 ctrl+c to quit

1) calibre-1.11.0-i486-1alien.txz
2) calibre-1.35.0-i486-1alien.txz
#? 
same for GUI, if dependencies are checked:

Code: Select all

Could not find: LIBS.TXT

Code: Select all

Message Fatal error LIBS.TXT
@Ed_P
You can edit '/etc/usm/usm.conf':

Code: Select all

# Storage of database files (e.g PACKAGES.TXT)
DBDIR=/mnt/data/usm
to store your database outside container - should work on ntfs.

@brokenman
1. Could you add (to your todo list) option to disable message: "Your files are ready Would you like to open the storage folder now?" - GUI
2. and add "show link" option - sometimes I prefer to use my download manager because I need to stop and resume downloading but need link for it - CLI.

roadie
Full of knowledge
Full of knowledge
Posts: 205
Joined: 02 Jan 2011, 18:41
Distribution: Porteus 3.5...with a twist
Location: In a hayfield

Re: USM bug reports

Post#37 by roadie » 18 May 2014, 21:10

another bug - usm, alien or me? - calibre-1.37 vs calibre-1.35
The reference to 1.35 seems to be coming from /var/usm/alien/LIBS.TXT.

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

Re: USM bug reports

Post#38 by Ed_P » 18 May 2014, 23:27

fanthom wrote:please have a look on /etc/changes-exit.conf to make sure that directory where USM files are saved is not excluded.
I did and the USM files are not being excluded.
tome wrote:You can edit '/etc/usm/usm.conf':

Code: Select all

# Storage of database files (e.g PACKAGES.TXT)
DBDIR=/mnt/data/usm
to store your database outside container - should work on ntfs.
Thanks tome but I don't think the USM files are that big. Approx 80 MB.

However, according to the /etc/changes-exit.conf file /usr is saved in save.dat file and as shown in my before/after test my /usr folder is 1.1 GB!! Which is HUGH!!! An obviously not all being written to my save.dat file, but is it impacting other folder's files??

If the files to be saved are bigger than the save.dat size a msg/alert should be displayed informing the user rather than simply creating an incomplete file and suprizing the user when he/she reboots.
Ed

roadie
Full of knowledge
Full of knowledge
Posts: 205
Joined: 02 Jan 2011, 18:41
Distribution: Porteus 3.5...with a twist
Location: In a hayfield

Re: USM bug reports

Post#39 by roadie » 19 May 2014, 00:51

Thanks tome but I don't think the USM files are that big. Approx 80 MB.

However, according to the /etc/changes-exit.conf file /usr is saved in save.dat file and as shown in my before/after test my /usr folder is 1.1 GB!! Which is HUGH!!! An obviously not all being written to my save.dat file, but is it impacting other folder's files??

If the files to be saved are bigger than the save.dat size a msg/alert should be displayed informing the user rather than simply creating an incomplete file and suprizing the user when he/she reboots.
OMFG,
Ed_P....I don't think you're quite grasping how this system (aufs) works. The 'changes' cheatcode saves changes made to the running system....it don't save the entire system.....only, just the changes made....it saves any changes made to /usr.

It's really not trying to cram 1.1 gigs of data into your evil, tiny 256M savefile.....if it is, then something has been changed and I didn't do it.....so, you must have.

I've been playing with an Always Fresh LXDE install most of the day, and I just can't make USM do funny things....it just works every time with and without a savefile.

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

Re: USM bug reports

Post#40 by Ed_P » 19 May 2014, 02:41

roadie wrote:OMFG,
Ed_P....I don't think you're quite grasping how this system (aufs) works. The 'changes' cheatcode saves changes made to the running system....it don't save the entire system.....only, just the changes made....it saves any changes made to /usr.
Good point roadie. Thanks for the reminder. Image I was just using the names of the folders mloop displays when it mounts the save.dat file and relating them directly to the live system's folders. I have to look at the changes folder. fanthom point that out to me once but I forgot when I set up my test scripts.
It's really not trying to cram 1.1 gigs of data into your evil, tiny 256M savefile.....
Image
I've been playing with an Always Fresh LXDE install most of the day, and I just can't make USM do funny things....it just works every time with and without a savefile.
Sure, always taking the easy way out. :lol:
Ed

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

Re: USM bug reports

Post#41 by Ed_P » 21 May 2014, 16:07

An update.

Upgraded USM from 3.1.0 to 3.1.1 using the GUI interface. Nothing else, just the base USM module.

Save.dat is not full or hurting for space.

Code: Select all

 #################################
 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

du -sh
109M	/mnt/loop
Filesystem      Size  Used Avail Use% Mounted on
/dev/loop6      252M  122M  130M  49% /mnt/loop

228K	/mnt/loop/etc
27M	/mnt/loop/home
4.0K	/mnt/loop/opt
72K	/mnt/loop/root
3.3M	/mnt/loop/usr
79M	/mnt/loop/var

ls /mnt/loop/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

84K	/mnt/loop/etc/usm

796K	/mnt/loop/var/log
77M	/mnt/loop/var/usm

464K	/mnt/loop/home/guest/Downloads
16K	/mnt/loop/home/guest/Desktop
11M	/mnt/loop/home/guest/Backups
ls /mnt/loop/home/guest/Backups
FireFox  NetworkManager  spaceFM  wmWeather
ls /mnt/loop/home/guest/Backups/FireFox
bookmarks-2014-05-04.json  bookmarks.html  prefs.js
bookmarks-2014-05-18.json  places.sqlite
11M	/mnt/loop/home/guest/Backups/FireFox
I rebooted today and tried USM and I'm back to this.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -v
awk: fatal: cannot open file `/etc/usm/usm.conf' for reading (No such file or directory)
/usr/bin/usm: line 54: /etc/usm/usm.conf: No such file or directory
/usr/bin/usm: line 55: /share/usm/funcelementCreate: No such file or directory
/usr/bin/usm: line 56: /share/usm/funccleanup: No such file or directory
/usr/bin/usm: line 57: /share/usm/funcsystemSetup: No such file or directory
/usr/bin/usm: line 58: /share/usm/funccli: No such file or directory
/usr/bin/usm: line 59: /share/usm/funcgtkDialogs: No such file or directory
/usr/bin/usm: line 60: /share/usm/functxtStatic: No such file or directory
/usr/bin/usm: line 61: /share/usm/funcpackageSearch: No such file or directory
/usr/bin/usm: line 62: /share/usm/funcpackageInfo: No such file or directory
/usr/bin/usm: line 63: /share/usm/funcchecks: No such file or directory
/usr/bin/usm: line 64: /share/usm/funcpackageGet: No such file or directory
/usr/bin/usm: line 65: /share/usm/funcupdateDatabase: No such file or directory
/usr/bin/usm: line 66: /share/usm/funcchangelogs: No such file or directory
/usr/bin/usm: line 67: /share/usm/funcslackbuilds: No such file or directory
/usr/bin/usm: line 68: /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: 
/usr/bin/usm: line 240: cleanup: command not found
/usr/bin/usm: line 587: cleanup: command not found
root@porteus:/home/guest# 
Conclusions:

1. Something is wrong.
2. I don't know what is wrong. But I don't think it is my save.dat file's size.
3. Having to boot to Always Fresh to check the space usage on my save.dat file is getting to be a PITA.
4. Rebuilding my save.dat file repeatedly is getting old also.
5. I think the use of modules is having a negative impact on save.dat space!! If a module is tried then deleted / removed the files it added to the save.dat file remain.
Ed

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

Re: USM bug reports

Post#42 by fanthom » 21 May 2014, 16:17

"Having to boot to Always Fresh to check the space usage on my save.dat file is getting to be a PITA."
no need to. just run:

Code: Select all

df -h | head -n2
"I think the use of modules is having a negative impact on save.dat space!! If a module is tried then deleted / removed the files it added to the save.dat file remain."
correct. modules are read-only so every new files (like settings) or updated ones must be saved somewhere. here you go - they are saved in your save.dat. there is no way to avoid this if you want persistence (that's why you are using save.dat in first place).
Please add [Solved] to your thread title if the solution was found.

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

Re: USM bug reports

Post#43 by Ed_P » 21 May 2014, 17:08

fanthom wrote:"Having to boot to Always Fresh to check the space usage on my save.dat file is getting to be a PITA."
no need to. just run:

Code: Select all

df -h | head -n2
I don't think so.

Code: Select all

guest@porteus:~$ df -h | head -n2
Filesystem      Size  Used Avail Use% Mounted on
aufs            1.1G  7.5M  1.1G   1% /
guest@porteus:~$ 
verses mloop view

Code: Select all

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

du -sh
109M	/mnt/loop
Filesystem      Size  Used Avail Use% Mounted on
/dev/loop6      252M  122M  130M  49% /mnt/loop/
"I think the use of modules is having a negative impact on save.dat space!! If a module is tried then deleted / removed the files it added to the save.dat file remain."
correct. modules are read-only so every new files (like settings) or updated ones must be saved somewhere. here you go - they are saved in your save.dat. there is no way to avoid this if you want persistence (that's why you are using save.dat in first place).
Yes, but it seemed that once the module wrote to the save.dat file and the system was shut down and the module removed that when the system was rebooted the module's files in save.dat remained. I may have been mistaken about that though.

With the mloop view of my save.dat file it shows the /etc/ folder as being 228K with 84K being in /etc/usm and including the usm.conf file.

Code: Select all

Filesystem      Size  Used Avail Use% Mounted on
/dev/loop6      252M  122M  130M  49% /mnt/loop

228K	/mnt/loop/etc
27M	/mnt/loop/home
4.0K	/mnt/loop/opt
72K	/mnt/loop/root
3.3M	/mnt/loop/usr
79M	/mnt/loop/var

ls /mnt/loop/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
84K	/mnt/loop/etc/usm
the live system shows it as 7.4M but 0 for the /etc/usm folder.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# du -sh /etc
7.4M	/etc
root@porteus:/home/guest# du -sh /etc/usm
0	/etc/usm
root@porteus:/home/guest# 
thus the reason why USM is now failing.
Ed

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

Re: USM bug reports

Post#44 by fanthom » 21 May 2014, 20:16

'df -h | head -n2' will show the size of save.dat only when you boot with valid 'changes=' cheatocde. you must be booting in 'Always Fresh' or with 'changes=EXIT:' or 'changes-ro' cheats.
in last two cases you could run 'du -sh /mnt/live/memory/images/changes' to check how much of space is taken.
any chance you could upload your whole setup? it must be something in your save.dat or /rootcopy or one of the modules (did you ever create xzm from changes?).
please create new ISO from all of your modules + save.dat (compressed with zip to reduce size) and upload somewhere.

thanks
Please add [Solved] to your thread title if the solution was found.

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

Re: USM bug reports

Post#45 by Ed_P » 21 May 2014, 21:08

fanthom wrote:'df -h | head -n2' will show the size of save.dat only when you boot with valid 'changes=' cheatocde. you must be booting in 'Always Fresh' or with 'changes=EXIT:' or 'changes-ro' cheats.
Yes, I am booting with the 'changes=EXIT:' cheatcode, which I thought was valid.
in last two cases you could run 'du -sh /mnt/live/memory/images/changes' to check how much of space is taken.
Excellent!! :good:

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# du -sh /mnt/live/memory/images/changes
109M	/mnt/live/memory/images/changes
root@porteus:/home/guest# df -h /mnt/live/memory/images/changes
Filesystem      Size  Used Avail Use% Mounted on
-               252M  122M  130M  49% /mnt/live/memory/images/changes
Thank you Image fanthom

BTW Why is the 109M value not the same as the 122M in the df -h command? Isn't the latter more accurate?
any chance you could upload your whole setup? it must be something in your save.dat or /rootcopy or one of the modules (did you ever create xzm from changes?).
please create new ISO from all of your modules + save.dat (compressed with zip to reduce size) and upload somewhere.

thanks
I'll see what i can do. I do create xzm modules from my save.dat file periodically but only use it on my extramod= no update mode. In the interim maybe these displays can help?

grub4dos bootmgr code

Code: Select all

title Porteus 3.0  changes=      \n 213MB\n Porteus-RazorQT-v3.0-x86_64.iso 
find --set-root                       /ISOs/Porteus-RazorQT-v3.0-x86_64.iso
map --heads=0 --sectors-per-track=0   /ISOs/Porteus-RazorQT-v3.0-x86_64.iso (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz    from=/ISOs/Porteus-RazorQT-v3.0-x86_64.iso changes=EXIT:/porteus/changes/porteussave.dat extramod=/mnt/sda5/porteus/modules volume=40 
initrd /boot/syslinux/initrd.xz

title Porteus 3.0  extramod=     \n 213MB\n Porteus-RazorQT-v3.0-x86_64.iso 
find --set-root                       /ISOs/Porteus-RazorQT-v3.0-x86_64.iso
map --heads=0 --sectors-per-track=0   /ISOs/Porteus-RazorQT-v3.0-x86_64.iso (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz    from=/ISOs/Porteus-RazorQT-v3.0-x86_64.iso extramod=/mnt/sda5/porteus/modules;/mnt/sda5/porteus/modsavedat volume=33
initrd /boot/syslinux/initrd.xz

title Porteus 3.0  Always Fresh  \n 213MB\n Porteus-RazorQT-v3.0-x86_64.iso \n Use to debug and to check space usage of porteus.dat file.
find --set-root                       /ISOs/Porteus-RazorQT-v3.0-x86_64.iso
map --heads=0 --sectors-per-track=0   /ISOs/Porteus-RazorQT-v3.0-x86_64.iso (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz    from=/ISOs/Porteus-RazorQT-v3.0-x86_64.iso 
initrd /boot/syslinux/initrd.xz

Code: Select all

root@porteus:/home/guest# ./modules.sh
cat /proc/cmdline
quiet from=/ISOs/Porteus-RazorQT-v3.0-x86_64.iso changes=EXIT:/porteus/changes/porteussave.dat extramod=/mnt/sda5/porteus/modules volume=40 

ls /mnt/sda5/porteus/modules
001-core_fixes-20140408-x86_64-1prt.xzm   jre-7u55-x86_64-1.xzm
07-printing.xzm				  keepassx-0.4.3-x86_64-2dj.xzm
flash-plugin-11.2.202.350-x86_64-1gv.xzm  qemu-1.6.2.xzm
gnucash-2.6.2.xzm			  wmweather-2.4.5-x86_64-1ponce.xzm

ls /mnt/live/memory/images
000-kernel.xzm
001-core.xzm
001-core_fixes-20140408-x86_64-1prt.xzm
002-xorg.xzm
003-razor.xzm
04-firefox.xzm
07-printing.xzm
changes
flash-plugin-11.2.202.350-x86_64-1gv.xzm
gnucash-2.6.2.xzm
jre-7u55-x86_64-1.xzm
keepassx-0.4.3-x86_64-2dj.xzm
qemu-1.6.2.xzm
wmweather-2.4.5-x86_64-1ponce.xzm


Note that the wine module and it's required 64-bit support modules are not being used.
Ed

Post Reply