| 1 |
Kumba wrote: |
| 2 |
> I don't doubt this. The smallest drive I managed to kludge gentoo on |
| 3 |
> was 1GB, and that required NFS mounting, and waiting about 5 days for |
| 4 |
> gcc to build over nfs (was a sparcstation 20). |
| 5 |
|
| 6 |
yes, access via nfs is slooow. also, emerge sync took about 33MBs of |
| 7 |
memory, which is half of the 64MBs in the Zaurus. little space for file |
| 8 |
caching :) |
| 9 |
|
| 10 |
but: isn't it possible to curtail the portage tree size? clearly, some |
| 11 |
packages are not viable at all on the Zaurus, I don't see a reason to |
| 12 |
have space wasted on them... |
| 13 |
|
| 14 |
> Stage1's need a seed stage, essentially a stage2 at minimum. I had to |
| 15 |
|
| 16 |
OK, I see. |
| 17 |
|
| 18 |
do I understand correclty that basically we should start to get basic |
| 19 |
packages to compile properly. but what packages exaclty? sys-devel/* ? |
| 20 |
|
| 21 |
> These precautions you speak of will need to be documented too. One of |
| 22 |
> the people working on the Zaurus stuff may want to maintain a |
| 23 |
> guidexml-based installation guide. Should arm get re-incorporated into |
| 24 |
> gentoo sometime down the road, this will be a required piece, especially |
| 25 |
> to get it integrated into the Gentoo Handbook. |
| 26 |
|
| 27 |
yes, I see, handy format indeed... |
| 28 |
|
| 29 |
|
| 30 |
Akos |
| 31 |
|
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-embedded@g.o mailing list |
Archives