[SOLVED] xzm modules issues testing newer one
Posted: 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
However I have just spotted
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
but openssl version is still wrong. Ok lets try a search....Porteus is on sda3
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
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
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.
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/
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
Reboot now has
Code: Select all
ls /var/log/packages/openssl*
/var/log/packages/openssl-1.0.2d-x86_64-1
Code: Select all
umount /mnt/sda1
umount /mnt/sda4
find / -name openssl
(snip)
/mnt/live/memory/images/05-devel.xzm/usr/include/openssl
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*
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/
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.