Slashdot Mirror


How Do Your Machines Talk to Each Other?

VonGuard asks: "I'd imagine this is a common scenario out there for Slashdot readers: I have multiple desktops, all sitting right next to each other and all running different OS's. Linux, Mac OS X and 9, Windows 98, and XP. The problem is, despite these machines being only inches arpart physically, in the digital world, they are miles apart. I have no single way to get them all to talk to each other. NFS is impossibly complex, Appletalk is unreliable thanks to netatalk, while PCMacLan, and Samba make me feel like I'm giving into the Empire. Isn't there a simpler way to get files from one of these machines to the other? Right now, I use webservers and write little HTML files that link to the files on each machine. Isn't there a better way to do this?" Is there really a network sharing standard that works across a number of operating systems aside from Samba? Truth be told, Samba "works-for-me", so that's what I us. However, when it comes to simple file copying, sometimes a simple scp is all I need. What protocols do you use in networks that consist of 3 or more operating systems?

6 of 114 comments (clear)

  1. Uh.. by DrunkBastard · · Score: 5, Informative

    well, you could always use that little protocol called "file transfer protocol". Go figure. A protocol used to copy files. Works on every platform know to man kind. If you wanted to pull out a good ol' system that fell into disuse, get gopher working! As a side, there are scp protocols for pretty much everything as well.

    1. Re:Uh.. by JDWTopGuy · · Score: 3, Informative

      Yeah, I agree! Even if you can't run an FTP server on the OS 9 and winXP machines (I'm not saying it's impossible, I'm just guessing there's no bundled FTP server), FTP is bi-directional, so it shouldn't be too bad.

      OR you could just add WebDAV to Apache on either the Linux or OS X machine and be done with it all.

      --
      Ron Paul 2012
  2. Ah, a Debian user? by Tor · · Score: 4, Informative

    Since you ask right now, you are probably using the 'unstable' branch of Debian (where Netatalk recently broke for Mac OS X clients).

    That's when I decided to dig into the world of NetInfo - the NIS-like information system for Mac OS X. Basically, I now configured my Mac OS X client as a NIS client, which also auto-mount file shares from my Linux server via NFS. It's not that hard to set up, really. A nice side effect is that the network drives perform significantly better than they did using AFP/Netatalk.

    Of course, I also run Samba on my server. If you are looking for a single solution/protocol across platforms, then that's probably the route to go. Mac OS X comes with Samba.

    Then, if you are looking for file synchronization tools (as opposed to network file sharing), let me recommend a little utility called "unison". Runs on Linux, Mac OS X (UNIX), and Windows.

  3. X2VNC by bite.me · · Score: 5, Informative

    Creates a 1 pixel buffer at the edge of your screen. When you drag your mouse over it, it appears that the curser goes to other monitor, and the control of the keyboard too. Very handy. So with a combination of that, cygwin, samba, and netatalk, I can stay on top of all my files.

    Also, OS-X speaks samba, so there's less and less need for the appletalk protocol.

  4. Three letter file sharing is cool! by hrbrmstr · · Score: 3, Informative

    Boxen: Mac, Linux, Sun, XP, XP, XP, XP + BSD via vmware, & sometimes Knoppix. Apologies for the plethora of XP..lots of gaming between family members.

    Everything is configured to be an SMB server. Sun, Mac, Linux and BSD also export the shares as NFS servers. SMB, while an awful standard, just plain works thanks to the dedicated members of the Samba team (and all the forks of it). Use it and don't feel "slimy" just cause M$ made it so widely used. NFS isn't *that* difficult. If you've got many different types of boxes, you can easily do a "man" of the necessary stuff under everything but Mac OS X. Do a reply to this if you need to get it going on OS X since it's not as straightforward.

    Three of the XP boxen are really just clients, so they normally pull from the rest when necessary (MP3, AVI, home dirs, etc). Unix boxen (except the Mac) use pam/ldap to avoid duplication and i'm working on getting kerberos to tie (most of) them all together (someday I'll have time). The good thing about network home dirs and central file servers is that backups are a cinch and folks can move from win machine to win machine and retain profiles, etc.

    When I analyze traffic, I pretty much see most of the boxen accessing the Sun and Linux systems since they are the main storage beasts and one has the MP3's *:^)

    One very nice thing about SMB is that it is easily tunneled via SSH, so you can access your shares - securely - from almost anywhere you can ssh port tunnel to/from (it's cake on linux and try the ssh client from netsarang.com to do the same - as easily - under M$...or just install cygwin).

    I have to agree with one of the other posts: the Mac is just amazing when it comes to file sharing compatibility and speed (SMB shares map very fast and it handles NFS as a good BSD box should).

    hope this helps.

    --
    Mind the gap...
  5. You must give in by mrami · · Score: 3, Informative

    Many moons ago (1997) I was administering a system that was mixed Win95/MacOS8/FreeBSD and had absolutely no problems running netatalk and samba sharing the same FS. This was production w/ maybe 30 users. I still use samba for my home server (BSD/WinXP), and I can't imagine the quality of netatalk has decreased over the past 6 years... At least you'll be able to share.