The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Be there a "remote diff" utility?
Date: Thu, 16 May 2024 13:53:09 -0600	[thread overview]
Message-ID: <20240516195309.GB287325@mit.edu> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2405161623130.15285@aneurin.horsfall.org>

On Thu, May 16, 2024 at 04:34:54PM +1000, Dave Horsfall wrote:
> 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?  I see that Penguin/OS has already taken 
> "rdiff" which doesn't seem to do what I want.

rdiff is something which someone on the internet had created, as part
of the librsync package[1].  Thia isn't considered part of the core
package (for example, Debian consideres it as an "optional" package)
but rather something which various distributions have packaged for the
convenience for their users.

[1] https://librsync.github.io/

So if this is considered part of Penguin/OS, would we also consider
"nethack" or X11 part of BSD 4.3, since it was available and often
would be commonly installed on BSD 4.3 systems?  Or are all packages
which are in FreeBSD's ports "part of FreeBSD"?  Or all packages in
MacPorts part of MacOS?

In any case, the way I'd suggest that you do this that works as an
extention to the Unix philosohy of "Everything looks like a file" is
to use FUSE:

sshfs host1:/ ~/mnt/host1
sshfs host2:/ ~/mnt/host2
diff ~/mnt/host1/file1 ~/mnt/host2/file2

Cheers,

					- Ted

  parent reply	other threads:[~2024-05-16 19:58 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
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 [this message]
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=20240516195309.GB287325@mit.edu \
    --to=tytso@mit.edu \
    --cc=dave@horsfall.org \
    --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).