Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: 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: Chris Faylor Date: Mon, 30 Aug 1999 11:17:56 -0400 To: "Charles S. Wilson" Cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: New snapshots and old binaries Message-ID: <19990830111756.A2124@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: "Charles S. Wilson" , cygwin AT sourceware DOT cygnus DOT com References: <37C98524 DOT 6A62A265 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <37C98524.6A62A265@ece.gatech.edu>; from Charles S. Wilson on Sun, Aug 29, 1999 at 03:08:20PM -0400 On Sun, Aug 29, 1999 at 03:08:20PM -0400, Charles S. Wilson wrote: >Will I need to recompile ALL of these libraries and executables before >my system returns to "normal", or what? If the DLL is named cygwin1.dll it will be backwards compatible. If the cygwin DLL does not work with a .exe that uses cygwin1.dll then that's a bug in the DLL. The biggest change in using the snapshot will be that the mounts will be migrated to a new place in the registry but that should be transparent, too. I have seen occasional reports from people who indicated that they supposedly had problems with mount tables after upgrading to a snapshot but I've never had a clear idea what the problems are. The other thing that you may notice is that unmounted directories will be referred to as something like /cygdrive/c/foo rather than //c/foo although it is still (temporarily) permissable to use //c as a valid pathname. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com