This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: vi won't execute - symlink semantics changed?
- From: luke dot kendall at cisra dot canon dot com dot au
- To: cygwin at cygwin dot com
- Date: Fri, 15 Nov 2002 17:37:16 +1100 (EST)
- Subject: Re: vi won't execute - symlink semantics changed?
On 8 Nov, Corinna Vinschen wrote:
> On Fri, Nov 08, 2002 at 04:16:41PM +1100, luke.kendall@cisra.canon.com.au wrote:
> > I updated my Cygwin installation to the latest version, yesterday.
> > (That included the fresh bash-2.05-7 and binutils.)
> >
> > Since then, I can't run vi except by either specifying the full path
> > /usr/bin/vi or using vim. In other words, the symlink from vi ->
> > vim.exe does not get used.
> >
> > I also notice that if you do a test -x /usr/bin/vi that now fails; I
> > believe it used to succeed.
>
> I checked both with 1.3.15-2 and can't reproduce it.
Ah, I've found a partial answer. Although I installed Cygwin from my
account (luke), some files appear to be owned by the sysadmin person who
initially set the PC up (robs). He may also have done an install of the
default Cygwin stuff.
$ ls -l /usr/bin/vi*
lrwxrwxrwx 1 robs Domain U 18 Jul 24 11:15 /usr/bin/vi -> vim.exe
lrwxrwxrwx 1 robs Domain U 18 Jul 24 11:15 /usr/bin/view -> vim.exe
-rwx------ 1 robs Domain U 858112 Apr 3 2002 /usr/bin/vim.exe
lrwxrwxrwx 1 robs Domain U 18 Jul 24 11:15 /usr/bin/vimdiff -> vim.exe
-rwx------ 1 robs Domain U 1068 Apr 3 2002 /usr/bin/vimtutor
lrwxrwxrwx 1 luke Domain U 17 Oct 17 17:01 /usr/bin/virmf.exe -> mf.exe
lrwxrwxrwx 1 luke Domain U 20 Oct 17 17:01 /usr/bin/virmpost.exe -> mpost.exe
lrwxrwxrwx 1 luke Domain U 18 Oct 17 17:01 /usr/bin/virtex.exe -> tex.exe
$ test -x /usr/bin/vi && echo yes
So, why would these files be 700 mode?
luke
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/