> yours busybox2, or whatever. Then call "busybox2 ps", and you know > exactly what output you get.
I'm beginning to think that is the only usable solution. But hacking all my scripts to add busybox<space> will make them unreadable and take ages. And sometime I'd forget, or the next programmer would. I could try now and forever to identify when it matters and when it doesn't, but that's too much overhead. I think installing the new busybox version with my app, and hacking the path as seen by my app is the only acceptable route. I actually have a script set-standard-path.sh, which I have to invoke in the OpenVPN call-back scripts, as they start with no path set. So I'd just have to do that anywhere and everywhere at the start of all scripts. I use a common preamble included into all my scripts, so I can add it there. My isn't this fun :-) D > > - Lauri > > -- > _______________________________________________ > Surf the Web in a faster, safer and easier way: > Download Opera 9 at http://www.opera.com > > _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
