The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: tuhs@tuhs.org, ralph@inputplus.co.uk
Subject: [TUHS] Re: Be there a "remote diff" utility?
Date: Thu, 16 May 2024 03:01:11 -0600	[thread overview]
Message-ID: <202405160901.44G91CN0007274@freefriends.org> (raw)
In-Reply-To: <20240516073351.267351FAE3@orac.inputplus.co.uk>

Ralph Corderoy <ralph@inputplus.co.uk> wrote:

> > Maybe
> >
> >     diff -u <(ssh host1 cat file1) <(ssh host2 cat file2)
>
> This is annoyingly noisy if the remote SSH server has sshd_config(5)'s
> ‘Banner’ set which spews the contents of a file before authentication,
> e.g. the pointless
>
> [....]
>
> It appears on stderr so doesn't upset the diff but does clutter.

All true, I didn't think about that.

> And discarding stderr is too sloppy.

But the author of a personal script knows his/her remote machines
and can decide if

     diff -u <(ssh host1 cat file1 2>/dev/null) <(ssh host2 cat file2 2>/dev/null)

is appropriate or not.

My main point was that the problem is easily solved with a
few lines of shell, so no need for a utility, especially one
written in C or some other compiled language.

Thanks,

Arnold

  parent reply	other threads:[~2024-05-16  9:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16  6:34 [TUHS] " Dave Horsfall
2024-05-16  6:51 ` [TUHS] " arnold
2024-05-16  7:33   ` Ralph Corderoy
2024-05-16  8:59     ` George Michaelson
2024-05-16  9:01     ` arnold [this message]
2024-05-16 17:08       ` ron minnich
2024-05-16 18:51         ` Skip Tavakkolian
2024-05-16 19:51           ` Marc Donner
2024-05-16 19:53 ` Theodore Ts'o
2024-06-19 23:20   ` Alan D. Salewski
2024-05-16 12:31 Douglas McIlroy
2024-05-16 17:12 ` Bakul Shah via TUHS
2024-05-16 18:12   ` Rich Salz
2024-05-16 18:38     ` Ben Greenfield via TUHS

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=202405160901.44G91CN0007274@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=ralph@inputplus.co.uk \
    --cc=tuhs@tuhs.org \
    /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 NNTP newsgroup(s).