[opensuse] Please show your output from "ls -l /bin/vim"
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? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/06/2018 02: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?
It's executable here on 42.3. $ ll /usr/bin/vim /bin/vim /usr/bin/vi /bin/vi lrwxrwxrwx 1 root root 3 Jul 26 2017 /bin/vi -> vim -rwxr-xr-x 1 root root 2363952 Jul 2 2017 /bin/vim lrwxrwxrwx 1 root root 8 Jul 26 2017 /usr/bin/vi -> /bin/vim lrwxrwxrwx 1 root root 8 Jul 26 2017 /usr/bin/vim -> /bin/vim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Fri, 2018-04-06 at 14:50 -0400, 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?
Executable here on TW 20180403, but with a deeper rabbit hole... cmyers@caradhras:~> whereis -b vi vim vi: /usr/bin/vi /bin/vi vim: /usr/bin/vim /bin/vim /usr/share/vim cmyers@caradhras:~> ll /usr/bin/vi /usr/bin/vim /bin/vi /bin/vim lrwxrwxrwx 1 root root 12 Mar 29 06:31 /bin/vi -> /usr/bin/vim lrwxrwxrwx 1 root root 12 Mar 29 06:31 /bin/vim -> /usr/bin/vim lrwxrwxrwx 1 root root 3 Mar 29 06:31 /usr/bin/vi -> vim lrwxrwxrwx 1 root root 21 Mar 29 06:31 /usr/bin/vim -> /etc/alternatives/vim cmyers@caradhras:~> ll /etc/alternatives/vim lrwxrwxrwx 1 root root 18 Jul 26 2017 /etc/alternatives/vim -> /usr/bin/vim-nox11 cmyers@caradhras:~> ll /usr/bin/vim-nox11 - -rwxr-xr-x 1 root root 2988520 Mar 29 06:31 /usr/bin/vim-nox11 -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE7GM/Dul8WSWn72odQ1nEo4DFCIUFAlrHxEYACgkQQ1nEo4DF CIW6Uwf/VPAdD0WbZa3ABKeaIs30TRCWnExF3P6uPtIcAeo+3LdLX0b22BHmyvXX mtEzJYWV3/QH9c4vWUAJbXTfs1j/IF5iQ0tgAqi7juoBRwCdduthxP+s0Zi/ASzC Q1GPmPRaguwMZs+j15EPGPUxkbN/+vtQ5LaweciWmgSvLCwmKX6KDdbaIgozuVma kIPPKagyZ7QbvySMG9HDjvsYoxcE5ge2HCffv1q118qQns7jEIwwMJOEoonft8dd TjrtC3Fgf+jVCaujYVDUoDvye7u/5OHhGeHpfVuOky5Ga5uP6C/LBiYZOZOv+pV4 4CzkiGZzPBNFyn8AkFEf6FqytP/FeA== =dohl -----END PGP SIGNATURE-----
On 04/06/2018 03:02 PM, Christopher Myers wrote:
On Fri, 2018-04-06 at 14:50 -0400, 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?
Executable here on TW 20180403, but with a deeper rabbit hole...
cmyers@caradhras:~> whereis -b vi vim vi: /usr/bin/vi /bin/vi vim: /usr/bin/vim /bin/vim /usr/share/vim
cmyers@caradhras:~> ll /usr/bin/vi /usr/bin/vim /bin/vi /bin/vim lrwxrwxrwx 1 root root 12 Mar 29 06:31 /bin/vi -> /usr/bin/vim lrwxrwxrwx 1 root root 12 Mar 29 06:31 /bin/vim -> /usr/bin/vim lrwxrwxrwx 1 root root 3 Mar 29 06:31 /usr/bin/vi -> vim lrwxrwxrwx 1 root root 21 Mar 29 06:31 /usr/bin/vim -> /etc/alternatives/vim
cmyers@caradhras:~> ll /etc/alternatives/vim lrwxrwxrwx 1 root root 18 Jul 26 2017 /etc/alternatives/vim -> /usr/bin/vim-nox11
cmyers@caradhras:~> ll /usr/bin/vim-nox11 -rwxr-xr-x 1 root root 2988520 Mar 29 06:31 /usr/bin/vim-nox11 N�����r��y隊Z)z{.�ﮞ˛���m�)z{.��+�: �{Zr�az�'z��j)h���Ǿ� ޮ�^�ˬz�
Christopher, is your machine running at runlevel 3 only? Just curious. Thanks for all the responses. I should have said I'm running 42.3. I just changed the perms to 755, but this is turning out to be the most whacked-out Linux install I've ever seen, and that includes SLS from 1993. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-04-07 04:28, ken wrote:
Thanks for all the responses. I should have said I'm running 42.3.
I just changed the perms to 755, but this is turning out to be the most whacked-out Linux install I've ever seen, and that includes SLS from 1993.
And did vi/vim work previously? What could set it to not be executable? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 04/07/2018 07:36 AM, Carlos E. R. wrote:
On 2018-04-07 04:28, ken wrote:
Thanks for all the responses. I should have said I'm running 42.3.
I just changed the perms to 755, but this is turning out to be the most whacked-out Linux install I've ever seen, and that includes SLS from 1993. And did vi/vim work previously?
No, it never worked, always yielded an error message.
What could set it to not be executable?
I have absolutely no idea. Though I installed this 42.3 about a week ago, I never used vi until just very recently, so just discovered the problem. So the wrong permissions might well have been in place by the install. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-04-09 00:52, ken wrote:
On 04/07/2018 07:36 AM, Carlos E. R. wrote:
On 2018-04-07 04:28, ken wrote:
Thanks for all the responses. I should have said I'm running 42.3.
I just changed the perms to 755, but this is turning out to be the most whacked-out Linux install I've ever seen, and that includes SLS from 1993. And did vi/vim work previously?
No, it never worked, always yielded an error message.
What could set it to not be executable?
I have absolutely no idea. Though I installed this 42.3 about a week ago, I never used vi until just very recently, so just discovered the problem. So the wrong permissions might well have been in place by the install.
Where there other problems during the install? -- Cheers/Saludos Carlos E. R. (testing openSUSE Leap 15.0, at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/08/2018 07:50 PM, Carlos E. R. wrote:
On 2018-04-09 00:52, ken wrote:
On 04/07/2018 07:36 AM, Carlos E. R. wrote:
On 2018-04-07 04:28, ken wrote:
Thanks for all the responses. I should have said I'm running 42.3.
I just changed the perms to 755, but this is turning out to be the most whacked-out Linux install I've ever seen, and that includes SLS from 1993. And did vi/vim work previously?
No, it never worked, always yielded an error message.
What could set it to not be executable?
I have absolutely no idea. Though I installed this 42.3 about a week ago, I never used vi until just very recently, so just discovered the problem. So the wrong permissions might well have been in place by the install.
Where there other problems during the install?
Lots of them, some of which I've mentioned on this list already. Booting (UEFI) not correct... sort of like Carlos's ;problem No up/down arrows for scrolling in any apps. Permissions for vi wrongly set. No working audio volume controls. Keyboard configuration initially correct, but inexplicably changed to something very wrong. I'm sure that forgetting one or two others. I'm thinking it would be better (faster, easier) to re-install the whole system and hope for better luck next time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-04-09 19:15, ken wrote:
On 04/08/2018 07:50 PM, Carlos E. R. wrote:
Where there other problems during the install?
Lots of them, some of which I've mentioned on this list already.
Booting (UEFI) not correct... sort of like Carlos's ;problem No up/down arrows for scrolling in any apps. Permissions for vi wrongly set. No working audio volume controls. Keyboard configuration initially correct, but inexplicably changed to something very wrong.
I'm sure that forgetting one or two others. I'm thinking it would be better (faster, easier) to re-install the whole system and hope for better luck next time.
I would suspect that your installation media is bad. If you have only the oss, non-oss, and update repos, you could try a "zypper dup". Or install again, from different media and download image. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Le 06/04/2018 à 20:50, ken a écrit :
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?
ll /usr/bin/vim /bin/vim /usr/bin/vi /bin/vi lrwxrwxrwx 1 root root 3 11 sept. 2017 /bin/vi -> vim -rwxr-xr-x 1 root root 2363952 2 juil. 2017 /bin/vim
mine is ok jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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 C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On Sun, 8 Apr 2018 18:57:34 -0400 ken <gebser@mousecar.com> wrote:
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.
Yes, that's correct. The executable is vim, but if you call it using the name 'vi' then it changes its behaviour a bit. See it's documentation for details.
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.
And that's not correct. Something in your installation is broken. People like Carlos are trying to help you find out exactly what. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/04/18 07:44 AM, Dave Howorth wrote:
On Sun, 8 Apr 2018 18:57:34 -0400 ken <gebser@mousecar.com> wrote:
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.
Yes, that's correct. The executable is vim, but if you call it using the name 'vi' then it changes its behaviour a bit. See it's documentation for details.
And various others: # ls -li /usr/bin/*vim /usr/bin/vi 2240457 lrwxrwxrwx 1 root root 4 Mar 17 12:35 /usr/bin/egvim -> gvim 2233645 lrwxrwxrwx 1 root root 4 Mar 17 12:35 /usr/bin/evim -> gvim 2236789 -rwxr-xr-x 1 root root 2669008 Jul 2 2017 /usr/bin/gvim 2230148 -rwxr-xr-x 1 root root 2597280 Jan 17 10:22 /usr/bin/nvim 2236792 lrwxrwxrwx 1 root root 4 Mar 17 12:35 /usr/bin/rgvim -> gvim 2234333 lrwxrwxrwx 1 root root 3 Mar 17 11:32 /usr/bin/rvim -> vim 2228964 lrwxrwxrwx 1 root root 8 Mar 17 11:32 /usr/bin/vi -> /bin/vim 2234302 lrwxrwxrwx 1 root root 8 Mar 17 11:32 /usr/bin/vim -> /bin/vim ? nvim ? Information for package neovim: ------------------------------- Repository : openSUSE-Leap-42.3-Update Name : neovim Version : 0.2.0-3.1 Arch : x86_64 Vendor : openSUSE Installed Size : 14.3 MiB Installed : Yes Status : up-to-date Source package : neovim-0.2.0-3.1.src Summary : Vim-fork focused on extensibility and agility Description : Neovim is a refactor - and sometimes redactor - in the tradition of Vim, which itself derives from Stevie. It is not a rewrite, but a continuation and extension of Vim. Many rewrites, clones, emulators and imitators exist; some are very clever, but none are Vim. Neovim strives to be a superset of Vim, notwithstanding some intentionally removed misfeatures; excepting those few and carefully-considered excisions, Neovim is Vim. It is built for users who want the good parts of Vim, without compromise, and more.
And that's not correct. Something in your installation is broken. People like Carlos are trying to help you find out exactly what.
I *expect* my system to be broken when I start arbitrarily mucking around with it, but NOT like that and not something as basic as VI or, ${DEITY} forbid, BASH. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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?
Looks good: (on 42.3) test422:~ # ll /usr/bin/vim /bin/vim /usr/bin/vi /bin/vi lrwxrwxrwx 1 root root 3 Jan 25 19:06 /bin/vi -> vim -rwxr-xr-x 1 root root 2363952 Jul 2 2017 /bin/vim lrwxrwxrwx 1 root root 8 Jan 25 19:06 /usr/bin/vi -> /bin/vim lrwxrwxrwx 1 root root 8 Jan 25 19:06 /usr/bin/vim -> /bin/vim On Leap 15: jensen:~ # ll /usr/bin/vi /bin/vi /usr/bin/vim /bin/vim lrwxrwxrwx 1 root root 12 Mar 24 07:33 /bin/vi -> /usr/bin/vim lrwxrwxrwx 1 root root 12 Mar 24 07:33 /bin/vim -> /usr/bin/vim lrwxrwxrwx 1 root root 3 Mar 24 07:33 /usr/bin/vi -> vim lrwxrwxrwx 1 root root 21 Mar 24 07:33 /usr/bin/vim -> /etc/alternatives/vim jensen:~ # l /etc/alternatives/vim lrwxrwxrwx 1 root root 18 Mar 28 19:33 /etc/alternatives/vim -> /usr/bin/vim-nox11* -- Per Jessen, Zürich (14.3°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Anton Aylward -
Carlos E. R. -
Christopher Myers -
Dave Howorth -
David C. Rankin -
James Knott -
jdd＠dodin.org -
ken -
Per Jessen