On Tuesday 22 October 2024 20:29:14 BST Michael wrote: > On Tuesday 22 October 2024 18:01:55 BST Matt Jolly wrote: > > It should not matter; the virtual root involves bind mounting directories > > into a single location - that could be 4 different partitions, a bunch of > > subvolumes, or some directories scattered across a single partition, or > > some combination of those options. > > All good and fair, but then why Peter's reported error of duplicate exports?
I don't understand that either. Well, it's just one thing actually: it looks as though the remote mount still isn't right, so that some transfers just seem to vanish down a black hole. Now I have the NFS mounting working, apparently, with no reported errors, but I still can't get the combined system to behave. I mount the i5's portage tree and packages directory on a partition on the M9, chroot into it, 'env-update && . /etc/profile' and attempt to 'emerge --sync' (this is using the Git method). Everything starts to go well, and gkrellm on the i5 shows plausible network traffic on both machines - but no disk transfers. This goes on for a couple of minutes until I give up. Before starting any of that I recovered a backup of the i5 and untarred it into the chroot partition; not the whole thing, just the root FS and /var, which I've kept separate for many years. Oh, and /usr/local. The backup was just two days old. While bug-hunting, I created two new partitions on the i5: one each for the portage tree and the packages directory. That was to eliminate the possibility that the NFS mount was failing because it wasn't at a file-system root. Also while bug-hunting, I found an extra-long Ethernet cable and strung the i5 into the LAN that way. The M9 only ever sees the LAN, whereas I can now start and stop the LAN and WLAN at will on the i5. The Fritz!Box router sits at the junction. Eventually, of course, once I get this setup working, the cable will go back in the cupboard. -- Regards, Peter.
