Lines Matching full:filesystem

1 # OpenBMC Flash Layout and Filesystem Documentation
5 how the Linux filesystem is setup, filesystem layouts, overlays, boot options,
30 Before starting execution, systemd requires the root filesystem and all binaries
34 ### Root filesystem
36 For storage of the root filesystem, a read-only volume was selected. This allows
37 the majority of the filesystem content, including all executables and static
38 data files, to be stored in a read-only filesystem image. Replacing read-only
39 filesystem images allows the space used by the content to be confirmed at build
43 An effort has been made to adhere to the Filesystem Hierarchy Standard [FHS][].
50 read-only filesystem content. This applies to systems with limited attached
53 To load the root filesystem, the initramfs locates and mounts the squashfs and
58 implementation, and details are located in the Supported Filesystem Choices
61 ## Supported Filesystem Choices
64 information is given for each filesystem such as how the filesystem is stored on
65 flash, how the filesystem is instantiated during system boot/init, and how code
66 update handles the filesystem.
68 ### Writable Filesystem Options
72 The majority of the filesystem is stored in a read-only squashfs in an MTD
74 mounted read-write using the JFFS2 filesystem. This read-write filesystem is
75 mounted over the entire filesystem space allowing all files and directories to
78 This filesystem stack requires the mounts to be performed from an initramfs. The
84 read-write filesystem are copied into RAM by the initramfs and used to assemble
87 MTD partitions and white listed files to the writable overlay filesystem.
91 This is the default filesystem in OpenBMC. It is used in several BMC systems
94 storage is typically in the 10s of MB, so staging the filesystem to RAM is not
99 The majority of the filesystem is stored in a read-only squashfs in a static UBI
115 enough flash storage to store at least 2 copies of the filesystem. This can be