Which is good and best. But you will now find that other common puppy utils written in bash/gtkdialog will not work correctly even if bash is on your system because gtkdialog uses system call in C which uses /bin/sh -c "command_string" which will not see functions exported by bash using export -f. Note that that problem will remain despite the script being written to itself use #!/bin/bash. Nevertheless I still think that /bin/sh should not be a link to /bin/bash other than as an ugly fudge to the gtkdialog issue - i.e. your link to busybox sh is correct IMO. The Puppy bash/gtkdialog programs need to be modified (partially re-written) to work correctly when /bin/sh does not point to /bin/bash is 'correct' (non-ugly-fudge) solution to that.mistfire wrote:Thanks @fred for your suggestion I made a symlink of sh to busybox-pup and the slitaz installer page in tazpanel works. Also puppy core apps still working.
Either that, and perhaps better, gtkdialog program itself could do with being modified to not use C system call (which always uses /bin/sh -c "command_string") but instead to use bash if required (maybe via fork/exec calls). Then it would be easy to modify existing apps to work (maybe a one line fix). But these matters are not specifically tazpup problems - they are problems for the bash/gtkdialog program authors.
wiak