On Tuesday, 10 March 2020 09:49:48 GMT Michael wrote:
> I'm glad you got it going. I don't use NFS at the moment, but with a fleet
> of ancient systems hanging around I may start doing this soon to accelerate
> emerges for most of them by using a faster PC.
Well, I haven't got that far yet becau
On Tuesday, 10 March 2020 09:43:18 GMT Peter Humphrey wrote:
> On Tuesday, 10 March 2020 09:27:54 GMT Michael wrote:
> > mount -t nfs 192.168.1.4:portage /mnt/clrn/usr/portage
> >
> > or
> >
> > mount -t nfs 192.168.1.4:/portage /mnt/clrn/usr/portage
>
> Well, even after all the times I read th
On Tuesday, 10 March 2020 09:27:54 GMT Michael wrote:
> On Tuesday, 10 March 2020 08:17:41 GMT netfab wrote:
> > Le 09/03/20 à 17:03, Peter Humphrey a tapoté :
> > > mount -t nfs 192.168.1.4:/mnt/nfs/portage /mnt/clrn/usr/portage #
> > > script on the client
> > >
> > > Result:
> > > * Mounting ch
On Tuesday, 10 March 2020 08:17:41 GMT netfab wrote:
> Le 09/03/20 à 17:03, Peter Humphrey a tapoté :
> > mount -t nfs 192.168.1.4:/mnt/nfs/portage /mnt/clrn/usr/portage #
> > script on the client
> >
> > Result:
> > * Mounting chroot dirs under /mnt/clrn ...
> > mount.nfs: mounting 192.168.1.4:/m
Le 09/03/20 à 17:03, Peter Humphrey a tapoté :
> mount -t nfs 192.168.1.4:/mnt/nfs/portage /mnt/clrn/usr/portage #
> script on the client
>
> Result:
> * Mounting chroot dirs under /mnt/clrn ...
> mount.nfs: mounting 192.168.1.4:/mnt/nfs/portage failed, reason given
> by server: No such file or di
Hello list,
I decided to have another go at fixing my nfs setup. The host 192.168.1.4
exports its portage directory to this host, 192.168.1.5. I used to use nfs-v3
for this, but it wasn't working right so I'm trying with v4.
The problem is that, every time I tell this machine to mount the remote
6 matches
Mail list logo
