----- Original Message -----
From: "Rajko M."
On Tuesday 29 July 2008 09:52:21 am Nico Sabbi wrote:
On Tuesday 29 July 2008 16:42:06 Rajko M. wrote:
On Tuesday 29 July 2008 03:13:34 am Nico Sabbi wrote:
Hi, is there a console/text file-manager alternative to mc? mc works quite well, but it has some limitations (especially in its ftp part) that sometimes annoy me a lot.
It would be nice to know what particular features are annoying you. Maybe authors can do something about.
- the symlinking transfer was never implemented (lftp implements it)
You mean if you want to copy symlink (F5) it will copy symlink, but not the directory where symlink points to.
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 When you fire up mc and use shell-link (ssh) to connect to the remote box: * fakefoo will appear like a regular file in the file list * it will have a * if executable, or no mode indicator if a plain file, etc, but never an @ * it will have a length of 36 (the length of the real file) * if you view fakefoo, all you will get is "012" (the length of the filename in the symlink) * if you copy fakefoo, the new file on the local side will be a plain file not a symlink, and the contents will be "012" * if the symlink contained say "/path/to/foo" instead of "foo" then the viewing/copying fakefoo would get you "0123456789ab" (the length of the filename in the symlink) That's a pretty ugly behaviour, receiving a dozen bytes from an executable, or "#!/bi" instead of a script, but in each case saved in a local plain file with the same execute & other perms set. Let alone the more correct thing would be to receive a symlink anyways, not any content of the symlink target file. (setting aside the "dive into symlinks" feature) Because of this, I still use mc for a lot of miscelaneous file shuffling, including via ftp and ssh, but I just always do so with this in mind. Any ime I need to move a whole tree that might contain symlinks or other special files, I just use rsync instead. 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. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org