1 |
On Thu, Mar 24, 2011 at 3:13 PM, Ed W <lists@××××××××××.com> wrote: |
2 |
> On 23/03/2011 14:54, Kfir Lavi wrote: |
3 |
>> Wow James thanks a lot for your insight. |
4 |
>> It seems that WR is a giant BSP house, which is good for really preliminary |
5 |
>> explorations of new hardware. I can see their benefit for an |
6 |
>> organization that |
7 |
>> don't really know what is Linux. |
8 |
>> The company I work with have a lot of projects. Most of them relay on a |
9 |
>> known |
10 |
>> and debugged hardware. I'm not intending to change all of their working |
11 |
>> way, |
12 |
>> but for a start I'm trying to push Gentoo in the project I'm working on, |
13 |
> |
14 |
> I think the most important question for you is the "best tools for the |
15 |
> job". I can't answer that, but just some advocacy for gentoo as an |
16 |
> embedded tool, look back at the thread "Some good words for Gentoo |
17 |
> Embedded"? |
18 |
> |
19 |
> I'm only building a small x86 board and I haven't mastered Catalyst so |
20 |
> I'm building my root using what is popularly known as "Tiny Gentoo". |
21 |
> However, the construction is incredibly simple and roughly my build is a |
22 |
> script which wraps something like: |
23 |
> |
24 |
> ROOT=/builds/my-build emerge baselayout uclibc busybox openresolv\ |
25 |
> dhcpcd dropbear your_other_stuff |
26 |
> |
27 |
> And pretty much that's it, you have a working, bootable, build. Give or |
28 |
> take fixing a bunch of bugs in ebuilds which aren't tested on your |
29 |
> architecture, this means you now have the entire portage library at your |
30 |
> disposal for building your embedded system, and that's likely worth a lot? |
31 |
> |
32 |
> I think you end up deviating from standard portage quite a bit for |
33 |
> embedded and surely lots of folks here have great experience that we |
34 |
> don't seem to share much? But I find for example I need a lot of |
35 |
> customised /etc/ scripts, or tweaks to init.d files, etc. It's tricky |
36 |
> to decide if these should be overlays added at the end, or to patch the |
37 |
> ebuild to install them pre-customised. I use a bit of a blend and |
38 |
> recently I have started trying to use /etc/portage/patches/cat/pkg |
39 |
> (badly documented) as a way to hook into ebuilds without having to patch |
40 |
> every version, forever, and lightly tweak the install. |
41 |
> |
42 |
> |
43 |
> I think "tools" are very personal and you can make a case for the tools |
44 |
> which fit your needs. However, I guess the point here is only that |
45 |
> Gentoo is a very nice tool for embedded and may meet the requirements of |
46 |
> many folks have, but who otherwise pass it over for more well known |
47 |
> alternatives. |
48 |
> |
49 |
> Good luck and if you do use Gentoo, please share something on what you |
50 |
> learn? |
51 |
> |
52 |
> Ed W |
53 |
> |
54 |
> |
55 |
|
56 |
Oh, |
57 |
I find it very hard to share or document what I'm doing. I really want |
58 |
to do it, |
59 |
and my gentoo blog really needs some new content, but I just don't have time. |
60 |
I'm working everyday until 22:00 and my 7months son also needs me, so I really |
61 |
try to be everywhere. |
62 |
I'm pushing Gentoo, because it can be tailored automatically for a lot |
63 |
of projects. |
64 |
From small devices to a cluster. The initial go is very hard with |
65 |
steep curve, but |
66 |
what I aim for is the ease of use and replication when problem strike or when |
67 |
moving to new project. |
68 |
As for Catalyst, I'll try to post my conclusion about this tool for our use. |
69 |
|
70 |
I'll try to document more what I'm doing. |
71 |
Regards, |
72 |
Kfir |