Searched full:rootfs (Results 1 – 25 of 31) sorted by relevance
12
| /Documentation/filesystems/ |
| D | ramfs-rootfs-initramfs.rst | 4 Ramfs, rootfs and initramfs
75 What is rootfs?
78 Rootfs is a special instance of ramfs (or tmpfs, if that's enabled), which is
79 always present in 2.6 systems. You can't unmount rootfs for approximately the
84 Most systems just mount another filesystem over rootfs and ignore it. The
87 If CONFIG_TMPFS is enabled, rootfs will use tmpfs instead of ramfs by
95 extracted into rootfs when the kernel boots up. After extracting, the kernel
96 checks to see if rootfs contains a file "init", and if so it executes it as PID
99 any). If rootfs does not contain an init program after the embedded cpio
124 umount the ramdisk. But initramfs is rootfs: you can neither pivot_root
[all …]
|
| D | ubifs.rst | 122 Mount "rootfs" volume of UBI device 0 to /mnt/ubifs ("rootfs" is volume
125 $ mount -t ubifs ubi0:rootfs /mnt/ubifs
128 to UBI and mount volume "rootfs":
129 ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs
|
| D | index.rst | 112 ramfs-rootfs-initramfs
|
| D | automount-support.rst | 84 rootfs for example). It does this by passing the MNT_EXPIRE flag to
|
| /Documentation/bpf/ |
| D | s390.rst | 21 * Disk image with s390 rootfs
82 mkdir ./s390.rootfs
83 sudo mount /dev/loopX ./s390.rootfs
98 ./s390.rootfs
99 sudo umount ./s390.rootfs
|
| /Documentation/driver-api/firmware/ |
| D | direct-fs-lookup.rst | 22 a race is possible with loading the driver and the real rootfs not yet being
30 when the real rootfs is ready and mounted.
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | tplink,safeloader-partitions.yaml | 22 partitions contain fully changeable content (like rootfs).
55 linux,rootfs;
|
| D | brcm,bcm963xx-cfe-nor-partitions.txt | 8 header found at beginning of the second erase block, containing the rootfs and
|
| D | brcm,bcm963xx-imagetag.txt | 9 sizes of the rootfs and kernel parts contained in the firmware.
|
| D | brcm,trx.txt | 16 useful for systems that keep kernel and rootfs separated.
|
| D | fixed-partitions.yaml | 99 linux,rootfs;
|
| D | partition.yaml | 55 linux,rootfs:
|
| /Documentation/filesystems/smb/ |
| D | cifsroot.rst | 68 Path to SMB share (rootfs).
80 path = /path/to/rootfs
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | phram.yaml | 44 label = "rootfs";
|
| /Documentation/translations/zh_TW/admin-guide/ |
| D | init.rst | 27 2) **初始化二進制不存在於根文件系統上init binary doesn't exist on rootfs** ：
|
| /Documentation/translations/zh_CN/admin-guide/ |
| D | init.rst | 24 2) **初始化二进制不存在于根文件系统上init binary doesn't exist on rootfs** ：
|
| /Documentation/tee/ |
| D | op-tee.rst | 116 * Attack vector: Replace the OP-TEE OS image in the rootfs to gain control of
120 rootfs, otherwise an attacker can modify the loaded OP-TEE binary by
121 modifying it in the rootfs.
|
| /Documentation/admin-guide/ |
| D | init.rst | 12 2) **init binary doesn't exist on rootfs**: Make sure you have the correct
|
| /Documentation/userspace-api/ |
| D | mfd_noexec.rst | 18 executables should come from the rootfs, which is protected by verified
|
| /Documentation/hwmon/ |
| D | smpro-hwmon.rst | 38 The sysfs files are allocated in the SMpro rootfs folder, with one root
|
| /Documentation/admin-guide/mm/ |
| D | shrinker_debugfs.rst | 29 rcu-kfree-0 sb-hugetlbfs-33 sb-rootfs-2 sb-tmpfs-49
|
| /Documentation/devicetree/bindings/mtd/ |
| D | marvell,nand-controller.yaml | 178 label = "Rootfs";
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-init.rst | 63 `zero` constrained, not meant for rootfs
|
| /Documentation/PCI/endpoint/ |
| D | pci-test-howto.rst | 137 The tool and script will be located in <rootfs>/usr/bin/
|
| /Documentation/arch/x86/ |
| D | pti.rst | 188 as mount(8) failing to mount the rootfs. These have
|
12