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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Corrected multiple places the file size was not being properly updated.	Joel Sherrill	1999-02-10	1	-2/+8
\|
*	Corrected spacing and added some new error checks that were needed	Joel Sherrill	1999-02-05	1	-9/+9
\| \| \| \|	to avoid dereferencing NULLs.
*	Added imfs_fdatasync routine that gets called from both fdatasync and datasync.	Jennifer Averett	1998-12-03	1	-0/+26
\|
*	Added a imfs fdatasync routine that gets called for fdatasync and datasync.	Jennifer Averett	1998-12-03	1	-0/+4
\|
*	Modifications for RTEMS_UNIX.	Jennifer Averett	1998-12-03	1	-1/+10
\|
*	Added base version of file system infrastructure. This includes a major	Joel Sherrill	1998-11-23	26	-0/+4268
	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.