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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: jorg DOT schaible AT db DOT com X-Lotus-FromDomain: DMG UK AT DEUBAINT To: cygwin AT sourceware DOT cygnus DOT com Message-ID: <002568CE.003F5257.00@sdbo1003.srv.uk.deuba.com> Date: Thu, 27 Apr 2000 11:31:36 +0000 Subject: mount policy Mime-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id FAA27080 Hello, after installing the new 1.1.0 version I recognized the binary mounts created by setup (or the cygwin1.dll). Up to now I worked with the B20.1 and have always used text based mounts and had never problems. What advantage do I have in which situation from a binary mount especially because I read other users having problems with make, etc. ? I also used to have the following mount mount $TEMP /tmp to sync the temporary directories for Windows and Cygwin. Should I prefer here a symbolic link ? Pros & cons for mount vs. ln ? Regards, Jörg -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com