CVSROOT: /cvs
Module name: src
Changes by: k...@cvs.openbsd.org 2025/03/29 08:26:41
Modified files:
distrib/miniroot: install.sub
distrib/amd64/common: install.md
Log message:
Reuse dmesg.boot file for amd64 MDEFI check, clarify this usage pattern
install.md r1.63 assumed it to be present, r1.64 reverted to plain dmesg(8),
now hoist creation of the current boot's dmesg in a new DMESGBOOT variable
for reuse (again) and tweak comments around it.
There are different reasons and ways the installer looks at dmesg:
- Here it concerns feature detection of something that won't change across
reboots or during install/upgrade time: whether we booted via EFI/GPT.
- scan_dmesg() uses that file to lookup keyboards, displays, consoles, etc.
- diskinfo() on the other hand needs to see all disks at runtime,
so live 'dmesg | ...' is needed to find latest attach line for them.
- start_dmesg_listener() is its own mechanism and keeps a file to watch
for changes, i.e. nothing that should change whilst refining the above
mentioned.
deraadt agrees
OK afresh1
