On Thu, 28 Dec 2006, peter kerzum wrote:
>>> First of all sorry for top posting =)
>>> Pavel, you don't understand most usual trouble in whole IT =)
>> Maybe I don't - but a good problem report would make
>> it easier for me to understand.
> Yeah, I believe this particular discussion (mc in putty window on utf/non-utf
> should leave its trace in some faq =) The trouble is not only border chars,
> defunct keyboard with wrong TERM setting
This has been discussed on the mailing list many times. Searching the
archives should help. Setting TERM properly is vital for any curses
based app out there. I admit that it causes confusion but this is how
>>> You'll need it sometimes. Then if Shell VFS is misbehaving, just free it and
>>> bookmark (you should have SSH keys installed in order to avoid password). Be
>>> that 'Shell link' is buggy (especially about permissions) and SLOW.
>>> Consider using
>>> 'scp' and 'rsync' from command line.
>> What do you mean by SLOW ?
> Well, first of all -- slow enough to render whole system
> to something impossible. First, I'm using mc 4.6.1 shipped within standard
> slack 10.2.
> What I'm talking about was always the case unless any recent work is still
> unknown to
> me. So, welcome numbers =)
> With shell link it takes a total of 30 sec, with 24 of them dedicated to
> the 'writing of data' and the next 6 to a pause obscure to me.
> As you can see, impact on larger files is even larger.
> And this was not LAN! I used to use Samba and NFS to copy music with MC
> at my home.
2006-03-30 Dmitry Butskoj <buc at odusz dot so-cdu dot ru>
* fish.c (fish_file_store): Improve the upload speed by using the
`head' utility when possible. Fallback to a new improved `dd' method
if `head' is not availaible or just stupid.
I don't know how slack build their MC package . You may want to check
whether this patch is included - if it is not icluded you could ask the
maintainer to add it. It should make a difference.
Mc mailing list