1 |
On Wed, Mar 23, 2011 at 3:49 PM, wireless <wireless@×××××××××××.com> wrote: |
2 |
|
3 |
> On 03/23/11 05:46, Kfir Lavi wrote: |
4 |
> |
5 |
> > I'm trying to migrate a big company to Gentoo. |
6 |
> > This company have a contract with Wind River for support and use. |
7 |
> > I don't have any experience with Wind River, so I would be happy to |
8 |
> > hear your experience with it, and what it's pros and cons. |
9 |
> |
10 |
> > Regards, |
11 |
> > Kfir |
12 |
> |
13 |
> All by yourself? That's a LARGE statement. |
14 |
> |
15 |
> Wind River is the 600 lb Gorilla in the commercial |
16 |
> RTOS space. Everything from proprietary, to BSDish to embedded |
17 |
> Linux, state machines...... you name it they sell |
18 |
> (and mostly) support it. |
19 |
> |
20 |
> |
21 |
> Large companies use Wind River, because of many reasons, |
22 |
> but it is a "one stop shop" and Business managers |
23 |
> like that. Wind River can write (and often do) the |
24 |
> entire code for products or products lines, fast and |
25 |
> efficient. However, their "Achilles heal" is |
26 |
> they are EXPENSIVE to partner with; most often retaining |
27 |
> the intellectual property rights to all of the codes they |
28 |
> develop or sell. |
29 |
> |
30 |
> Their business model is the "lock-in" and often, after years |
31 |
> of a relationship with a company, the victim (um, I mean customer) |
32 |
> finds out that WR is licensing the code to a competitor..... |
33 |
> Bad ju-ju, but legal and happens all the time. |
34 |
> |
35 |
> |
36 |
> So you are talking about helping a company take the "long road" to |
37 |
> freedom and profitability, via embedded Linux (Gentoo specifically). |
38 |
> |
39 |
> Depending on the complexity of the of their codes, number of products, |
40 |
> etc, etc, you can easily be successful. However, be realistic. Pick |
41 |
> off the "low hanging fruit"; i.e. simple products to re-write the code |
42 |
> or new product offerings. WR will often get companies in a "tangled" |
43 |
> mess by the choices of processors, SOC, video chips etc etc where |
44 |
> NDAs and no published specifications make WR the only choice, or a |
45 |
> complete (hardware and software) redesign. |
46 |
> |
47 |
> My advice: |
48 |
> Work smart, build a team (open source) that gradually assimilates |
49 |
> new products and the other easy "knock-off" and take your time. |
50 |
> Walking into a large company and pitching "kick WR out" is difficult |
51 |
> in many circumstances. Most of all, remember that in this company their |
52 |
> are managers that drink and eat and "sup" with WR and they have built |
53 |
> a career on a partnership with WR. They'll stab you in the back and |
54 |
> you'll never see it coming. |
55 |
> |
56 |
> Also remember companies want to make a profit. So their management will |
57 |
> need "some sort of angle" as to what they have unique about their |
58 |
> product so other cannot just copy the code and sell it. When you |
59 |
> maintain proprietary source code, that is the lock for a company, |
60 |
> combined with patents. When you pitch open source solutions, you |
61 |
> and the company manager, must figure out a "unique" hook so as to |
62 |
> protect that company's investment and profit potential of the product |
63 |
> that is now open sources. YMMV. |
64 |
> |
65 |
> |
66 |
> |
67 |
> Caveat Emptor! |
68 |
> |
69 |
> But it is entirely doable depending on the "TEAM" you build as the |
70 |
> leader of this venture. |
71 |
> |
72 |
> GOOD LUCK! |
73 |
> James |
74 |
> |
75 |
> Wow James thanks a lot for your insight. |
76 |
It seems that WR is a giant BSP house, which is good for really preliminary |
77 |
explorations of new hardware. I can see their benefit for an organization |
78 |
that |
79 |
don't really know what is Linux. |
80 |
The company I work with have a lot of projects. Most of them relay on a |
81 |
known |
82 |
and debugged hardware. I'm not intending to change all of their working way, |
83 |
|
84 |
but for a start I'm trying to push Gentoo in the project I'm working on, and |
85 |
if it |
86 |
does happen, it will propagate to other similar projects. |
87 |
One important point you made is that WR keeps their intellectual property |
88 |
rights |
89 |
for helping you. I didn't know this. |
90 |
|
91 |
Do you happen to know if they let you compile your project from source, or |
92 |
they |
93 |
give you binaries? How many packages I can expect them to support in their |
94 |
tree? |
95 |
|
96 |
Thanks for your answers, |
97 |
Kfir |