The best place to learn about any command-line interfaces is to be an old fart, and have already learned it 20 years ago. It helps if you're so stuck in your old ways that you refuse to give them up for the new-fangled gadgetry of the future (aka, a GUI).
Yeah, I'd say the best place to learn would likely be to google for a tutorial.
And good to meet you too ATS16805...
I've tried lots of FTP clients and pretty much just use FileZilla. ncftp is great for command-line stuff.
out of curiousity, where would be a good place to start if i wanted to learn a bit about FTP from the command line?
Hrm, get a real OS and type:
$ man ftp
The best place to learn about any command-line interfaces is to be an old fart, and have already learned it 20 years ago. It helps if you're so stuck in your old ways that you refuse to give them up for the new-fangled gadgetry of the future (aka, a GUI).
// dalecosp is an older fart than BuzzLY, but not sure about Sxooter. However, both of them are more fully-trained in CS, and it's a hobby-turned-pseudocareer for me.
FWIW, and if it matters to anyone at all, the 'Nix-like ftp CLI clients are tons better than trying it on windoze.
You still use ftp? Haven't you heard of scp? Sheesh, next you'll be telling me you still use telnet.
You 'talkin to me? On a publicly available ftp server, you bet I do! But for other stuff I chose sftp over scp, for no particular reason I can recall ATM.
I also use http, ppp, pptp, rstp, TCP, UDP, ICMP, NTP, SMTP, POP, IMAP, AUP, PnP, sometimes NNTP, RIP, SNMP, and, of course, PHP. Hmm, I think I need to go "P" ....
And I still find an occasional use for telnet. But not for remote logins on my boxen ...
Gee, does P appear as the final character in more geekronyms than any other letter?
Well, I just find "ssh" easier to type than "telnet". But then, instead of logging out of a machine to get back to whichever one I had logged in from, I usually ssh there....
I do have a valid reason for this. It means I don't accidentally do something on the wrong box because I popped my login stack too many (or not enough) times.
It's not a very good reason, but it is valid.
Works .... I use ssh all the time, too --- it just doesn't rhyme/end with "P".... I have found, though, that when using xterm/aterm/Eterm, I tend to look at the title bar before I notice the hostname in the prompt, so I generally have one or more terminals ssh'ed into each box on one or more of my multiple desktops. If I'm not sitting on a GUI, then I'm probably more likely to daisy-chain from one to another as you mention.
Weedpacket wrote:You still use ftp? Haven't you heard of scp?
actually, no i haven't. anyone care to give the new-guy the rundown?
Sure. See attached --- this one culled from FreeBSD 5.4 --- a gazillon other versions available, perhaps, but the instructions should be about the same.
Oh, BTW, weedpacket was probably just joshing me. 
What, don't your primitive ftp clients support this command:
set authentication ssl
and since I use it to talk to a mainframe halfway across the country that another company owns, no, I can't use scp.
What's that saying about everything looking like a nail when all you've got is a hammer?
set authentication ssl
I still think "ssh" is easier to type..... I suppose I could create a file with that in it and have "ssh" run "ftp -s:ssl.config"....
What I want to know is: what does everything look like when all you've got is a Swiss Army knife?
A horse's hoof, probably....
Yeah, but that mainframe still doesn't know what ssh is either...
Heck, we even had to program our ftp server to send out responses on our ftp port for the mainframe to understand it. Sometimes, I really do think dinosaurs still roam the land.
hmph. i guess i'll go to the back of the room and sit at my desk. (sniff...sniff...)
From the man page for scp:
NAME
scp - secure copy (remote file copy program)
DESCRIPTION
scp copies files between hosts on a network. It uses ssh(1) for data
transfer, and uses the same authentication and provides the same secu-
rity as ssh(1). Unlike rcp(1), scp will ask for passwords or
passphrases if they are needed for authentication.
Any file name may contain a host and user specification to indicate that
the file is to be copied to/from that host. Copies between two remote
hosts are permitted.I think I've mentioned this on here before, if I have I appologise.
My client of choice? KDE, might sound odd but when you hear about it's kio modules for scp (fish), ftp, http, the list goes on. What is really cool about kio modules is that they're built right into KDE so they can be used in any KDE applications. I can open a file in kate or kdevelop using fish (let's say fish://bubblenut@example.com/file.php) edit it, save it and it will be saved on the remote server, how cool is that? If it's file management you need then just open up the path in konqueror and drag and drop your files as if it were a local directory.
Incidentally, I recently found out that you can do the same with vim using "vim scp://rob@example.com//file.php".
I do like kioslaves. I really do. I'm reminded of Plan 9's idea that "everything is a filesystem". Just opening "audiocd:/mp3/" and then copying the files listed there....
kioslaves, I thought kio modules didn't sound right but I couldn't be bothered to check
One thing that confuses me about the audiocd one is that through konqueror I can copy mp3's from a cd to my machine without any trouble but if I try to use KAudioCreator - which I'd have thought would be using the same tools - it fails completely. Oh well, drag and drop's easier anyway.
I use smart FTP at work and home.