RE: [SLE] Mac OSX clients can't talk to my SuSE9 Server
OK, I'm willing to entertain this notion. Does that mean OSX has a built in NFS client ? Will this setup fully support Mac file resource forks ? Stuart.
"John N. Alegre"
5/5/2004 3:53:42 PM >>> For OS X use standard NFS import export not Appletalk.
However, the OSX client machines refuse to login to the server. They can see the server in the list of available servers, and when they
On 05-May-04 Stuart Powell wrote: try
to connect it prompts them for an ID and password, but then it never connects. The same ID and password on an OS9 box works just fine. Has anyone had any success getting OSX clients to talk to SuSE9 via Appletalk ? If so, were there any special steps involved ? I'm not a Mac user myself, so I don't even know where to begin troubleshooting this from the client end.
------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------
* Stuart Powell (spowell@pcsolutionsmn.com) [040505 14:03]:
OK, I'm willing to entertain this notion. Does that mean OSX has a built in NFS client ? Will this setup fully support Mac file resource forks ?
Yes, actually it does. You could also setup a Samba server on this SUSE machine and the Macs should be able to see the shares in the finder with no problems. I've read about people having a lot of luck with both NFS and Samba. Appletalk is really a throwback that one shouldn't use with OSX.
"John N. Alegre"
5/5/2004 3:53:42 PM >>> For OS X use standard NFS import export not Appletalk.
-- "There is no need to teach that stars can fall out of the sky and land on a flat Earth in order to defend religious faith."
Stuart, On 05-May-04 Stuart Powell wrote:
Does that mean OSX has a built in NFS client ?
OS X is BSD Unix with some Jobs Quarks but BSD Unix still. It is all there. The changes all have to do with the old NetInfo Database that is often used instead of where you put normal BSD stuff. It is not hard to work out. Docs are pretty lacking out of the box but the University of OReilly has tons of stuff. If you can get your hands on any old NeXTStep docs they are really helpful. Mac OS X is just a NeXT cube underneath. In my hands exported NFS linux directories mount under the Finder just fine. john ------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------
Hi, I have some Mac OS X users that seem to have a vanishing file problem. I was thinking that it might have something to do with Netatalk. How do you import NFS on OS X? Mike Brandonisio Chief Technology Officer Mercor Media Inc. Main 312.628.5870 x229 Alt 630.665.5613 http://www.mercormedia.com mbrando@mercormedia.com -----Original Message----- From: listhub@libros.andante.mn.org [mailto:listhub@libros.andante.mn.org] Sent: Wednesday, May 05, 2004 4:52 PM To: Stuart Powell Cc: suse-linux-e@suse.com Subject: RE: [SLE] Mac OSX clients can't talk to my SuSE9 Server Stuart, On 05-May-04 Stuart Powell wrote:
Does that mean OSX has a built in NFS client ?
OS X is BSD Unix with some Jobs Quarks but BSD Unix still. It is all there. The changes all have to do with the old NetInfo Database that is often used instead of where you put normal BSD stuff. It is not hard to work out. Docs are pretty lacking out of the box but the University of OReilly has tons of stuff. If you can get your hands on any old NeXTStep docs they are really helpful. Mac OS X is just a NeXT cube underneath. In my hands exported NFS linux directories mount under the Finder just fine. john ------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------ -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Stuart Powell wrote:
OK, I'm willing to entertain this notion. Does that mean OSX has a built in NFS client ? Will this setup fully support Mac file resource forks ?
They already told you Mac OSX has BSD under the skin. BSD, like all the other OS, doesn't have the two-forks notion. If you transfer a Mac OS9 style file with NFS (or FTP, or scp, or whatever transfer files out of OSX), you loose the resource fork. For that you need Appletalk.
Stuart.
[snip] Ciao, Ermanno Polli
* Ermanno Polli (ermanno.polli@lnf.infn.it) [040506 01:56]:
Stuart Powell wrote:
OK, I'm willing to entertain this notion. Does that mean OSX has a built in NFS client ? Will this setup fully support Mac file resource forks ?
They already told you Mac OSX has BSD under the skin.
BSD, like all the other OS, doesn't have the two-forks notion. If you transfer a Mac OS9 style file with NFS (or FTP, or scp, or whatever transfer files out of OSX), you loose the resource fork. For that you need Appletalk.
Or you could just make the directory on the server an NFS export and have the OSX machines mount it at boot over the network as if it was a local drive. Then if you copy the file via the finder then it WILL copy everything that's needed. If your using ftp or scp then just have the person use stuffit to compress the files together and this will get everything that's needed to make the files usable on any other Mac. -- "There is no need to teach that stars can fall out of the sky and land on a flat Earth in order to defend religious faith."
On 06-May-04 Ben Rosenberg wrote:
Or you could just make the directory on the server an NFS export and have the OSX machines mount it at boot over the network as if it was a local drive. Then if you copy the file via the finder then it WILL copy everything that's needed. If your using ftp or scp then just have the person use stuffit to compress the files together and this will get everything that's needed to make the files usable on any other Mac.
This is exactly correct. Use standard Linux / UNIX to export / mount an NFS drive. This will appear on the desktop as a drive. Copy Mac files to and from that drive and 9.0 resource fork will be preserved to and from. Note that OS X files do no longer use the concept of a resource fork john ------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------
John N. Alegre wrote:
On 06-May-04 Ben Rosenberg wrote:
Or you could just make the directory on the server an NFS export and have the OSX machines mount it at boot over the network as if it was a local drive. Then if you copy the file via the finder then it WILL copy everything that's needed. If your using ftp or scp then just have the person use stuffit to compress the files together and this will get everything that's needed to make the files usable on any other Mac.
This is exactly correct.
Yes, but I understood the problem was (apart from AppleTalk not working on SuSE) plainly transferring the two-forks Mac files.
Use standard Linux / UNIX to export / mount an NFS drive. This will appear on the desktop as a drive. Copy Mac files to and from that drive and 9.0 resource fork will be preserved to and from. Note that OS X files do no longer use the
Are you sure?? I remember warnings about not to do that. The resource fork is lost in *any* case. This is the main reason of using Stuffit or the old binhex format.
concept of a resource fork
Of course. That's why I was talking about "old Mac OS9 files". Now the "resources" are in a mess of directories, under the main framework directory...
john ------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------
Ciao, Ermanno Polli
participants (5)
-
Ben Rosenberg
-
Ermanno Polli
-
John N. Alegre
-
Mike Brandonisio
-
Stuart Powell