summaryrefslogtreecommitdiffstats
path: root/cpukit/libfs/src/imfs/imfs_handlers_memfile.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* 2001-01-22 Ralf Corsepius <corsepiu@faw.uni-ulm.de>Joel Sherrill2001-01-221-0/+4
| | | | | | | * configure.in: Add src/imfs/config.h * src/imfs/Makefile.am: Add INCLUDES += -I. to pickup config.h * src/imfs/.cvsignore: Add config.h and stamp-h * src/imfs/*.c: Add config.h support.
* 2001-01-12 Jake Janovetz <janovetz@uiuc.edu>Joel Sherrill2001-01-121-4/+4
| | | | | | | | | | | | | | * src/imfs/imfs.h, src/imfs/imfs_creat.c, src/imfs/imfs_debug.c, src/imfs/imfs_eval.c, src/imfs/imfs_fchmod.c, src/imfs/imfs_handlers_memfile.c, src/imfs/imfs_init.c, src/imfs/imfs_initsupp.c, src/imfs/imfs_stat.c, src/imfs/memfile.c, src/imfs/miniimfs_init.c: Final developmental update to "tarfs". When rtems_tarfs_load() is called, it checks the permissions on each file. If there is write permission, it just creates a standard file using "creat()" and therefore, uses the IMFS MEMORY_FILE. If there is no write permission, it creates a LINEAR_FILE node with the appropriate properties. If the permission is ever changed to writeable, IMFS_fchmod converts it to a regular memory file.
* 2000-12-12 Jake Janovetz <janovetz@uiuc.edu>Joel Sherrill2000-12-131-0/+17
| | | | | | | | | | | | | * src/imfs/linearfile.c, src/imfs/imfs_load_tar.c: New files. * src/imfs/Makefile.am, src/imfs/imfs.h, src/imfs/imfs_creat.c, src/imfs/imfs_debug.c, src/imfs/imfs_eval.c, src/imfs/imfs_handlers_memfile.c, src/imfs/imfs_init.c, src/imfs/imfs_initsupp.c, src/imfs/imfs_stat.c, src/imfs/miniimfs_init.c: Added "tarfs". This is not really a tar filesystem. It is a way to load a tar image into the IMFS but actually leave bulky file contents in the original tar image. It essentially adds the linear file type and associated support and a loader routine.
* Updated copyright notice.Joel Sherrill1999-11-171-2/+1
|
* Added handler for fsync. For the memfile it is the same as the data sync.Jennifer Averett1999-11-161-1/+1
|
* The object memfile.o was being included in the miniIMFS even though itJoel Sherrill1999-11-021-1/+1
| | | | | | | 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.
* Moved the rmnod callback from the operations table to the handler table.Jennifer Averett1999-10-291-1/+2
|
* New files created by split of old imfs_handlers.c.Joel Sherrill1999-10-261-0/+37