Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 14 Apr 2005 13:33:10 +0200 From: Corinna Vinschen To: Cygwin List Subject: Re: cygwin on Mac: files in Virtual PC "shared folder" Message-ID: <20050414113310.GB5908@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: Cygwin List References: <3d0b16f3b50f2acdb38a5479b9813ce4@dcs.warwick.ac.uk> <6.2.1.2.0.20050413180131.03cf4bf8@pop.prospeed.net> <6c620aa8a3e08df24c9dd17cf8f27c83@dcs.warwick.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6c620aa8a3e08df24c9dd17cf8f27c83@dcs.warwick.ac.uk> User-Agent: Mutt/1.4.2i On Apr 14 10:54, Ashley Ward wrote: > 2) The '\' character used in Windows share names is an escape character > to bash -- so the example "mount \\pollux\home\joe\data /data" in the > cygwin manual (example 3.10) is misleading. For me, that style of > example gives error messages about "/data", not the Windows share > (actually the cause of the problem), which doesn't help. I do see the > mentions in manual around that point about using the Windows command > shell (presumably with the cygwin bin in the PATH?) and also about > using '/' rather than '\', but it doesn't seem very clear to me -- > perhaps the example could be changed to "mount '\\pollux\home\joe\data' > /data"? Erm... *cough, cough*, you're not a slave of the user manual, right? Why not just try it? Using forward slashes or \\ in bash seems quite natural to me. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/