RE: [Devil-linux-develop] [0.6Beta1] New release, 4 new problems!

[Bruce S. <bw...@ar...>]

> >Out of curiosity, doesn't mount -auto "resolve" this problem (though I
> >haven't actually tried it myself)?  It is supposed to automatically
> >determine the correct type.
> 
> It should, but we still got some message.
> Bruce was running into problems with the "-t auto", I don't know what
> caused it.
> @Bruce: can you try the "-t auto"  again ?

Yes, I'll take a look again.  It is really strange.  It worked in the
first script, but failed in the second script.

> >>> o I See that we have (again) moved a key binary - echo (from
> >>> /bin/echo to /usr/bin/echo). 
>
> That's unfortunately not always possible. The coreutils package for
> example, replaced 3 other packages.
> There are so many files included, you just don't see anymore what's going
> on.

If you really want to use the full path for echo in scripts, try this
code which should work no matter what bin directory contains echo:

-------------------------------------
ECHO=$(whereis -b echo|cut -d' ' -f2)
# ...
$ECHO message to display
$ECHO another message
#
-------------------------------------

# OR #

-------------------------------------
if [ -x /bin/echo ]; then
	ECHO=/bin/echo
elif [ -x /usr/bin/echo ]; then
	ECHO=/usr/bin/echo
else
	echo cannot find echo
	exit 1
fi
# ...
$ECHO message to display
$ECHO another message
#
-------------------------------------

# OR #

-------------------------------------
for e in $(echo $PATH | sed 's/:/ /g')
do
	if [ -x "$e/echo" ]; then
		ECHO="$e/echo"
		break
	fi
done
# ...
$ECHO message to display
$ECHO another message
#
-------------------------------------


 - BS