public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: realpath issue with native[strict] symlinks
Date: Wed, 12 May 2021 10:14:00 +0200	[thread overview]
Message-ID: <YJuOSIQV0L4QbGLX@calimero.vinschen.de> (raw)
In-Reply-To: <1515122016.20210512101026@yandex.ru>

On May 12 10:10, Andrey Repin via Cygwin wrote:
> Greetings, Corinna Vinschen via Cygwin!
> 
> > I reworked the code handling native symlinks to handle virtual drives
> > as well.  It might even be a tiny bit quicker now.
> 
> > The changes have a behavioral change, but I think this is for the
> > better: Virtual drives are not treated as drives anymore, but as
> > symlinks.  Given they are just pointers to other drives or directories,
> > tha't much closer to reality.  I. e., in case of my above virtual drive
> > T:, what you'll see in the /cygdrive dir (unless your cygdrive prefix is
> > / only) is this:
> 
> > $ ls /cygdrive
> > $ ls -lG /mnt
> > total 16
> > d---r-x---+ 1 TrustedInstaller  0 Apr 29 21:07 c
> > drwxr-xr-x  1 corinna           0 Dec 31  1979 e
> > lrwxrwxrwx  1 corinna          32 May  6 20:43 t -> /cygdrive/c/cygwin64/home/corinna/tmp
> 
> > I uploaded new developer snapshots to https://cygwin.com/snapshots/
> > for testing.
> 
> Interesting effect.
> I do have fstab entry
> none / cygdrive noacl,binary,nouser,posix=0 0 0
> And this is what I see with and without changes.
> 
> (3.2.0)
> $ ls -ld /proc/cygdrive/{a..z} 2> /dev/null
> drwxr-x--- 1 anrdaemon None 0 апр 22 23:12 /proc/cygdrive/c
> drwxr-x--- 1 anrdaemon None 0 апр 30 18:05 /proc/cygdrive/d
> drwxr-x--- 1 anrdaemon None 0 апр 22 23:11 /proc/cygdrive/e
> drwxr-x--- 1 anrdaemon None 0 май 11 21:27 /proc/cygdrive/w
> drwxr-x--- 1 anrdaemon None 0 фев 14  2018 /proc/cygdrive/y
> drwxr-x--- 1 anrdaemon None 0 май 12 03:59 /proc/cygdrive/z
> 
> (snapshot)
> $ ls -ld /proc/cygdrive/{a..z} 2> /dev/null
> drwxr-x--- 1 anrdaemon None  0 апр 22 23:12 /proc/cygdrive/c
> drwxr-x--- 1 anrdaemon None  0 апр 30 18:05 /proc/cygdrive/d
> drwxr-x--- 1 anrdaemon None  0 апр 22 23:11 /proc/cygdrive/e
> drwxr-x--- 1 anrdaemon None  0 май 11 21:27 /proc/cygdrive/w
> lrwxrwxrwx 1 anrdaemon None 35 фев 14  2018 /proc/cygdrive/y -> //HOSTING64.DARKDRAGON.LAN/wwwroot/
> lrwxrwxrwx 1 anrdaemon None 35 май 12 03:59 /proc/cygdrive/z -> //DAEMON1.DARKDRAGON.LAN/anrdaemon/

Great, this is the Tip of the Day!

> I think I like these changes.
> Thank you very much.

You're welcome.


Corinna

  reply	other threads:[~2021-05-12  8:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27  5:44 Orgad Shaneh
2021-05-04 19:52 ` Orgad Shaneh
2021-05-06 17:44   ` Corinna Vinschen
2021-05-06 18:36     ` Orgad Shaneh
2021-05-07 21:20       ` Corinna Vinschen
2021-05-09 11:35         ` Orgad Shaneh
2021-05-10  7:50           ` Corinna Vinschen
2021-05-12  7:10         ` Andrey Repin
2021-05-12  8:14           ` Corinna Vinschen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-27 20:21 Jeremy Drake
2021-05-28 19:23 ` Jeremy Drake
2021-06-08  0:01   ` Jeremy Drake
2021-05-18 20:01 Jeremy Drake
2021-05-19 12:42 ` Corinna Vinschen
2021-05-15  4:12 Jeremy Drake
2021-05-17 10:12 ` Corinna Vinschen
2021-04-18  7:59 Orgad Shaneh
2021-04-19 12:58 ` 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=YJuOSIQV0L4QbGLX@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).