useful libraries (includes NIC drivers)

[ccaudle at pdq.net (ccaudle)]

>===== Original Message From <joel at OARcorp.com> =====
[regarding OSKit being GPL}
>But if I read your comments right, this is mostly on the device drivers so
>is not THAT big a factor.  Other components are still significant savings.

The source code is of course the final authority, but from what I can tell of 
the current snap shot, the components which come from Linux are hardware 
drivers (NIC, IDE, SCSI), and the EXT2, FAT, and VFAT file systems.
>From FreeBSD and NetBSD you get TCP/IP stack, FFS file system, tty drivers, 
and a math library.

All the rest comes from the University of Utah, and is mostly GPL, but the 
docs provide a phone number so that you can "pursue alternate licensing 
terms."
The UofU code includes the higher level file system organization, an "address 
map manager," disk partitioning code, Bootp support, executable loading 
support, and a stripped down, small implementation of the standard C lib.  I 
think the name space implementation is in the address map manager.

The way this code is structured, I don't think it would make sense to make it 
a "part" of RTEMS.  It is made to be portable, so that there is not a need to 
do that.  You supply an argument to the configure script to tell it to use 
your cross compiler, and you end up with a directory full of headers and 
library files that you can link to your application code.
This just happens to be useful for me at the moment, so I thought I would pass 
along the information.  Feel free to use or disregard as is appropriate to 
your situation.

-- Chris