Re: Dell Latitude E6230 Wireless Issues
I'm not an expert on scripts, but I doubt it is advisable to include sudo in them. I believe the idea is to require sudo to run the entire script instead of its component parts.
This is actually a question that I've had all along--if I have a "sudo" in a script and a user with less-than-admin privs goes to run it how does Linux handle that? Does it prompt for a PW? Does it depend on how the said file is chmod'ed?
/etc/rc.local is run in its entirety by the system with full (~sudo) priveleges. Therefor, you can put the commands in without sudo; for example:
I did NOT make it persistent and here's why: I note that I can only run the command as sudo. If I put "sudo [anything]" in rc.local how does the machine operate on that? I mean, doesn't a password have to be entered once the machine hits the "sudo" command in rc.local?
# By default this script does nothing.
modprobe -r wl
iw reg set US
Correct, although until you add something it is only executing 'exit 0'. I suppose one could, for reasons unknown to me, disable rc.local by chmodding to 600 so it was readable and writable by root only but not executable.
it appears to be set already to 755. So, although there is nothing in the file, it is ALREADY executing, correct?
Just for the fun of it, let's try rc.local and let me know the result. Off to lunch.
"Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.