Reply To: (solved) unplugdrive.sh

#82102
Robin
Member

    Many thanks, @tamix, for your approach, scripting all these tasks, which I have described at several threads her in forum already. Obviously there was overlooked something by the package maintainers of antiX-goodies package, some important additional precautions necessary to run the bugfixed versions of unplugdrive from 0.82c and above properly. Also the most recent and completely bugfixed version 0.90 suitable for antiX 19 has not made its way into the antix 19.5 ISO, and also not in the antiX package repository at all. I can’t package unplugdrive 0.90 separately as an update, since this would conflict with the existing antiX-goodies package. So all we can do is waiting until antiX-goodies package maintainer once will notice there is a need to fix some settings. Until then your patch script will help people to create the needed system settings more easily themselves.

    Please refer to the instructions I have described when the first patched version in need of these precautions was launched, which was 0.82c: http://www.antixforum.com/forums/topic/cant-find-source-of-unplugdrive/page/2/#post-59484 They apply for all versions up to 0.90, the latest antiX 19 version. Possibly it is enough already to add the proposed alias along with the added line in sudoers file to make the taskline-icon work.

    As far I can see, your script does mostly exactly what I’ve described there. Great!

    In case you’d like to improve your script changing all the entries in the localised files also: A single-liner will be sufficient probably, you could try to add a command like:
    sed 's/unplugdrive/sudo unplugdrive/;s/sudo sudo/sudo/' /usr/share/antiX/localisation/*/icewm/toolbar*
    (and possibly another one, similar to this for jwm/tray)
    Once you have checked that everything in this line works as expected and reliable, just add the i option: sed -i … to let it change all the files directly instead of printing to command line only. If you want to create backup copies, use sed -i.bak … instead.

    In antiX 21 all these precautions are no longer needed, since we made unplugdrive 0.93 and above run properly in sudoed and unsudoed mode both, but please, don’t ever use 0.93 on antiX 19.x, it will fail unnoticed while telling everything is fine. To allow non-sudoed mode again, Xecure has created a special crafted version of the helper tool pumount (which I had dismissed before because the original version of pumount turned out to be unreliable, we can use it only in the Xecure patched version to have it reliable), while I modified the script logic to additionally allow non-sudoed mode and engage different preparation methods and commands depending whether unplugdrive is run with sudo or without sudo.

    P.S.:

    Now an admin might explain us what is going on with that strange worldfence for a quite standard post.

    There lives a thread somewhere here in board discussing exactly these problems. It’s a wordfence thing, nothing can be done to help it, so we have to live with it. E.g. I get many times the strange response from the server: “Are you really sure you want to do this?” instead of simply adding my answer to a thread. OK, just reload page and start over. Second attempt is successfully most time.

    Windows is like a submarine. Open a window and serious problems will start.