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 Date: Fri, 13 Oct 2000 08:59:53 -0400 From: Jeffrey Juliano Reply-To: Jeffrey Juliano To: cygwin AT sources DOT redhat DOT com Subject: Re: Newbie: W2K and Mounting problem. Message-ID: <764984234.971427593@[192.168.0.16]> In-Reply-To: <20001012155159.A22871@cygnus.com> X-Mailer: Mulberry/2.0.5b3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline --On Thurs, Oct 12, 2000 3:51 PM -0400 Chris Faylor wrote: > Both the archives and the FAQ should state that if you are using backslash > style paths in a bash shell, you have to either do: I would expect http://sources.redhat.com/cygwin/faq/faq.html#SEC44 to explain it, and failing that, assume it's not mentioned in the FAQ. I wish people would do an archive search before posting for help. (Is that mentioned in the FAQ?) But in this case, perhaps the error message from mount could be improved to make it easier for a newby to figure it out himself. Seems to me (haven't checked the source) that the single backslash sucks up the space character, leaving the mount command with just a single argument. If so, then shouldn't mount dump a usage statement instead of giving the error that it does? If I'm right, I'm willing to volunteer for this one, but not until next week. -jeff -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com