On 2025-01-31 06:23, Roland Mainz via Cygwin wrote:
On Thu, Jan 30, 2025 at 2:34 PM Cedric Blancher <cedric.blanc...@gmail.com>
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
