On 2008-04-01 at 18:43 +0100, Dagfinn Ilmari Mannsåker wrote:
Serves him right for not quoting untrusted data properly.
So you never recursively scp data?
scp per SSHv1 and OpenSSH SSHv2 protocol (but not ssh.com SSHv2, where
it's retargeted to use the SFTP protocol backend) uses rcp as the
Back during the whole scp1 versus scp2 fiasco, I got used to using
tar cfz - directory | ssh u...@host sh -c cd $wherever; tar xfz -
Both scp and rsync suffer mightily from hatefully poor layering.
On Tue, Apr 01, 2008 at 05:05:41PM -0500, Peter da Silva wrote:
Both scp and rsync suffer mightily from hatefully poor layering.
What's hateful about rsync?
Nicholas Clark
On 2008-04-01, at 17:16, Nicholas Clark wrote:
What's hateful about rsync?
Unless someone has done a complete rewrite from scratch in the past
couple of years...
The protocol is a horrible mishmash. The only spec is the code.
There isn't (or wasn't) any stream mode, so you can't use the
Peter da Silva wrote:
On 2008-04-01, at 17:16, Nicholas Clark wrote:
What's hateful about rsync?
There isn't (or wasn't) any stream mode, so you can't use the
equivalent of rsync ... - | ssh foo rsync -, instead you have magic
syntax to specify rsh/ssh connections and environment variables
Peter da Silva wrote:
Back during the whole scp1 versus scp2 fiasco, I got used to using
tar cfz - directory | ssh u...@host sh -c cd $wherever; tar xfz -
Tsk tsk.
cd $wherever tar xfpz -
Just in case something bad happened to $wherever since last time.
(I've had a script very much like
David Cantrell wrote:
Filename character limits are also perfectly sensible. Unix, for
example, doesn't let you use / or NUL in filenames, and for all
practical purposes you shouldn't be using a vast number of other
characters either - \'()*;? and so on. Unix will let you shoot
yourself in the
On 2008-04-01, at 18:01, num...@deathwyrm.com wrote:
Certain limits are unavoidable, but allowing more than the basic 26
letters is greatly appreciated by the non-English world.
VMS follows the lead of RSX, and allows the entire RADIX-50 character
set apart from space. What more do you
On Tue, Apr 01, 2008 at 07:01:06PM -0400, num...@deathwyrm.com wrote:
David Cantrell wrote:
Filename character limits are also perfectly sensible. Unix, for
example, doesn't let you use / or NUL in filenames, and for all
practical purposes you shouldn't be using a vast number of other
David Cantrell wrote:
On Tue, Apr 01, 2008 at 07:01:06PM -0400, num...@deathwyrm.com wrote:
David Cantrell wrote:
Filename character limits are also perfectly sensible. Unix, for
example, doesn't let you use / or NUL in filenames, and for all
practical purposes you shouldn't be using a vast
On 2008-04-01, at 18:18, David Cantrell wrote:
Remember when VMS was created.
Released 1977
Now look to see what other OSes cared about non-English speakers at
the time.
IBM had EBCDIC variants for most European languages by 1974. File
names? Files can have names? o_O ;;;
1976: CDC
11 matches
Mail list logo
