Accessing problem

repo · 02-23-2009, 03:28 AM

what is the output from

Quote:

whereis insmod

shariefbe · 02-23-2009, 06:50 AM

The output of whereis insmod is

[sharief@localhost ~]$ whereis insmod
insmod: /sbin/insmod.static /sbin/insmod /usr/share/man/man8/insmod.8.gz
[sharief@localhost ~]$

repo · 02-23-2009, 07:10 AM

seems to me the PATH is screwed up when you use sudo
you could try to create another user and see if the problem persist with this user.

You could try to remove and reinstall sudo

also make sure
/etc/sudoers contains

Code:

root    ALL=(ALL) ALL

Another option is to use su
open a terminal and type

Code:

su

give the root password

no you are in a rootshell.

I never use sudo

PTrenholme · 02-23-2009, 10:43 AM

Or just use sudo /sbin/insmod ... or (to avoid PATH problems) sudo /sbin/insmod.static .... Notice that those locations were listed in the output of the whereis command.

You might also consider using modprobe instead of insmod to load a kernel module. See man modprobe for more information. If you're following a instructions you found in a book, the suggestion to use insmod implies (to me) that the book may be somewhat outdated.

shariefbe · 02-23-2009, 10:43 PM

I attached my sudoers file with this reply..please refer it and say what to do....

repo · 02-24-2009, 06:02 AM

Backup your sudoers file
mv /etc/sudoers /etc/sudoers.backup
Create a new sudoers file with the following content

Quote:

# /etc/sudoers
#
# This file MUST be edited with the 'visudo' command as root.
#
# See the man page for details on how to write a sudoers file.
#
Defaults env_reset
# Host alias specification
# User alias specification
# Cmnd alias specification
# User privilege specification
root ALL=(ALL) ALL
# Uncomment to allow members of group sudo to not need a password
# (Note that later entries override this, so you might need to move
# it further down)
# %sudo ALL=NOPASSWD: ALL

recreate the sudo user

PTrenholme · 02-24-2009, 04:39 PM

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:

Code:

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 that insmod is like modprobe -- you only get output if there is a problem when the kernel module is inserted.)