From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] rsh-0.17-3
Date: Mon, 16 Jul 2018 15:29:00 -0000 [thread overview]
Message-ID: <20180716152920.GC27673@calimero.vinschen.de> (raw)
In-Reply-To: <CANnLRdjVVx2b35iC-q4ktB0nkWZOb0mO3XKPnjTov0RiOpmw+A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2192 bytes --]
On Jul 16 11:09, Stephen John Smoogen wrote:
> On 16 July 2018 at 10:22, cyg Simple <cygsimple@gmail.com> 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?
> >
>
> I don't have any recent proof. Most of mine is 6-8 years old so I
> can't say if they are still in production. I am extrapolating of what
> people ask on IRC and mailing lists at times and going by experience
> of where that software would have been used and why it takes forever
> to get rid of it. [I don't like rsh/rlogin/rcp and would prefer it was
> gone. I just have found that fighting that battle has a very very long
> tail of "oh we still use that... yeah we are running a RSX11
> controller now on an ARM chip but its embedded software only talks rsh
> so lets put an SSH proxy on this windows box and have it rsh to it." ]
>
> I also don't have any recent proof that 90-95% of the software in the
> Cygwin distribution is used anywhere. I just have hearsay that people
> use X and various network servers on it.. so if my proof is needed to
> keep stuff in.. I would expect a lot smaller distribution soon.
... but we could probably fit the entire distro on a CD again ;)
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-07-16 15:29 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 [this message]
2018-07-16 20:14 ` Brian Inglis
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=20180716152920.GC27673@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).