summaryrefslogtreecommitdiffstats
path: root/meta-filesystems/README.md
diff options
context:
space:
mode:
authorKhem Raj <raj.khem@gmail.com>2023-06-15 20:21:57 -0700
committerKhem Raj <raj.khem@gmail.com>2023-06-17 08:30:01 -0700
commitc1f86dac48e9af79b153c2f101c36ad78a60cfdf (patch)
tree59ef18044e3a3529b579c5a600c4e85a3d206c11 /meta-filesystems/README.md
parent051c15a36d871ba6ae0252923c05f40e6fdefd91 (diff)
downloadmeta-openembedded-c1f86dac48e9af79b153c2f101c36ad78a60cfdf.tar.gz
layers: Move READMEs to markdown format
The READMEs are often viewed from websites markdown format which is much as readable as text and yet friendlier in browsers. Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-filesystems/README.md')
-rw-r--r--meta-filesystems/README.md101
1 files changed, 101 insertions, 0 deletions
diff --git a/meta-filesystems/README.md b/meta-filesystems/README.md
new file mode 100644
index 0000000000..78a4429ce2
--- /dev/null
+++ b/meta-filesystems/README.md
@@ -0,0 +1,101 @@
1This README file contains information on the contents of the
2filesystems layer.
3
4Please see the corresponding sections below for details.
5
6
7Dependencies
8============
9
10This layer depends on:
11
12 URI: git://git.openembedded.org/openembedded-core
13 layers: meta
14 branch: master
15
16 URI: git://git.openembedded.org/meta-openembedded
17 layers: meta-oe
18 branch: master
19
20Patches
21=======
22
23Please submit any patches against the filesystems layer to the
24OpenEmbedded development mailing list (openembedded-devel@lists.openembedded.org)
25with '[meta-filesystems]' in the subject.
26
27Layer maintainer: Khem Raj <raj.khem@gmail.com>
28
29When sending single patches, please use something like:
30
31 git send-email -1 -M \
32 --to openembedded-devel@lists.openembedded.org \
33 --subject-prefix='meta-filesystems][PATCH'
34
35
36Table of Contents
37=================
38
39 I. Adding the filesystems layer to your build
40 II. Misc
41
42
43I. Adding the filesystems layer to your build
44=================================================
45
46In order to use this layer, you need to make the build system aware of
47it.
48
49Assuming the filesystems layer exists at the top-level of your
50yocto build tree, you can add it to the build system by adding the
51location of the filesystems layer to bblayers.conf, along with any
52other layers needed. e.g.:
53
54 BBLAYERS ?= " \
55 /path/to/yocto/meta \
56 /path/to/yocto/meta-oe \
57 /path/to/yocto/meta-filesystems \
58 "
59
60
61II. Misc
62========
63
64 --- physfs ---
65 A library to provide abstract access to various archives
66
67 --- fuse ---
68 Filesystem in Userspace (FUSE) is a simple interface for userspace programs
69 to export a virtual filesystem to the Linux kernel.
70
71 --- ifuse ---
72 A fuse filesystem to access the contents of an iPhone or iPod Touch
73
74 --- sshfs-fuse ---
75 A filesystem client based on the SSH File Transfer Protocol
76
77 --- owfs ---
78 An easy way to use the 1-Wire file system
79
80 --- ntfs-3g-ntfsprogs ---
81 The ntfs-3g is a freely available read/write NTFS driver for Linux and
82 ntfsprogs includes utilities for doing all required tasks to NTFS partitions.
83
84 --- cramfs ---
85 Builds cramfs filesystems for embedded systems
86
87 --- smbnetfs ---
88 SMBNetFS is a Linux/FreeBSD filesystem that allow you to use samba/microsoft
89 network in the same manner as the network neighborhood in Microsoft Windows.
90
91 --- fuse-exfat ---
92 A read and write exFAT driver for FUSE
93
94 --- exfat-utils ---
95 Utilities to create, check, label and dump exFAT filesystem
96
97 --- f2fs-tools ---
98 Tools needed for creating and managing f2fs partitions
99
100 --- xfsprogs ---
101 It provides XFS filesystem utilities.