| 1 |
Jonathan Callen <jcallen <at> gentoo.org> writes: |
| 2 |
|
| 3 |
|
| 4 |
> The list of all profiles that can be chosen (for all architectures) |
| 5 |
> can be found in ${PORTDIR}/profiles/profiles.desc . There are other |
| 6 |
> "profile-like" directories under ${PORTDIR}/profiles, but these are |
| 7 |
> only used as parents for a "complete" profile, as would be listed in |
| 8 |
> profiles.desc. Most profiles do not change much, if anything, in the |
| 9 |
> <at> system set. The <at> system set contains much more than you would |
| 10 |
> probably need for a dedicated, embedded device. |
| 11 |
|
| 12 |
|
| 13 |
OK. |
| 14 |
|
| 15 |
So I want to build and embedded gentoo system on an amd64: |
| 16 |
|
| 17 |
model name : AMD FX(tm)-8350 Eight-Core Processor |
| 18 |
|
| 19 |
What this the embedded profile? (show me the syntax for this?). |
| 20 |
|
| 21 |
|
| 22 |
I only need busybox (looking at the other embedded profiles). If I choose to |
| 23 |
install iptables, as the only package, after busybox, the dependancy-tree |
| 24 |
will pull in what else I need. Then just mod the kernel and I have embedded |
| 25 |
gentoo on an amd64 system with iptables. |
| 26 |
|
| 27 |
This will work, right? Isn't this what you are implying, or is the |
| 28 |
profile system incomplete? |
| 29 |
|
| 30 |
|
| 31 |
|
| 32 |
James |
Archives