Searched full:mounted (Results 1 – 25 of 989) sorted by relevance
12345678910>>...40
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | sharedsubtree.rst | 24 that got mounted recently. Shared subtree semantics provide the necessary
82 And the same is true even when /dev/sd0 is mounted on /mnt/a. The
144 or too many mounted file systems
164 access the CD that got mounted recently.
177 So when a CD is inserted and mounted at /cdrom that mount gets
229 and if /usr has a versioning filesystem mounted, then that
274 to the same peer group. Anything mounted or unmounted under
322 be bind mounted.
386 mounted on mount 'B' at dentry 'b'. Also new mount 'C1', 'C2', 'C3' ...
387 are created and mounted at the dentry 'b' on all mounts where 'B'
[all …]
|
| D | autofs.rst | 13 might be needed are mounted. Processes that try to access those
39 filesystem type. Several "autofs" filesystems can be mounted and they
62 directory is a mount trap only if the filesystem is mounted *direct*
66 filesystem is mounted *indirect* and they are empty.
95 should be mounted on the directory and to return it. The VFS is
120 Firstly, before checking to see if any filesystem is mounted on the
129 expiry (automatic unmounting of the mounted filesystem) to
144 filesystem can be mounted below the first and for both of them to
176 be mounted or RCU-walk cannot handle the path.
182 would be safe to follow down into any mounted directory and the only
[all …]
|
| D | tmpfs.rst | 41 2) glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
117 when tmpfs is mounted by appending them to the mode before the NodeList.
133 tmpfs being mounted, but from time to time runs a kernel built without
136 mount options. It can be added later, when the tmpfs is already mounted
150 parameters with chmod(1), chown(1) and chgrp(1) on a mounted filesystem.
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | sharedsubtree.rst | 24 that got mounted recently. Shared subtree semantics provide the necessary
82 And the same is true even when /dev/sd0 is mounted on /mnt/a. The
144 or too many mounted file systems
165 access the CD that got mounted recently.
178 So when a CD is inserted and mounted at /cdrom that mount gets
230 and if /usr has a versioning filesystem mounted, then that
275 to the same peer group. Anything mounted or unmounted under
323 be bind mounted.
387 mounted on mount 'B' at dentry 'b'. Also new mount 'C1', 'C2', 'C3' ...
388 are created and mounted at the dentry 'b' on all mounts where 'B'
[all …]
|
| D | autofs.rst | 13 might be needed are mounted. Processes that try to access those
39 filesystem type. Several "autofs" filesystems can be mounted and they
62 directory is a mount trap only if the filesystem is mounted *direct*
66 filesystem is mounted *indirect* and they are empty.
95 should be mounted on the directory and to return it. The VFS is
120 Firstly, before checking to see if any filesystem is mounted on the
129 expiry (automatic unmounting of the mounted filesystem) to
144 filesystem can be mounted below the first and for both of them to
176 be mounted or RCU-walk cannot handle the path.
182 would be safe to follow down into any mounted directory and the only
[all …]
|
| D | ntfs3.rst | 16 - Supports NFS export of mounted NTFS volumes.
57 the NTFS volume is mounted.
99 - Use this parameter to show all meta-files (System Files) on a mounted
|
| D | devpts.rst | 22 the devpts filesystem in this manner devpts should be mounted with
28 kernel.pty.reserve = 1024 - reserved for filesystems mounted from the initial mount namespace
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | initrd.rst | 9 This RAM disk can then be mounted as the root file system and programs
10 can be run from it. Afterwards, a new root file system can be mounted
33 4) root device is mounted. if it is ``/dev/ram0``, the initrd image is
34 then mounted as root
47 procedure. Also note that file systems mounted under initrd continue to
65 the "normal" root file system is mounted. initrd data can be read
76 initrd is mounted as root, and the normal boot procedure is followed,
77 with the RAM disk mounted as root.
111 If initrd will not be mounted in some cases, its content is still
161 overwriting mounted devices, trying to start already running demons,
[all …]
|
| D | binderfs.rst | 15 Android binderfs can be mounted with::
26 binderfs filesystem can be mounted in user namespaces.
31 binderfs instances can be mounted with a limit on the number of binder
38 ``stats=global`` is only available for a binderfs instance mounted in the
79 Assuming an instance of binderfs has been mounted at ``/dev/binderfs``, the
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | initrd.rst | 9 This RAM disk can then be mounted as the root file system and programs
10 can be run from it. Afterwards, a new root file system can be mounted
33 4) root device is mounted. if it is ``/dev/ram0``, the initrd image is
34 then mounted as root
47 procedure. Also note that file systems mounted under initrd continue to
65 the "normal" root file system is mounted. initrd data can be read
76 initrd is mounted as root, and the normal boot procedure is followed,
77 with the RAM disk mounted as root.
111 If initrd will not be mounted in some cases, its content is still
161 overwriting mounted devices, trying to start already running demons,
[all …]
|
| D | binderfs.rst | 15 Android binderfs can be mounted with::
26 binderfs filesystem can be mounted in user namespaces.
31 binderfs instances can be mounted with a limit on the number of binder
38 ``stats=global`` is only available for a binderfs instance mounted in the
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/ |
| D | mount-matrix.txt | 22 and thus implying that the component should be mounted in a certain orientation
27 mounted on the same chassis as this screen, will likely take the screen as
36 A sensor can be mounted in any angle along the axes relative to the frame of
150 So unless the sensor is ideally mounted, we need a means to indicate the
183 mechanically mounted in an ideal way and we need no transformation):
189 The sensor is mounted 30 degrees (Pi/6 radians) tilted along the X axis, so we
196 The sensor is flipped 180 degrees (Pi radians) around the Z axis, i.e. mounted
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/iio/ |
| D | mount-matrix.txt | 22 and thus implying that the component should be mounted in a certain orientation
27 mounted on the same chassis as this screen, will likely take the screen as
36 A sensor can be mounted in any angle along the axes relative to the frame of
150 So unless the sensor is ideally mounted, we need a means to indicate the
183 mechanically mounted in an ideal way and we need no transformation):
189 The sensor is mounted 30 degrees (Pi/6 radians) tilted along the X axis, so we
196 The sensor is flipped 180 degrees (Pi radians) around the Z axis, i.e. mounted
|
| /kernel/linux/linux-6.6/fs/ntfs/ |
| D | debug.c | 13 * @sb: super block of mounted ntfs filesystem
17 * Outputs a warning to the syslog for the mounted ntfs filesystem described
56 * @sb: super block of mounted ntfs filesystem
60 * Outputs an error to the syslog for the mounted ntfs filesystem described
|
| /kernel/linux/linux-5.10/fs/ntfs/ |
| D | debug.c | 13 * @sb: super block of mounted ntfs filesystem
17 * Outputs a warning to the syslog for the mounted ntfs filesystem described
56 * @sb: super block of mounted ntfs filesystem
60 * Outputs an error to the syslog for the mounted ntfs filesystem described
|
| /kernel/linux/linux-5.10/tools/testing/selftests/kexec/ |
| D | kexec_common_lib.sh | 47 # Make sure that efivar_fs is mounted in the normal location
49 log_info "efivars is not mounted on $efivarfs"
179 # Make sure that securityfs is mounted
188 log_fail "$SECURITYFS :securityfs is not mounted"
|
| /kernel/linux/linux-6.6/tools/testing/selftests/kexec/ |
| D | kexec_common_lib.sh | 47 # Make sure that efivar_fs is mounted in the normal location
49 log_info "efivars is not mounted on $efivarfs"
178 # Make sure that securityfs is mounted
187 log_fail "$SECURITYFS :securityfs is not mounted"
|
| /kernel/linux/linux-5.10/drivers/base/ |
| D | Kconfig | 48 bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
53 mounted the root filesystem. The behavior can be overridden
56 the devtmpfs filesystem always needs to be mounted manually
57 after the rootfs is mounted.
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | mount.h | 5 * linkedlist with mounted filesystems.
43 * mount cannot be bind mounted, since this is how we create a mount
72 struct dentry *mnt_root; /* root of the mounted tree */
|
| D | sysv_fs.h | 42 char s_ronly; /* flag whether fs is mounted read-only */
83 char s_ronly; /* flag whether fs is mounted read-only */
112 char s_ronly; /* flag whether fs is mounted read-only */
142 char s_ronly; /* flag whether fs is mounted read-only */
180 char s_ronly; /* flag whether fs is mounted read-only */
|
| /kernel/linux/linux-6.6/drivers/base/ |
| D | Kconfig | 51 bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
56 mounted the root filesystem. The behavior can be overridden
59 the devtmpfs filesystem always needs to be mounted manually
60 after the rootfs is mounted.
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | mount.h | 5 * linkedlist with mounted filesystems.
42 * mount cannot be bind mounted, since this is how we create a mount
71 struct dentry *mnt_root; /* root of the mounted tree */
|
| D | sysv_fs.h | 42 char s_ronly; /* flag whether fs is mounted read-only */
83 char s_ronly; /* flag whether fs is mounted read-only */
112 char s_ronly; /* flag whether fs is mounted read-only */
142 char s_ronly; /* flag whether fs is mounted read-only */
180 char s_ronly; /* flag whether fs is mounted read-only */
|
| /kernel/linux/linux-6.6/Documentation/block/ |
| D | switching-sched.rst | 11 assuming that you have sysfs mounted on /sys. If you don't have sysfs mounted,
|
| /kernel/linux/linux-5.10/Documentation/block/ |
| D | switching-sched.rst | 11 assuming that you have sysfs mounted on /sys. If you don't have sysfs mounted,
|
12345678910>>...40