[svlug] help transfering data over 1394 cable

[Rick Moen]

Quoting Daniel Gimpelevich (daniel at gimpelevich.san-francisco.ca.us):

> "something" != "a transport"
> TCP would be the desired transport:

That is a different meaning of the term "transport", in a different
context.  Remember where I said "in _this_ context"?  That's why.

> I would have brought up netcat, as Scott did, if it had some form of
> integrated integrity check.

Why don't you wish it had perpetual motion, while you're at it?  And
maybe a rocket assist.

> > I don't suppose you've noticed that you're not helping?  
> 
> #include "helping.h"
> if (!helping())
> 	meet(pot, kettle);
> else
> 	information.flags |= USEFUL;
> 
> helping.h:
> #define helping() is_grokking(user)

Oh?  _One_ of us provided correct information and a complete recipe for 
moving the file with the desired speed advantage and avoidance of
pointless complexity.  The other of us compared rsync to ssh as
alternatives (possibly not being aware that the first runs _over_ the
second) and advised Christian he'd have to find an "rcp daemon" [sic]
before he could run rcp.

Guess which is which?

> > Since such a thing as an "rcp daemon" doesn't exist, that would indeed
> > be difficult -- and also irrelevant.  What one enables, in fact, is
> > rshd.  (Usually, the binary is named in.rshd , indicating that it's
> > intended to be run under one of the superservers.)
> 
> Semantics...
> I intentionally avoided the above point for brevity.

I believe you misspelled "I gave Christian misleadingly bad information
on a subject I was already aware I knew nothing about."

> > and the need to move 1.5 TB of video
> > files over a private network segment would seem to qualify, too.
> 
> Did anybody mention that the network segment is _not_ private?

Irony alert:  You're recommending _NFS_ for that?  The No Friggin'
Security filesystem?

I was, in fact, going to get around to pointing out precisely that flaw
in Christian's plan:  If he's going to connect the two machines to a
switch that's connected to public networks, then the only network
mechanisms he could reasonably use to move his 1.5 terabytes of video
files would be cryptographically authenticated ones such as scp, sftp,
kerberised ftp, or ftp-ssl (or variants such as FISH).  Which, again,
means he'd better cultivate a _real_ sense of patience, since the
transfer is going to take geologic time.

_Or_ he can do the sensible thing and go buy or borrow a $20 second
ethernet card, so that the data transfer can be over a private network
segment after all, and thus use reasonably fast transfer mechanisms
without exposing his systems to bend-over security.