1 |
On Tuesday, 24 April 2018 09:43:35 BST Peter Humphrey wrote: |
2 |
> On Sunday, 22 April 2018 06:13:30 BST Peter Humphrey wrote: |
3 |
> > I've been NFS-exporting the portage treee from a 32-bit atom box to a |
4 |
> > chroot on my workstation, and it's worked well for years, if slowly. |
5 |
> > |
6 |
> > Now when I try to do the same with a 64-bit celeron machine I'm having a |
7 |
> > problem getting portage to work. If the required distfile is already |
8 |
> > present, no problem, but otherwise, trying to fetch it just hangs. No |
9 |
> > errors, no status, no fetch log, no progress. |
10 |
> > |
11 |
> > Www-client/links works in the chroot as expected, so the network is set up |
12 |
> > all right; portage just can't use it. |
13 |
> > |
14 |
> > I've compared /etc/exports on the two clients; also the chroot setup |
15 |
> > scripts, /usr/portage permissions, the USE flags of nfs-utils and |
16 |
> > everything else I can think of. All identical apart from obvious things |
17 |
> > like 32/64 bits and network names and IPs. Google hasn't helped either. |
18 |
> > |
19 |
> > Any ideas, anyone? |
20 |
> |
21 |
> Never mind. I've rebuilt the chroot from stage 3 and it seems to be working |
22 |
> fine. |
23 |
|
24 |
The appearance was deceptive; all the distfiles needed must have been present |
25 |
already. Today, one wasn't and the fetching process hung and had to be killed. |
26 |
|
27 |
So, again, what could possibly prevent portage from seeing the network inside |
28 |
a chroot, while other programs use it just the same as always? |
29 |
|
30 |
-- |
31 |
Regards, |
32 |
Peter. |