Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 20 Apr 2004 22:35:16 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Emulating hard links on FAT et al.
Message-ID: <20040420203516.GB31665@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <F76C9B2DA2FC4C4CA0A18E288BBCBCF7082177FA AT nihexchange24 DOT nih DOT gov> <00da01c42709$d9daca80$66fda287 AT docbill002>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00da01c42709$d9daca80$66fda287@docbill002>
User-Agent: Mutt/1.4.2i

On Apr 20 15:00, Bill C. Riemers wrote:
> One obvious thing hard links allow is a way to have the same file with
> different permissions.  With a symbolic link you need both access
> permissions for the symbolic link and actual file.  i.e.
> 
>   ln -s /tmp/foo.exe /home/bcr/foo.exe
>   chmod ugo-x /tmp/foo.exe
>   chmod ugo+x /home/bcr/foo.exe
> 
> With a hardlink, you only need access permissions for the hardlink...

That's not how it works.  Hardlinks are nothing but multiple directory
entries for the same file.  The directory entry typically only consists
of a name and a inode number.  The inode contains the file specific
control information.  Obviously hardlinks to the same file point to
the same inode.  Therefore all hardlinks to the same file have the same
permissions, owner, etc, since it's *one* file with *one* owner and *one*
set of permissions.  And, yes, it's implemented on NTFS like this.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/