[SOLVED] xzm modules issues testing newer one

Post here if you are a new Porteus member and you're looking for some help.
Post Reply
aus9

[SOLVED] xzm modules issues testing newer one

Post#1 by aus9 » 28 Oct 2015, 23:26

Hi

Subject changed to reduce length to add solved
I am on 64 bit LWQt. original xzm was openssl v 1.0.1e. I used USM to update to v 1.0.1p .I built (currently testing) v 1.0.2d. My lack of Porteus awareness has caught me out, sorry. Here is my current issue.....feel free to have a laugh....

what I thought I could do was....
deactivate the xzm v 1.0.1p
activate the xzm v 1.0.2d
reboot and test

empty line added to make it easier to read to code box

Code: Select all

 openssl version -a && ls /mnt/live/memory/images | grep openssl
OpenSSL 1.0.1p 9 Jul 2015
built on: Thu Jul  9 12:59:08 2015
platform: linux-x86_64
options:  bn(64,64) rc4(16x,int) des(idx,cisc,16,int) blowfish(idx) 
compiler: gcc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
OPENSSLDIR: "/etc/ssl"

openssl-1.0.2d-x86_64-1.xzm/
However I have just spotted

Code: Select all

ls /var/log/packages/openssl*
/var/log/packages/openssl-1.0.1p-x86_64-1_slack14.1  /var/log/packages/openssl-1.0.2d-x86_64-1
I am about to delete the older package and reboot and try again. But thought I would post my lack of knowledge for all to see, in case it helps someone.

Reboot now has

Code: Select all

ls /var/log/packages/openssl*
/var/log/packages/openssl-1.0.2d-x86_64-1
but openssl version is still wrong. Ok lets try a search....Porteus is on sda3

Code: Select all

umount /mnt/sda1
umount /mnt/sda4
find / -name openssl
(snip)
/mnt/live/memory/images/05-devel.xzm/usr/include/openssl
OK I will try deactivating the devel xzm and reboot

Reboot ....No that wasn't it ....it may be because I tend to boot with changes bootcode

Code: Select all

ls -al /mnt/sda3/porteus/changes/usr/bin/openssl 
-rwxr-xr-x 1 root root 536024 Jul 10 02:01 /mnt/sda3/porteus/changes/usr/bin/openssl*
this looks likely as I have only built v 1.0.2d today I will delete any others I find in changes

OK without reboot, I deleted all I could find for openssl stuff in changes
deactivate and then activated the same module and now Ihave it

Code: Select all

openssl version -a && ls /mnt/live/memory/images | grep openssl
OpenSSL 1.0.2d 9 Jul 2015 (Library: OpenSSL 1.0.1p 9 Jul 2015)
built on: Thu Jul  9 12:59:08 2015
platform: linux-x86_64
options:  bn(64,64) rc4(16x,int) des(idx,cisc,16,int) blowfish(idx) 
compiler: gcc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
OPENSSLDIR: "/etc/ssl"
openssl-1.0.2d-x86_64-1.xzm/
I will still do a reboot to see my changes are OK

slightly offtopic the XZM devel has the openssl (v1.0.1e) headers. That won't affect anyone unless they need my headers and they can get them in other ways

Reboot hmmm openssl version -a && ls /mnt/live/memory/images | grep openssl is still OK but more testing of other matters.

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

Re: [SOLVED] xzm modules issues testing newer one

Post#2 by Ed_P » 29 Oct 2015, 04:06

TTBOMK When booting and modules with the same name the last one loaded overrides the one(s) loaded before it.
Ed

aus9

Re: [SOLVED] xzm modules issues testing newer one

Post#3 by aus9 » 29 Oct 2015, 04:54

Ed_P

I won't edit first post now you have replied.
I just noticed....an old script was in /var/log/scripts for openssl

so you don't deactivate and delete different version modules from your modules folder?

2) if not, I am guessing you are saying the order of the files in modules matters?

looking into /var/log/porteus-livedb
# snip
# Modules activated during boot time:
/mnt/sda3/porteus/base/000-kernel.xzm
/mnt/sda3/porteus/base/001-core.xzm
/mnt/sda3/porteus/base/001-core_alldesktops-150124.xzm
/mnt/sda3/porteus/base/002-xorg.xzm
/mnt/sda3/porteus/base/002-xorg_alldesktops-150126.xzm
/mnt/sda3/porteus/base/003-lxqt.xzm
/mnt/sda3/porteus/base/004-lxqt_fixes-150120.xzm
/mnt/sda3/porteus/base/05-devel.xzm
/mnt/sda3/porteus/modules/AlsaMixer.app-0.1-x86_64-1_slack.xzm
/mnt/sda3/porteus/modules/ca-certificates-20150426-noarch-2_slack14.1.xzm
/mnt/sda3/porteus/modules/google-chrome-39.0.2171.65-x86_64-bundle.xzm
/mnt/sda3/porteus/modules/locales-en_AU.utf8-x86_64-1prt.xzm
/mnt/sda3/porteus/modules/mirage-1.0_pre2-x86_64-1_slack.xzm
/mnt/sda3/porteus/modules/mtpaint-3.40-x86_64-bundle.xzm
/mnt/sda3/porteus/modules/nano-2.3.2-x86_64-1.xzm
/mnt/sda3/porteus/modules/openssl-1.0.2d-x86_64-1.xzm
/mnt/sda3/porteus/modules/pycairo-1.8.10-x86_64-2.xzm
/mnt/sda3/porteus/modules/pygobject-2.28.6-x86_64-2.xzm
/mnt/sda3/porteus/modules/pygtk-2.24.0-x86_64-1.xzm
/mnt/sda3/porteus/modules/python-2.7.5-x86_64-1.xzm
/mnt/sda3/porteus/modules/tls-1.6-x86_64-1_slack.xzm
/mnt/sda3/porteus/modules/usm-latest-0.0-noarch-1.xzm
/mnt/sda3/porteus/modules/vlc-2.2.1-x86_64-bundle.xzm
/mnt/sda3/porteus/modules/xxdiff-401-x86_64-1_slack.xzm
/mnt/sda3/porteus/modules/youtube-dl-2015.10.09-x86_64-bundle.xzm

I can see that the naming of the base packages now makes sense.

Maybe I should name my package

Z-private-openssl-1.0.2d-x86_64-1.xzm ?
Its currently a private package but I hope to share it once I sort out my knowledge of Porteus or lack thereof

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

Re: [SOLVED] xzm modules issues testing newer one

Post#4 by Ed_P » 29 Oct 2015, 05:12

aus9 wrote:so you don't deactivate and delete different version modules from your modules folder?
It depends on the module. I usually depend older versions once I have proven the newer one works. Initially I deactivate the old one, activate the new one and try it. Then I reboot and retest it and if still good I delete the old one, to save space usually.

But not always. Firefox is in the ISO I boot and newer versions are in my Modules folder. The Modules version overrides the version in the ISO I downloaded.
2) if not, I am guessing you are saying the order of the files in modules matters?
Yes.
Maybe I should name my package

Zxopenssl-1.0.2d-x86_64-1.xzm ?
It doesn't have to be that dramatic, openssl-1.0.99d-x86_64-1.xzm should work also. :wink:
Ed

aus9

Re: [SOLVED] xzm modules issues testing newer one

Post#5 by aus9 » 29 Oct 2015, 09:01

thanks

also I now think I was wrong to prepend z
I am allowed to think once a week

cheers

Post Reply