Message 127673 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	loewis
Recipients	jcea, loewis, movement, pitrou
Date	2011-01-31.23:53:12
SpamBayes Score	9.4745957e-07
Marked as misclassified	No
Message-id	<4D474B67.6050402@v.loewis.de>
In-reply-to	<1296515222.1.0.23783742745.issue11016@psf.upfronthosting.co.za>

Content
>> Apparently, contributor have the illusion that the values they put >> into the file are somehow standardized, when they are actually not. > > Are there actual bugs with that or is it merely a theoretical concern? Neither, nor (i.e. it's in the middle). I'm not aware of an actual problem, but I very much doubt that SF_SNAPSHOT really has the same meaning on all systems (IOW, chances are high that some system has allocated the same bit to mean something different). Looking in more detail: for the S_IFMT flags, OSX/Darwin/FreeBSD defines 0xe000 as S_IFWHT (whiteout), but Solaris defines it as S_IFPORT (event port).

>> Apparently, contributor have the illusion that the values they put
>> into the file are somehow standardized, when they are actually not.
> 
> Are there actual bugs with that or is it merely a theoretical concern?

Neither, nor (i.e. it's in the middle). I'm not aware of an actual
problem, but I very much doubt that SF_SNAPSHOT really has the same
meaning on all systems (IOW, chances are high that some system has
allocated the same bit to mean something different).

Looking in more detail: for the S_IFMT flags, OSX/Darwin/FreeBSD defines
0xe000 as S_IFWHT (whiteout), but Solaris defines it as
S_IFPORT (event port).

History
Date	User	Action	Args
2011-01-31 23:53:13	loewis	set	recipients: + loewis, jcea, pitrou, movement
2011-01-31 23:53:12	loewis	link	issue11016 messages
2011-01-31 23:53:12	loewis	create