[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnu-arch-users] fish vs sftp -- not the same, folks.
From: |
Charles Duffy |
Subject: |
[Gnu-arch-users] fish vs sftp -- not the same, folks. |
Date: |
Thu, 25 Dec 2003 13:58:25 -0600 |
I've heard quite enough disinformation on this list lately.
A few quotes to clear it up:
>From the man page of lftp 3.0.x:
> Fish is a protocol working over an ssh connection to a unix account.
> SFtp is a protocol implemented in ssh2 as sftp subsystem.
By Aaron J. Seigo on Friday 14/Feb/2003, @00:39:
> fish works even on systems that don't allow or can't do sftp (crazy
> admins, old ssh, etc). otherwise they're pretty much the same
> functionality wise. fish puts a perl script in your home dir
> (.fishsrv.pl), while sftp doesn't require that. instead it requires a
> ssh2 server that has sftp support turned on.
By Gunter Ohrner on Friday 14/Feb/2003, @16:25
> Additionally, or, more precise, because of these differences, in my
> experience sftp has a much better performance on low-end servers and
> does not load their CPU that much.
>
> In contrast an advantage of fish is that it does support symlinks
> transparently while sftp does not, at least not with my current server
> configuration which is pretty much Debian Woody default concerning the
> sshd.
Now, will people please stop spouting junk about fish and sftp being two
different names for the same thing?
- [Gnu-arch-users] fish vs sftp -- not the same, folks.,
Charles Duffy <=