DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=Aj4d4V1QQCollymEJLX/bpimV7kJmYoMuP5dUutsPIqK7L/YGyKZl
	VFCfTzbxBpf6k/a8F1pa5GRsSbbr91BeKRvTt4EOQqkbpIuIAHXIqGUvm7z9yDg7
	rae0vyqCOHvdKkXwquc7Eoian/vaILLDGDldb3zmSRT6qpUfuU8FzY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Fri, 6 Dec 2019 12:07:09 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 3.0.7(0.338/5/3): Possible reference to Developer's instances of dev files in deployed build
Message-ID: <20191206110709.GB3499@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20191206045537 DOT GA22631 AT shackleton DOT labs DOT net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="jq0ap7NbKX2Kqbes"
Content-Disposition: inline
In-Reply-To: <20191206045537.GA22631@shackleton.labs.net>
User-Agent: Mutt/1.12.1 (2019-06-15)

--jq0ap7NbKX2Kqbes
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Dec  6 04:55, Wilfed Olaf Sulla via cygwin wrote:
> >On 12/5/2019 2:16 PM, Corinna Vinschen wrote:
> >> On Dec  5 16:10, Ken Brown wrote:
> >>> On 12/5/2019 7:52 AM, Corinna Vinschen wrote:
> >>>> On Dec  5 10:18, Corinna Vinschen wrote:
> >>>> The only problem here is that I can't reproduce the assertion failur=
e.
> >>>>
> >>>> I created a Samba share on a Linux machine, mounted it as drive Z:,
> >>>> and set the "always available offline" property of the drive.
> >>>>
> >>>> After syncing I accessed the drive, then I stopped Samba on the Linux
> >>>> server to switch the drive into offline mode.  Then I ran `ls -la
> >>>> /cygdrive/z'.  After a few secs I got the offline content cached on =
the
> >>>> local machine.  I also tried `ls -la /cygdrive/' and `cd /cygdrive; =
ls
> >>>> -la', but every time I got the expected output.  In the cases I tried
> >>>> to list /cygdrive itself I got the expected output, all drives except
> >>>> the z drive.
> >>>>
> >>>> I tried this with Cygwin 3.1.0-0.8.x86_64 on Windows 7 and Windows 1=
0.
> >>>>
> >>>> So either there's something very special in Wilfed's setup, or I'm
> >>>> doing something wrong.  Which is it?
> >>>
> >>> How does your strace output compare to Wilfed's when you list /cygdri=
ve?  Does
> >>> it show a failed attempt to list Z: with an error from NtCreateFile?
> >>=20
> >> Not at all.  The strace doesn't show any attempt to open Z:.
> >
> >Then I wonder what's different about Wilfed's setup that causes an attem=
pt to=20
> >open Z: when it's offline.
> >
> >I'm grasping at straws, but could the difference be related to the fact =
that his=20
> >drive Z: is not a Samba share?  Here's an excerpt from the mount output =
in one=20
> >of his earlier emails (when Z: is online):
> >
> >V: on /cygdrive/v type smbfs (binary,noacl,posix=3D0,user,noumount,auto)
> >W: on /cygdrive/w type smbfs (binary,noacl,posix=3D0,user,noumount,auto)
> >X: on /cygdrive/x type smbfs (binary,noacl,posix=3D0,user,noumount,auto)
> >Y: on /cygdrive/y type smbfs (binary,noacl,posix=3D0,user,noumount,auto)
> >Z: on /cygdrive/z type cifs (binary,noacl,posix=3D0,user,noumount,auto)
> >                        ^^^^
> >
> >Ken
> >
>=20
> Hi,
>=20
> The drive mapping was created in a Windows context for use within a
> Windows context - i.e. via Explorer - onto a device on a remote node;
> there has been no specific configuration applied within the context of
> Cygwin.

That's not the point, actually.  Setting up drives is always a Windows
thingy.  Cygwin just reads the configuration and tries to map it into
a POSIX context.

> Whether or not the device is available, there is a Z: drive mapping
> maintained within Explorer, however the /cygdrive/z/ mount is only
> available if the device is available.

Right.  Cygwin uses a simple mechanism to check the drives to show
under /cygdrive.  Basically it just calls the Win32 function
GetLogicalDriveStrings(), then, for each drive, it checks the
QueryDosDevice mapping.  Right now it only accepts cdrom, floppy,
harddrive, LanmanRedirector (SMB) and MRxNfs (NFS).  All other
drive types are treated as "no disk".  This is fixable with probably not
too much effort.

> The problem is exhibited on:
>=20
> Windows 7 Professional Ver 6.1 Build 7601 Service Pack 1

Yeah, that's what I tried, too, as I wrote, besides W10.  I'm still not
seeing the assertion failure.  I tried this with a "normal" mapping of
the remote drive, as well as with a drive marked "available offline", to
no avail.  That's why *maybe* the drive type is part of the problem.


Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

--jq0ap7NbKX2Kqbes
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAl3qNl0ACgkQ9TYGna5E
T6A+JA/+OeYWzRWl7TKSWsVfxVdTo1Py9fMpuVw2iP96KTOX9KBcK2nyTQRfAIW1
Xwz+vtqSsopuD4TNc3NTyqTqUiwiIPzGwIwXfyPi12LgGmv52EhmBzh2RjIkDaj2
EyyJnqmQRyvoayorAWaZEo3NOTjoSVhXnN5yyYU3WzZlWPhTWfmQHLj1sA7JYUfz
jBKTPqIj4PvKwy2oCs1qfLAt/tXIYT0xLfTifmSlVwYoMRD/j2JdjJIwbcTyYSHS
wGUTmBWVHTUWDW0nzCDnQJTxaQ7k3SI7VDwXQiiHyCOVfPKDDL4x19Aa5RjcwAmv
+Ahcki9a+tMeTtbSpOGFMqt1QvTCeVNpO/fKZeZcxwwg5SFFys7Zi2uhIFPrOKzE
MYBh6v4LbeOFmZ33wPWLT/VWZUcHZK4BSlpu4F8Zh/MpNRhIP2b4LbZVSkTZbO/s
G57hTt31UOCUUhBbDzUe6wCGOyK6Gucv1wNn6mEEeuqN3TtqPxBl0Sd6wkDPfYKL
MQ/P/qKb7bCYchYuI1nP2tpwuIW0n1kYAzeISGE8v4CZQZFf2kwoOUxVSWf9O1Fw
n6Gfp2kZehlpHJ3MTvwW3ocd4mDkD9uFWcIvcCBZuQANvsHnxagWa6NUwpIyrTkc
sDtTSnjBaqJ05a4Lz/1/4SeV1VIoqWQyBs82kT8LwSwcMBSVUHc=
=j61q
-----END PGP SIGNATURE-----

--jq0ap7NbKX2Kqbes--