Sudo Problem
 

I uncommented
in the sudoers file and added my user to the "wheel" group and when i try
it says
What should i do to fix that?

How did you edit the file? The proper way is with the visudo command. Editing this file manually is not a good idea. If you don't like the editor which visudo uses, you can set the EDITOR environment variable. For example, if it uses vi, and you like nano, you might enter this command (as root):
You can fix the sudoers file permissions like this:

I logged in as root and edited it with kwrite.
I tried what you said,
and when i try to do a command (i.e)

Now sudo appears to be functioning correctly, but your modprobe command is failing. To verify sudo's success, sudo a command which should surely succeed:
If you see 0 after the hello world, sudo if fixed.

As for the psmouse module, my debian install has this built into the kernel - it is not a loadable module. You can check if this is the case with your installation with this command:
If you see "CONFIG_PSMOUSE=y", PSMOUSE is built into the kernel, not a module.

I tried that and it worked.

The "CONFIG_PSMOUSE=y" came up, when i did that.

I run "modprobe psmouse" all the time as root so that my touchpad works and it does work as root.

And it works as root? On this machine? In the same installation of debain? In my debian installation typing modprobe psmouse as root gives the same error message as you see when you run it with sudo. I can think of no reason why it would work as root, but not with sudo.

I'm running Slackware 11.

Try:Sudo works in the user's environment by default, so if /sbin isn't in your user's $PATH then sudo won't be able to find it even though it's executing the program with root priviledges. I've run into this problem before and this should hopefully be your fix.

That worked, now my question is how do i add /sbin to my $PATH?
I'm pretty new to slackware and still dont know what that is exactly.
And thanks alot for the help, both of you.

I beg your pardon. I think I must have been cross posting in my mind Too many threads, too few braincells. :)

Add following line to .bashrc
PATH = $PATH:/sbin

to edit .bashrc open terminal in home directory
>gedit .bashrc

It should be
Note that you should not have any relative paths in your path, the most commonly found one is "." - the current working directory. This is security risk - if some program creates a file which has the same name as a utility which is often run as root in the current directory, you don't want a risk to run it accidentally. Now you are doing admin stuff from this user, you should check your PATH is safe.

Amended (thanks matthewg42)

Add following line to .bashrc
PATH = $PATH:/sbin
export PATH

This is something I've seen many times - setting PATH first, then exporting it. Is there some advantage to doing this over having it all in one command, "export PATH=..."?

It says .bashrc doesnt exist.

Ah, one thing - are you using bash? do to find out.

Yes, it says im using bash.

You can just create the .bashrc file in your home directory then. You could just edit it, or this command will create it:

I did this and didnt get any complaints. However, it still does the samething.

After creating .bashrc, exit terminal and open a new terminal and try
If it doesn't work, do ctrl H in home directory and see if .bash_profile is there
if it is there, put the same code there & retry opening a new terminal

This has nothing to do in bashrc, it has to be in a profile file
~/.profile
~/.bash_profile
/etc/profile

man bash for explanation

You're creating it in your $HOME directory? It certainly should get used. From the bash manual page:
nx5000 is sort of right though, ~/.bash_profile is probably a better place to put it, although it you put it there, to see the change you'll have to log out of X (to GUI login screen) and back in, or if you use startx, log out of X, log out of console and then log in again. This is because the .bash_profile is only read on the initial login shell.

There wasnt a .bash_profile so i created one and added that code and now it works great. Thanks alot for all the help everyone, I really appreciate it.