back on mailing list, please reply always there
On 02.01.2022 08:09, cyg...@kosowsky.org wrote:
Thanks. It works!
Nice to know
Marco Atzeri wrote at about 00:33:29 +0100 on Sunday, January 2, 2022:
> On 02.01.2022 00:01, cyg...@kosowsky.org wrote:
> > Hi,
> > About a month ago, a threa
On 02.01.2022 00:01, cyg...@kosowsky.org wrote:
Hi,
About a month ago, a thread with the above title mentioned that a
patch to the problem was submitted.
I am encountering the same problem on my Cygwin/Win10/Vbox 6.1.30
installation.
Any idea when that patch will be pushed to production?
Or bar
Hi,
About a month ago, a thread with the above title mentioned that a
patch to the problem was submitted.
I am encountering the same problem on my Cygwin/Win10/Vbox 6.1.30
installation.
Any idea when that patch will be pushed to production?
Or barring that, is there a test version that I could do
On Dec 9 17:16, Takashi Yano wrote:
> On Wed, 8 Dec 2021 11:37:39 +0100
> Corinna Vinschen wrote:
> > On Dec 8 17:20, Takashi Yano wrote:
> > > On Tue, 7 Dec 2021 18:15:42 +0100
> > > I confirmed that your patch works nicely.
> > >
> > > ...except when the drive is created by subst using UNC pat
On Wed, 8 Dec 2021 11:37:39 +0100
Corinna Vinschen wrote:
> On Dec 8 17:20, Takashi Yano wrote:
> > On Tue, 7 Dec 2021 18:15:42 +0100
> > I confirmed that your patch works nicely.
> >
> > ...except when the drive is created by subst using UNC path,
> > e.g. subst w: \\server\share.
> >
> > In th
On Dec 8 17:20, Takashi Yano wrote:
> On Tue, 7 Dec 2021 18:15:42 +0100
> Corinna Vinschen wrote:
> > Hi Takashi,
> >
> > - Forwarded message from Corinna Vinschen
> > -
> > > The idea of the GFPNBH call is to short-circuit the path_conv handling
> > > in case we have native Windows sym
On Tue, 7 Dec 2021 18:15:42 +0100
Corinna Vinschen wrote:
> Hi Takashi,
>
> - Forwarded message from Corinna Vinschen
> -
> > The idea of the GFPNBH call is to short-circuit the path_conv handling
> > in case we have native Windows symlinks in the path. My example above
> > was only con
On Dec 8 00:32, Takashi Yano wrote:
> On Tue, 7 Dec 2021 15:57:56 +0100
> Corinna Vinschen wrote:
> > On Dec 7 09:46, Takashi Yano wrote:
> > > I think '/cygdrive/z/..' should be '/cygdrive', however,
> > > in current cygwin, it is interpreted into '//VBoxSrv'.
> > >
> > > Is this as you intende
On Wed, 8 Dec 2021 00:32:49 +0900
Takashi Yano wrote:
> With my patch, above case behaves like:
>
> $ mount
> C:/cygwin/bin on /usr/bin type ntfs (binary,auto)
> C:/cygwin/lib on /usr/lib type ntfs (binary,auto)
> C:/cygwin on / type ntfs (binary,auto)
> C: on /cygdrive/c type ntfs (binary,posix=0
On Tue, 7 Dec 2021 15:57:56 +0100
Corinna Vinschen wrote:
> On Dec 7 09:46, Takashi Yano wrote:
> > I think '/cygdrive/z/..' should be '/cygdrive', however,
> > in current cygwin, it is interpreted into '//VBoxSrv'.
> >
> > Is this as you intended?
> >
> > With my patch which stops to treat UNC
On Dec 7 09:46, Takashi Yano wrote:
> On Mon, 6 Dec 2021 19:55:27 +0900
> Takashi Yano wrote:
> > First, I think the same. However, with this patch, it sometimes causes
> > hang for a few seconds around the code:
> [...]
> > with path_copy of "//VBoxSrv". I am not sure why.
That's expected and no
On Mon, 6 Dec 2021 19:55:27 +0900
Takashi Yano wrote:
> First, I think the same. However, with this patch, it sometimes causes
> hang for a few seconds around the code:
[...]
> with path_copy of "//VBoxSrv". I am not sure why.
>
> In addition,
> https://cygwin.com/pipermail/cygwin/2021-December/25
On Mon, 6 Dec 2021 11:16:30 +0100
Corinna Vinschen wrote:
> > For example, RtlEqualUnicodeString() compares \??\UNC\VBoxSrv\tmp and
> > \??\UNC\VBoxSrv\tmp\, then it fails.
> > [...]
> > + if (wcsstr (fpbuf, L"?\\UNC\\") == fpbuf)
> > + goto file_not_symlink;
> > +
>
> Isn't
On Dec 5 11:54, Takashi Yano wrote:
> On Tue, 30 Nov 2021 19:04:57 +0200
> Oskar Skog wrote:
> > vboxsharedfs file systems no longer work. Any attempt to access will
> > result in "too many levels of symbolic links".
> >
> > This only affects the VirtualBox shared folder, the Samba share works
>
On Mon, 6 Dec 2021 12:31:35 +0900
Takashi Yano wrote:
> cygwin symbolic link seems to work only in NTFS file system.
This is not right. cygwin symlink needs 'SYSTEM' attribute.
So it does not work in file system which does not support
that attributes. Windows file system, such as NTFS, FAT,
suppor
On 2021-12-06 05:31, Takashi Yano wrote:
On Sun, 5 Dec 2021 16:49:13 +0200
Oskar Skog wrote:
But if I create a symlink on that filesystem, it's not identified as a
symlink. Although, I don't know if this has ever worked as it is the
first time I've ever tested it, it probably hasn't ever worked
On Sun, 5 Dec 2021 16:49:13 +0200
Oskar Skog wrote:
> But if I create a symlink on that filesystem, it's not identified as a
> symlink. Although, I don't know if this has ever worked as it is the
> first time I've ever tested it, it probably hasn't ever worked (see
> below).
>
> user@DESKTOP-*
On 2021-12-05 04:54, Takashi Yano wrote:
On Tue, 30 Nov 2021 19:04:57 +0200
Oskar Skog wrote:
vboxsharedfs file systems no longer work. Any attempt to access will
result in "too many levels of symbolic links".
This only affects the VirtualBox shared folder, the Samba share works
just fine.
...
On 2021-12-05 04:54, Takashi Yano wrote:
In 64bit Windows10, for vbox shared path, GetFinalPathNameByHandleW()
returns path with trailing '\'. As a result, RtlEqualUnicodeString()
fails and tries to resolve symlink repeatedly.
For example, RtlEqualUnicodeString() compares \??\UNC\VBoxSrv\tmp and
On Tue, 30 Nov 2021 19:04:57 +0200
Oskar Skog wrote:
> vboxsharedfs file systems no longer work. Any attempt to access will
> result in "too many levels of symbolic links".
>
> This only affects the VirtualBox shared folder, the Samba share works
> just fine.
>
> Last time I updated (before today
On Nov 30 19:04, Oskar Skog wrote:
> vboxsharedfs file systems no longer work. Any attempt to access will
> result in "too many levels of symbolic links".
>
> This only affects the VirtualBox shared folder, the Samba share works
> just fine.
>
> Last time I updated (before today) was sometime bef
@cygwin.com
Subject: vboxsharedfs - Too many levels of symbolic links
Check twice before you click! This email originated from outside PNNL.
vboxsharedfs file systems no longer work. Any attempt to access will result in
"too many levels of symbolic links".
This only affects the Virtual
vboxsharedfs file systems no longer work. Any attempt to access will
result in "too many levels of symbolic links".
This only affects the VirtualBox shared folder, the Samba share works
just fine.
Last time I updated (before today) was sometime before the 10th of
September.
MSYS2 has the same p
23 matches
Mail list logo
