X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=1.7 required=5.0 tests=AWL,BAYES_20
X-Spam-Check-By:	sourceware.org
X-TPG-Junk-Checked:	Yes
X-TPG-Junk-Status:	Message not scanned because user authenticated using SMTP AUTH
X-TPG-Abuse:	host=123-243-74-63.tpgi.com.au; ip=123.243.74.63; date=Thu, 23 Jul 2009 01:40:22 +1000; auth=a/dd58RmThMRQbJLhdmDwr/fcSovfa0vOzWc399V3Kc=
Message-ID:	<4A6732E1.8000103@shaddybaddah.name>
Date:	Thu, 23 Jul 2009 01:40:17 +1000
From:	Shaddy Baddah <helium AT shaddybaddah DOT name>
Reply-To:	cygwin AT cygwin DOT com,
	"Shaddy Baddah (please keep me)" <helium AT shaddybaddah DOT name>
User-Agent:	Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Yesterday's CVS ci solved VBoxSharedFolderFS issues
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

 Hi,

I've been trying to work through a problem with running cygwin from a
VBoxSharedFolderFS (VirtualBox) folder mounted on my guest host. I've
tried to work through the problem on my own, as I would imagine that
VBoxSharedFolderFS support in cygwin is of almost zero importance.

However I thought it at least interesting to note that yesterday's CVS
checkins (just as a coincidence, I've been working through the problem
over the last couple of days) seem to have made this work a lot
better. Before these checkins, I could not start bash. It would take
up full utilisation of the CPU, and could only be killed through the
task manager. ash was working in its place, but behaviour of almost
all the tools was inconsistent.

The only thing obviously broken now are symlinks. I've done some
debugging and tracked it down to the fact that any call like this:

path.c:2254:      if (NT_SUCCESS (status)
path.c:2255:      && NT_SUCCESS (status
path.c:2256:             = NtQueryInformationFile (h, &io, &fbi, sizeof fbi,
path.c:2257:                           FileBasicInformation)))

will return STATUS_NOT_SUPPORTED. I will need to do some further
learning to understand if this is a show stopper for symlinks,
although any wisdom dispensed would be greatly appreciated.

Regards,
Shaddy


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

- Raw text -