I've noticed that I need to double quote file names in scp:> scp gaelicWizard:"Desktop/Picture 1.pdf" . > scp: Desktop/Picture: No such file or directory > scp: 1.pdf: No such file or directoryWhy is this necessary? Wouldn't it be much better to have scp communicate with its server-side counterpart with null-terminated strings, not to have the server interpret the strings separately? Thanx, JP -- Every time you share on a P2P network, God kills a kitten. Please think of the kittens. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2426 bytes Desc: not available Url : http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20031204/b0b7aa45/attachment.bin
Historical reasons. Refer to how 'rcp' worked, and you'll find it does the same thing. - Ben On Thu, 4 Dec 2003, John Davidorff Pell wrote:> I've noticed that I need to double quote file names in scp: > > > scp gaelicWizard:"Desktop/Picture 1.pdf" . > > scp: Desktop/Picture: No such file or directory > > scp: 1.pdf: No such file or directory > > Why is this necessary? Wouldn't it be much better to have scp > communicate with its server-side counterpart with null-terminated > strings, not to have the server interpret the strings separately? > > Thanx, > JP > > > > -- > Every time you share on a P2P network, God kills a kitten. > Please think of the kittens. > >
Don't use SCP, it's pretty flaky. ssh.com prefers sftp, but I've been grumbling for a scp->tar wrapper. Just do this for now: tar cf - <files/directories> | ssh user at host "cd /path && tar xvf -" It's more awkward to type, but it's much more reliable. --Dan John Davidorff Pell wrote:> I've noticed that I need to double quote file names in scp: > >> scp gaelicWizard:"Desktop/Picture 1.pdf" . >> scp: Desktop/Picture: No such file or directory >> scp: 1.pdf: No such file or directory > > > Why is this necessary? Wouldn't it be much better to have scp > communicate with its server-side counterpart with null-terminated > strings, not to have the server interpret the strings separately? > > Thanx, > JP > > > > -- > Every time you share on a P2P network, God kills a kitten. > Please think of the kittens. > >------------------------------------------------------------------------ > >_______________________________________________ >openssh-unix-dev mailing list >openssh-unix-dev at mindrot.org >http://www.mindrot.org/mailman/listinfo/openssh-unix-dev > >