Well, your sudoers
file looks fairly standard, although I, personally, would never
use the NOPASSWD option for a command as potentially destructive as a command run with root privilege. (Entering the password gives to time to think before you act.)
I do notice that my sudoers
uses a slightly different format for the env_keep string:
Defaults env_keep = "COLORS DISPLAY HOSTNAME HISTSIZE INPUTRC KDEDIR LS_COLORS"
Defaults env_keep += "MAIL PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS LC_CTYPE"
Defaults env_keep += "LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES"
Defaults env_keep += "LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE"
Defaults env_keep += "LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET XAUTHORITY"
But I'm on Fedora 10, not the old, unsupported, obsolete, Fedora 8.
Note, in any case, that PATH
is not in the env_keep
since it is set by the default PATH and ~/.bashrc
of "root" when sudo
spawns a sub-shell in which the command executes.
So, what happens when you do a $ sudo /sbin/insmod atl2.ko
? If the command works, IIRC, you should get no output. (I think
is like modprobe
-- you only get output if there is a problem when the kernel module is inserted.)