11-03-2021, 08:20 PM
(This post was last modified: 11-03-2021, 08:22 PM by TheOldPresbyope.
Edit Reason: wordsmithing
)
Let's take it slow then.
In user pi's home directory
where the wget command is one line but in my browser it's displayed as two.
If you get the same 'malformed response' message when you invoke the new ashuffle, then we're done here.
If the new ashuffle runs successfully, however, then you can try the following.
We're using 'sudo' for many of these commands because you're working in a system directory.
In this example, I went an extra step, renaming the old binary and creating a symlink "ashuffle" so the new binary would be invoked instead. If for some reason you want to revert to the old binary, just repeat the symlink creation step but pointing to ashuffle.dist instead of ashuffle.3123
I'll be interested to hear if the new binary makes any difference. Again, we haven't done anything here that might be needed to deal with the new command option. Gotta leave some work for the next guy
Regards,
Ken
In user pi's home directory
Code:
# get the new binary
wget https://github.com/joshkunz/ashuffle/releases/download/v3.12.3/ashuffle.armv6h-linux-gnueabihf -O ashuffle.3123
#mark it as executable
chmod +x ashuffle.3123
# invoke it
./ashuffle.3123
If you get the same 'malformed response' message when you invoke the new ashuffle, then we're done here.
If the new ashuffle runs successfully, however, then you can try the following.
Code:
# move the new binary to the appropriate system directory
sudo mv ashuffle.3123 /usr/local/bin/ashuffle.3123
# change to the directory to make life easier
cd /usr/local/bin
# rename the existing binary
sudo mv ashuffle ashuffle.dist
# create a symlink to the new binary
sudo ln -s ashuffle.3123 ashuffle
# change back to the home directory
cd
We're using 'sudo' for many of these commands because you're working in a system directory.
In this example, I went an extra step, renaming the old binary and creating a symlink "ashuffle" so the new binary would be invoked instead. If for some reason you want to revert to the old binary, just repeat the symlink creation step but pointing to ashuffle.dist instead of ashuffle.3123
I'll be interested to hear if the new binary makes any difference. Again, we haven't done anything here that might be needed to deal with the new command option. Gotta leave some work for the next guy
Regards,
Ken