X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 17 Mar 2010 19:28:40 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin 1.7: why there is a directory E/cygwin/dev in the tree   of  	cygwin ?
Message-ID: <20100317182840.GW6505@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <485797401003160836l4a74aee2q527fa059765502a9 AT mail DOT gmail DOT com>  <20100316154432 DOT GB18610 AT ednor DOT casa DOT cgf DOT cx>  <416096c61003160854v4f18669ep57635447a8b55061 AT mail DOT gmail DOT com>  <4B9FE12F DOT 4020008 AT hones DOT org DOT uk>  <485797401003170119v484779f0p28304ffe1491951 AT mail DOT gmail DOT com>  <4BA11DB7 DOT 8030804 AT redhat DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BA11DB7.8030804@redhat.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Mar 17 12:21, Eric Blake wrote:
> On 03/17/2010 02:19 AM, rolandc wrote:
> > I do not understand why the postinstall script bash.sh is so complex
> > 
> >     DEVDIR="$(cygpath -au "C:/$(cygpath -am /dev/)" | sed 's|/c/\(.\):/|/\1/|')"
> >     mkdir -p "$DEVDIR" || result=1
> > 
> > it would be simple (too simple?) to
> >     mkdir -p /dev || result=1
> 
> Yes, it would be too simple.  /dev already exists, so the mkdir would
> fail to do anything useful.  We REALLY want to create the underlying
> Windows directory at the same location at where /dev would be mounted,
> and to do that, we really do want to know the windows location (drive
> letter and all) of /.  Then, by using mkdir of that fancy windows path
> that happens to live at the same place as where /dev normally resolves
> to, then we can guarantee that /dev/stdin gets created as an actual
> symlink in the windows heirarchy (since it does NOT resolve via the /dev
> magic mount point), and that tab-completion can see any contents placed
> into the windows counterpart directory.

Nothing of this should be necessary since the 000-cygwin-post-install.sh
script from the base-cygwin package already creates /dev.


Corinna

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

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