i am having a bit of difficulty getting scripts to run in slack 9.0.

If i issue commands like 'sleep 1' and 'iwpriv wlan0 wlan_para channel=8' manually to get my wireless card working everything is ok.

i wrote a script to issue the commands for me.
it is as follows...

#! /bin/bash
#----------------------------------------------------
# Load Wireless LAN driver
#----------------------------------------------------

echo "Loading wireless LAN driver, please wait..."

insmod -f rtl8180_24x
sleep 1
iwpriv wlan0 wlan_para channel=8
sleep 1
iwpriv wlan0 wlan_para authtype=opensystem
sleep1
iwpriv wlan0 wlan_para ssid2scan=DONS_WIFI_ROUTER
sleep 1
iwpriv wlan0 wlan_para ssid=DONS_WIFI_ROUTER
sleep 1
#iwpriv wlan0 wlan_para preamble=long
#iwpriv wlan0 wlan_para networktype=infra
iwpriv wlan0 wlan_para basicrates=0xf,oprates=0xf
sleep 1
#
iwpriv wlan0 wlan_para encmode=off
sleep 1
iwpriv wlan0 wlan_para wepmode=off
sleep 1
#
ifconfig wlan0 192.168.0.12 netmask 255.255.255.0
sleep 1
#
iwpriv wlan0 enable

when i try to execute th script i get errors like

> wlanup
sh: /usr/bin/wlanup: /bin/bash
: bad interpreter: No such file or directory

i have tried using '#! /bin/sh' at the start of the script with no luck

i issued 'which bash' and got
/bin/bash

any help or hints would be appreciated
thanks,
Don =)

try adding the full paths to the commands you want to run. if you continue to have problems do 'ls -la /bin/bash' and see if it points to something else. i'd also check the modify time of bash. maybe something changed?

Try: #!/bin/sh without the space, bash never worked for me in scripts

thanks for the replies,


here is the result of 'ls -la /bin/bash'

-rwxr-xr-x 1 root bin 628664 Sep 23 2002 /bin/bash

does this mean that bash is not present?


i laso did 'ls -la /bin/sh' and got

lrwxrwxrwx 1 root root 4 Aug 26 03:12 /bin/sh -> bash




I also tried '#!/bin/sh' without the space in the script and there was no change when i run it...

: bad interpreter: No such file or directory

thanks again,
Don =)

If you notice on the wlanup output, you have the error output line broken into two segments.

first segment is: sh: /usr/bin/wlanup: /bin/bash
second segment is: : bad interpreter: No such file or directory

when it should not be. To test write a test script file with just the line:

#!/bin/basho

and see the output of it (when you do this, use a *NIX editor like vi, or emacs).

Comparing your output, with the basho output, you can see that yours breaks at /bin/bash, which leads to the conclusion that the line where you define #!/bin/bash has a \r character appended at the end of it.

Another way to see this, is to run a trace of your script. To do that, you simple run your script like so:

sh -x ./wlanup

and then check the trace output.

How to fix?

delete the entire first line (i.e. #!/bin/bash), and re-write it.

However, from the looks of it, whichever editor you used to write your script, may have appended more \r characters on every line, which means, you may have to re-type the script using a *nix type editor.

Make sure you do not use any funky windows, type editor, otherwise the problem may happen again.

Hope this helped.

GL

//edit: added comment

wow, cool.

thanks for the help, LNXman.

i rewrote the script with vi and it worked well

what do you mean by a '\r' character being appended to the line, and how can i tell if this is the case?

did you try what he suggested? making a script with

#!basho


(hint: /r is carriage return, ie line break)

yeah, that was only for testing purposes though

Most editors shows a "weird" character if the break character is not the one for Linux. Windows uses \r\n (#0D,#0A in hexadecimal or 13, 10 in decimal) as end characters for each line while linux uses only \n. As LNXman you may have used a editor which used Windows ending line characters when saving.
I don't know about other editors but mcedit (included in Slackware) shows ^M when it finds that "spare" character.

you could use tr tool to convert dos to unix text :

cat file_in_dos.txt | tr -d "\r" > file_in_unix.txt