Posted by: Administrator
on March 26, 2007 07:34 PM
Don't search for a use case that matches your tool, at least if you're not a PR guy. It's just the opposite. You'll remember this tool if you someday hit a use case for it. Making up a use case looks always a bit constructed. I doubt there will be a task that it is absolutely better at than any other software. But then, you miss another point: By using an integrated solution for those socket-related tasks, you'll only have to learn one tool.
But since you mentioned scp: Why the heck would I bother to use scp (bad suggestion, sftp is so much more reliable) with all its authorization and encryption (OK, that can be disabled) overhead when piping tar output onto a socket is absolutely sufficient and the network is trusted (e.g. a virtual one on one physical machine)? I wouldn't even bother to include 1 MB of OpenSSL goodness to my embedded devices, BTW, so there might be circumstances when SSH isn't even an option.
Oh, and by the way: netcat doesn't have readline integration, AFAIK. Not that I ever missed it...
Learn about Linux
Download Linux
Get Linux help
Re:But what is it REALLY for?
Posted by: Administrator on March 26, 2007 07:34 PMBut since you mentioned scp: Why the heck would I bother to use scp (bad suggestion, sftp is so much more reliable) with all its authorization and encryption (OK, that can be disabled) overhead when piping tar output onto a socket is absolutely sufficient and the network is trusted (e.g. a virtual one on one physical machine)? I wouldn't even bother to include 1 MB of OpenSSL goodness to my embedded devices, BTW, so there might be circumstances when SSH isn't even an option.
Oh, and by the way: netcat doesn't have readline integration, AFAIK. Not that I ever missed it...
#