Re: [PATCH] fsync.2: no writability requirements, must operate on directories

[Alejandro Colomar <alx@kernel.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1642 bytes --]

On 2023-08-03 15:22, Alejandro Colomar wrote:
> Hi!
> 
> On 2023-08-03 13:52, наб wrote:
>> POSIX has for a long time implied that directories are fsyncable,
>> and since Issue 8 explicitly specifies directory syncing semantics:
>>   https://www.austingroupbugs.net/view.php?id=672
>>
>> Simultaneously, directories being unopenable for writing is a
>> Longest-Standing UNIX Semantic, present in the UNIX Programmer's Manual
>> under directory (V), and has always been enshrined in the standards.
>>
>> Kill the FUD that says that some UNIXes require the fd to be writable:
>> they /must not/ and this confuses users:
>>   https://101010.pl/@eater@cijber.social/110824211348995583
>>
>> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
>> ---
>>  man2/fsync.2 | 6 ------
>>  1 file changed, 6 deletions(-)
>>
>> diff --git a/man2/fsync.2 b/man2/fsync.2
>> index 1043e6a1b..9ced40b28 100644
>> --- a/man2/fsync.2
>> +++ b/man2/fsync.2
>> @@ -155,12 +155,6 @@ .SH VERSIONS
>>  .\" POSIX.1-2001: It shall be defined to -1 or 0 or 200112L.
>>  .\" -1: unavailable, 0: ask using sysconf().
>>  .\" glibc defines them to 1.
>> -.PP
>> -On some UNIX systems (but not Linux),
>> -.I fd
>> -must be a
>> -.I writable
>> -file descriptor.
> 
> But that's still true.  HP-UX and AIX had that issue.  I'd move
> that paragraph to HISTORY, and say "some old UNIX systems".

s/old/ancient/  :)

> 
> Cheers,
> Alex
> 
>>  .SH STANDARDS
>>  POSIX.1-2008.
>>  .SH HISTORY
> 

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]