Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-Id: <5.1.0.14.2.20021015073457.01fd7d68@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Tue, 15 Oct 2002 07:37:46 -0700 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: Re: cygwin copy In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Michael, % cygcheck mount Found: D:\cygwin\bin\mount.exe D:\cygwin\bin\mount.exe D:\cygwin\bin\cygwin1.dll D:\WINNT\System32\KERNEL32.dll D:\WINNT\System32\NTDLL.DLL Does this not mean that the mount command does use Cygwin1.dll? Randall Schulz Mountain View, CA USA At 07:00 2002-10-15, Michael A Chase wrote: >On Tue, 15 Oct 2002 09:51:01 -0400 (EDT) Igor Pechtchanski > wrote: > > > It's interesting that all three replies to this message mentioned the > > registry... While Vince should only have mentioned that it's *currently* > > held in the registry, Pavel actually recommended exporting it. As I've > > been mildly chided for this before, here's an equivalent registry-free > > solution: > > > > On the source machine: > > $ mount -m > restore_mounts.sh > > On the target: > > $ ./restore_mounts.sh > > (after the appropriate file transfer, of course). > > > > I should mention that Fergus's solution with setup.exe should also work. > >You could also create restore_mounts.bat the same way and run it in a MSDOS >window. The mount command does not depend on cygwin1.dll and the `mount >-m` output should work under MSDOS 'shells' as well as under Cygwin shells. > >-- >Mac :}) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/