X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Tue, 24 Aug 2010 18:28:10 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.7: Basic file operations fail on network shares provided by Tru64 Advanced Server
Message-ID:	<20100824162810.GU6726@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4C73712F DOT 7000801 AT dla-marbach DOT de> <20100824083631 DOT GN6726 AT calimero DOT vinschen DOT de> <i5042b$fln$1 AT dough DOT gmane DOT org> <20100824122144 DOT GS6726 AT calimero DOT vinschen DOT de> <i50qpr$k60$1 AT dough DOT gmane DOT org>
MIME-Version:	1.0
In-Reply-To:	<i50qpr$k60$1@dough.gmane.org>
User-Agent:	Mutt/1.5.20 (2009-06-14)
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 Aug 24 18:08, Heinz Werner Kramski wrote:
> Am 24.08.2010 14:21, schrieb Corinna Vinschen:
> >I prepared three test DLLs which all request another set of access
> >rights:
> >
> >   http://cygwin.de/cygwin-ug-177/cygwin1-test1.dll.bz2
> >   (md5sum 29c3d46465113e69922938a65f693c61)
> >
> >   http://cygwin.de/cygwin-ug-177/cygwin1-test2.dll.bz2
> >   (md5sum 8e2facf7fc0641f130a2ed2b69c5665a)
> >
> >   http://cygwin.de/cygwin-ug-177/cygwin1-test3.dll.bz2
> >   (md5sum c3b52a03d47fc068b5915a95710723b3)
> >
> >Would you mind to test all three and report back?
> 
> Good news: mv works with test2 (but fails with test1 and test3).
> Thanks a lot!

Good news, indeed.

> RCS now works again (also in Windows Emacs), and so does a ~ 1300
> lines script I'm currently working on. Is it safe to use this
> cygwin1-test2.dll for serious work? We are just preparing a new
> master image for several PCs and would like to include a working
> Cygwin 1.7.

Please wait.  I was hoping that you could test a little bit further.
I prepared another DLL, which is very close to the "real" thing.
There's another flag which I have to know if it's required or not.

  http://cygwin.de/cygwin-ug-177/cygwin1-test4.dll.bz2
  (md5sum 889a86df2c2aafd010249b27bf10f411)

If it works, we're finished.  If not, we probably need just one more
iteration.

In the meantime, can you send the output of `mount' to this list?
I would like to make sure that the drives are really recognized as
"cifs".

As for the ihash issue, after giving this some thought I tend to keep it
as it is, so you will have to use it on your Tru64 drives.  At least for
the next Cygwin release 1.7.7.  If it's getting too awkward at some
point, we can discuss this again.


Thanks in advance,
Corinna

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

--
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 -