-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-07-30 at 02:08 -0400, Brian K. White wrote:
Worse than that. When you copy a symlink via ssh, you don't get any indication it's a symlink, and you get is a few bytes of the beginning of the file. Say on the remote site there is a file "fakefoo". fakefoo is a symlink to "foo". That is, it's a relative link to another file in the current directory, the symlink actually contains just "foo" not "/path/to/foo" Say the content of foo is: 0123456789abcdefghijklmnopqrstuvwxyz
...
I don't remember if this maybe only happens via ssh or ftp, or maybe only when sshing or ftp-ing to certain ssh or ftp servers. Definitely it hapens at least via ssh between any combination of linux, freebsd, sco open server, though they all use the same openssh which is surely the meaningful element other than mc itself, not the underlying os.
It does not happen when you copy trees locally. I have used this function often, copying symlinks, and never noticed the problem you refer. With a remote tree I don't know. Could you write a bugzilla? Your info is very detailed, and it should be worth it, so we can hope they correct it sometime. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIkDfKtTMYHG2NR9URAgs/AJ93sA7TORxdbN/RS4Qi0T4UkoqAswCfSj44 7NId+cC65ug240eM1iCG8FY= =G2KX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org