On 04/06/2018 11:41 PM, David C. Rankin wrote:
On 04/06/2018 01:50 PM, ken wrote:
What boffoness is this!?
$ whereis -b vi vim vi: /usr/bin/vi /bin/vi vim: /usr/bin/vim /bin/vim /usr/share/vim
$ ll /usr/bin/vim /bin/vim /usr/bin/vi /bin/vi lrwxrwxrwx 1 root root 3 Mar 24 02:10 /bin/vi -> vim -rw-r--r-- 1 root root 2363952 Jul 2 2017 /bin/vim lrwxrwxrwx 1 root root 8 Mar 24 02:10 /usr/bin/vi -> /bin/vim lrwxrwxrwx 1 root root 8 Mar 24 02:10 /usr/bin/vim -> /bin/vim
In short, everything is a symlink to /bin/vim, but /bin/vim doesn't have execute permissions. Why/How can this be? Does anyone else have this utter strangeness?
Of course,
Unless you have used vi before -- you really mean vim when you say vi. So all are symlinked to the vim executable. If suse follows the rest of the world, all will end up under /usr at some point in the future and /bin and /sbin will simply be symlinks for historical purposes pointing to /usr/bin and /usr/sbin. Symlinks provide the flexibility at either the application level (like vim) or for entire system directories to be managed in a transparent manner without bothering the user. I suspect the /usr/bin links are in manner forward looking links to accommodate the move when, and if, it occurs.
The links within /bin itself are to save you from the inadvertent launching vi when you meant vim (prevent you from banging on the keyboard in frustration). If you are used to the link pointing to vim, you are in for a real surprise when you sit down at a distro that has both vi and vim installed...
David, you seem to have missed the thrust of my post. First, all the symlinks for both vi and vim point to the same executable. Secondly, that executable had permissions with the executable bits off... meaning that it wouldn't run. I've never seen that before after an install of any linux or unix system. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org