Searched refs:symlinks (Results 1 – 25 of 46) sorted by relevance
12
| /linux-6.6.21/scripts/gdb/linux/ |
| D | Makefile | 5 symlinks := $(patsubst $(srctree)/$(src)/%,%,$(wildcard $(srctree)/$(src)/*.py)) macro
10 always-y += $(symlinks)
11 $(addprefix $(obj)/, $(symlinks)): FORCE
|
| /linux-6.6.21/Documentation/ABI/testing/ |
| D | sysfs-devices-consumer | 5 The /sys/devices/.../consumer:<consumer> are symlinks to device
8 bus:device name. There can be zero or more of these symlinks
|
| D | sysfs-devices-supplier | 5 The /sys/devices/.../supplier:<supplier> are symlinks to device
8 bus:device name. There can be zero or more of these symlinks
|
| D | sysfs-class | 8 of either subdirectories, or symlinks to other
12 to handle both subdirectories or symlinks in order to
|
| D | sysfs-devices | 14 on the symlinks there to point to the proper location
|
| D | sysfs-firmware-qemu_fw_cfg | 85 blob names, ending in symlinks to the by_key entry for each
94 Construction of the directory tree and symlinks is done on a
|
| /linux-6.6.21/Documentation/filesystems/ |
| D | path-lookup.rst | 9 - <https://lwn.net/Articles/650786/> A walk among the symlinks
27 the early parts of the analysis we will divide off symlinks - leaving
28 them until the final part. Well before we get to symlinks we have
839 automount point is found, or in a couple of cases involving symlinks.
937 A walk among the symlinks
943 symlinks and lead to the special care needed for the final component.
951 appear in a path prior to the final component: directories and symlinks.
974 There are two reasons for placing limits on how many symlinks can
995 at most 40 (MAXSYMLINKS) symlinks in any one path lookup. It previously imposed
1002 symlinks. In many cases this will be sufficient. If it isn't, a
[all …]
|
| D | hpfs.rst | 103 You can do symlinks on HPFS partition, symlinks are achieved by setting extended
105 chgrp symlinks but I don't know what is it good for. chmoding symlink results
106 in chmoding file where symlink points. These symlinks are just for Linux use and
107 incompatible with OS/2. OS/2 PmShell symlinks are not supported because they are
|
| D | sysfs.rst | 315 devices/ contains symlinks for each device discovered in the system
330 directories there are symlinks named <major>:<minor>. These symlinks
|
| D | hfs.rst | 59 * You can't create hard- or symlinks, device files, sockets or FIFOs.
|
| D | romfs.rst | 18 about 30K (and does not support device nodes or symlinks), while the
141 please remember that only regular files, and symlinks are supposed to
|
| D | porting.rst | 238 and let it call whatever you had as ->revlidate() + (for symlinks that
545 from ->follow_link for normal symlinks, or nd_jump_link for magic
597 for embedded ("fast") symlinks just set inode->i_link to wherever the
626 symlinks. That includes any preseeding that might be done during symlink
664 symlinks are no longer the only inodes that do *not* have i_bdev/i_cdev/
750 ->readlink is optional for symlinks. Don't set, unless filesystem needs
|
| D | autofs.rst | 49 Objects can only be created by the automount daemon: symlinks are
239 time stamp on each directory or symlink. For symlinks it genuinely
306 remove directories and symlinks using normal filesystem operations.
544 create directories or symlinks in the root directory, but not in other
|
| /linux-6.6.21/Documentation/driver-api/driver-model/ |
| D | binding.rst | 94 of the driver is decremented. All symlinks between the two are removed.
98 one. The device is removed from that list and the symlinks removed.
|
| /linux-6.6.21/Documentation/admin-guide/mm/ |
| D | numaperf.rst | 45 kernel provides symlinks to each other. The following example lists the
48 # symlinks -v /sys/devices/system/node/nodeX/access0/targets/
51 # symlinks -v /sys/devices/system/node/nodeY/access0/initiators/
|
| /linux-6.6.21/Documentation/hwmon/ |
| D | acpi_power_meter.rst | 37 contains symlinks to the devices that this meter measures.
|
| /linux-6.6.21/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 105 The directory containing symlinks to memory initiator
115 The directory containing symlinks to memory targets that
|
| D | sysfs-bus-firewire | 136 Users: udev rules to create /dev/disk/by-id/ symlinks
|
| /linux-6.6.21/drivers/base/ |
| D | Kconfig | 39 symlinks, and apply needed permissions.
42 symlinks.
|
| /linux-6.6.21/drivers/fsi/ |
| D | Kconfig | 29 symlinks in /dev/fsi/by-path when this option is enabled.
|
| /linux-6.6.21/Documentation/filesystems/spufs/ |
| D | spu_create.rst | 74 ELOOP Too many symlinks were found while resolving pathname.
|
| /linux-6.6.21/Documentation/admin-guide/cifs/ |
| D | usage.rst | 187 supported this feature. Samba server does not allow symlinks that refer to files
188 outside of the share, so in Samba versions prior to 3.0.6, most symlinks to
194 such symlinks safely by converting unsafe symlinks (ie symlinks to server
198 application using the cifs vfs. Absolute symlinks will work to Samba 3.0.5 or
636 Enable support for Minshall+French symlinks
639 'sfu' option. Minshall+French symlinks are used even if
|
| D | todo.rst | 116 types. Try nested symlinks (8 deep). Return max path name in stat -f information
|
| /linux-6.6.21/Documentation/usb/ |
| D | gadget_configfs.rst | 100 Where function drivers support it, functions may allow symlinks to these custom
389 - associating functions with configurations (symlinks)
|
| /linux-6.6.21/Documentation/admin-guide/ |
| D | devices.rst | 228 symlinks and lock all possible names; additionally, it is recommended
238 installed in the order the symlinks are resolved.
|
12