I have always been able to "ifconfig" to config or bring my eth0 up or down. But this is very strange. I have always been able to issue the "ifconfig" command in every linux distro that I have ever tried. Never a prob. But if config gives me a "[root@localhost sbin]# ifconfig" "bash: ifconfig: command not found" ahhh.. I have tried everything that I can think of. I tried using up and eth0 up... nothing. I dont get it.. I am using fedora core linux and I used to be able to use ifconfig, and my eth0 is working and I am posting from my linux box right now... does anyone know what the problem could be... I have read the man page and googled it up and searched linux forums, I have not found someone with the same problem as me and got it fixed.. this really puzzles me.. any Ideas can help. I am stumped by this one.. if anyone needs to know anyinfo about my system. please let me know..
thanks good people.

Blackulatech1

:-)

dude is this a joke?

/sbin/ifconfig

it either doesnt exist or you need to add its location to your shells path.
You dont have to lie to kick it man.

sounds to me that ifconfig isnt in your path, type "whereis ifconfig" to find the binary, then you can execute it by its full path or by changing your path to include the directory its in.

I wasent lying. :-) Where do I edit the shell path? well. I'll google up an answer to my shell path question and then get back to you if I have to. Thanks for the help man.. :-)

blackulatech1

AutOPSY - politeness costs nothing.

If Blackulafedora1 says that the command has stopped working, then it has stopped working. Do not call someone a liar or otherwise insult them unnecessarily on LQ.

blackulafedora1 - open up a console and type in whereis ifconfig and see what that gives you. Post back with the answer.

try going into root, then try the command again

.profile .login .bashrc .bash_profile

should contain a PATH variable somewhere.

Your path variable will be in your home directory, locate by typing ls -a

.cshrc .something, one of those shell files.

[QUOTE]Originally posted by XavierP
[B]AutOPSY - politeness costs nothing.

If Blackulafedora1 says that the command has stopped working, then it has stopped working. Do not call someone a liar or otherwise insult them unnecessarily on LQ.


I didnt mean it like that, but I apologize anyhow.

Cool. The main drawback of typed conversations is that it is hard to get vocal inflections correct. Things that sound fine in normal conversation can look wrong when typed.

But moving on ......

ifconfig: /sbin/ifconfig /usr/share/man/man8/ifconfig.8.gz

This is what it gave me...

I googled for linux PATH bash, and found some stuff but not exactally what I was looking for.

lemme read these other replies about editing PATH and I'll get back in a min..

thanks for all your help.. :-)

blackulafedora1

oh yea... ls -a .bashrc returned this to me

.bashrc

humm

should or could I edit .bashrc

I need to look and see exactally what .bashrc is. I know that a file starting with "." is a hidden file some type of special file. Might not be hidden? heh. thanks

what I was getting from google. that I mentioned at the start of my last post was an export PATH=$PATH **** something??? heh.. :-) I dont think that it pertained to what I was looking for, not exactally at least.

I guess I'm really glad that I was able to use ifconfig a few weeks ago to get my eth0 setup. or else I might have real problems getting info. I just wonder how it got removed from my PATH or what happened to it.. heh

How are you getting to root?

As a user, your path does not include /sbin or /usr/sbin which means that you wouldn't have that command available to you unless you specified the absolute (full) path. Even then, as a user, you may not have permission to execute it.

There are several ways of becoming root. Simply using the "su" command can act differently in various distros. Normally, when you simply use su, I believe it gives you only /bin /sbin /usr/bin and /usr/sbin. (Correct me if I'm wrong, people )

Using the command "su -" actually logs root in, and rereads your /etc/profile and /etc/bashrc if they exist and sets up full system wide environment variables as well as any /root/.bashrc .login .bash_profile that are user specific (to root, in this case.)

If you log in with su - or actually log in at a login: prompt with root, you may find it's still in your path.

Using su by itself in Fedora Core may simply give your regular user root permissions, but not change the executable paths.



PS -- export PATH is exactly what you're looking for.

man bash
the bash howto at www.tldp.org

There's lots of info out there, get crackin'! (Or hackin, whichever may be your preference.)

--Shade

Thanks Shade.. :-) I was under the impression that "su" gave me full root permissions. I was using "su" not "su -" I really enjoy using linux, I come from a DOS and Windows backround, and linux is better for my thirsty mind. Now, I love linux. :-) Sometimes I just think I am doing the right thing ie. "su" vs. "su -" and I learn a little something and get a push in the right direction by someone that wants me to find the computing experience that is right for me, and was right for them. UNIX is the best. Solid. Thanks again Shade. I will post more, I'm sure of that. I have many questions about how linux works, and some of the answers will not be found by me. Sometimes I am blind to things.

blackulafedora1

Thank you all for your help.. :-)

Thanks Shade.. :-) :-) "su -" solved my root permissions problem (which was all it was to begin with). I got ifconfig kickin right away.. I guess I logged on to my system as root before.. heh heh... Peace man..

blackulafedora1

:-)