Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Mon, 13 Nov 2000 14:35:22 -0500
Message-Id: <200011131935.OAA26182@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: earnie_boyd AT yahoo DOT com
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <20001113193253.7701.qmail@web122.yahoomail.com> (message from
	Earnie Boyd on Mon, 13 Nov 2000 11:32:53 -0800 (PST))
Subject: Re: setup drops mount?
References:  <20001113193253 DOT 7701 DOT qmail AT web122 DOT yahoomail DOT com>


> Assuming what?  That the bin directory isn't relative to the user selected root
> mount path?  Or that the mounted bin directory is actually not contained within
> the d:\foo (where d:\foo is the user chosen root mount path) directory but is
> mounted somewhere else?  The way setup operates today, you're screwed if you
> move the bin directory anyway and try to update.  So, maybe if this is an
> update the translation should happen anyway.  But, ...

Yes, this is what I was talking about.

If you want to add code that retains existing mount points *if* they
reflect the "usual" locations of those directories (i.e. they exist
just to set flags), it's OK with me.  That should be simpler than full
support for arbitrary mount tables.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com