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 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: mount and ln commands Date: Tue, 18 Nov 2003 18:43:13 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: To: , X-OriginalArrivalTime: 18 Nov 2003 18:43:14.0236 (UTC) FILETIME=[D2DD4FC0:01C3AE03] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id hAIIip84004830 I think you'll find the backslash-forwardslash thing is dependant on whether you are running a version of Windoze NT (2000, XP, etc) or Windoze 95 (98, Me, etc). Historical note: The backslash-forwardslash thing was inherited from MS-DOS which inherited it from QDOS, which was itself a (dis)functional copy of CP/M which was often run from terminals with different special character keys than modern PCs. Unix, OTOH, was run on terminals with a different character set and so used the forwardslash as a separator in directory names and the hyphen to mark parameters. [History lesson ends] -----Original Message----- From: Shankar Unni [mailto:shankar@cotagesoft.com] Sent: 18 November 2003 18:25 To: cygwin@cygwin.com Subject: Re: mount and ln commands Erica Ramsey wrote: > $ mount -tf "c:\PalmDev" /PalmDev Use C:\\PalmDev. Or better still, since Windows is really (trust me!) agnostic about this under the command shell skin, use "C:/PalmDev" (i.e. forward slashes). -- 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/ -- 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/