</itemizedlist>
&comedi; works with standard Linux kernels, but also with its
real-time extensions <ulink url="http://www.rtai.org">RTAI</ulink> and
-<ulink url="http://www.fsmlabs.com/products/openrtlinux/">RTLinux/Free</ulink>.
+<ulink url="http://www.rtlinux-gpl.org/">RTLinux/GPL</ulink>.
</para>
<para>
This section gives a high-level introduction to which functionality
<emphasis role="strong">Real-time vs. non real-time.</emphasis>
If the device is to be used in a
<ulink
- url="http://www.fsmlabs.com/products/openrtlinux/">RTLinux/Free
+ url="http://www.rtlinux-gpl.org/">RTLinux/GPL
</ulink>
or <ulink url="http://www.rtai.org">RTAI</ulink> application,
there are a few extra requirements, because not all system calls are
available in the kernel of the real-time operating systems
<ulink
- url="http://www.fsmlabs.com/products/openrtlinux/">RTLinux/Free
+ url="http://www.rtlinux-gpl.org/">RTLinux/GPL
</ulink>
or <ulink url="http://www.rtai.org">RTAI</ulink>.
The APIs of RTAI and RTLinux/Free differ in
hardware. It can be useful if you are sampling at high frequency, or
if your hardware has a small onboard data buffer. You must have a
real-time kernel (<ulink url="http://www.rtai.org">RTAI</ulink> or
-<ulink url="http://fsmlabs.com/community/">RTLinux/Free</ulink>)
+<ulink url="http://www.rtlinux-gpl.org/">RTLinux/GPL</ulink>)
and must compile &comedi; with real-time support, or this flag will do
nothing.
</para>