Gentoo Archives: gentoo-dev

From: Douglas Russell <puggy@×××××××××.com>
To: John Nilsson <john@×××××××.nu>
Cc: gentoo-dev@g.o
Subject: Re: [gentoo-dev] Portage through SSH
Date: Sun, 31 Aug 2003 18:31:38
Message-Id: 200308311929.52988.puggy@bobspants.com
In Reply to: Re: [gentoo-dev] Portage through SSH by John Nilsson
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 I think this kind of capability is what is being developed by the
5 gentoo-server people...
6
7 Puggy
8
9 On Sunday 31 August 2003 7:14 pm, John Nilsson wrote:
10 > Some requirement thoughts:
11 > A network of gentoo hosts should have only one portage processing server
12 > and any number of installation leafs.
13 >
14 > First of all portage needs to easily handle more than one installation.
15 > Second the "leaf-installations" should have a very strict minimum
16 > requiremnts.
17 > Third redundancy is probably important. The information to restore a
18 > lost "leaf" should be availible on booth the portage host and on the
19 > leaf it self.
20 >
21 > /John
22 >
23 > Georgi Georgiev wrote:
24 > > On 31/08/2003 at 17:15:02(+0200), John Nilsson used 2.0K just to say:
25 > >>For me the problem is that the machines cant even run emerge sync, much
26 > >>less search for deps and that kind of calculations. I want EVERYTHING
27 > >>portage to be executed on one host (or with distcc a selected few) but
28 > >>still be able to manage the software on the other hosts. Best would be
29 > >>if I could uninstall portage from the other hosts completely.
30 > >
31 > > You can mount the remote filesystems over nfs and then set
32 > > ROOT=/mnt/remote to make the portage on the original system install stuff
33 > > on the remote one. This method also has its problems of course. Last time
34 > > I tried it -- I had lots of trouble with for example mplayer
35 > > autodetecting some libraries on the compiling computer that are not
36 > > installed on the slow host that I was compiling for. Even emerge -p was
37 > > failing because the version of glibc on the compiling system was older
38 > > (only by a release) than the one on the remote system.
39 > > http://bugs.gentoo.org/show_bug.cgi?id=22722
40 > >
41 > > Another thing I tried -- mount the remote filesystems with full
42 > > permissions, chroot over there and start compiling. You may want to
43 > > "mount -o bind /var/tmp/portage /mnt/remote/var/tmp/portage" and also do
44 > > the same with /usr/portage. I of course assume that programs compiled on
45 > > the slow machine would run on the fast one as well (and this is usually
46 > > the case).
47 >
48 > --
49 > gentoo-dev@g.o mailing list
50 -----BEGIN PGP SIGNATURE-----
51 Version: GnuPG v1.2.2 (GNU/Linux)
52
53 iD8DBQE/Uj6fXYnvgFdTojMRAsbGAKDgTFol2ogpWUCEYHRbB6nMJndh1wCcCTlz
54 y1EEnpYe3yB2WfzMNQNLptw=
55 =mHcD
56 -----END PGP SIGNATURE-----
57
58
59 --
60 gentoo-dev@g.o mailing list