I was told this too. Being familiar with both RTAI internals and
(in the past) RTLinux internals, I found this statement to be
rather questonable. However, since I hadn't gone over _every line_
of the code, I couldn't be sure.
So I wrote a perl script that compares two entire source trees, and
looks to see which source lines are similar, ignoring whitespace,
punctuation, etc. It turned out to be surprisingly good at its
task -- I checked RTAI against other projects that I work on,
and it showed me all the segments of code that I copied between the
projects. I checked RTAI against itself, and it showed me that all
the examples are very similar. I checked RTAI against the kernel,
and it picked up matches between the patch files in the RTAI source
and the files that the patches patch in the kernel source.
I checked RTAI vs. RTLinux, and it turned up 2 things: an example
written by Jerry Epplin, and the implementation of rt_printk(),
which was written by me. Neither of these were "originally" in
RTLinux, they were both "originally" posted to the RTLinux mailing
list.
There was one more match that was publicly claimed as copying by
the maintainer of RTLinux -- a few fields in the scheduler structure.
The script caught those, too, once I set the threshhold down to 3
lines, which also picked up hundreds of mismatches. But strangely, I
found the same lines in an OS textbook dated 1987. I wonder who
copied whom.
[By the way, if someone reminds me, I'll make the script available
for download. It's quite useful.]
> Isn't it true that RTAI used to be called "my-rtai"
> and the guy who did that work freely admitted that it was a fork of the
> RT/Linux source base?
No, it was never a fork. RTAI, in its DOS form, existed before
RTLinux.
> Second, that's what patents are all about, it's about protecting your
> investment.
Then why doesn't USENIX or New Mexico Tech own it? They were the
ones that paid for the development of RTLinux.
dave...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/