rtems

RTOS/rtems

Files

Kinsey Moore 1ecb4e3047 cpukit/jffs2: Properly commit JFFS2 data

When unmounting a JFFS2 filesystem, any outstanding write buffers must
be flushed to disk. In some circumstances, these write buffers are
instantiated by a garbage collection pass and as such no inode number is
associated with it. Due to the way that JFFS2 processes these garbage
collection passes, a write buffer without any associated inodes will not
be flushed unless it is forced with jffs2_flush_wbuf_pad().

2024-03-14 17:13:23 -05:00

src

cpukit/jffs2: Properly commit JFFS2 data

2024-03-14 17:13:23 -05:00

README

Remove All CVS Id Strings Possible Using a Script

2012-05-11 08:44:13 -05:00

README

This directory contains for the "file system" library. All supported
file systems live under this tree.

Currently the supported file systems in this library are:

- IMFS or In Memory File System

   This is the only root file system on RTEMS at the moment. It supports
   files, directories, device nodes and mount points. It can also be
   configured to be the miniIMFS.

- TFTP and FTP filesystem are part of the libnetworking library.

- DEVFS or Device File system

- DOSFS, a FAT 12/16/32 MSDOS compatible file system.

- NFS Client, can mount NFS exported file systems.

- PIPE, a pipe file system.

- RFS, The RTEMS File System.

--Chris Johns and Joel Sherrill
  17 Feb 2010