linux/poky.git/meta/recipes-core/udev/udev-extraconf, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

udev-extraconf: Avoid slashes in mountpoint names

2025-10-06T22:15:59+00:00

Devices with labels such as "Hello/World/Foo/Bar" cause mount.sh to create the directory structure @MOUNT_BASE@/Hello/World/Foo/Bar. The partition is mounted to the nested "Bar" directory. On device removal, the directory structure is not cleaned up. This commit replaces all forward slashes in partition labels by underscores to avoid this edge case. (From OE-Core rev: aa071e2f44b9f76883a7c316ea79c60ae3824d6c) Signed-off-by: Robert Tiemann Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

udev-extraconf: Speed up mount.sh

2025-10-06T22:15:59+00:00

On devices with many partitions, running blkid without parameters can be rather slow because all block devices are inspected: $ time /sbin/blkid real 0m0.474s user 0m0.026s sys 0m0.172s versus $ time /sbin/blkid /dev/mmcblk0p10 real 0m0.027s user 0m0.002s sys 0m0.018s Plugging in a device with 5 partitions means that mount.sh is going to be executed 5 times, and so will be blkid. In the real-world case outlined above, this adds up to an overhead of about 2.3 seconds for blkid alone. This commit changes mount.sh so that the block device of interest is passed directly to blkid such that blkid inspects only that device, leading to significant speedup. (From OE-Core rev: 5e90348ce2fa400c77641062aa0b1efb52c9f955) Signed-off-by: Robert Tiemann Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

udev-extraconf: Switch from ifconfig to ip

2025-02-20T11:57:49+00:00

ifconfig is obsolete, drop the call and replace with ip instead. (From OE-Core rev: e18e29728ace57d7ef1409c3c13df9e1857af3ac) Signed-off-by: Richard Purdie

udev-extraconf: Allow FAT mount group to be specified

2025-01-14T11:57:52+00:00

Adds a variable that allows the group given permissions to access FAT mounted file systems to be specified, instead of being hardcoded to 'disk'. As a note, the usage of 'disk' as the mount group is not a very secure default, since the disk user usually has read/write access to all block devices in /dev/, meaning that adding a user to this group for the purpose of accessing FAT file systems effectively gives the write access to all block devices. (From OE-Core rev: c723dbc329d4cf2a75022f8dd1cfa304383bb4f5) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

udev-extraconf: fix network.sh script did not configure hotplugged interfaces

2024-10-22T11:28:18+00:00

Udev script network.sh is called when a new ethernet interface is plugged (eg. USB). Due to some (old) missing files, this script does nothing, instead of configuring the interfaces with ifup. I just commented the corresponding lines to allow the script to reach the part where it calls ifup. (From OE-Core rev: 160f7139172ffdf510a0d7d4e85f7fbaac7fd000) Signed-off-by: Regis Dargent Fixes [YOCTO 15616] network.sh relies on (long) missing files (eg. /etc/network/options, /etc/init.d/network) to decide if it should configure the new network interface (ifup) or put its name in /etc/udev_network_queue for future initialization by /etc/init.d/network service. The actual result was that the new hotplugged interface was never automatically configured. Removing the obsolete tests allows the script to do its intended job. Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

udev-extraconf: Add collect flag to mount

2024-09-10T12:05:00+00:00

Adds extra "--collect" flag to the mount command within automount_systemd. This is intended to fix an observed deadlock after rapidly inserting and removing external media. This is because if the mount command fails, the transient mount will enter a failed state. The next time the media is inserted, automount_systemd bails because the first consition finds that the file path for the failed transient mount still exists. This leaves the external media unmounted and cannot be mounted until the mount is fixed via systemctl or the device is rebooted. Adding "--collect" ensures that the transient mount is cleaned up after entering a failed state, which ensures that the media can still be mounted when it's re-inserted. (From OE-Core rev: f0cda74d73eb8c14cd6f695f514108f1e94984a6) Signed-off-by: Colin McAllister Signed-off-by: Richard Purdie

udev-extraconf: fix unmount directories containing octal-escaped chars

2024-01-26T16:06:29+00:00

USB devices are auto-mounted in a directory named like theirs labels. Special characters like whitespace are octal-escaped in /proc/mounts output. Using directly this output file as an argument for umount failed and the mount directory can't be removed as still busy. Using printf allows these special characters to be unescaped. (From OE-Core rev: 37f17625d931a06888388682dc2b1f5a2d298125) Signed-off-by: Jonathan GUILLOT Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

udev-extraconf: mount.sh: check if filesystem is supported before mounting

2023-11-10T17:44:27+00:00

Check if the filesystem is supported by the kernel before trying to mount it. Systemd-mount will mount the directories asynchronously resulting in stale directories if the devices filesystem is not supported. (From OE-Core rev: 695e0a41e3c1cb47484605934a57e7df591bd19f) Signed-off-by: Lukas Funke Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

udev-extraconf:mount.sh: fix a umount issue

2022-07-23T12:55:26+00:00

Only touching /tmp/.automount-$name is not good enough, it must contain the mount name, otherwise umount could not get the path from it. (From OE-Core rev: ccea69032329f3ba43c727d9eb71b1d063b89824) Signed-off-by: Ming Liu Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie