From: David Dougall Subject: Re: rpc.mountd + rpc.nfsd Date: Tue, 3 Sep 2002 08:26:06 -0600 (MDT) Sender: nfs-admin@lists.sourceforge.net Message-ID: References: <3D74BD0F.1020207@linkvest.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: "nfs@sourceforge.net" Return-path: To: Jean-Eric Cuendet In-Reply-To: <3D74BD0F.1020207@linkvest.com> Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: Have you looked at sharity? I have not used it much, but from what I understand, it does exactly what you are asking. --David Dougall On Tue, 3 Sep 2002, Jean-Eric Cuendet wrote: > > > > > >I suspect you would be better off starting with am-utils than > >nfs-server. (am-utils is a sophisticated auto-mount daemon). > > > Everyone that I ask about that tell me the same: use amd... > But (except if I miss something), it's absolutely NOT suitable for that! > > Explainations: > amd mounts a smb share in the filesystem (say, mounting //server/share > => /smb). To mount, you must provide a user/pwd. Then there is some > mount time fixed uid/gid used to "own" the files on the machine. > If the authentication is done by user1 and then user2 is accessing > files, the permissions will be checked on user1 on the SMB server, and > with uid/gid on the client. If user2 has access to files that user1 > haven't, user2 will be denied access... > If user2 have access that user1 don't , access will be granted anyway > (if uid/gid on the client is OK). > > The goal is to check the perms on a per access basis. When user1 access > files, we use its auth token to check if access is granted. Client > doesn't anything, only the SMB server makes checks. > Then, if user2 access other files, we use its auth token, which let him > access different files. > It's the same as network neighborood in Windows. Only files that the > USER (not the machine) have access are acessible. > > Am I missing something with amd? > > >If I understand you correctly, the nfs server will be on the same > >machine as the nfs client that accesses that server. And then the > >server reaches out over the network with SMB. > > > Yes, that's it! The nfs-server is only a bridge. Access is only provided > for 127.0.0.1 > > >In that case you don't need mountd at all. When the server starts, it > >mounts itself and then starts responding to NFS requests. > > > Cooool. It's simpler! So, server mounting itself doesn't need mountd. > How do I do that? > - Implementing NFSD RPC calls. > - Starting NFSD > - Mounting the server (mount -t nfs localhost:/ /smb) > Why isn't mountd needed? What does it provide that is not needed? > > >It is much easier not to re-invent the wheel. For the actual file > >access, don't do that via NFS, simply mount the SMB share using smbfs > >somewhere and direct the client to that. Only use NFS for the browsing. > > > The same problem as explained before... > > >I'm not sure about the 'different-users-see-different-things' bit, but > > > That's just the point that don't work and that's very important in this > thing. > > >there are elements of that in Erez' hlfsd (Home Link File System) so I > >suspect he could help there too. > > > I'll have a look at that. But I suspect that it won't change things. > > Thanks anyway for everything. > -jec > > PS: Are you a RedHat employee or not? > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > NFS maillist - NFS@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs > > ______________________________________ Inflex Virus Scanner - installed on mailserver for domain @et.byu.edu Queries to: postmaster@et.byu.edu ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs