USM

[Ed_P]

The only issue is that USM is not working... so I can not install it...

You don't need to install it, or USM. Download it and copy it to your /porteus/modules folder.

BTW The ponce file I posted for you may not have been the most current one but it was unzipped so it should have gotten you pass the error you were receiving and allowed USM to work downloading apps from non-ponce systems.

[brokenman]

Can someone run the following commands after updating USM and upload the module somewhere?

Code: Select all

mkdir /tmp/un
cp -a --parents /var/usm /tmp/un
rm -r /tmp/un/var/usm/local*
dir2xzm /tmp/un /tmp/usm-db.xzm

johnsmith, after you update USM activate this module (just double click on it) and you should be able to use USM. I want to see if your USM runs in this state. For presistence please copy this module into your /mnt/sdXy/porteus/modules folder.

[Bogomips]

^ There is one caveat. Has to be run for 64bit m/c, as the files do not look architecture independent.

[francois]

@ johnsmith:

Here is the 64 bit module:
http://www.mediafire.com/download/w4k5b ... usm-db.xzm

Please download into /porteus/modules folder and activate with the submenu provided by a right click.

[johnsmith]

I have downloaded that module from Mediafire.
I have copied it to /porteus/module/ directory.
I have updated USM only, from 3.1.7 to 3.1.9 on Always Fresh, as per your indications.
I have activated that module.
I have tried to update all after it.
And I blow my brain later...
Attached the result:
http://www.mediafire.com/view/8lai87p68 ... pshot1.png

There is another issue I have seen during all this days.
When you run USM (Gui one, no by console) once, it works. But if you don´t close it and you try to update twice, it does nothing. Is it normal?

[Ed_P]

I have tried to update all after it.

Why??
The downloaded module is an updated USM database. Once you have updated USM to 3.1.9, closed the USM GUI, and activated the USM module, open USM to search for and to download the apps you want.

[johnsmith]

When i tried to open USM, it showed me that there was no database!!!

[Ed_P]

Do you have these alldesktops and fixes modules?

Code: Select all

guest@porteus:~$ ls /mnt/live/memory/images | grep 00
000-kernel.xzm/
001-core.xzm/
001-core_alldesktops-150124.xzm/
002-xorg.xzm/
002-xorg_alldesktops-150126.xzm/
003-lxqt.xzm/
004-lxqt_fixes-150120.xzm/

If not click on menu > System Tools > Porteus Settings Centre and it's the top entry on the General Settings menu. Once downloaded put them into the /porteus/modules/ directory and reboot.

Not sure they will fix the USM problem your having but something is different with your system then what the rest of us are running.

I am going to update my USM files and create a module for you to download and put in your /porteus/modules/ folder in place of the one your got from francois. Once you have it there reboot and run the this script.

boot.sh

Code: Select all

#!/bin/sh

if [ `whoami` != "root" ]; then  
  echo "Enter root's password" 
  su -c "sh $0 $1"
  exit 
fi

# http://forum.porteus.org/viewtopic.php?f=53&t=3801&start=30#p28472
# awk 'c-->0;/Booting device:/{c=1}' /var/log/porteus-livedbg
BOOTDEV=`grep -A1 "Booting" /var/log/porteus-livedbg|tail -n1|sed 's^//^/^g'`
TYPE=`grep "/dev/${BOOTDEV:5}" /var/log/porteus-livedbg`
KERNEL=`uname -a`
SAVEDAT=`grep "save.dat/" /var/log/porteus-livedbg`
BOOTMODE=`grep -A1 "Porteus data" /var/log/porteus-livedbg|tail -n1|sed 's^//^/^g'`

echo 
echo "Boot device:  " "$BOOTDEV"
echo "Boot device format:" "${TYPE: -7}"
echo "Boot mode:    " "$BOOTMODE"
echo "OS:     " `cat /etc/porteus-version`
echo "ARCH:   " "`echo $MACHTYPE | sed -e 's/-.*$//'`"  
echo "Kernel: "  "${KERNEL:0:30}"
if [ "$SAVEDAT" != "" ]; then     
   echo "Save.dat file:" "${SAVEDAT:0:-8}"
fi
echo "Cmdline:" "`cat /proc/cmdline`"
echo 
echo "Modules:" "`ls /mnt/live/memory/images`"
echo 
echo "USM:    " "`usm -v`"
ls -gR /var/usm 

- update -

New USM database module: https://drive.google.com/file/d/0B1Uj3O ... sp=sharing

You will need to update the USM app to 3.1.9 yourself.


BTW If you are booting in standard Always Fresh mode you are not loading the modules in the /porteus/modules/ folder.

You have two option imo. 1. You can add the extramod=/porteus/modules/ to the AF menu entry. 2. You can create a new save.dat file and run in normal mode.

[johnsmith]

First issue, I'm ussing KDE, so i can't have the same packages.
But ok, I have downloaded the ones I haven't and I have copied to /porteus/modules/

Then, I have created my own profile, with the .dat file and all this issues.
I have copied your USM database module to /porteus/modules/

Restart.

I have seen on the restart that the 2 packages I have copied to /porteus/modules/ were no needed as they already exists. (so even in the always fresh mode, the system is keeping them)

Then I have updated USM to 3.1.9.
Then I have run your script:

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# cd /tmp
root@porteus:/tmp# ./boot.sh

Boot device:   /mnt/sdb1
Boot device format: "vfat" 
Boot mode:     /mnt/sdb1/porteus
OS:      Porteus-v3.1
ARCH:    x86_64
Kernel:  Linux porteus 3.17.4-porteus #
Cmdline: quiet initrd=initrd.xz changes=/mnt/sdb1/porteus/save.dat kmap=es,us BOOT_IMAGE=vmlinuz 

Modules: 000-kernel.xzm
001-core.xzm
001-core_alldesktops-150124.xzm
002-xorg.xzm
002-xorg_alldesktops-150126.xzm
003-kde.xzm
04-chrome.xzm
05-devel.xzm
06-libreoffice.xzm
07-printing.xzm
08-skype.xzm
database-usm-20151210.xzm
nVidia-340.58-porteus-v3.1-x86_64-1ftm.xzm

USM:      You are using USM version:  3.1.9
/var/usm:
total 0
drwxr-xr-x 2 root   6 Sep 24 22:26 alien
drwxr-xr-x 2 root  21 Sep 24 22:26 local
drwxr-xr-x 2 root   6 Sep 24 22:26 ponce
drwxr-xr-x 2 root   6 Sep 24 22:26 salix
drwxr-xr-x 2 guest 38 Dec 10 05:28 sbo
drwxr-xr-x 2 root   6 Sep 24 22:26 slackonly
drwxr-xr-x 2 root   6 Sep 24 22:26 slackware
drwxr-xr-x 2 guest 88 Dec 10 05:26 slackwarepatches
drwxr-xr-x 2 root   6 Sep 24 22:26 slacky

/var/usm/alien:
total 455
-rw-r--r-- 1 guest 174266 Dec  9 08:12 CHECKSUMS.md5
-rw-r--r-- 1 guest  51367 Dec 10 05:24 LIBS.TXT
-rw-r--r-- 1 guest  91154 Dec 10 05:24 OPTIFEST
-rw-r--r-- 1 guest 147728 Dec 10 05:24 PACKAGES.TXT

/var/usm/local:
total 152
-rw-r--r-- 1 root 152746 Dec 10 12:31 libs.txt

/var/usm/ponce:
total 635
-rw-r--r-- 1 guest 190717 Aug 17 06:37 CHECKSUMS.md5
-rw-r--r-- 1 guest 115565 Dec 10 05:25 LIBS.TXT
-rw-r--r-- 1 guest  60966 Dec 10 05:25 OPTIFEST
-rw-r--r-- 1 guest 281425 Aug 17 06:37 PACKAGES.TXT

/var/usm/salix:
total 696
-rw-r--r-- 1 guest  74573 Dec  9 08:11 CHECKSUMS.md5
-rw-r--r-- 1 guest 142333 Dec 10 05:24 LIBS.TXT
-rw-r--r-- 1 guest  62151 Dec 10 05:24 OPTIFEST
-rw-r--r-- 1 guest 432793 Dec 10 05:25 PACKAGES.TXT

/var/usm/sbo:
total 2765
-rw-r--r-- 1 guest 2831115 Dec 10 05:28 SLACKBUILDS.TXT

/var/usm/slackonly:
total 9212
-rw-r--r-- 1 guest 3668249 Dec  6 09:42 CHECKSUMS.md5
-rw-r--r-- 1 guest 1144252 Dec 10 05:27 LIBS.TXT
-rw-r--r-- 1 guest  624098 Dec 10 05:27 OPTIFEST
-rw-r--r-- 1 guest 3995621 Dec  6 09:26 PACKAGES.TXT

/var/usm/slackware:
total 1347
-rw-r--r-- 1 guest 263541 Nov  3  2013 CHECKSUMS.md5
-rw-r--r-- 1 guest 298678 Dec 10 05:26 LIBS.TXT
-rw-r--r-- 1 guest 152124 Dec 10 05:26 OPTIFEST
-rw-r--r-- 1 guest 663291 Dec 10 05:26 PACKAGES.TXT

/var/usm/slackwarepatches:
total 176
-rw-r--r-- 1 guest 71560 Dec  3 07:48 CHECKSUMS.md5
-rw-r--r-- 1 guest 22168 Dec 10 05:26 LIBS.TXT
-rw-r--r-- 1 guest 38773 Dec 10 05:26 OPTIFEST
-rw-r--r-- 1 guest 46493 Dec  3 07:48 PACKAGES.TXT

/var/usm/slacky:
total 573
-rw-r--r-- 1 guest 156555 Jul 18 03:01 CHECKSUMS.md5
-rw-r--r-- 1 guest  83399 Dec 10 05:25 LIBS.TXT
-rw-r--r-- 1 guest  50852 Dec 10 05:25 OPTIFEST
-rw-r--r-- 1 guest 294487 Jul 18 03:00 PACKAGES.TXT
root@porteus:/tmp# 
 

And then, I have tried to update all twice... and.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -u all
alien was updated 80 seconds ago. Skipping.
salix was updated 72 seconds ago. Skipping.
slacky was updated 62 seconds ago. Skipping.
 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

gzip: /var/usm/ponce/CHECKSUMS.md5.gz: not in gzip format
          

==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while usm was running:                       
 
FATAL ERROR!
usm update_database 270
Could not decompress: CHECKSUMS.md5.gz
 
============================================================================== 

root@porteus:/home/guest#  

[roadie]

@johnsmith

You need to boot Porteus in Always Fresh mode....base_only.

No other modules...no save.dat....no profile. Then download the file brokenman linked to...the usm-latest-0.0-noarch-1.txz.

Keep it in your download folder....right click on it in your file manager and convert it to .xzm...then activate it. Then try updating USM.

This is the only way to isolate the problem. Other modules can cause problems....save.dat files will definitely do it. Your profile is a save file.

Again, this is the only way.

[Ed_P]

And then, I have tried to update all twice...

Why??? The USM database module you downloaded has all the USM files updated. You simply need to run USM to download whatever apps you want.

Since you are saving changes whatever the USM updates that you ran did are now there.

[johnsmith]

Dear Ed_P...

It's true!
I have the same error every time that I run USM, but now, if a search for any module, it works.
I am having the same problem with ponce... but if, at least, I can download what I need... Cool!!!

Thank you very much to all of you!!!

One last question...
Every time that I download a new package, in order to run it, it's only an issue of activate or deactivate?
Or is it needed to copy to any folder?

[francois]

When you download a package, you better have it converted to a module. Modules end with .xzm. As these modules are saved in the /tmp folder, if you do not move them to the /porteus/modules or to another permanent folder they will be erased at reboot. The content of the /tmp folder is erased at each reboot.

When you put the new module or package in the /porteus/modules folder (or in the /porteus/base folder), the package will be available at next reboot, unless you activate that module. If you put the module elsewhere the module will not be part of the system at reboot.

[Ed_P]

if you do not move them to the /porteus/modules or to another permanent folder

Actually copying the modules works just as well.

My question is, if the boot device is in Linux format, 'Boot device format: "vfat"' why does johnsmith need a save.dat file? Aren't all changes being saved to the boot device?? And even with the save.dat being used??

[johnsmith]

Vfat is a Microsoft partition system, so that's why I need a save.dat file.

Francois, I have checked and all the packages downloaded to /tmp/usm/ are there even if I restart the system. Maybe it is deleted when the folder belongs to guest user.

Another question: I have seen that when you download a package that need some others, you can merge them and keep in one xzm file.
But is there any way to merge xzm packages?

For example: I downloaded Gimp, and it is merged with some libraries that I didn't have in my system. Later one, I have downloaded some Gimp plugins, so I will need this packages when I run Gimp, but I won't use further so, is there any way to merge all these packages with Gimp xzm file or in one package call "Gimplugins.xzm"?

And the last one: How can I see all the packages available? My problem is that I came form Ubuntu so I don't remember the libraries I was using on there (WYSIWYC system - What You See Is What You Click ) but i'm usually working with Tcl/Tk and I don't know If I just downloaded all the required libraries... for example, I didn't find tcl_doc or tk_doc.

Regards