From: Peter Rehley <peter@rehley.net>
To: cygwin-talk@cygwin.com
Subject: Re: Running 1.5 and 1.7 sshd in parallel
Date: Sat, 27 Jun 2009 06:24:00 -0000 [thread overview]
Message-ID: <56CF5731-4BCF-47F6-B5D9-EAE4FB17BA9D@rehley.net> (raw)
In-Reply-To: <20090627021047.GA1614@ednor.casa.cgf.cx>
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
next prev parent reply other threads:[~2009-06-27 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <690f5ac90906260819j4a977530if44a82324eddc229@mail.gmail.com>
[not found] ` <20090626152445.GP30864@calimero.vinschen.de>
2009-06-26 15:35 ` Christopher Faylor
2009-06-27 1:41 ` Dave Korn
2009-06-27 2:11 ` Christopher Faylor
2009-06-27 6:24 ` Peter Rehley [this message]
2009-06-27 7:56 ` Dave Korn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56CF5731-4BCF-47F6-B5D9-EAE4FB17BA9D@rehley.net \
--to=peter@rehley.net \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).