can't find modprobe

[puelly]

Hi guys,

I recently install FC6 and been trying to setup a dwl-122 wireless adapter. I got the recommended drivers and compiled it but I can't seem to find the module utilities. there's no "modprobe" or "lsmod" on my system when i try running these commands. Can someone tell me what package I need to install to get these commands back.

Thanks.

PS. I do see "modutil" command

[leigh123@linux]

try

su -
modprobe

if that doesn't work try

su -
/sbin/modprobe

[Thetargos]

If you are trying to issue those commands with only "su" priviledges, that is not enough.

These commands live under /sbin/, which means only root (with its full PATH) can access them. If you're becoming root with "su" you'll need to issue "su" with "su -" to load root's PATH, alternatively you may call the commands with the full path (from just a "su") like

/sbin/modprobe
/sbin/lsmod


edit
Leigh beat me to it :D

[leigh123@linux]

I think modutils was replaced with module-init-tools


su -
yum install module-init-tools

[Thetargos]

Since those commands are needed by the system and to load modules from /etc/modprobe.conf, most likely it is already updated to module-init-tools ;)

[tomoir_III]

Are you sure you can't just try


whereis modprobe


find it? The whereis command is very useful. I used it to find modprobe, fdisk, and other things. BTW, does anyone know how to make those programs available simply through the comand-line, and not having to specify the directory?

[Thetargos]

BTW, does anyone know how to make those programs available simply through the comand-line, and not having to specify the directory?
Add the /sbin/ and /usr/sbin directories to your PATH... Be careful, as these commands are intended to be used for administrative tasks only and doing so, may expose your system, not to mention this imposes a security risk.

[tomoir_III]

But if I copy them to my path, then if I change directories, I won't have those programs readily available anymore..

[Thetargos]

I didn't say to copy them to your path, but rather to make them available under your PATH... I did that on purpose, as describing how to do that (IMO) poses a security risk. Remember that PATH is an environment variable ;)

[puelly]

thank you guys. the su - -> modprobe methond worked.

thanks for all your replys.

[tomoir_III]

I didn't say to copy them to your path, but rather to make them available under your PATH... I did that on purpose, as describing how to do that (IMO) poses a security risk. Remember that PATH is an environment variable ;)


Oh! Okay, sorry about that, I just didn't read it right. Thanks for the tip, too! :D
*scurries off to enjoy faster command-line abilities* :D