Author ned.deily
Recipients amaury.forgeotdarc, gregory.p.smith, ned.deily, r.david.murray, schmir, twb
Date 2009-09-30.21:29:41
SpamBayes Score 3.67615e-06
Marked as misclassified No
Message-id <1254346182.98.0.474878586018.issue6972@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, as shipped from the factory, the default "root" file system is 
still case-insensitive but the user can change that.  There there are 
file systems on attached disk images and NFS-mounted file systems, etc 
etc.  More to the point, it's not a system attribute, rather it's a 
file-system attribute and, since a file system mount point can be almost 
anywhere in a directory structure, in general, you can't predict where 
you're going to encounter insensitive vs -sensitive behavior; it could 
vary from directory to directory.  But isn't dealing with case-
insensitive behavior just a special case of the general case of what 
extract/extractall do about overwriting existing files?  I don't see 
that addressed in the current docs.
History
Date User Action Args
2009-09-30 21:29:43ned.deilysetrecipients: + ned.deily, gregory.p.smith, amaury.forgeotdarc, schmir, r.david.murray, twb
2009-09-30 21:29:42ned.deilysetmessageid: <1254346182.98.0.474878586018.issue6972@psf.upfronthosting.co.za>
2009-09-30 21:29:41ned.deilylinkissue6972 messages
2009-09-30 21:29:41ned.deilycreate