1 |
Richard Freeman posted |
2 |
<37186.202.248.61.99.1129855791.squirrel@××××××××××××.org>, excerpted |
3 |
below, on Thu, 20 Oct 2005 20:49:51 -0400: |
4 |
|
5 |
> Keep in mind that you can run x86 in a chroot just fine, and that is |
6 |
> reasonably convenient for anything other than servers/daemons since they |
7 |
> aren't running out of /etc/init.d. |
8 |
|
9 |
This bears reemphasis. There's little reason except for simple |
10 |
time/laziness that a 100% x86 install would be better than a mainly amd64 |
11 |
system, since for the few things that /are/ binary only or not yet ported |
12 |
to amd64, an x86 chroot should be the maximum required solution. Most x86 |
13 |
applications won't even need that, as they'll run just fine on an amd64 |
14 |
system with the appropriate emul-linux-x86-XXXX libs installed. |
15 |
|
16 |
Do note that the emul-linux stuff is binary packages, however, generally |
17 |
lightly optimized as they are designed to run on ia64/itanic as well. For |
18 |
more optimization or just because you are more comfortable with |
19 |
from-source, the chroot does work, but it's really not necessary for the |
20 |
vast majority of users that need only the occasional 32-bit app. |
21 |
|
22 |
If you /do/ choose to go 32-bit chroot, but it's DEFINITELY a recommended |
23 |
read in ANY case, take a look at the amd64 technotes, available here: |
24 |
|
25 |
http://www.gentoo.org/proj/en/base/amd64/technotes/index.xml |
26 |
|
27 |
*** AGAIN, READ THE ABOVE TECH NOTES!!! *** They will answer a number of |
28 |
questions before you ask and could save you some major headaches |
29 |
needlessly going thru stuff others have already figured out. |
30 |
|
31 |
> I'm guessing that if you're adventurous enough to be running gentoo in the |
32 |
> first place you'll be fairly happy with amd64. There are also lots of |
33 |
> ways to contribute if you run amd64. Just about all package developers |
34 |
> who are running on x86 are happy to receive feedback from amd64 users, |
35 |
> especially if you suggest patches (not that I personnally excel at this). |
36 |
> In this way even a somewhat novice programmer can contribute to major |
37 |
> projects in ways that some of the more senior developers cannot by virtue |
38 |
> of having a different platform to test on. I think you'll also find that |
39 |
> amd64 has one of the largest groups of dedicated developers in gentoo, and |
40 |
> the amd64 herd is probably larger than any comparable group on almost any |
41 |
> distro... |
42 |
|
43 |
That has been my experience as well. I'll reemphasize the sizable amd64 |
44 |
herd part, and add that amd64 was the first to have arch testers (ATs), |
45 |
and is still the only herd to have more than a small handful. These ATs |
46 |
have become an enormous resource to the Gentoo AMD64 team, one reason the |
47 |
idea has been exported to some of the other archs as well. |
48 |
|
49 |
ATs are sort of developers in training, altho the AT position is certainly |
50 |
important in its own right, as well. They take a certification quiz and |
51 |
do much of the grunt work in testing that a package is actually stable |
52 |
enough on AMD64 to get the ~amd64 keyword, and eventually be upgraded to |
53 |
amd64 stable. They have read access to the CVS/Subversion tree, and |
54 |
slightly elevated privileges on bugzilla, but any proposed patches and the |
55 |
like still go thru a fully certified Gentoo developer to get into the |
56 |
tree. It's pretty safe to say that the ATs are one of the big reasons the |
57 |
number of packages in portage available to amd64 and ~amd64 users has |
58 |
grown to be near that of x86, and that is becoming more the case every |
59 |
day. |
60 |
|
61 |
(Let me be clear that I write this as a user, not an AT or developer |
62 |
myself, tho I certainly intend to become an AT at some point, only haven't |
63 |
yet.) |
64 |
|
65 |
-- |
66 |
Duncan - List replies preferred. No HTML msgs. |
67 |
"Every nonfree program has a lord, a master -- |
68 |
and if you use the program, he is your master." Richard Stallman in |
69 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
70 |
|
71 |
|
72 |
-- |
73 |
gentoo-amd64@g.o mailing list |