Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Most likely your .bash_profile is corrupted. Since the other accounts are working, you may refer one of the working accounts profile.
No, that is not "most likely"; it is ONE possibility; please don't jump to conclusions without having any evidence to support them. It is much MORE likely that (since it WAS working), that the OP has manually entered a command to modify their path, or that another shell script has been run that overwrote the PATH variable. Also, you say ".bash_profile"...but don't mention the .profile, or .bashrc, ALL of which may be involved here. Since you have 'certifications', haven't you studied which files get read when a user logs in?
OP, have you recently edited your system profile? Your user profile? (ANY of them?). Logging out/back in is the best first step, since that will reset ALL your environment variables. If it still doesn't work, then you can work around it initally, just by typing
..which will put most things back in your path (like vi, etc.), and let you diagnose the problem more easily.
On my Centos 6.5, vim is /usr/bin/vim and vi is purely an alias to vim (ie no /usr/bin/ entry).
iirc, last time I yum installed 'vi', it really does install /usr/bin/vi ie NOT a symlink to vim.
Guess different distros do it differently.
QN: what happens on openSUSE if you specifically(!) install 'vi'; do you get a real one?
On my Centos 6.5, vim is /usr/bin/vim and vi is purely an alias to vim (ie no /usr/bin/ entry). iirc, last time I yum installed 'vi', it really does install /usr/bin/vi ie NOT a symlink to vim.
Guess different distros do it differently. QN: what happens on openSUSE if you specifically(!) install 'vi'; do you get a real one?
Don't know. If I query the vi package through yast, it tells me that vi is part of the vim-base package, which is already installed. I presume I could install it from source, but then I'd have to remove the symlink.