View Single Post
Old 07-21-2014, 04:50 PM   #1009
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by williamrochira View Post

exec /mnt/us/esys/bin/busybox ash
# # # # <- never reached by **prior** shell and not passed to new.
But echo $PATH returns:

/usr/local/bin:/bin:/usr/bin:/usr/sbin:/sbin:/usr/local/python/bin

So the export PATH=/mnt/us/esys/bin:/mnt/us/esys/usr/bin:$PATH didn't work...
The exec shell function does not pass the current command file and the current point of execution in it.

Ah, well, at least the Busybox version 1.17 (or whatever) ash that Amazon uses doesn't.

Hmm...
Maybe passing the new version of ash some argument(s) or option(s) might work.
As in:
exec /mnt/us/esys/bin/busybox ash -l
(-l, "ell" for "login shell" ? - - maybe)

- - - -

Thanks everyone for the help here.
knc1 is offline   Reply With Quote