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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Updated copyright notice.	Joel Sherrill	1999-11-17	1	-2/+1
\|
*	Fixed comment	Jennifer Averett	1999-11-05	1	-1/+1
\|
*	Unmount was failing as a side-effect of splitting the rmnod handler	Joel Sherrill	1999-11-05	1	-0/+77
\| \| \| \|	and not handling every case properly.
*	The object memfile.o was being included in the miniIMFS even though it	Joel Sherrill	1999-11-02	1	-98/+0
\| \| \| \| \| \| \|	should not have been. This required that IMFS_rmnod be split into three separate (per file type) routines to avoid dependencies. In the end, a miniIMFS application is 6K smaller than one using the full IMFS.
*	Spacing.	Joel Sherrill	1999-10-12	1	-0/+1
\|
*	Added base version of file system infrastructure. This includes a major	Joel Sherrill	1998-11-23	1	-0/+97
	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.