Home › Forums › OS X Server and Client Discussion › File Serving › Static Mounting NFS in /Network
- This topic is empty.
-
AuthorPosts
-
January 4, 2005 at 12:54 am #360294
Anonymous
GuestI have 2 Panther client computers, one of which I would like to act as the master, and serve files/applications for both machines. I would like the static mount points in /Network to look the same on both machines.
(Let’s call the two machines master and slave.) Here’s the problem I’m having:
On the master, the mountpoint appears as the whole volume and not the NFS share, so that /Network/Applications contains my root-level directories (Applications, Library, System), and not the contents of /Applications.
The slave mounts the NFS share in /Network/Applications just fine, and works great.
So, is it possible to do a “localhost” NFS connection like I’m trying to do on the master? And without it showing the entire volume?
January 4, 2005 at 10:28 am #360303Anonymous
GuestYou’re undoubtedly right that I’m doing this the hard way… I’m just shooting in the dark after reading bits and pieces from a dozen partially-relevant and sometimes outdated HOWTO articles.
(I also just realized that the resource forks are lost when sharing through NFS, so my original solution probably wouldn’t have worked as well as I hoped anyway…)
Basically, what I want to have is networked home directories on the client, and host shared resources that appear in the same place on both machines (our project files, some applications). I was under the assumption that /Network would be the best place to put stuff like this, but maybe it isn’t. (See article here for my inspiration.)
Having things show in the same place between machines is preferred so that links don’t break (e.g. question marks in the Dock & Finder sidebar). Plus, it would just be less confusing to find stuff when moving between machines.
For the home directory part, I first tried following this article, but had trouble getting the automount to show up. I also didn’t like the fact that the sharepoint needs to be world-readable over AFP.
Then I found it worked rather well by using NFS to mount onto the client’s /Users. (see article here, about 2/3 down.) Perfect for my needs, except for the resource fork issue.
I have 2 Macs in my home office, and I was hoping I wouldn’t need OS X Server to do something like this. I’m not too concerned with scaling up or the initial “hacking” needed to get things to work… If it’s at all possible… (I know — I’m dreaming, right?)
Also, if I got Server, would the server Mac still be just as usable as a Client workstation?
-
AuthorPosts
- You must be logged in to reply to this topic.