On Wed, Jun 15, 2016 at 05:54:47PM -0500, [email protected] wrote: > > #!/bin/sh on the first line of any bash script produces "No such file or > directory." /bin/sh is linked to bash. #!/bin/bash produces the same > result. > > All scripts work and I've always ignored the message but I'm curious of what > I have wrong.
That sounds weird - I would expect the scripts to fail to run if you get that error message. Certainly my own scripts do not report that. Does ldd /bin/bash show any missing files ? Is /tools still on your PATH (but hopefully, deleted in a finished system - or else moved out of the way) ? ĸen -- I had to walk fifteen miles to school, barefoot in the snow. Uphill both ways. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
