This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: if [ -w branching: how to spot a locked USB stick

On Fri, Jul 13, 2007 at 04:15:26PM +0200, Corinna Vinschen wrote:
>On Jul 13 08:00, Eric Blake wrote:
>> According to Corinna Vinschen on 7/13/2007 7:06 AM:
>> >> Actually, this is a cygwin question.  Bash's [ command only reports what
>> >> access("/h",W_OK) tells it to report, 
>> > 
>> > It's the latter.  The fact that the USB stick is locked doesn't
>> > mean that the permission bits returned by the OS calls are augmented
>> > to reflect the fact that the stick is not writable.  All permission
>> > bits are still intact.  Only when actually trying to write to the device,
>> > you'll get the Win32 error message equivalent of EROFS.
>> But POSIX requires access(...,W_OK) to fail with EROFS on a read-only file
>> system.  Is there any way for cygwin to easily determine this without
>> actually attempting a write?
>Not that I'm aware of.  I added this to my TODO list.  However, as

Why do I see another bullet item for the "Why is cygwin so slow" discussion


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]