Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com To: cygwin AT sources DOT redhat DOT com Subject: Re: Setting cygdrive prefix to '/' causes disappearing mounts References: <20000915232050 DOT A8958 AT cygnus DOT com> <20000916002450 DOT A9313 AT cygnus DOT com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 18 Sep 2000 05:11:28 +0900 In-Reply-To: Chris Faylor's message of Sat, 16 Sep 2000 00:24:50 -0400 Message-ID: Lines: 28 X-Mailer: Gnus v5.3/Emacs 19.34 >>> On Sat, 16 Sep 2000 00:24:50 -0400 >>> Chris Faylor said: > She's also probably the most recent person, excluding me, to look at the > mount code. Hmm... with the possible exception of Kazuhiro Fujieda and > Jason Tishler. I know the cause of this problem. `mount_info::read_mounts' can delete all registry keys of which names include the current cygdrive prefix. When I rewrited the mount code sometime ago, I noticed this logic and preserved it. The mount code doesn't allow mount entries under the cygdrive prefix at all. But it let us change the cygdrive prefix into a parent directory of existing mount entries. After that, it rejects them. We have two alternatives to solve this problem. 1. Allow mount entries under the cygdrive prefix. 2. Keep the cygdrive prefix away from parent directories of existing mount entries. I can't find possible problems triggered by the former solution. The latter solution won't let us change the cygdrive prefix into '/'. ____ | AIST Kazuhiro Fujieda | HOKURIKU School of Information Science o_/ 1990 Japan Advanced Institute of Science and Technology -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com