/bin/sh path search broken

[Larry Brigman]

On 10/17/06, Denis Vlasenko <vda.linux at googlemail.com> wrote:
> On Tuesday 17 October 2006 23:46, Larry Brigman wrote:
> > I have just upgrade a project I was working on from 1.1.2 to 1.2.1 and
> > things that just worked before have stopped.
> >
> > All of the processing of init scripts have stopped.
> > Login profile processing has stopped.
> >
> > The biggest sign that things have gone wrong is that
> > almost all commands won't work unless I am in the same directory as
> > busybox. I can also get things to work if I give an absolute path to
> > the program.
> > The only commands that I can get to work without error and without an
> > absolute path
> > are cd and export.
> >
> > Any ideas?
>
> Do you use "standalone shell" option? Does it work wothout?
> What "strace -ff -o logfile ash" shows in logfile when you try
> to run something?
I was running the standalone shell option but do I have to point my
scripts at ash?
I was able to get things running when I changed the first script that
was executed
prior to any tests to mount proc with /bin/mount -t proc /proc  from then on
everything seems to work again.  It has to be the full syntax as mount
doesn't seem able
to read /etc/fstab at this point either.

The only reason I found this problem so quick was that it had happened to me on
another project that I was using busybox on.  The shell script would
not find anything
until proc was mounted.