From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28915 invoked by alias); 27 Jun 2009 06:24:14 -0000 Received: (qmail 28904 invoked by uid 22791); 27 Jun 2009 06:24:13 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Received: from artdemusee.com (HELO rehley.net) (66.36.178.154) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Sat, 27 Jun 2009 06:24:04 +0000 Received: (qmail 11673 invoked from network); 26 Jun 2009 23:26:43 -0700 Received: from adsl-76-254-6-164.dsl.pltn13.sbcglobal.net (HELO peacock.guava.local) (76.254.6.164) by artdemusee.com with SMTP; 26 Jun 2009 23:26:43 -0700 Message-Id: <56CF5731-4BCF-47F6-B5D9-EAE4FB17BA9D@rehley.net> From: Peter Rehley To: cygwin-talk@cygwin.com In-Reply-To: <20090627021047.GA1614@ednor.casa.cgf.cx> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Subject: Re: Running 1.5 and 1.7 sshd in parallel Date: Sat, 27 Jun 2009 06:24:00 -0000 References: <690f5ac90906260819j4a977530if44a82324eddc229@mail.gmail.com> <20090626152445.GP30864@calimero.vinschen.de> <20090626153538.GF30070@ednor.casa.cgf.cx> <4A457BB5.4020109@gmail.com> <20090627021047.GA1614@ednor.casa.cgf.cx> X-IsSubscribed: yes Mailing-List: contact cygwin-talk-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: cygwin-talk-owner@cygwin.com Reply-To: The Vulgar and Unprofessional Cygwin-Talk List Mail-Followup-To: cygwin-talk@cygwin.com X-SW-Source: 2009-q2/txt/msg00052.txt.bz2 On Jun 26, 2009, at 07:10 PM, Christopher Faylor wrote: > On Sat, Jun 27, 2009 at 02:53:57AM +0100, Dave Korn wrote: >> Christopher Faylor wrote: >>> On Fri, Jun 26, 2009 at 05:24:45PM +0200, Corinna Vinschen wrote: >>>> On Jun 26 17:19, Federico Hernandez wrote: >>>>> Couldn't find anything on this: >>>>> >>>>> Would it be possible to run sshd 1.5 and 1.7 in parallel so one >>>>> could >>>>> ssh into cygwin 1.5 and 1.7 on the same machine at the same >>>>> time. Of >>>>> course on ssh would have to run on a different port. How would >>>>> one >>>>> setup this? >>>> Let the sshds use different ports, for instance 22 and 2022. >>> >>> And if that doesn't work we'll certainly work non-stop, around the >>> clock to make sure that this crucial functionality is implemented. >>> >>> Maybe we need a new mailing list to deal with this issue. >> >> Whaddaya want? Inferential reasoning or something? > > No, actually, I want 1.5, 1.7, and B20 to all work on the same machine > at the same time. Is that too much to ask? > > cgf Don't forget 1.3. For complete compatibility they all need to work .... in the same way. Peter