X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
X-Envelope-From: <jonathan_lanier@naughtydog.com>
X-Envelope-To: <cygwin@cygwin.com>
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: CIFS symlinks on network share break Cygwin
Date: Tue, 5 Feb 2008 12:08:19 -0800
Message-ID: <E173C70E3D81F74188D2778B96C5CD0D011B4CEE@postal1-dog.naughtydog.com>
In-Reply-To: <20080205142712.GA840@calimero.vinschen.de>
References: <E173C70E3D81F74188D2778B96C5CD0D011B4A73@postal1-dog.naughtydog.com> <20080204150853.GD5866@calimero.vinschen.de> <E173C70E3D81F74188D2778B96C5CD0D011B4AE2@postal1-dog.naughtydog.com> <20080204205620.GA2720@ednor.casa.cgf.cx> <E173C70E3D81F74188D2778B96C5CD0D011B4B5C@postal1-dog.naughtydog.com> <E173C70E3D81F74188D2778B96C5CD0D011B4BD0@postal1-dog.naughtydog.com> <02fb01c86795$9aeb5080$2e08a8c0@CAM.ARTIMI.COM> <20080205133450.GB307@calimero.vinschen.de> <032c01c867fd$c573da30$2e08a8c0@CAM.ARTIMI.COM> <20080205142712.GA840@calimero.vinschen.de>
From: "Jonathan Lanier" <jonathan_lanier@naughtydog.com>
To: <cygwin@cygwin.com>
X-Spam-Score: -11.44 () ALL_TRUSTED,USER_IN_WHITELIST
X-BorderEnvelope-To: <cygwin@cygwin.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m15KBiGn015852

>>   Yep, and it doesn't help.  It's solely down to the secureshare
>> stuff not presenting through the standard NT api; it's only visible
>> by using the shell extension dll. 
>> 
>>   (... which makes me wonder, could we possibly leverage that to do
>> some useful work for us in these situations...?)
> 
> Shure, if the DLL has a usefull documented API and a
> programmer is caring (or paid) enough to actually do it.

Well, I for one would love to have something like that.  I wonder if
NetApp could be poked/prodded to participate.  Makes me think also,
NetApp isn't the only CIFS server that supports Unix features - as
Corinna pointed out to me earlier, apparently Samba does this as well (I
haven't used Samba in years so I assumed that it could not).  And that
gives me a totally crazy idea - wouldn't it be nice if there were a
standardized, open set of extensions to allow Windows applications to
access native symlinks, attributes, and permissions over remote network
shares?  If there were such a thing, Cygwin could totally use that to
have seamless Unix-style integration with networks, as could other
applications.  If such a thing doesn't exist, it should.  If the CIFS
protocol already supports it, it should be exposed in the Windows OS.
Who do I need to vote for to make this happen?  :)

Also, it's very disappointing to hear about how the symlinks are
implemented in Vista.  Admin access?  What were they thinking?  Seems
like if Microsoft wants to solve their problems, they should re-engineer
the entire OS on top of a *nix kernel and be done with it.  Kind of like
Mac OS did...  Oh well.

--
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/


