1 |
Thomas Flavel wrote: |
2 |
|
3 |
> On Wed, Jan 24, 2001 at 03:29:04PM -0700, drobbins@g.o wrote: |
4 |
> |
5 |
> > 1.0_rc4-pre2 is fully compatible with all modern Intel and Intel-compatible |
6 |
> > processors, from the i486 on up. While 1.0_rc4-pre2 is optimized for the |
7 |
> > 486, Achim plans to build several different versions of 1.0_rc4 optimized for |
8 |
> > various processors. 1.0_rc4-pre2 has been tested on K6 systems and works |
9 |
> |
10 |
> I don't understand why not a 386? I kind of expected the distcd to be 386 |
11 |
> binaries, and then to compile and install optimised to whatever my processor |
12 |
> happens to be? What am I mis-understanding? ;) |
13 |
> |
14 |
> How would gentoo be installed on a 386? |
15 |
|
16 |
You can build all the sys packages with a CHOST of i386-pc-linux-gnu and merge them |
17 |
to some temporary place. |
18 |
Then chroot there and recompile and remerge all packages. Eighter do this a few times |
19 |
or follow the dependencies |
20 |
starting by glibc to be sure you have no statically linked in i486 assembler code in |
21 |
there. Then you can build the |
22 |
other stuff you need and you should have a i386 based system. |
23 |
Do you still use i386 ? My oldest is an i486SX/25 with a 200MB HD running as a |
24 |
firewall here under gentoo. |
25 |
The i486 version is definetly slower that the i686 version we had before using i386 |
26 |
won't make things better. |
27 |
If there really is a need for a i386 version I can build one. |
28 |
|
29 |
> |
30 |
> |
31 |
> > sys-* layout |
32 |
> > ------------ |
33 |
> > |
34 |
> > Achim and I have resolved how to determine what goes in the sys-* categories. |
35 |
> > We are breaking with FreeBSD tradition by making the sys-* categories contain |
36 |
> > _only_ a barebones, minimal system -- the minimal Gentoo system that can still |
37 |
> > recompile itself, with a few exceptions. Previously, what was included in |
38 |
> > sys-* was more of a subjective thing, i.e. what I would like to see in a basic |
39 |
> > Gentoo Linux server install, the tools I personally like, etc. |
40 |
> > |
41 |
> > Rather than do this, we're going to be integrating some new functionality into |
42 |
> > Portage that's going to be very, very nice and will allow everyone to have the |
43 |
> > kind of "base" system that they like. Portage will recognize your selection not |
44 |
> > only at install time, but throughout the lifetime of your system, prompting you |
45 |
> > to upgrade or add new packages when necessary. |
46 |
> |
47 |
> Excellent. Roughly what size is minimum now? |
48 |
|
49 |
Currently about 200MB with lots of package-docs, and the development tools, but if |
50 |
you unmerge |
51 |
all sys-devel packages beside the c++-libs and spython remove /usr/doc and /usr/src |
52 |
and all the static libs in /lib and /usr/lib you only need about 130MB and still have |
53 |
a runable system. Other optimizations could be turning of building |
54 |
of localdata-stuff in glibc removing unneccesary zoneinfo and terminfo entrys... |
55 |
|
56 |
Hmm, maybe we should introduce a new USE flag to trigger build of packages with only |
57 |
the really neccesary stuff. |
58 |
|
59 |
~Achim |
60 |
|
61 |
> |
62 |
> |
63 |
> - Tom |
64 |
> _______________________________________________ |
65 |
> gentoo-dev mailing list |
66 |
> gentoo-dev@g.o |
67 |
> http://www.gentoo.org/mailman/listinfo/gentoo-dev |