From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com, framstag@rus.uni-stuttgart.de
Subject: Re: hardlinks on directories?
Date: Thu, 30 Jan 2020 18:26:00 -0000 [thread overview]
Message-ID: <f0e439a1-652d-ad83-54c3-87c6661df8f7@redhat.com> (raw)
In-Reply-To: <20200130181516.GA29782@tik.uni-stuttgart.de>
On 1/30/20 12:15 PM, Ulli Horlacher wrote:
> (I am a UNIX senior admin, but have VERY few knowledge on Windows)
>
> UNIX does not support hard links on directories (in opposite to Windows?).
Windows does not either.
>
> Are this directory hard links?
No, rather they are parallel mount points (the same directory mounted
under two different names).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
--
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
next prev parent reply other threads:[~2020-01-30 18:26 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 [this message]
2020-01-31 10:18 ` Ulli Horlacher
2020-01-31 14:59 ` Brian Inglis
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=f0e439a1-652d-ad83-54c3-87c6661df8f7@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.com \
--cc=framstag@rus.uni-stuttgart.de \
/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).