Searched refs:symlinks (Results 1 – 25 of 43) sorted by relevance
12
| /Linux-v5.4/scripts/gdb/linux/ |
| D | Makefile | 5 symlinks := $(patsubst $(srctree)/$(src)/%,%,$(wildcard $(srctree)/$(src)/*.py)) macro
10 extra-y += $(symlinks)
11 $(addprefix $(obj)/, $(symlinks)): FORCE
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| 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 | 82 blob names, ending in symlinks to the by_key entry for each
91 Construction of the directory tree and symlinks is done on a
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | path-lookup.rst | 9 - <https://lwn.net/Articles/650786/> A walk among the symlinks
26 the early parts of the analysis we will divide off symlinks - leaving
27 them until the final part. Well before we get to symlinks we have
824 automount point is found, or in a couple of cases involving symlinks.
922 A walk among the symlinks
928 symlinks and lead to the special care needed for the final component.
936 appear in a path prior to the final component: directories and symlinks.
959 There are two reasons for placing limits on how many symlinks can
980 at most 40 symlinks in any one path lookup. It previously imposed a
987 symlinks. In many cases this will be sufficient. If it isn't, a
[all …]
|
| D | hpfs.txt | 92 You can do symlinks on HPFS partition, symlinks are achieved by setting extended
94 chgrp symlinks but I don't know what is it good for. chmoding symlink results
95 in chmoding file where symlink points. These symlinks are just for Linux use and
96 incompatible with OS/2. OS/2 PmShell symlinks are not supported because they are
|
| D | sysfs.txt | 304 devices/ contains symlinks for each device discovered in the system
316 directories there are symlinks named <major>:<minor>. These symlinks
|
| D | hfs.txt | 54 o You can't create hard- or symlinks, device files, sockets or FIFOs.
|
| D | porting.rst | 232 and let it call whatever you had as ->revlidate() + (for symlinks that
539 from ->follow_link for normal symlinks, or nd_jump_link for magic
591 for embedded ("fast") symlinks just set inode->i_link to wherever the
620 symlinks. That includes any preseeding that might be done during symlink
658 symlinks are no longer the only inodes that do *not* have i_bdev/i_cdev/
747 ->readlink is optional for symlinks. Don't set, unless filesystem needs
|
| D | romfs.txt | 14 about 30K (and does not support device nodes or symlinks), while the
134 please remember that only regular files, and symlinks are supposed to
|
| D | fscrypt.rst | 465 files, directories (recursively), and symlinks created in the
936 symlinks behave very similarly to their unencrypted counterparts ---
978 EXT4 filesystem with a 4K block size, unencrypted symlinks can be up
979 to 4095 bytes long, while encrypted symlinks can only be up to 4093
989 files, directories, and symlinks even before their encryption key has
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | numaperf.rst | 44 kernel provides symlinks to each other. The following example lists the
47 # symlinks -v /sys/devices/system/node/nodeX/access0/targets/
50 # symlinks -v /sys/devices/system/node/nodeY/access0/initiators/
|
| /Linux-v5.4/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.
|
| D | driver.rst | 140 directory will contain symlinks to the directories of devices it
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | acpi_power_meter.rst | 37 contains symlinks to the devices that this meter measures.
|
| /Linux-v5.4/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 | 133 Users: udev rules to create /dev/disk/by-id/ symlinks
|
| /Linux-v5.4/drivers/fsi/ |
| D | Kconfig | 29 symlinks in /dev/fsi/by-path when this option is enabled.
|
| /Linux-v5.4/drivers/base/ |
| D | Kconfig | 36 symlinks, and apply needed permissions.
39 symlinks.
|
| /Linux-v5.4/Documentation/admin-guide/cifs/ |
| D | usage.rst | 188 supported this feature. Samba server does not allow symlinks that refer to files
189 outside of the share, so in Samba versions prior to 3.0.6, most symlinks to
195 such symlinks safely by converting unsafe symlinks (ie symlinks to server
199 application using the cifs vfs. Absolute symlinks will work to Samba 3.0.5 or
637 Enable support for Minshall+French symlinks
640 'sfu' option. Minshall+French symlinks are used even if
|
| D | todo.rst | 114 types. Try nested symlinks (8 deep). Return max path name in stat -f information
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | devices.rst | 229 symlinks and lock all possible names; additionally, it is recommended
239 installed in the order the symlinks are resolved.
|
| /Linux-v5.4/Documentation/admin-guide/gpio/ |
| D | sysfs.rst | 165 symlinks from elsewhere in sysfs to the GPIO sysfs node. Drivers can
|
| /Linux-v5.4/Documentation/kbuild/ |
| D | kconfig.rst | 47 break symlinks when .config is a symlink to somewhere else.
|
| /Linux-v5.4/Documentation/usb/ |
| D | gadget_configfs.rst | 379 - associating functions with configurations (symlinks)
|
12
