Doug, that has crossed my mind too. Will try to look at it soon. On Fri, Jan 18, 2013 at 6:25 AM, Doug Burks <[email protected]> wrote: > This may be a stab in the dark, but I wonder if it could be related to > the fact that Ubuntu symlinks /bin/sh to /bin/dash by default? > > ls -alh /bin/sh > lrwxrwxrwx 1 root root 4 Jan 13 21:31 /bin/sh -> dash > > Doug > > On Thu, Jan 17, 2013 at 7:07 PM, Jon Schipp <[email protected]> wrote: >> Just pulled, this is the only one left. >> root@ubuntu:~/netsniff-ng/src# grep -R "/bin/sh" * >> astraceroute/build_geoip.sh:#!/bin/sh >> >> Daniel, same problem after pull. I'm pretty confident there's >> something funky going in with Ubuntu's shell startup files. I >> may have more time to investigate this weekend. >> >> On Thu, Jan 17, 2013 at 5:48 PM, Andrew Burgess <[email protected]> wrote: >>> >>> On 01/17/2013 06:14:07 AM, Daniel Borkmann wrote: >>> >>> >>> ./nacl_path.sh: 20: ./nacl_path.sh: source: not found >>> >>> Done! >>> >>> source ~/.bashrc >>> >>> /bin/sh: 1: source: not found >>> >>> make: *** [nacl] Error 127 >>> >>> i ran into something similar to this once and the problem turned out to >>> be an overly pedantic bash configuration on a little arm machine. if >>> the first line of the script that fails is "#!/bin/sh" you might try >>> changing it to "#!/bin/bash". even though the only shell on this >>> machine was bash, it had been configured to only allow bash extensions >>> if the script looked this way. on my fedora18 desktop, bash doesn't >>> care. >>> >>> there might also be an override for this, some flag or env var, so no >>> script changes would be necessary. >>> >>> hth >>> >>> -- >>> >>> >> >> -- >> >> > > > > -- > Doug Burks > http://securityonion.blogspot.com > > -- > >
--
