1 |
On Mon, 2004-10-04 at 23:33, Chris White wrote: |
2 |
> All, |
3 |
> |
4 |
> Maybe I've just not seen this, but what sort of footprint does |
5 |
> portage leave on embedded systems with low cpu/ram? |
6 |
|
7 |
I think what your asking about here is what we are starting to coin as a |
8 |
gentoo-lite system. A lot of people are gaining an interest in this. |
9 |
Running gentoo with portage on crappy old hardware. Or they just want |
10 |
the performance boast and lower memory usage. For a system like this I'd |
11 |
think you would want atleast a P75 with atleast 32M of of ram. |
12 |
Portage is not so big. But python itself is a beast. |
13 |
|
14 |
In one experiment I've managed to get pythons runtime down to about 2 |
15 |
Megs of HD space. And in another experiment with the portage tree itself |
16 |
I managed to get it down to 14 Megs with the use of squashfs and |
17 |
excluding a few things from the tree which I know are not needed to do |
18 |
emerge system. But a full portage-rsync tree compressed was about 17 |
19 |
Megs |
20 |
|
21 |
Now if we are talking embedded systems in the way I like to think of |
22 |
them (ie firmware) then the min requirements are about 4M of Ram and 3M |
23 |
of flash space using a semi default setup, give or take depending on the |
24 |
device your building for. |
25 |
|
26 |
> I ask this mainly |
27 |
> because it's a Good Thing To Know (tm) considering the last LWE |
28 |
> conference was full of people asking about using Gentoo for embedded |
29 |
> devices. |
30 |
portage needs work and a fair bit of it. |
31 |
Other than myself and mike more people need to propose ideas to the |
32 |
portage team to make things more flexible. |
33 |
|
34 |
> Something like higher end Palms may be able to dish it out, |
35 |
> but what happens when you get to lower end palms or even cell phones? |
36 |
|
37 |
What about them? |
38 |
Most cell phones are ARM based. |
39 |
Mike Frysinger is currently working on generic uclibc arm little endian |
40 |
stages. When he has those complete (and most of the bugs worked out) |
41 |
I'll start on generic uclibc arm big endian stages. When I have those |
42 |
complete and I'm happy with it I'm going to ship the device off to OSU |
43 |
so we can continue to support the arch from a (le||be) perspective. The |
44 |
unit I will be developing with is a nslu2 that was a donation to the |
45 |
gentoo embedded project thanks to the guys over at the nslu2-linux |
46 |
project (http://www.nslu2-linux.org/) who had a fund raiser in order to |
47 |
get me one. They ended up getting 9x the amount in donations needed to |
48 |
send me a unit and were able to send them to a number of other embedded |
49 |
projects. |
50 |
|
51 |
Unfortunately there are a few drawbacks to our embedded support right |
52 |
now. |
53 |
1) Lack of skilled (wo)manpower. |
54 |
2) Lack of proper cross-toolchain handling by portage. So everything is |
55 |
considered native-* vs cross-* (this means you must use the same host |
56 |
arch as your target arch) or use a binfmt_elf kernel module to emulate |
57 |
your target arch. |
58 |
3) package management for embedded devices. (no all devices are |
59 |
read-only) |
60 |
- ipkg format seems ideal here but I/we have not enough input from the |
61 |
community to tell what will be ideal in the long run. |
62 |
|
63 |
If anybody that has a decent level of cross compiling experience and |
64 |
thinks that they would be interested in gentoo supporting better cross-* |
65 |
support please contact me. (seriously motivated people only) |
66 |
|
67 |
> |
68 |
> Thanks ahead of time for any/all comments and hold on (*ChrisWhite |
69 |
> prepares fireproof suit)... and flames. |
70 |
|
71 |
hrmm flames.. none right now but as soon as I can think of something or |
72 |
get a blowtorch I'll be sure to direct it your way. |
73 |
|
74 |
-- |
75 |
Ned Ludd <solar@g.o> |
76 |
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer |