X-Spam-Check-By:	sourceware.org
Date:	Fri, 13 Jul 2007 17:58:55 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: if [ -w branching: how to spot a locked USB stick
Message-ID:	<20070713155855.GX6851@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<469715CF DOT 7090105 AT bonhard DOT uklinux DOT net> <46977404 DOT 6070105 AT byu DOT net> <20070713130620 DOT GT6851 AT calimero DOT vinschen DOT de> <46978595 DOT 5070605 AT byu DOT net> <20070713141526 DOT GW6851 AT calimero DOT vinschen DOT de> <20070713142703 DOT GC13962 AT ednor DOT casa DOT cgf DOT cx>
Mime-Version:	1.0
In-Reply-To:	<20070713142703.GC13962@ednor.casa.cgf.cx>
User-Agent:	Mutt/1.4.2.2i
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Jul 13 10:27, Christopher Faylor wrote:
> 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
> >usual, http://cygwin.com/acronyms/#PTC.
> 
> Why do I see another bullet item for the "Why is cygwin so slow" discussion
> here?

Actually I found that there's a laughable simple way to determine a
read-only device.  When calling GetVolumeInformation, the
FILE_READ_ONLY_VOLUME flag is set.  I just tested this with a USB
stick.  Since we have the information from fs_info anyway, a fix
should be very simple and not affect Cygwin's spee^Wslowness.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -