X-Recipient: archive-cygwin@delorie.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:to:subject:mime-version:message-id
	:content-type:content-transfer-encoding; q=dns; s=default; b=IOL
	G+dbnUwGc83YogXc00i+VFNbYS9qT/RaqPCJ17Zx1HdHSWMv45nTFjdTXk7AdgP2
	ZM7KzJSQXJXQutjRB6dPmpT3uGHOM3gg2rtocANiynQizf2NuzEQAgASEetFv0yb
	qS5O7zvrnUIF6bLmo1TojxJmiLWda96Gz5UZISVE=
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:to:subject:mime-version:message-id
	:content-type:content-transfer-encoding; s=default; bh=6aedC+3Z6
	DFkVXJ5cDQJx/yKByA=; b=S7ZQ+e2y6YOgB+s50wAhhnzqUkcyH/0UA+/BY6l2m
	UbB+zCjLzjFSx1N4ideHUG9Wrl/MnvmzvPWqxGHvQ9792LxGJrDiVuvdm9UtegD7
	mnUznC7ZnCVCeD/T9Pg+z5R/FZ9JzHlmqfLK4CN+pD70qMYSDqiUGkLqn0Qg7Z+/
	Ug=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.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
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-7.6 required=5.0 tests=BAYES_00,GIT_PATCH_2,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:567
X-HELO: co03.mbox.net
X-USANET-Received: from co03.mbox.net [127.0.0.1] by co03.mbox.net via mtad (C8.MAIN.4.17E) 	with ESMTP id 559XDamns4640M03; Mon, 01 Apr 2019 12:39:18 -0000
X-USANET-Routed: 3 gwsout-vs Q:bmvirus
X-USANET-Routed: 3 gwsout-vs Q:bmvirus
X-USANET-GWS2-Tenant: usa.net
X-USANET-GWS2-Tagid: UNKN
X-USANET-Source: 165.212.11.134  OUT  kdbotts@usa.net ca34.cms.usa.net CLR
X-USANET-MsgId: XID008XDamns1244X03
X-USANET-Auth: 165.212.8.203   AUTO kdbotts@usa.net web03.cms.usa.net CLR
Date: Mon, 01 Apr 2019 07:39:18 -0500
From: "KARL BOTTS" <kdbotts@usa.net>
To: <cygwin@cygwin.com>
Subject: Cygwin vs. Native Symlinks
Mime-Version: 1.0
Message-ID: <804XDamMs8784Set.1554122358@web03.cms.usa.net>
Content-Type: text/plain; charset=ISO-8859-1
Z-USANET-MsgId: XID565XDamns1808X34
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x31CdbZb015317


Corinna said:

> ... Which lets symlinking with nativestrict fail. "winsymlinks:native"
> will work, albeit creating a Cygwin symlink then.


I use "winsymlinks:native".  Is there a tool or method with which I can
create a Cygwin symlink by force?  (I doubt I would actually want to:
I just want to know if I can, and to test behavior of a Cygwin symlink.)

Is there a tool which will tell me whether a given symlink is Cygwin or
native?
(The output of both readlink and symlinks looks the same, regardless.)

---
Karl Botts, kdbotts@usa.net


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


