Folks,

Good morning, I am a newbie, Linux brought me a lot of challenges, which ones I am willing to try let me explain a
little bit in the past few days I was able to install my zydas adapter usb wireless I can make it work but after you restart it goes away with the ip address so next boot I got to restart it manually, I know there are a lot of of workarounds but I found one
that seems to be effective so you do not need to do a dhcp wlan0 every time you restart.

Script

1) Open up a terminal and go to /etc/init.d


Code:
cd /etc/init.d/2) make a new file called start-netorking as root


Code:
sudo vi start-networkingsubstitute vi with gedit or whatever if you wish

3) Make it a script that just starts your interfaces. Use this as an example:


Code:
#!/bin/bash

ifup wlan0
ifup eth1I have 2 interfaces called eth0 and eth1. You will probably only need the eth0 part if you only have 1 NIC.

4) change mode of script

Code:
sudo chmod 755 start-networking

5) Code:
cd ../rc2.d/7) make a link to your script in this dir


Code:
sudo ln -s ../init.d/start-networking S90start-networking


Now the ONLY problem is that when reboots it will ask you for
sudo for that script, remember I am a NEWBIE, so if asks for sudo will ask for a password and if you don't type it will skip the script "sudo ln -s ../init.d/start-networking S90start-networking" , how do I do in order to execute this script without being sudo? I know it might be risky but I found it's an efective workaround...how do I change permissions for this script and all
the scripts behind this in order to make ANY user able to run it at the boot time?


Thanks!

You need to specify which distro and version you're using.

For RedHat, Fedora Coreand or Debian you would NOT put sudo into an init script because init scripts run as root anyway.

Hi,

Thanks for the response, I am using Ubuntu 6.10, in that case Debian rules should apply...
wondering why is not working, say you have any ideas?
I heard I can add it at the rc.local which is the set of scripts from the boot proces..but at this point no idea where to start

thanks.

The way init scripts work (Debian and RedHat/Fedora):

You create the script in /etc/init.d.

You create a symbolic link in /etc/rc?.d back to the file in /etc/init.d. The ? is the run level in which you want the script to run. (That is to say there are multiple directories, rc1.d, rc2.d, rcS.d etc...)

The file in /etc/init.d should have a base name (e.g. start-networking) whereas the files in /etc/rc?.d would have a start name (e.g. S90start-networking) and/or a stop (kill) name (e.g. K10start-networking).

So creating a file like /etc/init.d/S90start-networking wouldn't work because there is no link in the run level directories.

The syntax of init scripts like this requires you to at least provide a start and a stop section. You should look at what you currently have in /etc/init.d then find the relevant links in /etc/rc?.d directories to get a good idea of how to set this up.

The main point in my earlier email was init scripts run as root so should not need you to include a "sudo" in them.