Hi,
Eekers, thanks for the catch :) /me is used to writing to actual dir's after
so just assumed it would right to ~ in that case.
--
Thanks and best regards,
Ryan Rix
TamsPalm - The PalmOS Blog
I don't want to touch you too much baby, 'cause
making love to you might drive me crazy
On Wed October 22 2008 04:16:47 pm
kitepilot@kitepilot.com wrote:
> This is true but,
> Just a note:
>
> scp *.jpg user@kitchen
>
> Will copy all the files ending in .jpg to a directory named user@kitchen in
> THIS machine, if it exists, or it will abort with an error.
>
> If you want to remote-copy, it has to have a colon :
>
> scp *.jpg user@kitchen:
> or
> scp *.jpg user@kitchen:~
> ET
>
> PS: been bitten with that one before...
>
> Ryan Rix writes:
> >> inet 192.168.1.66/24 brd 192.168.1.255 scope global eth0
> >
> > Yes, it's the first number after inet.
> >
> >> inet 192.168.1.64/24 brd 192.168.1.255 scope global eth0
> >
> > again, first after inet.
> >
> > What I personally would do, though it's a bit of a pain to set up, is if
> > your router supports DHCP reservations (dlink G router does here) you can
> > give each compy a 'static' dhcp address.
> >
> > After you have them all rounded up you can add entries to /etc/hosts
> > 192.168.1.66 bedroom
> > 192.168.1.64 kitchen
> > and such, till you're done on all the boxen
> >
> > then do /etc/init.d/networking restart
> > and now you can refer to your targets as 'kitchen' or 'bedroom' or
> > whatnot.
> >
> > scp *.jpg user@kitchen
> >
> > Note that if the username you are logged into on the source computer is
> > the same as your target's username it can be safely dropped, and it's
> > implied.
> >
> > --
> > Thanks and best regards,
> > Ryan Rix
> > TamsPalm - The PalmOS Blog
> >
> > My heart is human, my blood is boiling, my brain: IBM
> >
> > On Wed October 22 2008 03:23:09 pm Josef Lowder wrote:
> >> On 10/22/08, enrique <kitepilot@kitepilot.com> wrote:
> >> > Linux: Open up a terminal and type:
> >> > ip addr show
> >> > and choose the adapter that connects to the network you want.
> >> >
> >> > use scp as:
> >> > scp /file/to/copy user@machine:/copy/file/to
> >> >
> >> > It's easy, even I can do it.
> >>
> >> Thanks Enrique ... but the problem is ... you are brilliant
> >> and I guess I just don't have all the wires connected.
> >>
> >> I did find that I have to use /sbin/ip addr show
> >> since 'ip' was not found.
> >>
> >> But below are the results I got from my two linux boxes,
> >> and I can't figure out which of all these different number
> >> sets is the 'ip' number for each machine.
> >>
> >> == from machine "A"
> >> $ /sbin/ip addr show
> >> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >> inet 127.0.0.1/8 scope host lo
> >> 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
> >> link/ether 00:11:2f:06:65:08 brd ff:ff:ff:ff:ff:ff
> >> inet 192.168.1.64/24 brd 192.168.1.255 scope global eth0
> >>
> >> == from machine "B"
> >> $ /sbin/ip addr show
> >> 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >> inet 127.0.0.1/8 scope host lo
> >> 2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen
> >> 1000 link/ether 00:14:85:1e:5f:5e brd ff:ff:ff:ff:ff:ff
> >> inet 192.168.1.66/24 brd 192.168.1.255 scope global eth0
> >>
> >> Furthermore, from your excellent example (thank you very much),
> >> scp /file/to/copy user@machine:/copy/file/to
> >>
> >> I still do not understand how to put which numbers where,
> >> and how the actual syntax should look. Is it like this:
> >>
> >> scp /filenameA.txt/to/copy joe@12.34.56:/copy/filenameB.txt/to
> >>
> >> How would scp know in what directory or folder to put the file
> >> to be copied?
> >> ---------------------------------------------------
> >> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> >> To subscribe, unsubscribe, or to change your mail settings:
> >> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)
%20/me%20is%20used%20to%20writing%20to%20actual%20dir's%20after%20%0A>%20so%20just%20assumed%20it%20would%20right%20to%20~%20in%20that%20case.%0A>%20%0A>%20%0A>%20--%0A>%20Thanks%20and%20best%20regards,%0A>%20Ryan%20Rix%0A>%20TamsPalm%20-%20The%20PalmOS%20Blog%0A>%20%0A>%20I%20don't%20want%20to%20touch%20you%20too%20much%20baby,%20'cause%20%0A>%20making%20love%20to%20you%20might%20drive%20me%20crazy%0A>%20%0A>%20%0A>%20%0A>%20%0A>%20On%20Wed%20October%2022%202008%2004:16:47%20pm%20kitepilot@kitepilot.com%20wrote:%0A>%20>%20This%20is%20true%20but,%0A>%20>%20Just%20a%20note:%0A>%20>%0A>%20>%20scp%20*.jpg%20user@kitchen%0A>%20>%0A>%20>%20Will%20copy%20all%20the%20files%20ending%20in%20.jpg%20to%20a%20directory%20named%20user@kitchen%20in%0A>%20>%20THIS%20machine,%20if%20it%20exists,%20or%20it%20will%20abort%20with%20an%20error.%0A>%20>%0A>%20>%20If%20you%20want%20to%20remote-copy,%20it%20has%20to%20have%20a%20colon%20:%0A>%20>%0A>%20>%20scp%20*.jpg%20user@kitchen:%0A>%20>%20or%0A>%20>%20scp%20*.jpg%20user@kitchen:~%0A>%20>%20ET%0A>%20>%0A>%20>%20PS:%20been%20bitten%20with%20that%20one%20before...%0A>%20>%0A>%20>%20>%0A>%20>%20>%20Yes,%20it's%20the%20first%20number%20after%20inet.%0A>%20>%20>%0A>%20>%20>%0A>%20>%20>%20again,%20first%20after%20inet.%0A>%20>%20>%0A>%20>%20>%20What%20I%20personally%20would%20do,%20though%20it's%20a%20bit%20of%20a%20pain%20to%20set%20up,%20is%20if%0A>%20>%20>%20your%20router%20supports%20DHCP%20reservations%20(dlink%20G%20router%20does%20here)%20you%20can%0A>%20>%20>%20give%20each%20compy%20a%20'static'%20dhcp%20address.%0A>%20>%20>%0A>%20>%20>%20After%20you%20have%20them%20all%20rounded%20up%20you%20can%20add%20entries%20to%20/etc/hosts%0A>%20>%20>%20192.168.1.66%20bedroom%0A>%20>%20>%20192.168.1.64%20kitchen%0A>%20>%20>%20and%20such,%20till%20you're%20done%20on%20all%20the%20boxen%0A>%20>%20>%0A>%20>%20>%20then%20do%20/etc/init.d/networking%20restart%0A>%20>%20>%20and%20now%20you%20can%20refer%20to%20your%20targets%20as%20'kitchen'%20or%20'bedroom'%20or%0A>%20>%20>%20whatnot.%0A>%20>%20>%0A>%20>%20>%20scp%20*.jpg%20user@kitchen%0A>%20>%20>%0A>%20>%20>%20Note%20that%20if%20the%20username%20you%20are%20logged%20into%20on%20the%20source%20computer%20is%0A>%20>%20>%20the%20same%20as%20your%20target's%20username%20it%20can%20be%20safely%20dropped,%20and%20it's%0A>%20>%20>%20implied.%0A>%20>%20>%0A>%20>%20>%20--%0A>%20>%20>%20Thanks%20and%20best%20regards,%0A>%20>%20>%20Ryan%20Rix%0A>%20>%20>%20TamsPalm%20-%20The%20PalmOS%20Blog%0A>%20>%20>%0A>%20>%20>%20My%20heart%20is%20human,%20my%20blood%20is%20boiling,%20my%20brain:%20IBM%0A>%20>%20>%0A>%20>%20>%20On%20Wed%20October%2022%202008%2003:23:09%20pm%20Josef%20Lowder%20wrote:%0A>%20>%20>>%20On%2010/22/08,%20enrique%20<kitepilot@kitepilot.com>%20wrote:%0A>%20>%20>>%20>%20Linux:%20Open%20up%20a%20terminal%20and%20type:%0A>%20>%20>>%20>%20%20ip%20addr%20show%0A>%20>%20>>%20>%20%20and%20choose%20the%20adapter%20that%20connects%20to%20the%20network%20you%20want.%0A>%20>%20>>%20>%0A>%20>%20>>%20>%20%20use%20scp%20as:%0A>%20>%20>>%20>%20%20scp%20/file/to/copy%20user@machine:/copy/file/to%0A>%20>%20>>%20>%0A>%20>%20>>%20>%20%20It's%20easy,%20even%20I%20can%20do%20it.%0A>%20>%20>>%0A>%20>%20>>%20Thanks%20Enrique%20...%20but%20the%20problem%20is%20...%20you%20are%20brilliant%0A>%20>%20>>%20and%20I%20guess%20I%20just%20don't%20have%20all%20the%20wires%20connected.%0A>%20>%20>>%0A>%20>%20>>%20I%20did%20find%20that%20I%20have%20to%20use%20/sbin/ip%20addr%20show%0A>%20>%20>>%20since%20'ip'%20was%20not%20found.%0A>%20>%20>>%0A>%20>%20>>%20But%20below%20are%20the%20results%20I%20got%20from%20my%20two%20linux%20boxes,%0A>%20>%20>>%20and%20I%20can't%20figure%20out%20which%20of%20all%20these%20different%20number%0A>%20>%20>>%20sets%20is%20the%20'ip'%20number%20for%20each%20machine.%0A>%20>%20>>%0A>%20>%20>>%0A>%20>%20>>%0A>%20>%20>>%20Furthermore,%20from%20your%20excellent%20example%20(thank%20you%20very%20much),%0A>%20>%20>>%20scp%20/file/to/copy%20user@machine:/copy/file/to%0A>%20>%20>>%0A>%20>%20>>%20I%20still%20do%20not%20understand%20how%20to%20put%20which%20numbers%20where,%0A>%20>%20>>%20and%20how%20the%20actual%20syntax%20should%20look.%20%20Is%20it%20like%20this:%0A>%20>%20>>%0A>%20>%20>>%20%20scp%20/filenameA.txt/to/copy%20joe@12.34.56:/copy/filenameB.txt/to%0A>%20>%20>>%0A>%20>%20>>%20How%20would%20scp%20know%20in%20what%20directory%20or%20folder%20to%20put%20the%20file%0A>%20>%20>>%20to%20be%20copied?%0A>%20>%20>>%20---------------------------------------------------%0A>%20>%20>>%20PLUG-discuss%20mailing%20list%20-%20PLUG-discuss@lists.plug.phoenix.az.us%0A>%20>%20>>%20To%20subscribe,%20unsubscribe,%20or%20to%20change%20your%20mail%20settings:%0A>%20>%20>>%20http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss%0A>%20>%0A>%20>%20---------------------------------------------------%0A>%20>%20PLUG-discuss%20mailing%20list%20-%20PLUG-discuss@lists.plug.phoenix.az.us%0A>%20>%20To%20subscribe,%20unsubscribe,%20or%20to%20change%20your%20mail%20settings:%0A>%20>%20http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss%0A>%20%0A>%20%0A>%20---------------------------------------------------%0A>%20PLUG-discuss%20mailing%20list%20-%20PLUG-discuss@lists.plug.phoenix.az.us%0A>%20To%20subscribe,%20unsubscribe,%20or%20to%20change%20your%20mail%20settings:%0A>%20http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss "Reply to this message")