Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Does the server actually have an apostrophe ( ' ) in the name, or is that just an example? If it does, that's probably part of the problem. The shell is probably interpreting that as the beginning of a string. Try escaping it:
That's odd, because I went to go try it myself. Here's what I got:
$ scp test.txt helmet@spaceball1:/home/helmet/no_exist/test.txt
scp: /home/helmet/no_exist/test.txt: No such file or directory
Very odd indeed, because if my version were acting like yours, then I would have expected to see:
scp: helmet@spaceball1home/helmet/no_exist/test.txt: No such file or directory
That suggests there's something kinda funky going on... maybe scp is not interpreting the destination path correctly. Are there any special characters being used on the command line, like double quotes, or the like? Something that might cause confusion?
And for the record, my version of scp:
$ ssh -V
OpenSSH_3.9p1, OpenSSL 0.9.7e 25 Oct 2004
bash-3.00# ssh -V
OpenSSH_3.9p1, OpenSSL 0.9.7e 25 Oct 2004
Oh lol, he just reminded me...is now a bad time to mention that he's on a mac using its unix /bin/bash. Not sure if it matters though, seeing as he's able to ssh and sftp. His ssh -V says:
OpenSSH_3.6.1p1+CAN-2004-0175, SSH protocols 1.5/2.0, OpenSSL 0x0090702f
At this point, I think it's pretty clear there's something fubar'ed with his client. I don't know if he's using a linux box with a strange/old version of the ssh suite, or if he's using a windows client that needs some reconfiguring, but there's something wrong on his side.
I'll look the other way if you want to start bludgeoning at this point.
EDIT: That could be the problem. Mac ports (I have heard) are not always 100% faithful reproductions of their original unix counterparts. I would check the man page for his scp documentation. He may need to break up his command. For instance, he may need to do something like:
scp -u brian -ra foo'd test.txt /home/brian
Again, just an example, it will probably be different. In other words, specifying the user name with a command line option, the server to connect to, etc.
Unfortunately, I don't have any first-hand experience with a Mac, and can't give anything more than that...
Last edited by Dark_Helmet; 01-28-2005 at 09:50 PM.
Yeah, if he can ssh, then his version should be capable of handling the protocols to copy the file. Even doubly so if he can sftp (because an scp should be a trivial ftp connection). My guess is the command line syntax. I figure there's got to be something unique/different in the way he would have to specify the user name, server, and that sort of thing.