On Wed, 10 Nov 1999, Michael Stearne wrote:
> But if I want to get a file from the Mac to the PC I have to put in
> /home/shared with the Mac and then get if from /home/shared on the Win
> PC. So, what I was thinking was this. Make a dir on linux called
> /home/WindowsC. Then via smbmount, mount //winpc/c/ to
> /home/WindowsC. This works fine. Next step is to use AppleTalk to
> mount that dir (/home/WindowsC, which really has the contents of
> //winpc/c) and eliminate the middle step described above.
Surely this achieves exactly the same result as the standard practice of
having the file server offer a shared directory, with the exception that
now the shared directory is physically located on the PC? You can't cut
out the middle step - you can only reduce it from two steps to one: with
your proposed setup to get a file from the PC to the Mac you don't have to
move it from the PC to the shared directory (as the entire PC volume is
shared), but you still have to "get it from /home/WindowsC" on the Mac.
Instead of worrying about transfer files from one client machine to
another, why not use the file server more efficiently by working with
files stored on it, mounted from whichever client you happen to be at? If
you want to open a file that is stored on a remote file server, you
shouldn't have to copy it to your local client machine first - that would
be missing out on half the functionality of a file server.
--
Kendall Lister, Systems Operator for Charon I.S. - [EMAIL PROTECTED]
Charon Information Services - Friendly, Cheap Melbourne ISP: 9589 7781
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
