X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Message-ID: <4C76C35C.8090503@coastside.net> Date: Thu, 26 Aug 2010 12:41:16 -0700 From: Blaine Miller User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: How/Where do I get an older version of Cygwin? References: <4C76B56E DOT 3030702 AT coastside DOT net> <4C76BC59 DOT 6070501 AT cygwin DOT com> <4C76C031 DOT 1000802 AT coastside DOT net> In-Reply-To: <4C76C031.1000802@coastside.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: ecf88e7cc6fd12df69adbcfd4248abb35e89bb4777695beb00ff6c36d42eb1fab7a8c81eb6d2e895ac64e7af9e82d099350badd9bab72f9c350badd9bab72f9c X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Larry, Again, I agree. I'm between a rock and a hard place here. I have to prove it's not the current version of Cygwin (also read *free*) and new hardware (read *costs them some money*). I have related to you and others at Cygwin user list both of my issues of cron possibly causing a system fault and can't kill the ssmtp dead.letter running over. I will pass along that I'm on my own with the regression to the older version. Perhaps that'll wake them up... I dunno. I'm just in the middle. Thanks again for your support and assistance. Blaine Blaine Miller wrote: > Larry, > > I agree with you 100%. I'm getting heat from the folks above me to get > Cygwin up and operational. We're using it to scp and rsync files from > several linux boxes to a Cygwin-ed Windows 2003 box. Then we run > Symantec Backup Exec for Windows to do tape backups of the resulting > transferred files. > > Nothing I've said seem capable of convincing them that the problem is > other than Cygwin. I keep pointing out we've replaced everything > excpet the server hardware. > > Aside from downgrading and proving that the older version will have > the same problems, I have no alternative at this time. > > Again, I believe that the new(er) version is the way to go. But I need > to kill the cron issue and the ssmtp issue before I can demonstrate > that the new version is not the problem and the hardware may be the > real issue. > > Thanks for your continued support and assistance... > > Blaine > > Larry Hall (Cygwin) wrote: >> On 8/26/2010 2:41 PM, Blaine Miller wrote: >>> I'm having cron and ssmtp issues with the new(er) version of Cygwin, >>> 1.7.x.y. >>> Barring getting these items straightened out, how do I revert to an >>> older >>> version? >>> >>> I've been installing from a network setup.exe. I don't believe this >>> leaves a >>> copy on a local system. My co-workers tell me there has to be a way to >>> retrograde to an older version. >>> >>> Can anyone point me in the right direction? An older version of >>> setup.exe >>> perhaps? >> >> I'm not sure why you believe your problems are based in recent Cygwin >> versions but if you wanted to backtrack to 1.5.x, see this link: >> >> >> >> This an unsupported version of 1.5.x so if you go there, you're on >> your own. >> If your problems truly are the result of some recent change to >> Cygwin, your >> best bet is to investigate them, report the problems, and work to get >> them >> resolved, especially if something has regressed. Otherwise, you'll be >> stuck in the past forever without an upgrade path. >> > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple