public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] rsh-0.17-3
Date: Mon, 16 Jul 2018 20:14:00 -0000	[thread overview]
Message-ID: <0e847d25-7c0a-0f77-dd2f-48a4d354b676@SystematicSw.ab.ca> (raw)
In-Reply-To: <fdaa9599-27da-6504-8ee0-586672beb236@gmail.com>

On 2018-07-16 08:22, cyg Simple wrote:
> On 7/16/2018 10:02 AM, Stephen John Smoogen wrote:
>> Most of the rsh usage is going to be legacy hardware and systems which
>> various places still have in good numbers. Various industrial and lab
>> components might have been built in 1995 and is slower than your
>> iphone but the replacement costs tens or hundreds of millions of
>> dollars... (and still uses rsh for backwards compatibility). Payroll
>> systems in other places use rsh and rcp and cost large amounts to
>> 'upgrade'. The people running these don't show up mailing lists
>> because they may not even know that the system uses rsh/telnet or some
>> other obscure thing.. they just run a script on a Windows desktop that
>> someone wrote years ago. They only show up when stuff stops working.
> But are those scripts Cygwin?  I doubt they are.  Do you have proof of any?

More likely to be command scripts and NT/XP rcp/rexec/rsh utilities which I
wrote and used in NT/XP days before OpenSSH.
It's more likely those would be replaced in legacy systems with standalone
MinGW/native versions than a suite requiring Cygwin.
As Corinna says that's no reason not to let people shoot themselves in the foot.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

  parent reply	other threads:[~2018-07-16 20:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-15 19:55 Takashi Yano
2018-07-16  8:35 ` Achim Gratz
2018-07-16  8:49   ` Takashi Yano
2018-07-16  9:03     ` Achim Gratz
2018-07-16  9:16       ` Corinna Vinschen
2018-07-16  9:33         ` Corinna Vinschen
2018-07-16 13:54           ` cyg Simple
2018-07-16 14:02             ` Stephen John Smoogen
2018-07-16 14:22               ` cyg Simple
2018-07-16 15:09                 ` Stephen John Smoogen
2018-07-16 15:29                   ` Corinna Vinschen
2018-07-16 20:14                 ` Brian Inglis [this message]
2018-07-16 16:06             ` Takashi Yano
2018-07-16 16:40               ` cyg Simple
2018-07-17  8:25               ` Corinna Vinschen
2018-07-19 11:32                 ` Takashi Yano
2018-07-16 15:45           ` Achim Gratz
2018-07-17  8:27             ` Corinna Vinschen
2018-07-16 10:06         ` Achim Gratz
2018-07-16 10:22           ` Corinna Vinschen
2018-07-19 11:58 ` Takashi Yano
2018-07-26 18:45 ` Andrew Schulman

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=0e847d25-7c0a-0f77-dd2f-48a4d354b676@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-apps@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).