This is the mail archive of the email@example.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: mount command
- To: <firstname.lastname@example.org>
- Subject: Re: mount command
- From: "Richard Lyon" <email@example.com>
- Date: Thu, 25 Mar 1999 10:37:47 +1000
- Delivered-To: firstname.lastname@example.org
- Delivered-To: mailing list email@example.com
- Mailing-List: contact firstname.lastname@example.org; run by ezmlm
- Sender: email@example.com
See comments below:
From: DJ Delorie <firstname.lastname@example.org>
To: email@example.com <firstname.lastname@example.org>
Cc: email@example.com <firstname.lastname@example.org>
Date: Tuesday, 23 March 1999 7:36
Subject: Re: mount command
>You're using bash's builtin mkdir (or cygwin's mkdir.exe), and it's
>using the mount table. You need to use MS's shell so it won't know
>about the mount table.
OK, I tried doing it from explorer, the MS command prompt and bash.
After mounting the partition, the mount point works correctly for things
like -I option in gcc and cygpath. So I believe I have done the correct
thing. It's the
find command that doesn't work. I even get stranger results if I attempt
something like mount D:/topdirectory /home. Find generates the following
find: /home/filename: No such file or directory
for every file in topdirectory.
I have 20.1 installed.
Luckily it does appear I can use cygpath in install script to cope with
It converts the paths correctly to win32 format which work with find and
I consider this sort of behaviour as a bug. Before I consider filing a bug
report or maybe
trying to fix it, has anyone managed to get find to work across mounted
Want to unsubscribe from this list?
Send a message to email@example.com