X-Spam-Check-By:	sourceware.org
Date:	Fri, 21 Apr 2006 19:15:42 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin and Interix interoperability?
Message-ID:	<20060421171542.GA25876@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4447BE05 DOT 6070103 AT tibco DOT com> <20060420170449 DOT GA24155 AT trixie DOT casa DOT cgf DOT cx> <20060420204058 DOT GA7685 AT calimero DOT vinschen DOT de> <44480053 DOT 609 AT tibco DOT com> <20060421093909 DOT GA12661 AT calimero DOT vinschen DOT de> <44490A6A DOT 3090504 AT tibco DOT com>
Mime-Version:	1.0
In-Reply-To:	<44490A6A.3090504@tibco.com>
User-Agent:	Mutt/1.4.2i
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Apr 21 11:38, mwoehlke wrote:
> Corinna Vinschen wrote:
> >They are not understood by Windows, and that's documented.  They are
> >just translated into the file type they are pointing to by the NFS
> >client and then presented as file or directory to Windows clients.
> 
> Sorry for the confusion; that's what I meant. The point is, you can
> request an open on a symlink (including symlinks in the *middle* of a
> path) and it will transparently "work". That isn't the case for .lnk
> files (and unfortunately, neither way works on non-NFS volumes yet).

I don't get it.  We're using .lnk symlinks for quite some time and open
works transparently with them.  As for *real* symlink support, we're
waiting patiently for OS support (Vista/Longhorn).

> IMO making them look like hard links is better than making them obvious
> but less usable.

Still, there's no API to create symlinks since Win32 doesn't understand
symlinks.  Either create them with Interix or on the Unix machine which
provides the NFS shares.  For Cygwin they are just files or directories,
as for any other Win32 application.

> At any rate, Cygwin *isn't* the Windows API... Why shouldn't Cygwin be
> allowed to get it right for those API's that ask for POSIX-style
> permissions?

Cygwin is running in the Windows subsystem, Interix isn't.  Cygwin can
only use functions in the Win32 API, or in the native NT API as far as
the call is allowed from user space.

> How are you getting this information? Explorer won't give you "normal"
> security attributes on an NFS volume... is there a command-line tool I
> don't know about, or did you write your own?

I tweaked my local Cygwin, but you can just simply write your own
application using the Win32 API.  The required functions are all
documented.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -