DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 50VIX7xB3894980 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 50VIX7xB3894980 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=AvUg8O1y X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A958B3857737 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1738348385; bh=9nvhuNZRYOxNrfMzqb4gkmOxYnNN9zw/490R0T1iOs0=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=AvUg8O1yfxobuBv2/TIjs55BiZpnS35TyEHy70j1RoWQaAokAVm6B943uzfe56nee eJ5v7aW3tn9OH0sGLmMVVsvcbSnUVfjWuScLID+wwNXBTm3AxRT7FwxAmWnu20FjnH dZ7hNiY6CQv4fYZ1c+nw5nTK+GPfGfIrT2W5c7jM= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 76B403858402 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 76B403858402 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1738344485; cv=none; b=WsSKok8ZSATDaAzS1f5VUA5BuHPEVur8eJOhuV/eOUPg21MKxyXcwcYSassq9VcikXSFzDi0HuRqwSZBnupqagVrZW3eKcZT2dQkD3EgRr1I0/OvN2XwZcf7yOnpGzvkk3uZyX21uKcUdQ97cn3wXTdFKulR00t0IDzphDIyLg4= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1738344485; c=relaxed/simple; bh=GrQE4lis0krqMlkdF/QqiA0NBpFoCZWJC5bNapeV+jg=; h=Message-ID:Date:MIME-Version:From:Subject:To:DKIM-Signature; b=caPzgVuLcaaYsDgVfVgO5SJ9bzF7TPcdbfDZvdfAFK7MOUfToAjkmD3vIJwImiatzP++wbsO02drMny41ZSe5dEZvbV9/JxQMGVrRHc3tv9AR0dtDvgMqWpDCAlsIMqS/WJmc1a98adiPWml0wIqowc45kOUeEypB9XlswUYYPE= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 76B403858402 Message-ID: Date: Fri, 31 Jan 2025 10:28:00 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [Ms-nfs41-client-devel] Fwd: Implementing mkfifo, mknod support with NFS_SPECFILE_FIFO and NFS_SPECFILE_SOCK? Content-Language: en-CA To: cygwin AT cygwin DOT com References: Organization: Systematic Software In-Reply-To: X-Rspamd-Server: rspamout06 X-Rspamd-Queue-Id: 783351D X-Stat-Signature: tqi6aj4g8c9w5ouf4ufgecssa1p8ay81 X-Session-Marker: 427269616E2E496E676C69734053797374656D6174696353572E61622E6361 X-Session-ID: U2FsdGVkX1+iLjNntGptJz/0BxBLvkebYH6BjpaenTg= X-HE-Tag: 1738344481-74009 X-HE-Meta: U2FsdGVkX1/BhYIb1gOpp02lB7+YsSjsSj2DLaXCOwuUAmns+4LJ1aEc3P5xLJ9ABKNgmu07TrqT1BxLEwVEuWihswLEYfkD6fdxBTKrPIlAJbBVzJtzA4Of0OKBGMQqbC40kgf3LmqlURSPqYY6yZPVGiCtUNeiOzmUCPyiowo48/RChhKVAFHiZ2zt08onUyRkf67qUlglKkLPUEUCLKJNR5vQI9SQz1LR88dxxXIKhQnr9A3avB1LxxvsirigLWBEQREIfO4GeTZzlchzJNpf6HJbLTWrYOLgQkIDeun9Ubc25YHHHM2abW+suxO0GT5ULRcPLC9dXF4w7Msi0ZK2IkZgdyZx7TYNiwVBEb6xuI1dkhdbj7yLFKzKFTE71GzDrtBp6bg= X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Brian Inglis via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Brian Inglis Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 50VIX7xB3894980 On 2025-01-31 06:23, Roland Mainz via Cygwin wrote: > On Thu, Jan 30, 2025 at 2:34 PM Cedric Blancher wrote: > [snip] >> Does the ms-nfs41-client support NFS_SPECFILE_FIFO and NFS_SPECFILE_SOCK? > > No, but if Cygwin implements this for the Microsoft NFSv3 client then > I'll add support for ms-nfs41-client and ms-nfs42-client ASAP. > > But I really would prefer if Cygwin would NOT use |NFS_SPECFILE_LNK| > (all other |NFS_SPECFILE_*| would be OK), because it seems to be > limited to |2050| bytes, while ms-nfs41-client/ms-nfs42-client doesn't > have such a limit (currently supported are 4096 byte long paths, which > sites like CERN&&Pasteur really use (measured by the bug reports about > "... paths with 3280 bytes etc don't work...") ...). > > Question for Corinna: > Why did Cygwin never use > |NFS_SPECFILE_FIFO|/|NFS_SPECFILE_SOCK|/|NFS_SPECFILE_CHR| from > https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/ff4df658-7f27-476a-8025-4074c0121eec > ? One good reason to avoid MS protocols is that they *MAY* be patent encumbered and *MAY* require to be licensed - they don't really say - feel free to ask MS for permission to pay if you have funding?! -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut -- Antoine de Saint-Exupéry -- 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