Setarch command
Posted: 23 Mar 2018, 17:01
Dunno if the following is best put into the Port4.0rc4 bug report thread, or in a update-firefox related thread?
_____________________________________
My system: Porteus 4.0rc4 XFCE x86-64.
I downloaded the most recent firefox ESR (extended support release) en-UK version and put it into /tmp.
Now, the tricky issue here: I downloaded the i586 version. Still, it is only called /tmp/firefox-52.7.2esr.tar.bz2
Then I used the /usr/local/bin/update-firefox-live to convert it into a tgz and xzm.
Now, the package and module are called both /tmp/firefox-52.7.2esr-x86_64-1.
But still these are i586 versions, not x86-64 versions… The update-firefox-live script presumed it would be the same firefox tarball machine architecture than the running system… but the script presumed wrong.
I renamed both package and module into firefox-52.7.2esr-i586-1.* to have it obvious which arch these packages really are.
Just to make it sure it really was the i586 version, I activated it and tried running FFx:
And trying to start that FFx sure did fail:
It would be possible to add an architecture check, like, checking the main executable, that would here have been firefox/firefox-bin or firefox/firefox and then adjust the name of the created tgz / xzm accordingly… but who would want to code such extra check?
Also, I suggest removing either firefox/firefox-bin or firefox/firefox and replacing it with an symbolic link to the remaining other file, since both are the same anyway, and why have two large files in the tgz or xzm when one is sufficient?
… Oddly enough, the non ESR versions of FFx always have been the same, meaning the "firefox" and "firefox-bin" executable, but in this case, they are indeed not:
Any idea why they do differ? By creating FFx packages in the past (for both x86-64 and i586) the files "firefox" and "firefox-bin" always have been the same, but I never converted an ESR version before.
And as you can see, the sha1 BuildID is the very same for both "firefox" and "firefox-bin". So I don't really get why the files themselves do differ.
...
… …
<paranoia_mode=ON>"Because one of the files, the one usually started, got obviously manipulated by the 5eyes. HurrHurrHurr…"<paranoia_mode=OFF>
(*jk* there. xD Then again, who really knows, eh?)
________
*jk* is short for "just kidding", in case you did not know.
_____________________________________
My system: Porteus 4.0rc4 XFCE x86-64.
I downloaded the most recent firefox ESR (extended support release) en-UK version and put it into /tmp.
Now, the tricky issue here: I downloaded the i586 version. Still, it is only called /tmp/firefox-52.7.2esr.tar.bz2
Then I used the /usr/local/bin/update-firefox-live to convert it into a tgz and xzm.
Now, the package and module are called both /tmp/firefox-52.7.2esr-x86_64-1.
But still these are i586 versions, not x86-64 versions… The update-firefox-live script presumed it would be the same firefox tarball machine architecture than the running system… but the script presumed wrong.
I renamed both package and module into firefox-52.7.2esr-i586-1.* to have it obvious which arch these packages really are.
Just to make it sure it really was the i586 version, I activated it and tried running FFx:
Code: Select all
root@porteus:/# activate /mnt/sdb1/Porteus_modules/4.0/firefox-52.7.2esr-i586-1.xzm
Quiet mode: off
Updating shared library links: /sbin/ldconfig
Updating XFCE menu: update-desktop-database
Code: Select all
guest@porteus:/$ firefox
bash: /usr/bin/firefox: No such file or directory
guest@porteus:/$ file /usr/bin/firefox
/usr/bin/firefox: symbolic link to /usr/lib64/firefox-52.7.2esr/firefox
guest@porteus:/$ file /usr/lib64/firefox-52.7.2esr/firefox
/usr/lib64/firefox-52.7.2esr/firefox: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=5ea0c90bc9ddf68f8a3fb5c59e69e6b37c05766c, stripped
Code: Select all
<_<
>_>
<_<
>_<
… Oddly enough, the non ESR versions of FFx always have been the same, meaning the "firefox" and "firefox-bin" executable, but in this case, they are indeed not:
Code: Select all
root@porteus:/mnt/live/memory/images/firefox-52.7.2esr-i586-1.xzm/usr/lib64/firefox# md5sum firefox firefox-bin
4f4b680253152cba4aa3711f9b41d45d firefox
3800ebebd2d2e103776c2318780997a8 firefox-bin
root@porteus:/mnt/live/memory/images/firefox-52.7.2esr-i586-1.xzm/usr/lib64/firefox# sha1sum firefox firefox-bin
669aee883f5c8ff25eb0ff76019096d1614c0137 firefox
3a5c0520a7e4ac4d294816bf0c999261e56a1e08 firefox-bin
root@porteus:/mnt/live/memory/images/firefox-52.7.2esr-i586-1.xzm/usr/lib64/firefox# l firefox firefox-bin
-rwxr-xr-x 1 root 188016 2018-03-16 04:03 firefox
-rwxr-xr-x 1 root 188020 2018-03-16 04:03 firefox-bin
root@porteus:/mnt/live/memory/images/firefox-52.7.2esr-i586-1.xzm/usr/lib64/firefox# file firefox firefox-bin
firefox: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=5ea0c90bc9ddf68f8a3fb5c59e69e6b37c05766c, stripped
firefox-bin: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=5ea0c90bc9ddf68f8a3fb5c59e69e6b37c05766c, stripped
And as you can see, the sha1 BuildID is the very same for both "firefox" and "firefox-bin". So I don't really get why the files themselves do differ.
...
… …
<paranoia_mode=ON>"Because one of the files, the one usually started, got obviously manipulated by the 5eyes. HurrHurrHurr…"<paranoia_mode=OFF>
(*jk* there. xD Then again, who really knows, eh?)
________
*jk* is short for "just kidding", in case you did not know.