X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Matthew Woehlke Subject: Re: when to use a ln or a mount Date: Mon, 12 Mar 2007 09:49:33 -0600 Lines: 34 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.10) Gecko/20070221 Thunderbird/1.5.0.10 Mnenhy/0.7.4.0 In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 zzapper wrote: > Hi, > In my confused mind ln and mount seem to achieve the same thing. > In my case I want to have an easy to type path(s) to my old pc > > so I typed:- > > mount -f -u -b "//dell25/c/" "/o" > > but I also tested > > ln -s //dell25/c/ /old > > In the Cygwin context does one method have any advatanges over the over? One is probably faster (meaning how long it takes to resolve the Cygwin path to one Windows understands), though I couldn't tell you which. Also unless you are running configure scripts, or doing something else that needs to do such conversions thousands of times, quickly, you won't notice a difference. In the UNIX world the convention is to use symlinks often and binds infrequently (although I wouldn't consider this particular case a "bind"). There is also a limit to the number of mounts you can do on Cygwin. In this case, what you are doing is effective to mounting a remote file system, so "mount" would be traditional (and also your only choice on most UNIX's, which don't understand UNC paths). However, as you've noticed, either one works on Cygwin. :-) -- Matthew Emacs is a nice OS - but it lacks a good text editor. That's why I am using Vim. -- Anonymous -- 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/