Hi All,
I try to summarize _my_ thoughts after some discussions:
The top-level structure should be
/usr/src/
linux/
realtime/
Here as little as possible goes to linux, as we want to keep it easy to
follow the Linux kernel development.
All RT-Linux related stuff goes to realtime. In there we could provide a
structure like
/usr/src/realtime/
doc/
kurt/
posix/
rtai/
rtlinux/
drivers/
mbuff/
portable_fifos/
rt_com/
examples/
kurt/
posix/
rtai/
rtlinux/
posix/
rtai/
calibaration/
fifos/
schedulers/
rtlinux/
fifos/
schedulers/
(rtlinux1/)
I guess that is self-explanatory ?
I want to stress that there is a strong separation of Linux-intrusions
and plain add-ons (linux/ vs. realtime/).
Moreover we should provide a logigal separation within realtime/, not an
system-separation; that is, create doc/, drivers/, examples/ ... at that
level and separate by system (if needed) underneath.
I guess that is very well feasible, and if averybody adopts that scheme,
there shouldn't be any problems of interdependences or such, so each part
can independently be upgraded.
-- Jochen
Heinrich-Heine-Universit�t, Institut f�r Physikalische Chemie I
Universit�tsstr. 1, Geb. 26.43.02.29, 40225 D�sseldorf, Germany
phone 02118113681 fax 02118115195 -- www-public.rz.uni-duesseldorf.de/~jochen
[EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED]
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
