DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=QxkIyPvgnAhITaVjJFe9Xt6UqVA232b8q4HlZMFrK1/
	7lLYc/aopw/ZHrDQ1jSyqfXjxOa7eh5m6qJbDO3ue7fdLhfULRA1zn+DRCTQ1KLh
	+wiNNG0o4QklmpePzZLrXA7vO4isCo49TcpLRWrcR1j+wCsAgO1RNML5em64NyOs
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5342EF9A.7050409@tlinx.org>
Date: Mon, 07 Apr 2014 11:34:02 -0700
From: Linda Walsh <cygwin@tlinx.org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Request for Junctions be treated consistently
References: <5336C0DF.5080102@tlinx.org> <5336C23B.2070309@tlinx.org> <20140331102745.GD23383@calimero.vinschen.de> <533AEBD6.3040209@tlinx.org> <20140402084026.GM2508@calimero.vinschen.de> <533FE56D.5010809@tlinx.org> <20140407092342.GF2061@calimero.vinschen.de>
In-Reply-To: <20140407092342.GF2061@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Corinna Vinschen wrote:
> Look, directory reparse points are, by and large, symlinks to another,
> real directory entry.  The directory has a primary path, which is its
> own path under which it has been created, and the reparse point is just
> a pointer to this directory.  If that's not a symlink, what is?
---
	What is a mount 'bind' on linux?

	You could call it a symlink, but it acts like a mount.
Since both mountd and mountvol form "junctions", and not "symlinks (
as when you use 'mklink'), I'm asking the the junctions be treated
as volume mount points -- or like 'bind' on linux.  That way,
I can mount parts of the file system in common in multiple locations
and not have to worry about all the utilities that overwrite symlinks
instead of following them.

	But it was intended to allow grafting of the file system
into different locations for ease of administration.  Treating them
the same as symlinks removes that ability because most or many of
the linux utils will overwrite symlinks rather than follow them
as they would if it was a mount.


--
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