On Monday 2 December 2024 17:56:38 Greenwich Mean Time Michael wrote: > On Tuesday 26 November 2024 16:13:01 GMT Peter Humphrey wrote: > > I've spent several days-worth of my time over the last few weeks in trying > > to get my i5 box to export its portage tree and packages directory to a > > chroot on my M9 machine. I read all the docs, I thought about the help > > that was offered here, I changed file systems and partitions around - > > everything I could think of. > > > > The answer was simple, and I stumbled over it in a post on Stack Exchange: > > the behaviour of NFS mount calls changed in NFS v4. I didn't need to > > change /etc/ exports on the i5, but the NFS-mount call on the M9 did need > > to change. > > Can you please share the link?
Sorry Michael - it was at the end of infinitely many searches and I didn't make a note of it. <snip> I should have said: "in NFSv4 the client specifies the server path *relative* to the virtual root." > I had (another) look at the wiki. You're right, it seems to describe NFSv3 > only. I don't have NFSv3 here to compare. With NFSv4 you export the global > root directory to allow its subdirectories to be exported too - at least > this is how I understand it works on my systems. ...but today I see, buried in what you might call the small print: "If the NFS server or client support NFSv3 only, the full path to the exported directory (e.g. /export/home or /export/data) needs to be specified when mounting." [1] We could debate whether that's guidance enough. 1. https://wiki.gentoo.org/wiki/Nfs-utils#Mounting_exports , about a page down. -- Regards, Peter.
