Page 1 of 1
[HOWTO] figure out if you have a pure x86_64 system
Posted: 12 Feb 2020, 06:42
by Rava
HOWTO figure out if I do indeed have a pure x86_64 system.
My system: Porteus 5.0rc1 XFCE
While doing so I found one interesting inconsistency.
Code: Select all
# ls /var/log/packages |wc
546 546 14051
That tells me that currently I have 546 packages installed.
Code: Select all
# ls /var/log/packages | grep x86_64|wc
526 526 13471
Of the 546 526 are indeed x86_64
Code: Select all
ls /var/log/packages | grep noarch|wc
19 19 554
and 19 are of noarch (e.g. binary-less scripts and such)
Lets look what the missing one is about?
Good that grep can do an "inverted match".
Code: Select all
# ls /var/log/packages | grep -Ev "x86_64|noarch"|wc
1 1 26
# ls /var/log/packages | grep -Ev "x86_64|noarch"
mate-search-tool-1.20.1-2
Once again my fw script comes in handy. I posted it already on here.
(Aside from error display, the main line is just file $(which "$1") 2>/dev/null) So, let's see if the mate-search-tool is architecture-less or is of x86_64.
Code: Select all
# fw fw
/usr/local/bin/fw: Bourne-Again shell script, ASCII text executable
# fw mate-search-tool
/usr/bin/mate-search-tool: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, stripped
So… seems /var/lib/pkgtools/packages/mate-search-tool-1.20.1-2 should be called /var/lib/pkgtools/packages/mate-search-tool-1.20.1-2-x86_64-1 since it is indeed a x86_64 package.
But aside from finding that mate-search-tool inconsistency, I indeed have figured out that all programs installed are either of x86_64 (527 of 546 are, since mate-search-tool is also of x86_64) and 19 are of type noarch.
So yes, mission accomplished: I have indeed a pure x86_64 system.
[HOWTO] figure out if you have a pure x86_64 system
Posted: 12 Feb 2020, 07:03
by Ed_P
Interesting. My x86_64 Porteus 5.0rc1 lxde test system shows:
Code: Select all
guest@porteus:~$ ls /var/log/packages | wc
1 1 39
guest@porteus:~$ ls /var/log/packages | grep x84_64 |wc
0 0 0
guest@porteus:~$ ls /var/log/packages | grep noarch |wc
0 0 0
guest@porteus:~$ ls /var/log/packages | grep -Ev "x84_64|noarch"|wc
1 1 39
guest@porteus:~$ ls /var/log/packages | grep -Ev "x84_64|noarch"
flashplayer-plugin-32.0.0.303-x86_64-1
guest@porteus:~$
[HOWTO] figure out if you have a pure x86_64 system
Posted: 12 Feb 2020, 07:08
by Rava
Ed_P wrote: ↑12 Feb 2020, 07:03
In my system, /var/log/packages is a symlink:
Code: Select all
# file /var/log/packages
/var/log/packages: symbolic link to ../lib/pkgtools/packages
Maybe one module or another overwrote that symlink and created /var/log/packages as folder?
Then we can consider that module as broken.
Just check what /var/lib/pkgtools/packages instead of /var/log/packages would result in. And if indeed on your system /var/log/packages is a folder.
[HOWTO] figure out if you have a pure x86_64 system
Posted: 12 Feb 2020, 07:32
by Ed_P
Code: Select all
guest@porteus:~$ file /var/log/packages
/var/log/packages: directory
guest@porteus:~$ ls /var/log/packages
flashplayer-plugin-32.0.0.303-x86_64-1
guest@porteus:~$ ls /var/lib/pkgtools/packages
ConsoleKit2-1.0.0-x86_64-4
GConf-3.2.6-x86_64-4
ModemManager-1.10.0-x86_64-1
ModemManager-1.12.4-x86_64-1
NetworkManager-1.18.1-x86_64-1
NetworkManager-1.22.6-x86_64-1
OpenAL-1.18.0-x86_64-1_SBo
SDL2-2.0.10-x86_64-1
SDL2-2.0.9-x86_64-3
TLP-1.1-x86_64-1_SBo
TLP-1.2.2-x86_64-1_SBo
Xdialog-2.3.1-x86_64-1jay
a52dec-0.7.4-x86_64-3
:
:
[HOWTO] figure out if you have a pure x86_64 system
Posted: 12 Feb 2020, 22:31
by Rava
Please look into the module that contains flashplayer-plugin-32.0.0.303-x86_64-1 if that is the one that overwrote the symlink of /var/log/packages to /var/lib/pkgtools/packages .
[HOWTO] figure out if you have a pure x86_64 system
Posted: 13 Feb 2020, 04:52
by Ed_P
On my x86_64 Porteus 4.0 Cinnamon system I have:
Code: Select all
guest@porteus:~$ ls /var/log/packages | wc
624 624 16097
guest@porteus:~$ ls /var/log/packages | grep x84_64 |wc
0 0 0
guest@porteus:~$ ls /var/log/packages | grep noarch |wc
22 22 635
guest@porteus:~$ ls /var/log/packages | grep -Ev "x84_64|noarch"|wc
602 602 15462
guest@porteus:~$ ls /var/log/packages | grep -Ev "x84_64|noarch"
BeautifulSoup-4.6.0-x86_64-1jss
ConsoleKit2-1.0.0-x86_64-3
GConf-3.2.6-x86_64-3
ModemManager-1.6.12-x86_64-1
NetworkManager-1.8.4-x86_64-1jay
OpenAL-1.18.0-x86_64-1_SBo
SDL2-2.0.8-x86_64-1_SBo
TLP-1.1-x86_64-1_SBo
Xdialog-2.3.1-x86_64-1jay
a52dec-0.7.4-x86_64-2
aaa_base-14.2-x86_64-3
aaa_elflibs-14.2-x86_64-34
aaa_terminfo-6.1-x86_64-3
aalib-1.4rc5-x86_64-5
accountsservice-0.6.47-x86_64-1jss
acl-2.2.52-x86_64-1
acpid-2.0.28-x86_64-1
aisleriot-3.22.4-x86_64-1dj
alsa-lib-1.1.6-x86_64-2
alsa-plugins-1.1.6-x86_64-1
alsa-utils-1.1.6-x86_64-1
archivemount-0.8.3-x86_64-1jay
aspell-0.60.6.1-x86_64-3
asunder-2.8-x86_64-1jss
at-spi2-atk-2.26.2-x86_64-1
at-spi2-core-2.28.0-x86_64-1
atk-2.28.1-x86_64-1
atkmm-2.24.2-x86_64-2
attr-2.4.47-x86_64-1
audacious-3.9-gtk3-x86_64-1jss
audacious-plugins-3.9-gtk3-x86_64-1jss
audiofile-0.3.6-x86_64-1
babl-0.1.46-x86_64-1
bash-4.4.019-x86_64-2
bc-1.07.1-x86_64-1
bin-11.1-x86_64-1
blueman-2.0.5-x86_64-2
bluez-5.49-x86_64-2
boost-extra-1.66.0-x86_64-1jay
bridge-utils-1.5-x86_64-1
brscan-0.2.4-0.amd64
brscan-skey-0.2.4-1.amd64
brscan2-0.2.5-1.amd64
brscan3-0.2.11-5.amd64
brscan4-0.4.2-1.amd64
bzip2-1.0.6-x86_64-1
cairo-1.15.12-x86_64-1
cairomm-1.12.2-x86_64-2
caribou-0.4.21-x86_64-1jss
cdparanoia-III_10.2-x86_64-1
cdrdao-1.2.3-x86_64-3
cdrtools-3.01-x86_64-3
cgmanager-0.41-x86_64-3
cifs-utils-6.7-x86_64-1
cinnamon-3.8.6-x86_64-1jss
cinnamon-control-center-3.8.0-x86_64-1jss
cinnamon-desktop-3.8.0-x86_64-1jss
cinnamon-menus-3.8.0-x86_64-1jss
cinnamon-screensaver-3.8.0-x86_64-1jss
cinnamon-session-3.8.1-x86_64-1jss
cinnamon-settings-daemon-3.8.2-x86_64-1jss
cjs-3.8.0-x86_64-1jss
clutter-1.26.2-x86_64-1jss
clutter-gtk-1.8.4-x86_64-1jss
cndrvcups-common-3.90-1.x86_64
cndrvcups-ufr2-uk-3.50-1.x86_64
cndrvcups-ufr2lt-uk-1.40-1.x86_64
cndrvcups-utility-1.10-1.x86_64
cogl-1.22.2-x86_64-1jss
colord-1.4.3-x86_64-1jss
coreutils-8.29-x86_64-1
cpio-2.12-x86_64-1
cups-2.2.6-x86_64-1
cups-bjnp-2.0-x86_64-1_SBo
cups-filters-1.20.0-x86_64-1
cups-pdf-3.0.1-x86_64-1_slonly
curl-7.59.0-x86_64-2
cyrus-sasl-2.1.26-x86_64-3
db48-4.8.30-x86_64-2
dbus-1.12.6-x86_64-1
dbus-glib-0.110-x86_64-1
dbus-python-1.2.6-x86_64-1
dbus-python-1.2.6-x86_64-2
dconf-0.26.1-x86_64-2
dconf-editor-3.26.2-x86_64-2
dcron-4.5-x86_64-5
desktop-file-utils-0.23-x86_64-1
dhcp-4.4.1-x86_64-1
dhcpcd-7.0.3-x86_64-1
dialog-1.3_20170509-x86_64-1
diffutils-3.6-x86_64-1
djvulibre-3.5.27-x86_64-1
dmapi-2.2.12-x86_64-2
dmidecode-3.1-x86_64-1
dnsmasq-2.79-x86_64-1
dosfstools-4.1-x86_64-1
dri3proto-1.0-x86_64-2
dvd+rw-tools-7.1-x86_64-2
e2fsprogs-1.44.1-x86_64-1
eject-2.1.5-x86_64-4
elfutils-0.170-x86_64-1
enchant-1.6.1-x86_64-2
epson-inkjet-printer-escpr-1.6.18-x86_64-1_SBo
esound-0.2.41-x86_64-2
etc-15.0-x86_64-3
ethtool-4.15-x86_64-1
eudev-3.2.5-x86_64-1
exiv2-0.26-x86_64-2
extra-gcc-libs-7.3.0-x86_64-1jay
f2fs-tools-1.6.1-x86_64-1jay
faac-1.28-x86_64-1jay
faad2-2.7-x86_64-2_SBo
ffmpeg-3.4.2-x86_64-1jay
ffmpegthumbnailer-2.2.0-x86_64-1jss
fftw-3.3.7-x86_64-1
file-5.32-x86_64-1
file-roller-3.26.2-x86_64-1jss
findutils-4.4.2-x86_64-1
firefox-52.9.0esr-x86_64-1
flac-1.3.2-x86_64-1jay
flashplayer-plugin-32.0.0.303-x86_64-1
:
:
which includes the same flashplayer-plugin-32.0.0.303-x86_64-1 module. Not sure where/how I would look for something in that xzm module that would change a symlink.
[HOWTO] figure out if you have a pure x86_64 system
Posted: 13 Feb 2020, 06:12
by ncmprhnsbl
Ed_P wrote: ↑13 Feb 2020, 04:52
Not sure where/how I would look for something in that xzm module that would change a symlink.
any module made with porteus-4.0 (that is packaged in slackware format) will have it's package info in /var/log/packages(a dir)
if used in 5.0* , (in which /var/log/packages is symlinked to /var/lib/pkgtools/packages) the symlink will be overwritten with that^ directory..
presumably, if another 5.0* built module is subsequently activated, it would then overwrite it with a symlink again...
the reverse is true for a module built for 5.0* activated in 4.0* ..
[HOWTO] figure out if you have a pure x86_64 system
Posted: 13 Feb 2020, 06:39
by Rava
ncmprhnsbl wrote: ↑13 Feb 2020, 06:12
presumably, if another 5.0* built module is subsequently activated, it would then overwrite it with a symlink again...
the reverse is true for a module built for 5.0* activated in 4.0* ..
So, when the path got got overwritten by a symlink… what happens to the files in path? Are they gone/invisible for the system for the time being?
I presume both searching in /var/log/packages and /var/lib/pkgtools/packages is no valid option for a simple fix when 4.0 and 5.0 modules got mixed up…
___________________________________________________
Ed_P wrote: ↑13 Feb 2020, 04:52
On my x86_64 Porteus 4.0 Cinnamon system I have:
Code: Select all
guest@porteus:~$ ls /var/log/packages | wc
624 624 16097
guest@porteus:~$ ls /var/log/packages | grep x84_64 |wc
0 0 0
guest@porteus:~$ ls /var/log/packages | grep noarch |wc
22 22 635
guest@porteus:~$ ls /var/log/packages | grep -Ev "x84_64|noarch"|wc
602 602 15462
guest@porteus:~$ ls /var/log/packages | grep -Ev "x84_64|noarch"
BeautifulSoup-4.6.0-x86_64-1jss
ConsoleKit2-1.0.0-x86_64-3
[…]
Ed_P,
try grep x8
6_64 instead of the x8
4_64 you used.
Code: Select all
guest@porteus:~$ ls /var/log/packages/* | grep x86_64|wc
525 525 22879
guest@porteus:~$ ls /var/log/packages/* | grep x84_64|wc
0 0 0
[HOWTO] figure out if you have a pure x86_64 system
Posted: 13 Feb 2020, 07:54
by ncmprhnsbl
Rava wrote: ↑13 Feb 2020, 06:39
So, when the path got got overwritten by a symlink… what happens to the files in path? Are they gone/invisible for the system for the time being?
the work around would be to look directly at each module in /mnt/live/memory/images/
[HOWTO] figure out if you have a pure x86_64 system
Posted: 13 Feb 2020, 19:30
by Ed_P
Rava wrote: ↑13 Feb 2020, 06:39
Ed_P,
try grep x8
6_64 instead of the x8
4_64 you used.
Code: Select all
guest@porteus:~$ ls /var/log/packages | grep -Ev "x86_64|noarch"|wc
5 5 114
guest@porteus:~$ ls /var/log/packages | grep -Ev "x86_64|noarch"
brscan-0.2.4-0.amd64
brscan-skey-0.2.4-1.amd64
brscan2-0.2.5-1.amd64
brscan3-0.2.11-5.amd64
brscan4-0.4.2-1.amd64
guest@porteus:~$
ncmprhnsbl wrote: ↑13 Feb 2020, 06:12
any module made with porteus-4.0 (that is packaged in slackware format) will have it's package info in /var/log/packages(a dir)
if used in 5.0* , (in which /var/log/packages is symlinked to /var/lib/pkgtools/packages) the symlink will be overwritten with that^ directory..
presumably, if another 5.0* built module is subsequently activated, it would then overwrite it with a symlink again...
the reverse is true for a module built for 5.0* activated in 4.0* ..
Interesting. Somewhat scary even. I assumed a module is a module and copied the flashplayer module from my 4.0 system to my 5.0 system. You're saying I need to have your browser script build the flashplayer on the 5.0 system.
[HOWTO] figure out if you have a pure x86_64 system
Posted: 13 Feb 2020, 20:52
by Ed_P
So I booted 5.0, Openbox "DE", deactivated the flashplayer plugin, ran the Browser Update function and selected Flash Player. And this is what I got.
Code: Select all
Slackware package /tmp/flashplayer-plugin-32.0.0.330-x86_64-1.txz created.
Your module is ready at /tmp/flashplayer-plugin-32.0.0.330-x86_64-1.xzm
Please move it to the modules dir to be activated at boot time,
or to some other place outside of the live system to survive reboot.
sh-5.0# ls -l /tmp
total 7220
-rw-r--r-- 1 root root 7391144 Feb 13 15:45 flashplayer-plugin-32.0.0.330-x86_64-1.txz
drwx------ 7 guest users 140 Feb 13 15:43 xdg-runtime-guest
drwx------ 2 root root 40 Feb 13 15:43 xdg-runtime-root
sh-5.0#
Here's the whole screen output if your interested. Some things about symlinks at line 58.
Code: Select all
update-flash
sh-5.0# update-flash
[OK] User is root
[OK] Distro is Porteus
[OK] Internet connection exists
Downloading live script ...
Downloading: update-flash-live DONE
Work will be done in: /tmp
Searching online for latest flash player version ...
Installed version:
Latest version: 32.0.0.330
Would you like to continue? [y/n]
Would you like to create a Porteus module? [y/n]
Downloading: flash_player_npapi_linux.x86_64.tar.gz DONE
libflashplayer.so
readme.txt
LGPL/
LGPL/LGPL.txt
LGPL/notice.txt
usr/
usr/lib64/
usr/lib64/kde4/
usr/lib64/kde4/kcm_adobe_flash_player.so
usr/bin/
usr/bin/flash-player-properties
usr/share/
usr/share/icons/
usr/share/icons/hicolor/
usr/share/icons/hicolor/16x16/
usr/share/icons/hicolor/16x16/apps/
usr/share/icons/hicolor/16x16/apps/flash-player-properties.png
usr/share/icons/hicolor/32x32/
usr/share/icons/hicolor/32x32/apps/
usr/share/icons/hicolor/32x32/apps/flash-player-properties.png
usr/share/icons/hicolor/24x24/
usr/share/icons/hicolor/24x24/apps/
usr/share/icons/hicolor/24x24/apps/flash-player-properties.png
usr/share/icons/hicolor/22x22/
usr/share/icons/hicolor/22x22/apps/
usr/share/icons/hicolor/22x22/apps/flash-player-properties.png
usr/share/icons/hicolor/48x48/
usr/share/icons/hicolor/48x48/apps/
usr/share/icons/hicolor/48x48/apps/flash-player-properties.png
usr/share/applications/
usr/share/applications/flash-player-properties.desktop
usr/share/kde4/
usr/share/kde4/services/
usr/share/kde4/services/kcm_adobe_flash_player.desktop
usr/share/pixmaps/
usr/share/pixmaps/flash-player-properties.png
usr/lib/
usr/lib/kde4/
usr/lib/kde4/kcm_adobe_flash_player.so
license.pdf
chmod: cannot operate on dangling symlink 'usr/lib/kde4/kcm_adobe_flash_player.so'
Slackware package maker, version 3.14159265.
Searching for symbolic links:
usr/lib/kde4/kcm_adobe_flash_player.so /usr/lib64/kde4/kcm_adobe_flash_player.so
usr/lib64/mozilla /usr/lib/mozilla
usr/share/pixmaps/flash-player-properties.png ../icons/hicolor/48x48/apps/flash-player-properties.png
Making symbolic link creation script:
( cd usr/lib/kde4 ; rm -rf kcm_adobe_flash_player.so )
( cd usr/lib/kde4 ; ln -sf /usr/lib64/kde4/kcm_adobe_flash_player.so kcm_adobe_flash_player.so )
( cd usr/lib64 ; rm -rf mozilla )
( cd usr/lib64 ; ln -sf /usr/lib/mozilla mozilla )
( cd usr/share/pixmaps ; rm -rf flash-player-properties.png )
( cd usr/share/pixmaps ; ln -sf ../icons/hicolor/48x48/apps/flash-player-properties.png flash-player-properties.png )
Unless your existing installation script already contains the code
to create these links, you should append these lines to your existing
install script. Now's your chance. :^)
Would you like to add this stuff to the existing install script and
remove the symbolic links ([y]es, [n]o)? y
Removing symbolic links:
removed './usr/lib/kde4/kcm_adobe_flash_player.so'
removed './usr/share/pixmaps/flash-player-properties.png'
removed './usr/lib64/mozilla'
Updating your ./install/doinst.sh...
This next step is optional - you can set the directories in your package
to some sane permissions. If any of the directories in your package have
special permissions, then DO NOT reset them here!
Would you like to reset all directory permissions to 755 (drwxr-xr-x) and
directory ownerships to root.root ([y]es, [n]o)? n
Creating Slackware package: /tmp/flashplayer-plugin-32.0.0.330-x86_64-1.txz
./
install/
install/doinst.sh
install/slack-desc
license.pdf
usr/
usr/bin/
usr/bin/flash-player-properties
usr/lib/
usr/lib/kde4/
usr/lib/mozilla/
usr/lib/mozilla/plugins/
usr/lib/mozilla/plugins/libflashplayer.so
usr/lib64/
usr/lib64/kde4/
usr/lib64/kde4/kcm_adobe_flash_player.so
usr/share/
usr/share/applications/
usr/share/applications/flash-player-properties.desktop
usr/share/icons/
usr/share/icons/hicolor/
usr/share/icons/hicolor/16x16/
usr/share/icons/hicolor/16x16/apps/
usr/share/icons/hicolor/16x16/apps/flash-player-properties.png
usr/share/icons/hicolor/22x22/
usr/share/icons/hicolor/22x22/apps/
usr/share/icons/hicolor/22x22/apps/flash-player-properties.png
usr/share/icons/hicolor/24x24/
usr/share/icons/hicolor/24x24/apps/
usr/share/icons/hicolor/24x24/apps/flash-player-properties.png
usr/share/icons/hicolor/32x32/
usr/share/icons/hicolor/32x32/apps/
usr/share/icons/hicolor/32x32/apps/flash-player-properties.png
usr/share/icons/hicolor/48x48/
usr/share/icons/hicolor/48x48/apps/
usr/share/icons/hicolor/48x48/apps/flash-player-properties.png
usr/share/kde4/
usr/share/kde4/services/
usr/share/kde4/services/kcm_adobe_flash_player.desktop
usr/share/pixmaps/
Slackware package /tmp/flashplayer-plugin-32.0.0.330-x86_64-1.txz created.
Your module is ready at /tmp/flashplayer-plugin-32.0.0.330-x86_64-1.xzm
Please move it to the modules dir to be activated at boot time,
or to some other place outside of the live system to survive reboot.
sh-5.0# ls -l /tmp
total 7220
-rw-r--r-- 1 root root 7391144 Feb 13 15:45 flashplayer-plugin-32.0.0.330-x86_64-1.txz
drwx------ 7 guest users 140 Feb 13 15:43 xdg-runtime-guest
drwx------ 2 root root 40 Feb 13 15:43 xdg-runtime-root
sh-5.0#
guest@porteus:~$ cd /tmp
guest@porteus:/tmp$ ls
flashplayer-plugin-32.0.0.330-x86_64-1.txz xdg-runtime-guest/
spacefm-guest-350947eb.tmp/ xdg-runtime-root/
tmpaddon
guest@porteus:/tmp$ txz2xzm *.txz
Verifying package flashplayer-plugin-32.0.0.330-x86_64-1.txz.
Installing package flashplayer-plugin-32.0.0.330-x86_64-1.txz:
PACKAGE DESCRIPTION:
# flashplayer-plugin (flash plugin for web browsers)
#
# Provides Adobe Flash plugin for browsers that recognize
# /usr/lib/mozilla/plugins as a valid plugin directory
#
# Plugin is subject to Adobe terms of use:
# http://www.adobe.com/go/labs_term_of_use
#
# Plugin is subject to Adobe Flash EULA:
# http://labs.adobe.com/technologies/eula/flashplayer.html
#
Executing install script for flashplayer-plugin-32.0.0.330-x86_64-1.txz.
Package flashplayer-plugin-32.0.0.330-x86_64-1.txz installed.
Creating /tmp/flashplayer-plugin-32.0.0.330-x86_64-1.xzm
guest@porteus:/tmp$ ls
flashplayer-plugin-32.0.0.330-x86_64-1.txz tmpaddon
flashplayer-plugin-32.0.0.330-x86_64-1.xzm xdg-runtime-guest/
spacefm-guest-350947eb.tmp/ xdg-runtime-root/
guest@porteus:/tmp$
[HOWTO] figure out if you have a pure x86_64 system
Posted: 13 Feb 2020, 23:52
by ncmprhnsbl
Ed_P wrote: ↑13 Feb 2020, 19:30
Interesting. Somewhat scary even. I assumed a module is a module and copied the flashplayer module from my 4.0 system to my 5.0 system. You're saying I need to have your browser script build the flashplayer on the 5.0 system.
it's just a change that occured in the slackware package tools between 4.0 and 5.0, only affecting the package information files, nothing else.
if you wanted to, you could manually fix a module by extracting it, moving var/log/packages to /var/lib/pkgtools/ and recompressing it.
Ed_P wrote: ↑13 Feb 2020, 20:52
And this is what I got.
presume you chose n at "Would you like to create a Porteus module? [y/n]" , hence the output being a package.
have done some changes to the messages to be relevent to module or package output. thanks
Ed_P wrote: ↑13 Feb 2020, 20:52
Some things about symlinks at line 58.
not relevant here.
[HOWTO] figure out if you have a pure x86_64 system
Posted: 14 Feb 2020, 04:56
by Ed_P
My 50rc Openbox system with a flashplayer module built on the 50rc system results:
Code: Select all
~$ ls /var/log/packages | wc
554 554 14103
~$ ls /var/log/packages | grep x86_64 |wc
530 530 13411
~$ ls /var/log/packages | grep noarch |wc
23 23 664
~$ ls /var/log/packages | grep -Ev "x86_64|noarch"|wc
1 1 28
~$ ls /var/log/packages | grep -Ev "x86_64|noarch"
kernel-headers-5.4.18-x86-1
ncmprhnsbl wrote: ↑13 Feb 2020, 23:52
presume you chose n at "Would you like to create a Porteus module? [y/n]" , hence the output being a package.
have done some changes to the messages to be relevent to module or package output. thanks
I think I responded y to that prompt and in fact I even rebooted and reran the Flashplayer Update function a 2nd time and got the same results. I'll let you know how a rerun with your changes works out later.
[HOWTO] figure out if you have a pure x86_64 system
Posted: 14 Feb 2020, 05:07
by ncmprhnsbl
just tested, worked for me..