Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Tue, 6 Jun 2000 17:17:51 -0400
To:	Cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Re: mount's --change-cygdrive-prefix option (was Re: text / binary mounts (sorry))
Message-ID:	<20000606171751.A30312@cygnus.com>
Reply-To:	cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To:	Cygwin <cygwin AT sourceware DOT cygnus DOT com>
References:	<20000606210102 DOT 24531 DOT qmail AT web124 DOT yahoomail DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.2i
In-Reply-To:	<20000606210102.24531.qmail@web124.yahoomail.com>; from earnie_boyd@yahoo.com on Tue, Jun 06, 2000 at 02:01:02PM -0700

On Tue, Jun 06, 2000 at 02:01:02PM -0700, Earnie Boyd wrote:
>--- Jason Tishler <Jason DOT Tishler AT dothill DOT com> wrote:
>-8<-
>> The tougher issue is the desired semantics when reading the cygdrive
>> path prefix from the registry.  That is, what should be the
>> functionality of read_cygdrive_info_from_registry ():
>> 
>> 1. Should it search for the system path prefix and if not found,
>> then search for the user path prefix?  Or, should it search for the
>> user path prefix and then the system?
>> 
>> 2. When no path prefixes are found should it default the system path
>> prefix?  Or, should it default the user path prefix (as it currently
>> does)?
>> 
>> Any thoughts?
>
>The data supplied by the user in the user path prefix should override anything
>set in the system prefix and if the user path prefix doesn't exist the system
>path prefix should be used.  If neither system or user prefixes exist already
>then the initialization should continue to create the user path prefix.

That's correct.  In other words, the path prefix semantics should mirror the
regular mount semantics.

cgf

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

- Raw text -