@fanthom
Nope, it was a fresh boot without any old stuff... Strange. Where are all the files needed so that I can check, aside from /opt/ppm ?
Or is the stuff only in /opt/ppm ?
_________
UPDATE
I checked which PPM I seem to run, and it's from 002-xorg.xzm :
Code: Select all
guest@porteus:/mnt/live/memory/images$ cat ./002-xorg.xzm/opt/ppm/ppmversion
PPMVER:
120112
LPVER:
121207
Is that a date stamp? Then it's quite old indeed...
But these are the new ones that I got using the web page / XFCe 2.1rc2 / x86-64. (/x is a symlink that always points to the boot device...

)
Code: Select all
guest@porteus:/mnt/live/memory/images$ ls -o /x/porteus/base/
total 151392
drwxrwxrwx 2 root 4096 2013-07-17 12:48 .
drwxrwxrwx 7 root 4096 2013-07-19 11:11 ..
-rwxrwxrwx 1 root 14573568 2013-07-09 20:20 000-kernel.xzm
-rwxrwxrwx 1 root 45993984 2013-07-09 20:20 001-core.xzm
-rwxrwxrwx 1 root 37908480 2013-07-09 20:20 002-xorg.xzm
-rwxrwxrwx 1 root 24633344 2013-07-09 20:20 003-xfce.xzm
-rwxrwxrwx 1 root 25047040 2013-07-09 20:20 04-firefox.xzm
-rwxrwxrwx 1 root 6860800 2013-07-09 20:20 06-abiword.xzm
md5sums:
Code: Select all
f1ac7b859f69778fea9904a50da1c64a /x/porteus/base/000-kernel.xzm
957e88d056569e1b20b3749def9dc282 /x/porteus/base/001-core.xzm
7da378c8a19c621f86b2fda15427e2f9 /x/porteus/base/002-xorg.xzm
c66cb3c28f904cd81bfb844cc3583524 /x/porteus/base/003-xfce.xzm
c114de8ad2c53e5f2d1d539788a85285 /x/porteus/base/04-firefox.xzm
c29b99c12328475c68b3da113b4a8cdc /x/porteus/base/06-abiword.xzm
Sadly, there is no md5sums.txt on ponce.cc/porteus/x86_64/testing/Porteus-v2.1-rc2/ ... or am I just too stupid to find it?
I checked the md5sum from 002-xorg.xzm from ponce.cc/porteus/x86_64/testing/Porteus-v2.1-rc2/ and it's the same md5sum that I have with my used / local one...
Code: Select all
guest@porteus:/mnt/live/memory/images$ uname -a
Linux porteus 3.9.4-porteus #1 SMP PREEMPT Sat May 25 21:56:02 UTC 2013 x86_64 Intel(R) Pentium(R) D CPU 2.66GHz GenuineIntel GNU/Linux
... May 25 sounds indeed old for 2.1rc2... or not? O___o