From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: vboxsharedfs - Too many levels of symbolic links
Date: Mon, 6 Dec 2021 12:31:35 +0900 [thread overview]
Message-ID: <20211206123135.19fce6f5d2e186ab51bd53b8@nifty.ne.jp> (raw)
In-Reply-To: <36be1c59-efd1-5cfb-93c1-baf629a897dc@oskog97.com>
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-******* /cygdrive/z$ ln -s report.pdf test.pdf
> user@DESKTOP-******* /cygdrive/z$ ls -l report.pdf test.pdf
> -rw-r--r-- 1 user None 1454562 Nov 28 12:05 report.pdf
> -rw-r--r-- 1 user None 34 Dec 5 16:36 test.pdf
> user@DESKTOP-******* /cygdrive/z$ cat test.pdf
> !<symlink>▒▒report.pdfuser@DESKTOP-******* /cygdrive/z$
>
> I think it's because "special" attributes don't work on VirtualBox
> shared folders, I can't hide files in Explorer either.
>
> So I don't think the patch has caused any regression here.
I cannot reproduce that behaviour.
yano@DESKTOP-LSNFFD0 /cygdrive/z
$ echo AAAAAAAAAAAA > a
yano@DESKTOP-LSNFFD0 /cygdrive/z
$ ln -s a b
yano@DESKTOP-LSNFFD0 /cygdrive/z
$ ls -l b
lrwxrwxrwx 1 yano None 1 Dec 6 12:17 b -> a
yano@DESKTOP-LSNFFD0 /cygdrive/z
$ cat b
AAAAAAAAAAAA
yano@DESKTOP-LSNFFD0 /cygdrive/z
$ 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,user,noumount,auto)
D: on /cygdrive/d type iso9660 (binary,posix=0,user,noumount,auto)
Z: on /cygdrive/z type vboxsharedfolderfs (binary,posix=0,user,noumount,auto)
Are you running VirtualBox in non-windows host by any chance?
cygwin symbolic link seems to work only in NTFS file system.
If shared folder is in linux file system, cygwin symbolic link
does not work.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2021-12-06 3:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 17:04 Oskar Skog
2021-11-30 21:40 ` Gackle, Philip P
2021-12-02 10:43 ` Corinna Vinschen
2021-12-05 2:54 ` Takashi Yano
2021-12-05 14:49 ` Oskar Skog
2021-12-06 3:31 ` Takashi Yano [this message]
2021-12-06 6:34 ` Oskar Skog
2021-12-06 8:04 ` Takashi Yano
2021-12-06 10:16 ` Corinna Vinschen
2021-12-06 10:55 ` Takashi Yano
2021-12-07 0:46 ` Takashi Yano
2021-12-07 14:57 ` Corinna Vinschen
2021-12-07 15:32 ` Takashi Yano
2021-12-07 15:43 ` Takashi Yano
2021-12-07 16:03 ` Corinna Vinschen
[not found] <Ya+WvmECA+zAbuV9@calimero.vinschen.de>
2021-12-08 8:20 ` Takashi Yano
2021-12-08 10:37 ` Corinna Vinschen
2021-12-09 8:16 ` Takashi Yano
2021-12-09 9:16 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211206123135.19fce6f5d2e186ab51bd53b8@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).