delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
DomainKey-Signature: | a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:date:from:reply-to:message-id:to:subject | |
:in-reply-to:references:mime-version:content-type | |
:content-transfer-encoding; q=dns; s=default; b=hCwTRxoR6KQ2/yXC | |
YhW5SCiY4eIZErare04PAvGyL33JwxL1mMBVebbpHG16GTnn1sQ3+GYSOEyMsihP | |
adYDG+WUz22QwGLdBs16dk9UxxqW3aYQjy0HxNhS8mlj2YElsxsJT/zPwbVx3TNN | |
7POeWzW6oM+Porw09cDOvuUvRio= | |
DKIM-Signature: | v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:date:from:reply-to:message-id:to:subject | |
:in-reply-to:references:mime-version:content-type | |
:content-transfer-encoding; s=default; bh=PZshzvC4fuhF90sm3x0Nzr | |
iNJbk=; b=KzKfdOOwFXX6tYce6rEJMZ36OClqy64O3tNVDaYNCPVmQ5V/+ULliJ | |
rw50+EO64WizWAbIzNBfS9ehun7uo1bBnf/Vuo4Ybd4aQ0d7ZDIwl5njSD5ko+ku | |
/f/tbsLDVAJhUyINiWn3qvRTTkHIfzSuyK/JNo4FnyfGqerQ2Ins8= | |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.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 |
Authentication-Results: | sourceware.org; auth=none |
X-Virus-Found: | No |
X-Spam-SWARE-Status: | No, score=3.2 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=Admins, H*F:D*yandex.ru, H*x:Bat!, H*UA:Bat! |
X-HELO: | forward5m.cmail.yandex.net |
Authentication-Results: | smtp1h.mail.yandex.net; dkim=pass header.i=@yandex.ru |
X-Yandex-Suid-Status: | 1 0,1 0 |
Date: | Wed, 10 Aug 2016 13:46:07 +0300 |
From: | Andrey Repin <anrdaemon AT yandex DOT ru> |
Reply-To: | cygwin AT cygwin DOT com |
Message-ID: | <516102654.20160810134607@yandex.ru> |
To: | David Macek <david DOT macek DOT 0 AT gmail DOT com>, cygwin AT cygwin DOT com |
Subject: | Re: symbolic linls |
In-Reply-To: | <7bb4f190-d9a6-f7ab-d278-95cc945cd5b8@gmail.com> |
References: | <no1t0v$gs5$1 AT blaine DOT gmane DOT org> <336b469f-29ad-e319-62d6-975ced78f512 AT gmail DOT com> <828539974 DOT 20160810041631 AT yandex DOT ru> <7bb4f190-d9a6-f7ab-d278-95cc945cd5b8 AT gmail DOT com> |
MIME-Version: | 1.0 |
X-IsSubscribed: | yes |
Greetings, David Macek! >>>> As i understand Cygwin will soon no longer support Windows XP resp. >>>> 2003. This means that only Windows versions with native symbolic link >>>> functionality will be supported after that. Would it be possible to use >>>> only native symbolic links throughout esp. during setup.exe? >> >>> Short answer: No. >> >>> Long answer: >> >>> There are limitations to NTFS symlinks, other than OS support, that make >>> them incompatible with POSIX symlinks. See >>> <https://cygwin.com/cygwin-ug-net/using.html#pathnames-symlinks> and >>> <https://github.com/git-for-windows/git/wiki/Symbolic-Links> for more information. >> >> There's limitations, yes. But what do you mean by "incompatibility" ? > I mean differences between how NTFS symlinks work and how POSIX symlinks > (that Cygwin apps expect) work. It's described on the Git-for-Windows page I linked. Quoting: >> You need the SeCreateSymbolicLinkPrivilege privilege, which is by default >> assigned only to Administrators but can be assigned to normal users using >> Local Security Policy (or via Active Directory). Note that regardless of >> privilege assignment, members of the Administrators group will also require >> UAC elevation. That's limitation, but not necessarily an incompatibility. Do note "members of Administrators group". If your account is not a member of administrators group (which I don't see as necessity in everyday use), this will work transparently. Having ~14 years of experience, going through "all admin" in Win'9x to "default admin" in NT/2k, and "admin with UAC" in Vista+, I'm strongly considering excluding my account from Admins/Domain Admins group for my upcoming home AD that I'm preparing to solve some of the interoperability limitations of POSIX permissions system. Or, more precisely, limitations of Samba's treatment of POSIX permissions system :/ One can only wonder, why they have gone such a route. >> Symbolic links on remote filesystems are disabled by default (call fsutil >> behavior query SymlinkEvaluation to find out) Symlinks on remote FS didn't work straight in the best times. >> Symbolic links will only work on NTFS, not on FAT That's a given. >> Windows' symbolic links are typed: they need to know whether they point to >> a directory or to a file This is of no concern for an application. -- With best regards, Andrey Repin Wednesday, August 10, 2016 13:31:16 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |