aaah - i thought that the nfs server was solaris. i don't know if the trick i'm talking about works with that particular linux distro/nfs server combination
i think there is a file in linux (/etc/exports?) where you can specify nfs client access rules per client if you like On Thu, Mar 26, 2009 at 4:03 PM, Harry Putnam <reader at newsguy.com> wrote: > > Blake wrote: > >>> You might also try the /net trick (similar to automounting): > >>> ls /net/[hostname or ip]/path/to/share > >>> You might also try the /net trick (similar to automounting): > >>> ls /net/[hostname or ip]/path/to/share > > Harry asked: > >>> Blake, what is supposed to happen there? > >>> For me it just fails as not accessible. > >>> ls /net/192.168.0.2/pub > >>> ?ls: cannot access /net/192.168.0.2/pub: \ > > Blake responded: > >> To double check, is there a dir on your nfs host at /pub? ?You need >> to specify the full path. >> >> Is the client Linux in this case? ?Some Linux nfs client versions >> don't seem to be able to do this. ?(I don't remember which exactly). > > > Harry replies: > > It gets a bit confusing... in some cases the server is called server > and in others, host. > > I guess you want to know if there is /pub on the nfs server (a linux > machine), yes > > Is there a directory /pub on the client (an osol machine), yes (an > empty directory) > > So, client is Osol.11-109 and server is Gentoo linux in this case. > > > _______________________________________________ > opensolaris-help mailing list > opensolaris-help at opensolaris.org >
