linux/poky.git/meta/recipes-core/udev, branch 2.8_M2

udev-extraconf: do not mount swap partitions

2019-07-23T21:26:28+00:00

Swap is a special filesystem that cannot be mounted, so do not try to, otherwise we will have service that tries and fails to mount it with the following error: systemd[1]: Mounting /run/media/nvme0n1p3... mount[1229]: mount: /run/media/nvme0n1p3: unknown filesystem type 'swap'. (From OE-Core rev: 7a2c56da85326043f0663c29535ac3fb555d96fe) Signed-off-by: Oleksandr Kravchuk Signed-off-by: Richard Purdie

eudev: update to 3.2.8

2019-06-28T12:28:38+00:00

(From OE-Core rev: e2ae59520e3df661aced4f67fda630cca6aaf6f8) Signed-off-by: Oleksandr Kravchuk Signed-off-by: Richard Purdie

eudev: upgrade 3.2.5 -> 3.2.7

2018-12-20T14:53:55+00:00

For changes, see: https://github.com/gentoo/eudev/compare/v3.2.5...v3.2.7 (From OE-Core rev: dd2c4d9d85e70abacfa70fbe9281f393452875ea) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

udev-extraconf: Skip the entry in /etc/fstab when using the systemd-mount

2018-10-25T13:53:44+00:00

When using systemd, the systemd-fstab-generator would parse the /etc/fstab and create the corresponding unit dynamically. So we don't need to handle the ADD action for the partitions in /etc/fstab. (From OE-Core rev: 6104109ceba1a1323e42d67a632921fb91184ab6) Signed-off-by: Kevin Hao Signed-off-by: Richard Purdie

udev-extraconf: Fix the recursively dependency for the systemd-mount

2018-10-25T13:53:44+00:00

The commit 4ca9402c3720 ("udev-extraconf: Add systemd-mount to udev-extraconf/mount.sh") uses the systemd-mount to mount the new added disk partitions if systemd is used. But it forgot to move the codes which tries to mount the partition by using the configuration in /etc/fstab to the non-systemd function. And it will cause the systemd-mount try to mount the partition synchronously and trigger a recursively dependency like the following: dev-sda1.device -> run-media-sda1.mount -> dev-sda1.device (From OE-Core rev: fcf6a4d629c05048cbb7298e285d84ff73a320d2) Signed-off-by: Kevin Hao Signed-off-by: Richard Purdie

udev-extraconf: Use the canonical file name of systemd

2018-10-25T13:53:44+00:00

The new version of systemd has changed the symbolic link between /sbin/init and /lib/systemd/systemd to relative. So the output of the command 'readlink /sbin/init' become: ../lib/systemd/systemd Then it causes the following check of "/lib/systemd/systemd" to return false. Fix this issue by using the canonical file name of the systemd. (From OE-Core rev: 352b3f0b07370d8df7d6ae13c0bac0697f7751ba) Signed-off-by: Kevin Hao Signed-off-by: Richard Purdie

udev-hwdb: fix postinstall scripts failures when multilib enabled

2018-10-25T13:53:44+00:00

When multilib is enabled and both udev-hwdb and ${MLPREFIX}udev-hwdb are installed to image, it fails to run one of their postinstall scripts that they both call ${base_bindir}/udevadm with same user mode qemu. Duplicate udevadm and add postinst-intercept update_udev_hwdb to fix the failures. (From OE-Core rev: d6b737a31a8842cdc770b05e28503c81a691d10d) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie

udev-extraconf: Add systemd-mount to udev-extraconf/mount.sh

2018-09-17T07:41:44+00:00

Udev-extraconf works correctly with sysvinit in the aspect of automounting block devices. But it has a serious problem in case of systemd. Block devices automounted by udev is unaccessible to host space(out of udevd's private namespace). For example, we cannot format those block devices. e.g. root@qemux86:~# mkfs.ext4 /dev/sda1 mke2fs 1.43.8 (1-Jan-2018) /dev/sda1 contains a ext4 file system last mounted on Tue Apr 3 06:22:41 2018 Proceed anyway? (y,N) y /dev/sda1 is apparently in use by the system; will not make a filesystem here! Other distributions has no such problem, because they use a series of rules to manager block devices. Different types of block devices match different rules. But udev-extraconf just use one rule, automount.rules, which results in this problem. The 'systemd-mount' command is recommended by the systemd community to solve such problems. This patch makes use of 'systemd-mount' to solve the above problem. [YOCTO #12644] (From OE-Core rev: a0b3389c5afc23f622f793cbad8b4135093e6f08) (From OE-Core rev: 4af22800a7af4fcb80cafe08d982a4850d9dd2ad) Signed-off-by: Hongzhi.Song Signed-off-by: Richard Purdie

eudev: set configure option --with-rootlibexecdir

2018-09-13T06:42:28+00:00

Set configure option '--with-rootlibexecdir' for eudev to fix udev.pc file conflict: | file /usr/share/pkgconfig/udev.pc conflicts between attempted installs of eudev-dev-3.2.5-r0.core2_64 and lib32-eudev-dev-3.2.5-r0.x86 It alway sets 'udevdir' in udev.pc with value '/lib/udev' that systemd does the same thing. (From OE-Core rev: 2585f4252a3831bf9c5e6ab69d9da2c1325e6bc0) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie

udev: only run qemu from postinst scripts if qemu usermode is supported

2018-06-18T10:07:58+00:00

Otherwise, there would be a failure at image creation time; avoid that by postponing to first boot explicitly. (From OE-Core rev: f3247720dc4b1c49e8fad734e20b17ba55843b97) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie