Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 17 Feb 2004 16:42:57 -0500 (EST) From: Dick Repasky To: cygwin AT cygwin DOT com Subject: Path issue after umount -c Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes When following two commands are executed in a bash script umount -c C:/cygwin/home/me/experiment/bin/umount -A the second command fails with the error: script.sh: line x: /home/me/experiment/bin/umount: No such file or directory if when the script is run the Cygwin mount points are present in the registry. If try again (restore mounts), close all cygwin processes and manually delete all cygwin keys from the registry (actually CURRENT_USER keys don't matter, LOCAL_MACHINE keys do matter), and run the bash script again, the pair of commands runs without error. So, why after the umount is, is C:/cygwin/home/experiment/bin/umount being abbreviated as /home/experiment/bin/umount? The same thing happens if I run umount -A first and then supply a path to umount -c. Throughout all trials, the entire search path is PATH=/cygdrive/c/home/me/experiment/bin. Thanks, Dick -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/