Uwe Thiem wrote:
Too big a thing for A. There is a reason why it doesn't have its own portage
tree. ;-)
Uwe
You could also loopback mount a file just for portage, which shrinks the
needed space down considerably. I use reiserfs with tail packing to fit
the whole tree onto a 260 megabyte
Hi folks, here comes an interesting little problem.
I have two boxes, A and B, both running gentoo. Box B has got a full portage
tree, box A has none but nfs mounts it from B. This has worked for me for
several years.
Since some update lately, A can not nfs mount /usr/portage (or anything
On Fri, 9 Nov 2007 12:06:11 +0200, Uwe Thiem wrote:
Since some update lately, A can not nfs mount /usr/portage (or anything
else) from B. NFS mount is broken. I know that emerging nfs-utils will
cure the problem. On the other hand, I can not emerge nfs-utils on A
without nfs working. Hic
On 09 November 2007, Neil Bothwick wrote:
On Fri, 9 Nov 2007 12:06:11 +0200, Uwe Thiem wrote:
Since some update lately, A can not nfs mount /usr/portage (or anything
else) from B. NFS mount is broken. I know that emerging nfs-utils will
cure the problem. On the other hand, I can not emerge
On Fri, 9 Nov 2007 13:27:54 +0200, Uwe Thiem wrote:
Alternative, and less kludgy, solution. Tar up /usr/portage on B,
unpack it on A.
Too big a thing for A. There is a reason why it doesn't have its own
portage tree. ;-)
You could get away with copying only the directories you need. Or
5 matches
Mail list logo
