Thanks for this explanation. That is exactly what was happening. I regret
not noticing the issue from this:
# ldd stats.dll
ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x7ff9fc82)
KERNEL32.DLL => /cygdrive/c/Windows/System32/KERNEL32.DLL (0x7ff9fbf1)
KERNELBASE.dll => /cygdrive/
On Tue, Dec 5, 2023 at 4:39 AM Stephen P Carrier wrote:
>
Hi Stephen,
on this mailing list, for reply we use bottom post
https://curl.se/mail/etiquette.html#Do_Not_Top_Post
> Thanks for this explanation. That is exactly what was happening. I regret
> not noticing the issue from this:
>
> # ld
Am 01.12.2023 um 12:02 schrieb Corinna Vinschen via Cygwin:
On Dec 1 11:22, Cedric Blancher via Cygwin wrote:
Not all filesystems have a 128k block/stripe size, and certainly most
filesystems have smaller minimum hole sizes than 128k (e.g. 512bytes
is common, ref pathconf _PC_MIN_HOLE_SIZE).
Greetings, Corinna Vinschen via Cygwin!
> I don't know how Windows stores short files,
By Windows I Think you did mean NTFS.
Then yes, file data for certain short values is stored directly in $MFT.
This is not specifically file contents, and even if a file content is just 1
byte, not necessarily
On Dec 3 17:45, Cedric Blancher via Cygwin wrote:
> Good evening!
>
> What is the maximum path length and path element (single file, dirname
> length) in Win32 API,
https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation
> Cygwin APIs on Windows 11,
NAME_MAX is 255
5 matches
Mail list logo