The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ralph Corderoy <ralph@inputplus.co.uk>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Be there a "remote diff" utility?
Date: Thu, 16 May 2024 08:33:51 +0100	[thread overview]
Message-ID: <20240516073351.267351FAE3@orac.inputplus.co.uk> (raw)
In-Reply-To: <202405160651.44G6pi8G018059@freefriends.org>

Hi,

I've set ‘mail-followup-to: coff@tuhs.org’.

> > Every so often I want to compare files on remote machines, but all
> > I can do is to fetch them first (usually into /tmp); I'd like to do
> > something like:
> >
> >     rdiff host1:file1 host2:file2
> >
> > Breathes there such a beast?

No, nor should there.  It would be slain less it beget rcmp, rcomm,
rpaste, ...

> > Think of it as an extension to the Unix philosophy of "Everything
> > looks like a file"...

Then make remote files look local as far as their access is concerned.
Ideally at the system-call level.  Less ideal, at libc.a.

> 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

    This computer system is the property of ...

    Disconnect NOW if you have not been expressly authorised to use this
    system.  Unauthorised use is a criminal offence under the Computer
    Misuse Act 1990.

    Communications on or through ...uk's computer systems may be
    monitored or recorded to secure effective system operation and for
    other lawful purposes.

It appears on stderr so doesn't upset the diff but does clutter.
And discarding stderr is too sloppy.

-- 
Cheers, Ralph.

  reply	other threads:[~2024-05-16  7:34 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 [this message]
2024-05-16  8:59     ` George Michaelson
2024-05-16  9:01     ` arnold
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=20240516073351.267351FAE3@orac.inputplus.co.uk \
    --to=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).