ubuntu probably uses /etc/init.d/ You might also be interested in checking out the autolaoding features in /etc/modules.autoload.d/ (or something similer). As for the script... You can setuid the file itself. This will allow it to run as root. I would suggest finding the source of the problem instead, though.
On Tue, Feb 10, 2009 at 9:20 PM, Neil Sikka <[email protected]> wrote: > theres are some local boot scripts that are run as root everytime the > system comes up. check /etc/rc.d/rc.local. thats at least how Fedora does > it. > > > On Tue, Feb 10, 2009 at 5:28 PM, Nick Cummings <[email protected]> wrote: > >> Doh! I also meant to add that there are some other tools available for >> messing with this stuff that you can install with apt-get. Check out >> the packages: >> >> rcconf >> sysv-rc-conf >> sysvconfig >> >> Some of those may not be applicable, I don't know. I've not tried any >> of them. >> >> Alan Bromborsky wrote: >> > I have an ASUS motherboard with a builtin realtek sound chip. I am >> > running Ubuntu 8.10 amd64 and there is a problem with the os finding >> > the sound chip. A work around is to enter 'sudo rmmod snd_hda_intel' >> > and 'sudo modprobe snd_hda_intet' after the system boots. I wish to >> > automate this with a script. Obviously the script would be: >> > >> > #!/bin/sh >> > rmmod snd_hda_intel >> > modprobe snd_hda_intet >> > >> > The question is how do I give the script permission to run 'rmmod' and >> > 'modprobe' and how do I have it executed after the system has booted, >> > but before the logon prompt and where should I put it? Thank you. >> > > > > -- > Neil Sikka >
