This is the mail archive of the
mailing list for the Cygwin project.
Re: mount's --change-cygdrive-prefix option (was Re: text / binary mounts (sorry))
- To: Cygwin <cygwin at sourceware dot cygnus dot com>
- Subject: Re: mount's --change-cygdrive-prefix option (was Re: text / binary mounts (sorry))
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Tue, 6 Jun 2000 17:17:51 -0400
- References: <email@example.com>
- Reply-To: cygwin at sourceware dot cygnus dot com
On Tue, Jun 06, 2000 at 02:01:02PM -0700, Earnie Boyd wrote:
>--- Jason Tishler <Jason.Tishler@dothill.com> wrote:
>> 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
>> 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.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org