public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 0/7] Remove network test for ancient software
Date: Wed, 25 Oct 2017 10:59:31 +0200	[thread overview]
Message-ID: <20171025085931.GC5969@rei> (raw)
In-Reply-To: <CAL+h-jATfeJYYLa26c8TR5msL+cr9SJBLjZX17OQpNuU5KVvyQ@mail.gmail.com>

Hi!
> fwiw, rsh/rcp are still used in the embedded world where security is not a
> concern, but speed/size matters much more (e.g. development)

The question is how much do we care about maintaing the testcases for
these. I guess that rsh and rcp may be still useful in a certain cases
but for a general usage it has been replaced by scp and ssh long time
ago.

-- 
Cyril Hrubis
chrubis@suse.cz

      parent reply	other threads:[~2017-10-25  8:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 13:49 [LTP] [RFC PATCH 0/7] Remove network test for ancient software Petr Vorel
2017-10-18 13:49 ` [LTP] [RFC PATCH 1/7] net/tcp_cmds: Remove rwho test Petr Vorel
2017-10-25 15:16   ` Alexey Kodanev
2017-10-26  8:36     ` Petr Vorel
2017-10-26 12:57       ` Alexey Kodanev
2017-10-26 14:25         ` Petr Vorel
2017-10-18 13:49 ` [LTP] [RFC PATCH 2/7] net/tcp_cmds: Remove rdist test Petr Vorel
2017-10-18 13:49 ` [LTP] [RFC PATCH 3/7] net/tcp_cmds: Remove rlogin test Petr Vorel
2017-10-18 13:49 ` [LTP] [RFC PATCH 4/7] net/tcp_cmds: Remove rsh test Petr Vorel
2017-10-18 13:49 ` [LTP] [RFC PATCH 5/7] net/tcp_cmds: Remove rcp test Petr Vorel
2017-10-18 13:50 ` [LTP] [RFC PATCH 6/7] net/tcp_cmds: Remove finger test Petr Vorel
2017-10-18 13:50 ` [LTP] [RFC PATCH 7/7] net/tcp_cmds: Remove echo test Petr Vorel
2017-10-18 20:31 ` [LTP] [RFC PATCH 0/7] Remove network test for ancient software Mike Frysinger
2017-10-19  9:33   ` Petr Vorel
2017-10-25  8:59   ` Cyril Hrubis [this message]

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=20171025085931.GC5969@rei \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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