Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Tue, 6 Jun 2000 17:17:51 -0400 To: Cygwin Subject: Re: mount's --change-cygdrive-prefix option (was Re: text / binary mounts (sorry)) Message-ID: <20000606171751.A30312@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: Cygwin References: <20000606210102.24531.qmail@web124.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 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@sourceware.cygnus.com