My apologies if i came across as being confrontations.
No, no, not at all, I would never think that of you! I simply used a bit or rhetoric to try to get my point across. I am sorry if I expressed myself in a disrespectful manner or anyway to make you think that.
You can suid set the executable as mentioned in one of the posts above but that has security implications as mentioned.
I followed as' advice above, but the thing is, I can't get it to work. It is running the command but not as root, thus the modprobe command is rejected.
You can set up "sudo" but it has some security implications and it is not very much liked here.
I fully understand. I am only going to use this as a stop-gap solution for now, as I am planning to re-install in the not to distant future, when the next (2011) image is out and I get some time on my hands.
Can you give context to what the problem is, what does this module do, why do you not want the kernel to block it at boot time but you want to unload it not before the desktop start but after.
I think it better that I keep this to the initial thread (see below).
I am struggling to see what you are trying to achieve with this, is it that the rt61pci module is causing conflict? or that you do not wish it to load at all?
I can't blame you, as I know what I am asking is probably not the best approach, in principle.
All, I see that I have got some further action on the initial wifi-thread, so - unless there are objections - I shall take muungwana's advice and continue any wifi related issues over on that thread (whilst marking this thread as solved, even though it technically isn't.).
In this thread I was simply trying to establish a method to run a command from KDE start-up, with root privileges, etc... whatever that command might be.
Cheers for all you advice and help, it really is much appreciated!
the issue CJ is experiencing is explained better here: http://www.pclinuxos.com/forum/index.php/topic,91513.0.html
I have posted there the latest info about new driver module.