| 1 |
On Sunday, 22 April 2018 06:13:30 BST Peter Humphrey wrote: |
| 2 |
> I've been NFS-exporting the portage treee from a 32-bit atom box to a chroot |
| 3 |
> on my workstation, and it's worked well for years, if slowly. |
| 4 |
> |
| 5 |
> Now when I try to do the same with a 64-bit celeron machine I'm having a |
| 6 |
> problem getting portage to work. If the required distfile is already |
| 7 |
> present, no problem, but otherwise, trying to fetch it just hangs. No |
| 8 |
> errors, no status, no fetch log, no progress. |
| 9 |
> |
| 10 |
> Www-client/links works in the chroot as expected, so the network is set up |
| 11 |
> all right; portage just can't use it. |
| 12 |
> |
| 13 |
> I've compared /etc/exports on the two clients; also the chroot setup |
| 14 |
> scripts, /usr/portage permissions, the USE flags of nfs-utils and |
| 15 |
> everything else I can think of. All identical apart from obvious things |
| 16 |
> like 32/64 bits and network names and IPs. Google hasn't helped either. |
| 17 |
> |
| 18 |
> Any ideas, anyone? |
| 19 |
|
| 20 |
Never mind. I've rebuilt the chroot from stage 3 and it seems to be working |
| 21 |
fine. I only asked in the hope of not having to do that. But then, it didn't |
| 22 |
take too long really. Hey-ho. |
| 23 |
|
| 24 |
-- |
| 25 |
Regards, |
| 26 |
Peter. |
Archives