Computer Old Farts Forum
 help / color / mirror / Atom feed
From: John Cowan <cowan@ccil.org>
To: coff@tuhs.org
Subject: [COFF] Re: [TUHS] Re: Be there a "remote diff" utility?
Date: Thu, 16 May 2024 07:51:06 -0400	[thread overview]
Message-ID: <CAD2gp_TQjyrDxvRMQ7YXyW0tUQ=-EyVeABwxtAVFKRTijTb6gQ@mail.gmail.com> (raw)
In-Reply-To: <20240516073351.267351FAE3@orac.inputplus.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2411 bytes --]

The Newcastle Connection, aka Unix United, was an early experiment in
transparent networking: see <
https://web.archive.org/web/20160816184205/http://www.cs.ncl.ac.uk/research/pubs/articles/papers/399.pdf>
for a high-level description.  A name of the form "/../host/path"
represented a file or device on a remote host in a fully transparent way.
This was layered on V7 at the libc level, so that the kernel did not need
to be modified (though the shell did, since it was not libc-based at the
time).  MUNIX was an implementation of the same idea using System V as the
underlying system.

This appears to be a VHS vs. Betamax battle: NFS was not transparent, but
Sun had far more marketing clout.  However, the Manchester Connection
required a single uid space (as far as I can tell), which may also have
been a (perceived) institutional barrier.

On Thu, May 16, 2024 at 3:34 AM Ralph Corderoy <ralph@inputplus.co.uk>
wrote:

> 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.
>

[-- Attachment #2: Type: text/html, Size: 3361 bytes --]

       reply	other threads:[~2024-05-16 11:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.BSF.2.21.9999.2405161623130.15285@aneurin.horsfall.org>
     [not found] ` <202405160651.44G6pi8G018059@freefriends.org>
     [not found]   ` <20240516073351.267351FAE3@orac.inputplus.co.uk>
2024-05-16 11:51     ` John Cowan [this message]
2024-05-16 13:45       ` Dan Cross
2024-05-16 14:03         ` Larry McVoy
2024-05-16 14:43         ` John Cowan
2024-05-16 14:49           ` Dan Cross

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='CAD2gp_TQjyrDxvRMQ7YXyW0tUQ=-EyVeABwxtAVFKRTijTb6gQ@mail.gmail.com' \
    --to=cowan@ccil.org \
    --cc=coff@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).