| /linux-6.3-rc2/Documentation/admin-guide/ |
| A D | devices.rst | 77 /dev/fd /proc/self/fd symbolic File descriptors
78 /dev/stdin fd/0 symbolic stdin file descriptor
79 /dev/stdout fd/1 symbolic stdout file descriptor
80 /dev/stderr fd/2 symbolic stderr file descriptor
81 /dev/nfsd socksys symbolic Required by iBCS-2
82 /dev/X0R null symbolic Required by iBCS-2
95 /dev/ramdisk ram0 symbolic Backward compatibility
96 /dev/ftape qft0 symbolic Backward compatibility
97 /dev/bttv0 video0 symbolic Backward compatibility
98 /dev/radio radio0 symbolic Backward compatibility
[all …]
|
| A D | java.rst | 125 # Go down one more level of symbolic links
130 echo " Too many symbolic links encountered"
378 To add a Java program to your path best put a symbolic link to the main
|
| /linux-6.3-rc2/Documentation/PCI/endpoint/ |
| A D | pci-endpoint-cfs.rst | 84 The <EPF Device> directory can have a list of symbolic links
85 (<Symlink EPF Device 31>) to other <EPF Device>. These symbolic links should
108 The <EPC Device> directory will have a list of symbolic links to
109 <EPF Device>. These symbolic links should be created by the user to
|
| /linux-6.3-rc2/Documentation/ABI/testing/ |
| A D | sysfs-devices-memory | 93 When CONFIG_NUMA is enabled, a symbolic link that
96 For example, the following symbolic link is created for
107 /sys/devices/system/node/nodeX/memoryY is a symbolic link that
109 memory section directory. For example, the following symbolic
|
| A D | sysfs-devices-power_resources_D0 | 9 If present, it contains symbolic links to device directories
|
| A D | sysfs-devices-power_resources_wakeup | 9 If present, it contains symbolic links to device directories
|
| A D | sysfs-devices-power_resources_D1 | 10 If present, it contains symbolic links to device directories
|
| A D | sysfs-devices-power_resources_D2 | 10 If present, it contains symbolic links to device directories
|
| A D | sysfs-devices-power_resources_D3hot | 10 If present, it contains symbolic links to device directories
|
| A D | sysfs-dev | 8 beneath /sys/dev containing symbolic links with names of
|
| A D | sysfs-bus-vfio-mdev | 40 This directory contains symbolic links pointing to mdev
101 This is symbolic link pointing to supported type, <type-id>
|
| A D | sysfs-bus-pci | 182 This symbolic link appears when hardware supports the SR-IOV
184 The symbolic link points to the PCI device sysfs entry of the
191 This symbolic link appears when hardware supports the SR-IOV
194 The symbolic link points to the PCI device sysfs entry of
201 This symbolic link appears when a device is a Virtual Function.
202 The symbolic link points to the PCI device sysfs entry of the
227 This symbolic link points to the PCI hotplug controller driver
|
| A D | sysfs-bus-pci-devices-cciss | 33 Description: A symbolic link to /sys/block/cciss!cXdY
|
| /linux-6.3-rc2/Documentation/filesystems/ |
| A D | affs.rst | 95 symbolic links on an AFFS partition. Default = "/".
99 When symbolic links with an absolute path are created
152 with symbolic links. While Linux has a file system with exactly one
155 these entities are called "volumes". They have symbolic names which
156 can be used to access them. Thus, symbolic links can point to a
165 /amiga/WB and /amiga/Graphics). A symbolic link referring to
|
| A D | bfs.rst | 34 /dev/loopN device if /etc/mtab file on your system is a symbolic link to
|
| /linux-6.3-rc2/Documentation/i2c/ |
| A D | i2c-sysfs.rst | 40 There is a list of symbolic links under that directory. The links that
139 is to read the symbolic link ``device`` under the I2C bus directory by using
142 An alternative symbolic link to check is ``mux_device``. This link only exists
147 If the symbolic link points to a directory ending with ``.i2c``, it should be a
156 In this case, ``i2c-7`` is a physical I2C bus, so it does not have the symbolic
161 On the other hand, if the symbolic link points to another I2C bus, the I2C bus
223 # cd the channel symbolic link
326 There is a symbolic link named ``driver`` to tell what Linux kernel driver was
351 will have symbolic link ``channel-*`` inside its device directory.
352 These symbolic links point to their logical I2C bus directories::
|
| /linux-6.3-rc2/Documentation/trace/ |
| A D | events-msr.rst | 39 to add symbolic MSR names.
|
| /linux-6.3-rc2/tools/testing/selftests/tc-testing/plugin-lib/ |
| A D | README-PLUGINS | 2 Make a set of numbered symbolic links from there to the actual plugins.
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/clock/ |
| A D | brcm,kona-ccu.txt | 67 its symbolic specifier (rather than its numeric index value) should
112 its symbolic specifier (rather than its numeric index value) should
|
| /linux-6.3-rc2/Documentation/firmware-guide/acpi/ |
| A D | namespace.rst | 20 in this hierarchy there is a corresponding symbolic link in the
300 directory contains the "physical_node" symbolic link to the sysfs
302 sysfs directory will then contain the "firmware_node" symbolic link to
310 namespace object will contain the 'physical_node' symbolic link to the
|
| /linux-6.3-rc2/tools/thermal/tmon/ |
| A D | README | 15 introduced sysfs entry at /sys/class/thermal with a matrix of symbolic
|
| /linux-6.3-rc2/fs/isofs/ |
| A D | Kconfig | 8 long Unix filenames and symbolic links are also supported by this
|
| /linux-6.3-rc2/kernel/debug/kdb/ |
| A D | kdb_main.c | 1532 int symbolic, int nosect, int bytesperword, in kdb_md_line() argument
1556 if (symbolic) in kdb_md_line()
1606 int symbolic = 0; in kdb_md() local
1741 symbolic = 1; in kdb_md()
1756 int n, z, num = (symbolic ? 1 : (16 / bytesperword)); in kdb_md()
1769 kdb_md_line(fmtstr, addr, symbolic, nosect, bytesperword, in kdb_md()
|
| /linux-6.3-rc2/Documentation/locking/ |
| A D | mutex-design.rst | 95 - Uses symbolic names of mutexes, whenever they are printed
97 - Point-of-acquire tracking, symbolic lookup of function names,
|
| /linux-6.3-rc2/Documentation/networking/ |
| A D | netif-msg.rst | 35 e.g. "lance_debug", so that a kernel symbolic debugger could locate and
|