[DISCUSS : vxwork to linux]

[DISCUSS : vxwork to linux]

[Raz]

Hello rt. I wish to write a paper that describes what it means to port
from vxworks to linux rt in all apects but from your experience. The bellow
is a list of questions.

why did you port ? lack of hardware support ?

Is your system soft real time or hard time system ?

Can you estimate how many lines of code were ported ?

Was there an effort to teach the vxwork engineers linux ? did it
succeed / partialy succeed ?
If new engineers were recruited, was it difficult to find linux rt
programmers ? how long did
it take to recruit ?

Was the same team structure preserved or a new hirarchy created ?

how long did it take to the first linux product ?

Did you release new vxworks versions while migrating ? after the
migration is done ?
         if so , do you have the same engineers supporting the old code ?

What are the information resources you used for that ?
Did you consult with professionals ? how did you reach a decision what
sort of rt flavor to use ?

Were new positions/skills required  ? Did you recruit platform
engineers ? Kernel engineers ?

Did you use porting libraries or a nother solution ? did you change
the system design ? Did you use other programming languages other than
c and c++
to migrate ?

once the porting was complete can you estimate, does it take the same
effort to release
a product ?

What was the clients response when they were told you changed Os ? Did
they know or care ?

Is the linux product required to do more than the vx works product?

Were all engineers using the same operating system or did some
programmers use linux while others running
windows ? Did it matter ?

Were there any logistics changes due to the porting ? Did the IT
department took part , like switching exchange server
to something else ? vpn ?

Did you use the same source control system ? bug tracking system ?

Did you keep your code closed or is it open/partialy open ?

thank you
raz
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [DISCUSS : vxwork to linux]

[Sven-Thorsten Dietrich]

On Sat, 2010-08-14 at 00:27 +0300, Raz wrote:
> Hello rt. I wish to write a paper that describes what it means to port
> from vxworks to linux rt in all apects but from your experience. The bellow
> is a list of questions.
> 

Sounds like you are trying to get someone to write the paper for you?

I don't think too many folks on this list are porting from VxWorks to
Linux.

But you might want to contact Wind River, they might have a migration
guide you could cite. (Although I would speculate that a migration guide
the OTHER way might be easier to find)

Also, some of your questions are curiously irrelevant. Exchange server?
VPN. 

Where did you get this survey anyways? 

Is it copyrighted?

Cheers.

Sven


> why did you port ? lack of hardware support ?
> 
> Is your system soft real time or hard time system ?
> 
> Can you estimate how many lines of code were ported ?
> 
> Was there an effort to teach the vxwork engineers linux ? did it
> succeed / partialy succeed ?
> If new engineers were recruited, was it difficult to find linux rt
> programmers ? how long did
> it take to recruit ?
> 
> Was the same team structure preserved or a new hirarchy created ?
> 
> how long did it take to the first linux product ?
> 
> Did you release new vxworks versions while migrating ? after the
> migration is done ?
>          if so , do you have the same engineers supporting the old code ?
> 
> What are the information resources you used for that ?
> Did you consult with professionals ? how did you reach a decision what
> sort of rt flavor to use ?
> 
> Were new positions/skills required  ? Did you recruit platform
> engineers ? Kernel engineers ?
> 
> Did you use porting libraries or a nother solution ? did you change
> the system design ? Did you use other programming languages other than
> c and c++
> to migrate ?
> 
> once the porting was complete can you estimate, does it take the same
> effort to release
> a product ?
> 
> What was the clients response when they were told you changed Os ? Did
> they know or care ?
> 
> Is the linux product required to do more than the vx works product?
> 
> Were all engineers using the same operating system or did some
> programmers use linux while others running
> windows ? Did it matter ?
> 
> Were there any logistics changes due to the porting ? Did the IT
> department took part , like switching exchange server
> to something else ? vpn ?
> 
> Did you use the same source control system ? bug tracking system ?
> 
> Did you keep your code closed or is it open/partialy open ?
> 
> thank you
> raz
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [DISCUSS : vxwork to linux]

[Raz]

On Sat, Aug 14, 2010 at 1:53 AM, Sven-Thorsten Dietrich
<thebigcorporation@gmail.com> wrote:
> On Sat, 2010-08-14 at 00:27 +0300, Raz wrote:
>> Hello rt. I wish to write a paper that describes what it means to port
>> from vxworks to linux rt in all apects but from your experience. The bellow
>> is a list of questions.
>>
>
> Sounds like you are trying to get someone to write the paper for you?
no.  i want statistics.
> I don't think too many folks on this list are porting from VxWorks to
> Linux.
>
> But you might want to contact Wind River, they might have a migration
> guide you could cite. (Although I would speculate that a migration guide
> the OTHER way might be easier to find)
> Also, some of your questions are curiously irrelevant. Exchange server?
> VPN.
they are if your IT manager does not know much about linux. 6 years
has passed and i still have no VPN access through linux.
> Where did you get this survey anyways?
>
> Is it copyrighted?
i did not write anything yet. the only information i have is my own.
if i will write it, it will be copywrited but free.
> Cheers.
>
> Sven
thank you.
>> why did you port ? lack of hardware support ?
>>
>> Is your system soft real time or hard time system ?
>>
>> Can you estimate how many lines of code were ported ?
>>
>> Was there an effort to teach the vxwork engineers linux ? did it
>> succeed / partialy succeed ?
>> If new engineers were recruited, was it difficult to find linux rt
>> programmers ? how long did
>> it take to recruit ?
>>
>> Was the same team structure preserved or a new hirarchy created ?
>>
>> how long did it take to the first linux product ?
>>
>> Did you release new vxworks versions while migrating ? after the
>> migration is done ?
>>          if so , do you have the same engineers supporting the old code ?
>>
>> What are the information resources you used for that ?
>> Did you consult with professionals ? how did you reach a decision what
>> sort of rt flavor to use ?
>>
>> Were new positions/skills required  ? Did you recruit platform
>> engineers ? Kernel engineers ?
>>
>> Did you use porting libraries or a nother solution ? did you change
>> the system design ? Did you use other programming languages other than
>> c and c++
>> to migrate ?
>>
>> once the porting was complete can you estimate, does it take the same
>> effort to release
>> a product ?
>>
>> What was the clients response when they were told you changed Os ? Did
>> they know or care ?
>>
>> Is the linux product required to do more than the vx works product?
>>
>> Were all engineers using the same operating system or did some
>> programmers use linux while others running
>> windows ? Did it matter ?
>>
>> Were there any logistics changes due to the porting ? Did the IT
>> department took part , like switching exchange server
>> to something else ? vpn ?
>>
>> Did you use the same source control system ? bug tracking system ?
>>
>> Did you keep your code closed or is it open/partialy open ?
>>
>> thank you
>> raz
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

last patch (2.6.33.7-rt29)

[Madovsky]

For info
the las patch works very well on Fedora 10 64bits
with bonding (1NIC x 2 ports and 3NIC x 2 ports)

Regards

Franck