| /OK3568_Linux_fs/yocto/poky/documentation/ref-manual/ |
| H A D | structure.rst | 20 The OpenEmbedded build system does not support file or directory
36 This directory includes a copy of BitBake for ease of use. The copy
44 resides in the ``bitbake/bin/`` directory) starts. Sourcing the
57 This directory contains user configuration files and the output
65 directory separate from the :term:`Source Directory` by
66 providing a directory name when you ``source`` the setup script. For
76 This directory holds the source for the Yocto Project documentation as
80 ``ref-manual/`` directory.
87 This directory contains the minimal, underlying OpenEmbedded-Core
88 metadata. The directory holds recipes, common classes, and machine
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/filesystems/ext4/ |
| H A D | directory.rst | 6 In an ext4 filesystem, a directory is more or less a flat file that maps
8 filesystem. There can be many directory entries across the filesystem
11 such, directory entries are found by reading the data block(s)
12 associated with a directory file for the particular directory entry that
18 By default, each directory lists its entries in an “almost-linear”
20 sense because directory entries are not split across filesystem blocks.
21 Therefore, it is more accurate to say that a directory is a series of
22 data blocks and that each block contains a linear array of directory
26 directory is of course signified by reaching the end of the file. Unused
27 directory entries are signified by inode = 0. By default the filesystem
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/filesystems/ |
| H A D | directory-locking.rst | 6 Locking scheme used for directory operations is based on two
10 When taking the i_rwsem on multiple non-directory objects, we
16 1) read access. Locking rules: caller locks directory we are accessing.
25 4) rename() that is _not_ cross-directory. Locking rules: caller locks
28 if the target already exists, lock it. If the source is a non-directory,
37 * check that source is not a directory
43 6) cross-directory rename. The trickiest in the whole bunch. Locking
54 * If the target exists, lock it. If the source is a non-directory,
65 If no directory is its own ancestor, the scheme above is deadlock-free.
74 (1) if object removal or non-cross-directory rename holds lock on A and
[all …]
|
| H A D | dnotify.rst | 9 The intention of directory notification is to allow user applications
10 to be notified when a directory, or any of the files in it, are changed.
12 on a directory using a fcntl(2) call and the notifications themselves
19 DN_ACCESS A file in the directory was accessed (read)
20 DN_MODIFY A file in the directory was modified (write,truncate)
21 DN_CREATE A file was created in the directory
22 DN_DELETE A file was unlinked from directory
23 DN_RENAME A file in the directory was renamed
24 DN_ATTRIB A file in the directory had its attributes
36 file descriptor associated with the directory in which the event occurred.
[all …]
|
| H A D | overlayfs.rst | 26 non-directory objects may report an st_dev from the lower filesystem or
29 over the lifetime of a non-directory object. Many applications and
94 It would be more correct to refer to an upper and lower 'directory
96 directory trees to be in the same filesystem and there is no
113 upper and lower filesystems and refers to a non-directory in either,
117 Where both upper and lower objects are directories, a merged directory
121 "upperdir" are combined into a merged directory:
126 The "workdir" needs to be an empty directory on the same filesystem
129 Then whenever a lookup is requested in such a merged directory, the
130 lookup is performed in each actual directory and the combined result
[all …]
|
| /OK3568_Linux_fs/buildroot/dl/unixbench/git/UnixBench/testdir/ |
| H A D | large.txt | 4 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
5 …clint/lib/tls/i686/sse2/libgimpwidgets-2.0.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
6 stat64("/user/folk/clint/lib/tls/i686/sse2", 0xbfcdba08) = -1 ENOENT (No such file or directory)
7 …folk/clint/lib/tls/i686/libgimpwidgets-2.0.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
8 stat64("/user/folk/clint/lib/tls/i686", 0xbfcdba08) = -1 ENOENT (No such file or directory)
9 …folk/clint/lib/tls/sse2/libgimpwidgets-2.0.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
10 stat64("/user/folk/clint/lib/tls/sse2", 0xbfcdba08) = -1 ENOENT (No such file or directory)
11 …user/folk/clint/lib/tls/libgimpwidgets-2.0.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
12 stat64("/user/folk/clint/lib/tls", 0xbfcdba08) = -1 ENOENT (No such file or directory)
13 …olk/clint/lib/i686/sse2/libgimpwidgets-2.0.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
[all …]
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/dpkg/dpkg/ |
| H A D | 0001-Dpkg-Source-Archive-Prevent-directory-traversal-for-.patch | 4 Subject: [PATCH] Dpkg::Source::Archive: Prevent directory traversal for
9 which can lead to directory traversal situations on specially crafted
14 itself is not present as an actual directory on the tarball.
17 out of the source tree root directory, and then a debian.tar that
18 contains an entry within that symlink as if it was a directory, without
19 a directory entry for the symlink pathname itself, which will be
29 instead still use a temporary directory, then walk that directory and
30 remove any matching entry in the destination directory, replicating what
31 GNU tar would do, but in addition avoiding the directory traversal issue
76 - mkdir($dest) or syserr(g_('cannot create directory %s'), $dest);
[all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-networking/recipes-daemons/vsftpd/files/ |
| H A D | change-secure_chroot_dir.patch | 8 Change secure_chroot_dir pointing to a volatile directory.
26 -2b) vsftpd needs the (empty) directory /usr/share/empty in the default
27 +2b) vsftpd needs the (empty) directory /var/run/vsftpd/empty in the default
28 configuration. Add this directory in case it does not already exist. e.g.:
31 -mkdir: cannot create directory `/usr/share/empty': File exists
33 +mkdir: cannot create directory `/var/run/vsftpd/empty': File exists
36 valid home directory (which is NOT owned or writable by the user "ftp").
54 @@ -969,7 +969,7 @@ This option should be the name of a directory which is empty. Also, the
55 directory should not be writable by the ftp user. This directory is used
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | configfs-iio | 7 directory. It contains sub-groups corresponding to IIO
14 Industrial IO software triggers directory.
20 High resolution timers directory. Creating a directory here
27 Industrial IO software devices directory.
33 Dummy IIO devices directory. Creating a directory here will result
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-devtools/tcltk/tk/ |
| H A D | tkprivate.diff | 1 Patch by Chris Waters sets path which are normally point to a directory
10 # build directory.
15 # installed directory.
17 # different place than the directory containing the source files, this
28 # build directory.
33 # installed directory.
36 # Path to the Tk stub library in the build directory.
40 # Path to the Tk stub library in the install directory.
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/gnu-config/gnu-config/ |
| H A D | gnu-configize.in | 220 my ($directory) = @_;
225 verb "Entering directory `$directory'";
226 chdir $directory
227 or error "cannot chdir to $directory: $!";
233 verb "Leaving directory `$directory'";
247 for my $directory (@ARGV)
249 gnu_configize ($directory);
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-extended/unzip/unzip/ |
| H A D | CVE-2019-13232_p3.patch | 5 directory.
8 which is a zip container with the central directory placed at the
11 central directory, as well as the end of central directory records,
35 - span that covers the central directory though the end of the file. */
37 + spans that cover any extra bytes at the start, the central directory,
38 + the end of central directory record (including the Zip64 end of central
39 + directory locator, if present), and the Zip64 end of central directory
107 + end of central directory record,
109 + end of central directory locator,
111 + end of central directory record */
[all …]
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-graphics/shaderc/files/ |
| H A D | 0001-cmake-disable-building-external-dependencies.patch | 52 COMMENT "Update build-version.inc in the Shaderc build directory (if necessary).")
65 def mkdir_p(directory):
66 """Make the directory, and all its ancestors as required. Any of the
67 @@ -121,25 +122,32 @@ def get_version_string(project, directory):
68 directory, which consists of software version string and git description
72 - detailed_version_string_lst.append(deduce_software_version(directory))
73 - detailed_version_string_lst.append(describe(directory).replace('"', '\\"'))
74 + if isinstance(directory, str) and os.path.isdir(directory):
76 + detailed_version_string_lst.append(deduce_software_version(directory))
77 + detailed_version_string_lst.append(describe(directory).replace('"', '\\"'))
|
| /OK3568_Linux_fs/kernel/Documentation/PCI/endpoint/ |
| H A D | pci-endpoint-cfs.rst | 17 The PCI Endpoint Core layer creates pci_ep directory in the mounted configfs
18 directory. configfs can be mounted using the following command::
27 the *controllers* directory and every EPF driver present in the system
28 will have an entry in the *functions* directory.
38 Every registered EPF driver will be listed in controllers directory. The
51 user has to create a directory inside <EPF DriverN>.
53 Every <EPF device> directory consists of the following entries that can be
75 Every registered EPC device will be listed in controllers directory. The
89 The <EPC Device> directory will have a list of symbolic links to
93 The <EPC Device> directory will also have a *start* field. Once
|
| /OK3568_Linux_fs/buildroot/docs/manual/ |
| H A D | how-buildroot-works.txt | 16 * The +toolchain/+ directory contains the Makefiles
21 * The +arch/+ directory contains the definitions for all the processor
24 * The +package/+ directory contains the Makefiles and
27 sub-directory per package.
29 * The +linux/+ directory contains the Makefiles and associated files for
32 * The +boot/+ directory contains the Makefiles and associated files for
35 * The +system/+ directory contains support for system integration, e.g.
38 * The +fs/+ directory contains the Makefiles and
42 Each directory contains at least 2 files:
55 etc. in the output directory (+output/+ by default,
|
| H A D | customize-patches.txt | 20 . For every directory - +<global-patch-dir>+ - that exists in
25 directory exists.
27 * Otherwise, +<global-patch-dir>/<packagename>+ if the directory
33 * If a +series+ file exists in the package directory, then patches are
46 specifying a custom patch directory for packages. It can be used to
47 specify a patch directory for any package in buildroot. It should also
48 be used in place of the custom patch directory options that are
51 directory.
|
| /OK3568_Linux_fs/yocto/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-hello.rst | 23 your machine, the BitBake directory appears as follows::
44 At this point, you should have BitBake cloned to a directory that
51 directory to where your local BitBake files are and run the following
60 The recommended method to run BitBake is from a directory of your
61 choice. To be able to run BitBake from any directory, you need to add
68 Next, add the directory location
70 ``/home/scott-lenovo/bitbake/bin`` directory to the front of the
76 line while working from any directory.
117 #. **Create a Project Directory:** First, set up a directory for the
119 directory::
[all …]
|
| /OK3568_Linux_fs/buildroot/support/misc/ |
| H A D | target-dir-warning.txt | 4 This directory does *not* contain the root filesystem that you can use
7 files correctly in this directory to make it usable as a root
10 For that reason, do *not* use the contents of this directory to mount
11 your root filesystem over NFS or copy the contents of this directory
19 extract to your SD card or to some directory exposed through NFS,
21 images/rootfs.tar image in your Buildroot output directory, which you
27 directory, but there is a post-processing step to create device files
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/squashfs-tools/squashfs-tools/ |
| H A D | CVE-2021-41072.patch | 13 Subject: [PATCH] Unsquashfs: additional write outside destination directory
19 files outside of the destination directory.
22 that contain a symbolic link pointing outside of the destination directory,
23 coupled with an identically named file within the same directory, can
24 cause Unsquashfs to write files outside of the destination directory.
27 of the destination directory, which is then followed when writing the
28 duplicate identically named file within the directory.
31 filenames within a directory. As directories in v2.1, v3.x, and v4.0
85 + /* check directory for duplicate names. Need to sort directory first */
88 + ERROR("File system corrupted: directory has duplicate names\n");
[all …]
|
| /OK3568_Linux_fs/buildroot/package/netatalk/ |
| H A D | 0002-fix-ftbs-multiple-def-of-invalid_dircache_entries.patch | 10 etc/afpd/directory.h | 2 +-
13 diff --git a/etc/afpd/directory.h b/etc/afpd/directory.h
15 --- a/etc/afpd/directory.h
16 +++ b/etc/afpd/directory.h
|
| /OK3568_Linux_fs/u-boot/arch/ |
| H A D | Kconfig | 139 appropriate arch/<CONFIG_SYS_ARCH> directory.
146 arch/<CONFIG_SYS_ARCH>/cpu/<CONFIG_SYS_CPU> directory.
148 This is optional. For those targets without the CPU directory,
154 This option should contain the SoC name to build the directory
157 This is optional. For those targets without the SoC directory,
166 directory is compiled.
168 board/<CONFIG_SYS_VENDOR>/<CONFIG_SYS_BOARD> directory are compiled.
170 This is optional. For those targets without the vendor directory,
178 or board/<CONFIG_SYS_BOARD> directory is compiled depending on
181 This is optional. For those targets without the board directory,
|
| /OK3568_Linux_fs/yocto/poky/documentation/sdk-manual/ |
| H A D | using.rst | 34 usage. You can see the directory structure in the
35 ":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`"
46 appropriate :yocto_dl:`toolchain </releases/yocto/yocto-&DISTRO;/toolchain/>` directory within
91 into the ``poky_sdk`` folder in your home directory. You can choose to
93 However, because files need to be written under that directory during
104 If you do not have write permissions for the directory into which you
106 that case, set up the proper permissions in the directory and run the
114 Enter target directory for SDK (default: /opt/poky/&DISTRO;):
123 ":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`"
124 section for more details on the resulting directory structure of the installed
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/driver-model/ |
| H A D | binding.rst | 63 A symlink is created in the bus's 'devices' directory that points to
64 the device's directory in the physical hierarchy.
66 A symlink is created in the driver's 'devices' directory that points
67 to the device's directory in the physical hierarchy.
69 A directory for the device is created in the class's directory. A
70 symlink is created in that directory that points to the device's
74 physical directory to either its class directory, or the class's
75 top-level directory. One can also be created to point to its driver's
76 directory also.
|
| H A D | class.rst | 79 sysfs directory structure
81 There is a top-level sysfs directory named 'class'.
83 Each class gets a directory in the class directory, along with two
92 Drivers registered with the class get a symlink in the drivers/ directory
93 that points to the driver's directory (under its bus directory)::
102 Each device gets a symlink in the devices/ directory that points to the
103 device's directory in the physical hierarchy::
134 sysfs directory using::
140 class's directory in sysfs.
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/dynamic-layers/gnome-layer/recipes-graphics/openbox/openbox-xdgmenu/ |
| H A D | port-gnome-menus3.patch | 73 void process_directory(GMenuTreeDirectory *directory, gboolean isRoot)
79 - GSList *entryList = gmenu_tree_directory_get_contents (directory);
84 + GMenuTreeIter *iter = gmenu_tree_directory_iter (directory);
98 - g_strjoinv("&", g_strsplit(gmenu_tree_directory_get_name(directory),"&",0)),
99 - g_strjoinv("&", g_strsplit(gmenu_tree_directory_get_name(directory),"&",0)),
102 + g_strjoinv("&", g_strsplit(gmenu_tree_directory_get_name(directory),"&",0)),
103 + g_strjoinv("&", g_strsplit(gmenu_tree_directory_get_name(directory),"&",0)));
109 - g_strjoinv("&", g_strsplit(gmenu_tree_directory_get_name(directory),"&",0)),
110 - g_strjoinv("&", g_strsplit(gmenu_tree_directory_get_name(directory),"&",0)));
|