정말이지, 나온지 한시간도 안된 듯 한데, 우연히 일찍 알아챌 수 있었다.
내가 쓰는 선에선 별로 달라진 건 없다. 예전에 내가 올렸던 사항이 개선이 됐는지 여부도 모르겠다.
21.02.25 현재, 0.13.1 까지 공개됐다. (9일만에 개정판이라?)
아무튼, 제작자가 밝힌 개정 정보는 다음과 같다.
0.13.0 (2/15/2021)—This release implements one major user-visible change, several bug fixes (including one major one), and a few smaller improvements:
- The big new feature is implementation of a reboot into a firmware-specified boot option—that is, one that’s stored in the computer’s NVRAM and presented by the EFI’s own boot manager. This feature enables network booting, booting into exotic firmware-provided tools, and booting in ways that might bypass some problems. It can enable full-resolution HiDPI displays in macOS, for instance, which has long been a limitation of rEFInd. This feature also enables launching an EFI shell provided by the firmware, not just ones that are installed as EFI binaries on the hard disk. See this section of the documentation for a detailed description of this new ability.
- I’ve fixed a memory management bug that I believe was responsible for rEFInd 0.12.0 hanging on a few (mostly Apple) computers.
- I’ve imported several minor features and one mostly-behind-the-scenes change to video mode setting from RefindPlus:
- The list of Apple SIP/CSR values has been expanded to match changes in the values that Apple uses.
- The ext4fs driver now supports the EXT4_FEATURE_INCOMPAT_ENCRYPT flag, which means that filesystems that provide directory-level encryption are now supported, although rEFInd can read only from unencrypted directories on such filesystems.
- Aspects of RefindPlus’s video mode detection have been added to rEFInd. In testing, this change doesn’t make much difference, but it’s a base from which future improvements can be made.
- A new option to the resolution token in refind.conf, max, tells rEFInd to set the maximum possible video resolution. This works well on most computers, but there’s a chance that it will set a resolution that’s higher than your monitor supports, so it’s not the default, as it is in RefindPlus.
- Improved rEFInd’s detection of duplicated ext2/3/4 filesystems (as on some types of software RAID); the old code incorrectly marked filesystems with different UUIDs but the same label as duplicates.
- Fixed a bug that caused the mouse pointer to disappear on 64-bit systems when it was moved.
- Fixed a bug that caused EFI 1.x (UGA graphics) systems to hang if refind.conf has a resolution line that specified only one value. (This is a valid configuration for EFI 2.x/GOP graphics systems, but not for EFI 1.x/UGA.) When such a configuration is detected now, it is ignored.
- Replaced which with command -v in shell scripts. This should be more robust in theory.
- Fixed compiler problems with GCC versions 9 and 10.
0.13.1 (2/24/2021)—This release adds a couple of new features that won’t impact most people (although one is a fairly major addition) and several small bug fixes and minor changes:
- The biggest new feature is a logging facility: If log_level is set to a value higher than 0, rEFInd will log its actions in a UTF-16 file called refind.log in the same directory as the rEFInd binary, or on the first accessible ESP if rEFInd was launched from a read-only filesystem (such as an HFS+ volume). This feature is intended to assist in debugging problems, not for regular use, since it can slow rEFInd’s operation. Thus, it should be commented out or set to its default value of 0 in most cases. If you need to use it, values from 1 to 3 are currently supported, with higher values doing more logging. I’m likely to expand the amount of logging done, and may increase beyond level 3, in the future.
- To support the systemd Boot Loader Interface, rEFInd can now write the GUID of the partition from which rEFInd was launched to an EFI variable called LoaderDevicePartUUID whenever rEFInd launches a Linux kernel with EFI stub support, ELILO, or GRUB. (rEFInd does not touch this variable when launching macOS or Windows.) When this variable is present, systemd can use it to mount the ESP at /boot or /efi, if one of these directories is present and empty. This activity is enabled by setting write_systemd_vars true in refind.conf.
- rEFInd now checks EFI variables before writing them, and will not re-write them if doing so would not change them. Previously, rEFInd did this for its PreviousBoot variable; but now it does so for all writes to EFI variables, so as to minimize wear and tear on NVRAM.
- I have uncommented use_nvram and set it to false in refind.conf. This will cause new installations to save rEFInd’s own variables to disk rather than to NVRAM, to save wear and tear on the latter; however, if rEFInd is installed to a read-only filesystem (most likely HFS+), then features such as boot to the most-recently-booted OS and dynamic tag hiding will not work unless use_nvram is commented out or set to true. This change will not affect upgrades to existing installations.
- I have reverted some of the video device discovery changes made in version 0.13.0 after receiving a bug report indicating that they caused at least one Mac model to hang.
- Fixed a bug that could cause rEFInd to misbehave or hang if a disabled manual boot stanza referenced a volume with a name that existed but was unreadable.
- Version 0.13.0 failed to record boots to EFI-based boot options; thus, they would not be used as the default boot option when default_selection + was used on the next boot. This has now been fixed.
- Updated LodePNG library (which rEFInd uses for PNG support) to version 20201017.
- Additional replacements of which with command -v in mvrefind.
RSS - Posts