Hi everyone,

I have a weird problem. I just installed Red Hat 9 and noticed that bash commands are different from SuSE 8.2 ... For instance, in SuSE, I could use "insmod" and "modprobe" but didn't have "locate".

Quite the opposite with RH. I can "locate", but no "modprobe" or "insmod" or "lsmod".

What gives? I was always under the impression that bash was bash. Can different distro people "disallow" usage of commands like that? How can I get those commands to work in either dristribution?

Frankly, I like the terminal better in RH9 over SuSE, but overall, I like SuSE better than RH 9 (can't get a bunch of k programs to work right in RH9 like K3b and Rh seems to be really slooow).... Weird.

modprobe, locate, etc are programs. They have nothing to do with the shell. (i.e. you can execute them from csh, ksh, etc). Command line commands that are installed is, I guess, up to the distro choice. I would have thought all of the above were basic, but I guess not. Are you trying the above commands (modprobe), etc as a regular user. They are in /sbin which is only generally part of roots path. If so, in RH, as a regular user, /sbin/modprobe.

RO

That isn't bash or the shell, those from my knowledge or either not installed or not in your default path, etc.

Not sure if Suse is installed with locate by default but Redhat is, as along with the others that are only in root's default path.

locate/updatedb is present in suse. Don't know if you installed them.
They should recide here:
/usr/bin/locate (suse 7.2 + 8.1)

And trickybid and RolledOat are right: This has nothing to do with bash

hmmm.. ok thanks - still new to Linux and I was under the impression that those commands were in bash. lol don't get me to troubleshoot a linux system.. well I'm getting better but there's lots to learn. So I found modprobe (that's stored in /sbin). If I "cp" that to /usr/bin should it work then in a console/terminal? 'Cuz right now when I'm in terminal logged in as root I get "command not found" - so I'm presuming the command I type is looking for "modprobe" in /usr/bin - is that correct?

thanks
//Canon

I wouldn't recommend moving the command. The solution to this would be to add /sbin into root's path by either editing the global /etc/profile or in roots home directory if there is a .bashrc file.

You can have startup scripts or system services that call upon commands in /sbin and if you moved them, that can really mess up your system.

I would recommend adding it to your path or making a symlink to it.

Regards.