antiX live usb issue

[rs55]

ran sudo e4defrag -v vmlinuz :
"success"

[rs55]

A I mentioned way back- lum was working fine with mxlinux ( which has the 9660 installed)- on the same machine. So clearly mx is doing something else that is allowing it to work fine with the fuseiso9660.

[BitJam]

If you don't mind, please re-install one of those so you can test the fix I am preparing for you. Thanks!

[rs55]

ok reinstalling the 9660

[BitJam]

It's been a long day for me. I will try to get something for you to try tomorrow. I've got it working here but I want to tie it up nicely.

In the meantime, another little experiment to try is to comment out the line:

Code: Select all

    set_dirty_bytes

around line 2836 in /usr/local/lib/cli-shell-utils/cli-shell-utils.bash in the set_dirty_bytes() routine. This will cause the progress bar to rush to the end well before the files are all copied but it might have a positive effect on the fragmentation.

[rs55]

Oh - I'll try that. Which reminds me - I had changed a few parameters in sysctl relating to dirty bytes because my flash drive was taking extraordinarily long to unmount. This is what I changed:
vm.dirty_bytes= 600000000 ( 600MB)
vm.dirty_background_bytes=300000000 ( 300 MB)

I wonder if that was also playing into this lum issue.

I any event - last night I ran a dist-upgrade ( it installed over 1000 packages !) and it borked the machine ( I had originally chosen the testing branch at initial install of antix) . So I reinstalled from my live-usb and changed the repositories to stretch -( to avoid this upgrade in the future).
I had to temporarily re-enable debian-testing repo to get fuseiso9660 installed again. Now, lum is not even completing - it gives an error at creation time- with fuseiso9660 installed. ( works great with fuseiso9660 uinstalled)

It seems this fuseiso is not even there in the stretch branch .? ( only in debian-testing ?)

It seems the best strategy is to reinstall from scratch - choose the stretch install. Then only temporarily change the repo to debian-testing to install a handful of packages that are not in stretch. Is this safe? Or will those testing repo - apps have dependencies unmet in future upgrades from stretch.

[fehlix]

It seems this fuseiso is not even there in the stretch branch .? ( only in debian-testing ?)

Both are in stretch/stable:

Code: Select all

apt policy fuseiso*
fuseiso:
  Installed: 20070708-3.2+b1
  Candidate: 20070708-3.2+b1
  Version table:
 *** 20070708-3.2+b1 500
        500 http://ftp.de.debian.org/debian stretch/main amd64 Packages
        100 /var/lib/dpkg/status
fuseiso9660:
  Installed: (none)
  Candidate: 0.3-1.1+b1
  Version table:
     0.3-1.1+b1 500
        500 http://ftp.de.debian.org/debian stretch/main amd64 Packages

You would need to fix the recent keyring issue for antix like this:

Code: Select all

sudo apt update

You'll get some keyring expire warnings.

Code: Select all

apt download --print-uris antix-archive-keyring
'http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/stretch/pool/main/a/antix-archive-keyring/antix-archive-keyring_20019.3.13_all.deb'
antix-archive-keyring_20019.3.13_all.deb 19074
SHA256:5aabdf90fb48643e168646e39999ab95ae4526ea43879a1e812b4d27283f537c

Youl copy the URL and fetch with wget the keyring package directly:

Code: Select all

wget http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/stretch/pool/main/a/antix-archive-keyring/antix-archive-keyring_20019.3.13_all.deb
--2019-03-22 17:39:50--  http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/stretch/pool/main/a/antix-archive-keyring/antix-archive-keyring_20019.3.13_all.deb
Resolving ftp.halifax.rwth-aachen.de (ftp.halifax.rwth-aachen.de)... 137.226.34.46, 2a00:8a60:e012:a00::21
Connecting to ftp.halifax.rwth-aachen.de (ftp.halifax.rwth-aachen.de)|137.226.34.46|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 19074 (19K) [application/octet-stream]
Saving to: ‘antix-archive-keyring_20019.3.13_all.deb’

You shall verfiy the SHA256SUM listed above with the output of this command:

Code: Select all

sha256sum antix-archive-keyring_20019.3.13_all.deb
5aabdf90fb48643e168646e39999ab95ae4526ea43879a1e812b4d27283f537c  antix-archive-keyring_20019.3.13_all.deb

You install the downloaded keyring:

Code: Select all

sudo apt install ./antix-archive-keyring_20019.3.13_all.deb

and refresh the apt-package list again:

Code: Select all

sudo apt update

HTH

[rs55]

It's been a long day for me. I will try to get something for you to try tomorrow. I've got it working here but I want to tie it up nicely.

In the meantime, another little experiment to try is to comment out the line:

Code: Select all

    set_dirty_bytes

around line 2836 in /usr/local/lib/cli-shell-utils/cli-shell-utils.bash in the set_dirty_bytes() routine. This will cause the progress bar to rush to the end well before the files are all copied but it might have a positive effect on the fragmentation.

OK - I did a clean install of antix, using stretch this time ! Checked that fuseiso was installed - it was. Then I installed a few apps. Then used lum to flash my usb flash device. Got that vmlinuz error on boot from usb.
Then I went back in and commented out the set-dirty-bytes line as you suggested. No luck - stil getting that same vmlinuz error on boot.
I will uninstall fuseiso for now - pending any further advice from you. Thanks.

[anticapitalista]

On antiX, add the word dev to the /etc/apt/sources.list.d/antix.list so it reads

deb http://repo.antixlinux.com/stretch stretch main nosystemd nonfree dev

Code: Select all

apt-get update && apt-get dist-upgrade

This will install a bugfix version of lum (gui) and force removal of fuseiso (if installed) and it will install fuseiso9660

This creates a bootable live usb on my antiX-17 box.

[anticapitalista]

Just to add - the problem app seems to be fuseiso.
With it installed, we get the vmlinuz error.
Without it (and also with or without fuseiso9660), both lum gui and lum cli work as they should.