On Mon, Jun 8, 2009 at 4:02 AM, Barney Barumba<[email protected]> wrote: > On Fri, 5 Jun 2009, Denys Vlasenko wrote: > >> Pretty sure I met this problem ages ago. >> >> The PATH is not exported. God alone knows why not, but it isn't. >> >> Add the line >> >> export PATH >> >> to /etc/profile and you might be in luck. >> > > Still not sure what was causing it, but the problem only occurred when > I executed a shell directly from the /init script. When I link /init to > /bin/busybox and launch a shell from /etc/inittab everything works fine. > > I was only using the /init shell for testing while building the system, > so for me this is not really a problem any more. I'll try exporting the > path though just to see if that works, and let you know.
My theory is with PATH unset, a default PATH is used by libc, and was finding run-parts. But if PATH is unset, ifup is setting empty PATH, and that is not treated the same as unset PATH by libc! I fixed it in git. -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
