The device tree may passed by the firmware as UEFI configuration
table. Let lsefisystab display a short text and not only the GUID
for the device tree.
smbios: Add a module for retrieving SMBIOS information
The following are two use cases from Rajat Jain <email address hidden>:
1) We have a board that boots Linux and this board itself can be plugged
into one of different chassis types. We need to pass different
parameters to the kernel based on the "CHASSIS_TYPE" information
that is passed by the bios in the DMI/SMBIOS tables.
2) We may have a USB stick that can go into multiple boards, and the
exact kernel to be loaded depends on the machine information
(PRODUCT_NAME etc) passed via the DMI.
Signed-off-by: David Michael <email address hidden>
Reviewed-by: Daniel Kiper <email address hidden>
(cherry picked from commit 688023cd0ac4c985fd0e2ec477fcf1ec33a0e49c)
Patch-Name: cherrypick-smbios-module.patch
Skip /dev/disk/by-id/lvm-pvm-uuid entries from device iteration
The following LVM2 commit:
commit 417e52c13a8156b11c25c411d44bda8b32bf87e4
Author: Peter Rajnoha <email address hidden>
Date: Tue Feb 18 07:27:21 2014
udev: create /dev/disk/by-id/lvm-pv-uuid-<PV_UUID> symlink for a PV
We already have /dev/disk/by-id/dm-uuid-... (which encompasses the
VG UUID and LV UUID in case of LVs since the mapping's UUID is
VG+LV UUID together) and /dev/disk/by-id/dm-name-... (which encompasses
the VG and LV name in case of LVs).
This patch addds /dev/disk/by-id/lvm-pv-uuid-<PV_UUID> that completes
this scheme and makes navigation a bit easier using PV UUIDs since
one can navigate using PV UUIDs only and there's no need to do extra
PV UUID <--> kernel name matching (the PV UUID is stable across reboots).
This may come in handy in various scripts.
Since we already have the PV UUID stored in udev database (as a result
of blkid call - returned in ID_FS_UUID blkid's variable), this operation
is very cheap indeed, just creating the extra one symlink.
creates a udev rule that populates /dev/disk/by-id with LVM PVs
according to discovered UUIDs. That will trigger a bad logic in
debian-installer as the installer depends on grub_util_iterate_devices()
logic to discover the disks that can have grub installed.
This change only ignores those entries, so debian-installer bad
execution path is not triggered, just like grub_iterate_devices()
already does for other similar entries, like the partition ones.
Author: Rafael David Tinoco <email address hidden>
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1838525
Last-Update: 2019-10-07
Patch-Name: ubuntu-skip-disk-by-id-lvm-pvm-uuid-entries.patch
UBUNTU: Boot from multipath-dependent symlink when / is multipathed.
If / is multipathed, there will be multiple paths to the partition, so
using root=UUID= exposes the boot process to udev races. In addition
grub-probe --target device / in this case reports /dev/dm-1 or similar
-- better to use a symlink that depends on the multipath name.
