illusive IP command & troubleshooting network/USB connection on a CoreOS workstation
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.
illusive IP command & troubleshooting network/USB connection on a CoreOS workstation
I have a CoreOS (apparently synonymous with RedHat Enterprise) that has a Gnome GUI. I am also surrounded by LINUX books that aren't helpful because I am that new to this OS.
My two fundamental problems are (1) I can't see my NTFS formatted USB drive when I plug it in, and (2) I can't connect to the internet through my DSL LAN.
In order to help diagnose (2), I tried to query my IP address using the command "ip route". The error that I get is "bash: ip: command not found;" but I can see the man pages for "ip" when I query "man ip." Why is it that I can see the man page and still get a "command not found" error??? Do man pages describe more than what is installed? If not, am I not able to use "ip" because of my PATH defs? If so, where is "ip" located? I looked in /usr/bin and /usr/sbin without success.
I am stuck not being able to help myself resolve the primary problem of internet connectivity. The internet cable seems active: The green network connection light is on at both the computer and my router ends; yet, my web browser fails to bring up a website. Harumpf.
As for (1), I have 4xUSB ports in the front of my workstation. I have tested a couple of ports using a 1TB external and a 2GB jumpdrive, but I can't see either, which screams user error to me! I have a couple of drives mounted under "Computer", like "Memory stick drive" and "Compact flash drive", but none connect to the port with my external/jump drives. I have no idea where to go from here.
the command to find your local IP and interface information is ifconfig, not ip or route.
for ntfs support, you might need to enable it in CentOS by adding some packages/modules. I'm not sure what comes enabled by default, this page might help:
Some progress, I am connecting to the internet okay now! Perhaps due to re-boot? No idea.
In any case, /sbin/route and /sbin/ifconfig both work, but the individual commands do not.
[rmueller@localhost ~]$ ip route
bash: ip: command not found
[rmueller@localhost ~]$ ifconfig
bash: ifconfig: command not found
[rmueller@localhost ~]$ route
bash: route: command not found
This screams a path issue? Or does that just apply in windows? If so, what is the LINUX equiv.?
I'm afraid I still don't understand why man pages show up when "command not found."
It's a pathing problem - actually it's a Redhat problem because of the way the do their pathing (for non-root users). To find a command (so you can issue it specifically) use "which <command-name>".
The reason you get the man pages is they are installed in world viewable locations - actually a pretty good clue the command involved really is installed. Somewhere.
When I run into this I usually just "su -" (note the minus); this switches you to the super-user (root), and sets the pathing to root as well. "exit" to resume to the real world. You can adjust your user pathing, but I usually don't bother due to differing systems. Try "echo $PATH" on each (root and normal user) to see the difference.
syg00, "su -" worked like a charm! I hadn't realized the subtly of switching to root but keeping my user path by just using "su."
To add a PATH to my .bashrc, would I use
PATH = $PATH:/dir/of/choice
OR
export PATH = $PATH:/dir/of/choice
(or something else?)
I'm not sure what "export" has to offer, but I have seen this in a .bashrc file. I'm assuming that "$PATH:" indicates the current path with everything after the colon appending the path?
I'll start new post for further questions, as I'm starting to branch too far out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.