Re: IN your opinion what is the best way to share files between LInux and MAC OS X?

On May 31, 10:39 am, navti <nav...@xxxxxxxxx> wrote:
On May 31, 9:19 am, The Natural Philosopher <a...@xxx> wrote:

navti wrote:
On May 30, 9:58 pm, The Natural Philosopher <a...@xxx> wrote:
navti wrote:
On May 30, 9:34 pm, The Natural Philosopher <a...@xxx> wrote:
navti wrote:
IN your opinion what is the best way to share files between LInux and
MAC OS X?
I set up SAMBA on the LInux machine and the MAC (running the very
latest OSX) can copy files to the SAMBA share at lightning speeds.
When I try and copy files from the LInux machine to the Mac they take
an eternity.
So slow in fact I have to kill the process .
I would appreciate any thoughts on why that maybe and also if there is
a better way to share files (I guess HTTP-FTP would be the most
sensible option ).
That is very weird.
That's not a problem with the protocol, but with the installation
setup.
maybe, its KNoppix.
I don't think its a distro issue, or why is it fast one way not the other..

If you READ a file FROM linux using the mac, is it also slow?

All copying is taking place on the Mac to/from the SAMBA share.

If I copy a file from the MAC to the SAMBA share (which is writeable )
it is very fast.

If I then try and copy the file back from the SAMBA share to the Mac
it simply doesnt work.

It may be that linux's SMBclient is badly configured.

i dont use smbclient. all client activity takes place on the Mac,
SAMBA is the server only

Ok..smbclient on the MAC then!

What you are saying is that with the mac as a client to the SMB server,
on linux, you are getting asymmetrical responses.

Let's try something else. Is file LOADING of the samba server slow..i.e.
if you open a file on the server into a program on the MAC is it slow?

That is also unresponsive,

I will try another protocol and see what happens . That way we can
rule out the Mac filesystem as the culprit.

scp copied a 700 mb file from the samba-linux server to the mac-
smbclient computer in a few minutes .

so it must be something up with samba.

time for wireshark it would seem.

though running wireshark and understanding its output are 2 different
things,

.

Relevant Pages