rtems - RTEMS Kernel, file-systems, drivers, BSPs, samples, and testsuite.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Merged from 4.5.0-beta3a	Joel Sherrill	2000-06-12	1	-3/+3
\|
*	Updated copyright notice.	Joel Sherrill	1999-11-17	1	-2/+1
\|
*	Changed IMFS to use IMFS_NAME_MAX as the maximum length of a basename	Joel Sherrill	1999-02-24	1	-1/+1
\| \| \| \| \| \| \|	rather then NAME_MAX. NAME_MAX is 255 and that lets IMFS chew up memory too fast. Perhaps in the future, the places in IMFS that put a maximum length name string on the stack and the jnode structure does not include a maximu length name string can be fixed so this is not a problem.
*	Added base version of file system infrastructure. This includes a major	Joel Sherrill	1998-11-23	1	-0/+130
	overhaul of the RTEMS system call interface. This base file system is the "In-Memory File System" aka IMFS. The design and implementation was done by the following people: + Joel Sherrill (joel@OARcorp.com) + Jennifer Averett (jennifer@OARcorp.com) + Steve "Mr Mount" Salitasc (salitasc@OARcorp.com) + Kerwin Wade (wade@OARcorp.com) PROBLEMS ======== + It is VERY likely that merging this will break the UNIX port. This can/will be fixed. + There is likely some reentrancy/mutual exclusion needed. + Eventually, there should be a "mini-IMFS" description table to eliminate links, symlinks, etc to save memory. All you need to have "classic RTEMS" functionality is technically directories and device IO. All the rest could be left out to save memory.