From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: hardlinks on directories?
Date: Fri, 31 Jan 2020 14:59:00 -0000 [thread overview]
Message-ID: <bd6b2c71-670b-6d1b-fc01-10e5d0f033d5@SystematicSw.ab.ca> (raw)
In-Reply-To: <20200131101755.GA5074@tik.uni-stuttgart.de>
On 2020-01-31 03:17, Ulli Horlacher wrote:
> On Thu 2020-01-30 (12:26), Eric Blake wrote:
>
>>> Are this directory hard links?
>>
>> No, rather they are parallel mount points (the same directory mounted
>> under two different names).
>
> /: mount
> C:/cygwin64/bin on /usr/bin type ntfs (binary,auto)
> C:/cygwin64/lib on /usr/lib type ntfs (binary,auto)
> C:/cygwin64 on / type ntfs (binary,auto)
> C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
>
> That's it! Thanks!
>
> But why does Cygwin mount the directories /usr/bin and /usr/lib extra?
$ cmd /c dir `cygpath -aw /usr`
...
2020-01-30 17:51 <DIR> include
2020-01-19 13:55 <DIR> libexec
2019-09-29 13:38 <DIR> local
2020-01-19 13:55 <DIR> sbin
2020-01-19 13:56 <DIR> share
2016-10-25 14:43 <DIR> src
2019-12-18 11:07 <DIR> tmp
...
No /usr/bin nor /usr/lib.
> Why not a symbolic link?
Mounts ensure the paths exist and are identical to /bin /lib.
> And which process does this mounting?
Every Cygwin process at startup performs those mounts and any alternatives in
/etc/fstab and /etc/fstab.d/*, see "Cygwin User's Guide", Chapter 3. Using
Cygwin, /The Cygwin Mount Table/:
http://cygwin.com/cygwin-ug-net/using.html#mount-table
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
prev parent reply other threads:[~2020-01-31 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 18:16 Ulli Horlacher
2020-01-30 18:26 ` Eric Blake
2020-01-31 10:18 ` Ulli Horlacher
2020-01-31 14:59 ` Brian Inglis [this message]
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=bd6b2c71-670b-6d1b-fc01-10e5d0f033d5@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).