X-Recipient: archive-cygwin@delorie.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C9B2A385DC1A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1692298274;
	bh=4OHIW/zZYw1Sho6EP6AYAlC0132x8LBKvVBCwCsk5Dg=;
	h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=qk3PIFh5mXtCpOr6etiD4VrukhTXYBw5RrCnN4i87ywVRIqwemZ3RZAjYLivP5liA
	 pJ9vonHnbspczGL923OxpwIKSnn1kvpbEWOwhM0V/7/+AQKKlsjMxElCuYDR23My3h
	 tMDuAZ+jSc7GNd2tP70KnHHs8R2bP/Uo1pkRnV3A=
X-Original-To: cygwin@cygwin.com
Delivered-To: cygwin@cygwin.com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D6F623858D35
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1692298238; x=1692903038;
 h=content-transfer-encoding:to:subject:message-id:date:from
 :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc
 :subject:date:message-id:reply-to;
 bh=5qY/MP4BpnNogmho6P+MS2WvxAesA97iXcuzyShHLtc=;
 b=iRP63r7eLJyAmj+suyW3ZTcRgcg91TBGSfeecPaZw+M42VD+8Vx0ccw5G4UQ6fD/ki
 YIddf2cwi9RV/eVFY+ftpXTP30IymwL7AW/oKG+bWlQ7WU/vzZA+MHseL1NUXKsYVTIp
 chkpK1ejXQVZ4HvWp9Qw4ghvacap6/tt+MTsXo/gC1Cr2f09lUBApSGIWymj0aVgqPLQ
 2KyvPF9pMdj9DfvXcrvbQ0EP8w/IyoIttLteksKT35zo2zOb57lNowiAsv6ye/tc3m4c
 p0mnHSZa8xa9vXUKKDEHvGzS7G0xRz7gf5t9S0/eZ5xt3zRQNyDG0uF/JvwbGIP4ZZMw
 JGRw==
X-Gm-Message-State: AOJu0YymulAgUlzEQWsJdo9hNj7lNlMbdtmsW/py7obUheSVVPaGhiUB
 MrVZsz+bx0cwfEeUr0M/iWOzqjePGaP39mJ3Crd+1/4aYv8=
X-Google-Smtp-Source: AGHT+IHTVPqn/CDrgRzzbTmCR2oZVEKlNqeCbvQmDkrHe5QVAvvpFGQEB7Wbzof+JUrFU1FhZFmA2+ZkSArZvssnw2k=
X-Received: by 2002:a05:6808:ab6:b0:3a4:17cd:dd31 with SMTP id
 r22-20020a0568080ab600b003a417cddd31mr385891oij.14.1692298237930; Thu, 17 Aug
 2023 11:50:37 -0700 (PDT)
MIME-Version: 1.0
References: <a0f1e420-ae48-49a3-9300-c56f1948ad9b.8d485f54-9f47-42b0-bdcb-9635fbf663c3.6697971f-86bc-49dc-8072-c37095eed858@emailsignatures365.codetwo.com>
 <a0f1e420-ae48-49a3-9300-c56f1948ad9b.93e247b8-206a-49dd-b71c-9240681180cb.7748cdc6-d053-4197-9372-3b4751ae3949@emailsignatures365.codetwo.com>
 <a0f1e420-ae48-49a3-9300-c56f1948ad9b.e52b7f5f-5a09-4346-99f8-a6591191169c.10af45d3-4cfc-48f7-a293-b6d9fa78cdd1@emailsignatures365.codetwo.com>
 <AM5PR0502MB30752878C878948E660A73179210A@AM5PR0502MB3075.eurprd05.prod.outlook.com>
 <ZNoAR4fBMXknsn5z@calimero.vinschen.de>
 <CAKAoaQn47pu510onZDwh4baES-bhxtuSy3SxDCv7sXw5T94pzA@mail.gmail.com>
 <CAKAoaQnvSZDD6mitFsdD==aOi0n9h3JSAEiJo8QXCRAf58H_Sw@mail.gmail.com>
 <ZNqU5c5pMS2cQbsc@calimero.vinschen.de>
In-Reply-To: <ZNqU5c5pMS2cQbsc@calimero.vinschen.de>
Date: Thu, 17 Aug 2023 20:49:00 +0200
Message-ID: <CANH4o6OBo-vHUps6BbCn0X-w8Y49AADwB7PRfXPr+OH7GQ5TkQ@mail.gmail.com>
Subject: How does Cygwin detect MSFT NFSv3 file system? Re: Weird (path)
 problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...
To: cygwin@cygwin.com
X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.29
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Martin Wege via Cygwin <cygwin@cygwin.com>
Reply-To: Martin Wege <martin.l.wege@gmail.com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 37HIpFwG021722

On Mon, Aug 14, 2023 at 10:56 PM Corinna Vinschen via Cygwin
<cygwin@cygwin.com> wrote:
> and the result is the same.  Note that Cygwin supports MSFT NFSv3 but
> not CITI NFSv4.1 internally.  No gurantee that Cygwin always does what
> is necessary for that other NFS.

1. How does Cygwin detect whether something is a MSFT NFSv3, or not?
Cygwin /bin/mount lists the CITI NFSv4.1 as 'nfs', so there *IS*
something which detects that?
2. Are Cygwin soft link handing depend on MSFT NFSv3 or not, i.e. does
the Cygwin soft link code behave differently for MSFT NFSv3 file
systems?
3. Does Cygwin implement the pathconf() api?

Thanks,
Martin

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

