Landry Breuil wrote:
On 10/19/07, Jan Stary <[EMAIL PROTECTED]> wrote:
Again: set WRKOBJDIR on the client side and you don't need
to be writing in the remotely mounted tree at all.
I'm already setting WRKOBJDIR outside nfs-dir, the problem is more for
/usr/ports/packages .. i'd like it to be sh
Re
I'll add to that debug session that it works if i add spud to exports
line and locally mount /usr/ports :
[EMAIL PROTECTED]:~/ #mount -t nfs spud:/usr/ports /tmp/blah/
[EMAIL PROTECTED]:~/ #touch /tmp/blah/test
And tcpdump log on lo0 :
[EMAIL PROTECTED]:~/ #tcpdump -s 65000 -i lo0 port nfsd or
On 10/19/07, Jan Stary <[EMAIL PROTECTED]> wrote:
> > > > Again: set WRKOBJDIR on the client side and you don't need
> > > > to be writing in the remotely mounted tree at all.
>
> > I'm already setting WRKOBJDIR outside nfs-dir, the problem is more for
> > /usr/ports/packages .. i'd like it to be s
> > > Again: set WRKOBJDIR on the client side and you don't need
> > > to be writing in the remotely mounted tree at all.
> I'm already setting WRKOBJDIR outside nfs-dir, the problem is more for
> /usr/ports/packages .. i'd like it to be shared too, to install the
> same package on various sparc64
On 10/19/07, Jan Stary <[EMAIL PROTECTED]> wrote:
> Replying to myself,
>
> > Again: set WRKOBJDIR on the client side and you don't need
> > to be writing in the remotely mounted tree at all.
>
> the following is nonsense, of course:
>
> > Another advantage of that is that when you build some port
Replying to myself,
> Again: set WRKOBJDIR on the client side and you don't need
> to be writing in the remotely mounted tree at all.
the following is nonsense, of course:
> Another advantage of that is that when you build some port that requires
> e.g. the X11 to be installed, you only need it
On Oct 18 20:04:18, Landry Breuil wrote:
> i'm struggling to make my ports-tree usable on all my machines, it
> seems that in my configuration -maproot=root in /etc/exports doesn't
> work:
>
> on the server (4.1 stable), /etc/exports contains :
> /usr/ports -maproot=root client
> perms : drwxrwxr-
On 10/18/07, Dorian B|ttner <[EMAIL PROTECTED]> wrote:
> Landry Breuil schrieb:
> > Hi,
> >
> > i'm struggling to make my ports-tree usable on all my machines, it
> > seems that in my configuration -maproot=root in /etc/exports doesn't
> > work:
> >
> > on the server (4.1 stable), /etc/exports cont
Landry Breuil schrieb:
Hi,
i'm struggling to make my ports-tree usable on all my machines, it
seems that in my configuration -maproot=root in /etc/exports doesn't
work:
on the server (4.1 stable), /etc/exports contains :
/usr/ports -maproot=root client
perms : drwxrwxr-x 47 root wsrc 1024 Oc
9 matches
Mail list logo
