Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ifconfig doesn't work. Neither do many other commands. When I go into /sbin and type ./ifconfig then it does. However there are only very few items there even. Any ideas?
I've looked at Path variables etc and cant make a great load of sense out of them. Whatever i install doesnt work either.
modprobe is one whihc doesnt work either unless using the ./modprobe thing.
Unlike windows, bash only searchs the environment path for a command.
echo $PATH will display your path environment. /sbin isn't usually in a regular users path.
BTW ./ is a shortcut for current working directory.
You can always use the full path i.e. /sbin/ifconfig
If you used the su command then use su - instead. The - says to use root's path instead of the path of the regular user.
Cheers for that, doesnt explain why all teh commands that are supsoed to be there are not but it gives me a further insight into what on earth is happening.
As a guess im gonna have to lookup all the commands that dont work and install them right?
Some of the commands require that you are root or they will not run. The ones that require this are in sbin, however some of them that are in sbin do not require root privilages to run, such as ifconfig.
This fix? Try running them as root (su). Unless you are already running them as root, and I misread your question.
Appologies yep your right! Arggg i hate being a newbie but hey in time i won't be (lets hope). I have now progressed onto the next stage of the installing ndiswrapper. At the moment it seems the link from the kernel to the kernel source is wrong and ive tried all sorts!!! There is another post about it.
Thanks for teh help though..... (i was stuck on that one for too long!)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.