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 sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Tue, 20 Feb 2001 18:14:24 -0800 (PST) From: Doug Kaufman To: Earnie Boyd Subject: Re: lynx-dev Lynx tries to use a weird "cp" copy program whendownloadingfiles. In-Reply-To: <3A92E854.4C7FBD58@yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 20 Feb 2001, Earnie Boyd wrote: > Doug Kaufman wrote: > > > > On Tue, 20 Feb 2001, Earnie Boyd wrote: > > > > > Doug Kaufman wrote: > > > > > > > > On Tue, 20 Feb 2001, Malcolm Boekhoff wrote: > > > > > > > > > I can't get lynx to download anything using the default "save to > > > > > disk" option. > > > > > ... > > > > > If I type "lynx http://www.cygwin.com/setup.exe" and > > > > > then use the default "save to disk" option, the file appears to get > > > ... > > > Please note: It is advised to halt all Cygwin processes before updating > > > Cygwin. You will certainly run into problems with having Cygwin > > > processes executing while trying to update them. > > > > You lost me here. Where were we updating cygwin? > > That's what http://cygwin.com/setup.exe does, updates Cygwin and the > executables using it. You can't replace files that are open and files > that are executables are open while they are executing. > > After re-reading I see that the problem is that the lynx program used > hard coded paths as they existed in previous Cygwin versions. However, > if Lynx performs an execution of the file downloaded then my statement > stands true. Now I see what you are talking about. Lynx can't execute a program it receives, except in the unusual situation where someone has set their mailcap to execute files with ".exe" extension. Lynx downloads files to a temp directory, then copies to final destination (when the action is "save to file"). The only problem here seems to be that "cp" wasn't in the location hardcoded into the lynx binary. Creating a link to "cp" in the location the binary expects should solve the problem without creating any new ones. Doug P.S. I am on the lynx-dev list, but not on the cygwin list. I'll look for anything further in the archives, but replies from me might be a little delayed. __ Doug Kaufman Internet: dkaufman AT rahul DOT net -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple