ソフトアンテナ

Windows/Mac/Mobile用オンラインソフトのバージョンアップ状況を調べています。

詳細情報

タイトル rEFInd
URL http://www.rodsbooks.com/refind/index.html
バージョン 0.13.3.1   0.13.3   0.13.2   0.13.1   0.13.0   0.12.0   0.11.5   0.11.4   0.11.3   0.11.2   0.11.1  
更新日 2022/04/13
追加日 2016/05/04
種別 フリーソフト
説明 UEFI対応のブートマネージャ。

スクリーンショット

レビュー

レビューはありません。

更新グラフ

バージョン履歴

No.バージョン名日付
10.13.3.12022/04/13
Last Web page update: 4/12/2022
20.13.32022/04/11
Last Web page update: 4/10/2022
0.13.3 (4/10/2022)—This version features several minor bug fixes and new features:
rEFInd stopped compiling with GNU-EFI somewhere between GNU-EFI
versions 3.0.9 and 3.0.13; this version corrects that problem.
rEFInd could freeze when processing keystrokes in menus. This bug
is now fixed.
The option to return from the folded Linux kernel submenu was
missing; this bug is now fixed.
Bash script coding has been cleaned up.
The refind-install script contained a stray exit
command, which caused it to terminate prematurely. This problem has
been corrected.
rEFInd was reading the HiddenTools variable unnecessarily
often; this has been corrected.
When the timeout option was set to -1 and no
keyboard was attached, rEFInd could freeze. This problem has been
fixed.
The arrow icons visible when more icons than the screen can handle
could be incompletely erased if icon sizes were set manually in
(省略されました)
30.13.22021/03/14
Last Web page update: 3/13/2021
0.13.2 (3/13/2021)—I've fixed a number of bugs and added a few new features with this version:
This version fixes a memory management bugs that could cause rEFInd
to hang under certain unpredictable circumstances.
I've also fixed potential memory management bugs that could cause
HFS+, ext2fs, and ext4fs drivers to misbehave.
Version 0.13.1 introduced a bug that caused rEFInd to fail to load
properly signed EFI drivers when Secure Boot was enabled and used
via Shim. This is now fixed.
The mvrefind script has long had an unnoticed bug that
caused it to fail to create a new NVRAM entry to point to the moved
rEFInd.
MacOS 11 ("Big Sur") changed something in its sed utility
that caused the mountesp script to fail in that version of
macOS. This problem has been fixed.
I've improved Secure Boot support in the refind-install
script when run from Linux: The script can now install a Secure Boot
key using mokutil, which can slightly simplify the MOK
setup. It also now creates a backup NVRAM entry to boot directly,
(省略されました)
40.13.12021/02/25
Last Web page update: 2/24/2021
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:
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.
50.13.02021/02/16
Last Web page update: 2/15/2021
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:
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.
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.
Replaced which with command -v in shell scripts. This should be more robust in theory.
Fixed compiler problems with GCC versions 9 and 10.
copyright © 2012–2021 by Roderick W. Smith
60.12.02020/03/14
0.12.0 (3/13/2020)—This release sees a couple of major new
features and some other more minor changes:
A new EFI (not rEFInd) boot order maintenance feature is now
available, albeit disabled by default. To enable it, uncomment the
showtools option in refind.conf and ensure that
bootorder is among the options. The new feature will then
appear next time rEFInd is launched. This options enables you to
adjust the EFI's boot order. Selecting an option and pressing
the Enter key moves it to the top of the list. Selecting it and
pressing the minus (-) key or Delete deletes the entry. The
goal is to enable changing the computer's boot order from a rEFInd
emergency disk after a boot coup or similar problem. This feature is
therefore covered in more detail on
the page on boot coups. Although this feature is disabled by
default, it's enabled on my USB flash drive and CD-R images.
A new self-installation option is available, albeit disabled by
default. (It's enabled on my USB flash drive and CD-R images.) To
enable it, uncomment the showtools option in
refind.conf and add the install token to the list.
(省略されました)
70.11.52020/02/13
Last Web page update: 2/12/2020
0.11.5 (2/12/2020)—This release fixes a handful of
bugs and makes a few miscellaneous changes:
Fixed a bug that caused screen corruption when exiting the EFI
shell (and perhaps other programs) on some systems.
Implemented a workaround for buggy filesystem drivers that
could cause rEFInd to hang when re-scanning devices.
The NTFS driver is no longer built by default because it's produced
too many reports of hung systems. The source code is still included
and it can still be built, but the binary is now omitted.
Cleaned up excessive slashes (/) in pathname specifications
in refind-install script.
Corrected incorrect display of scanning for boot loaders
message under some circumstances.
Fine-tune the use of %v in refind_linux.conf: Do
not include the auto-detected initrd file when %v is
used, to give the user greater control over initrd file
specification. Note: Some users may need to adjust their
configuration files because of this change!
(省略されました)
80.11.42018/11/13
Last Web page update: 11/12/2018
0.11.4 (11/12/2018)—This release fixes a couple of small
but annoying bugs introduced in version 0.11.3 and improves some
filesystem drivers. More specifically:
Samuel Liao provided bug fixes to the NTFS driver relating to
fragmented files and filesystems with cluster sizes of over
4KiB.
Samuel Liao also added support for zstd decompression to the
btrfs driver. He's also fixed a RAID1 issue and added support
for RAID5 and 6.
Version 0.11.3 introduced a bug in both refind-install
and mountesp that caused these scripts to fail in
macOS's Recovery environment. These bugs have been squashed.
refind-install has long had a bug that caused it to
fail to properly identify the ESP in Linux when autofs was in
use. This bug has been squashed.
rEFInd 0.11.3 introduced a bug that caused the default of
booting to the last-booted OS to be lost unless it was set
explicitly via default_selection in refind.conf.
(省略されました)
90.11.32018/07/23
Last Web page update: 7/22/2018
0.11.3 (7/22/2018)—This release implements a number of
minor bug fixes and some more major improvements; its two changes are:
The new shutdown_after_timeout token in
refind.conf, if set, causes rEFInd to try to shut down the
computer rather than launch the default_selection when the
timeout value is reached. Note, however, that this feature
relies on EFI features that are not implemented by some EFIs. If the
feature is not implemented, the computer will reboot or hang. This
option is disabled by default, which results in the same behavior as
in previous versions of rEFInd.
The new use_nvram token, if set to false,
off, or 0, causes rEFInd to store its variables to
files on the hard disk (in the vars subdirectory of
rEFInd's home directory). When use_nvram is set to
true or one of its synonym, as is the default, these
variables are stored in NVRAM, as was always the case for previous
versions. This feature is intended to improve functionality on
computers with flaky NVRAM and to reduce wear-and-tear on the
(省略されました)
100.11.22017/10/23
0.11.2 (10/22/2017)—This is a minor bug-fix release; its
two notable improvements are:
I've fixed a bug, introduced in version 0.11.1, that caused setting
volumes in manual boot stanzas to not work.
I've fixed a bug, present since version 0.11.0, that caused the new
tag-hiding feature to not work unless it was explicitly enabled in
refind.conf. (It should have been enabled by default.)
110.11.12017/10/10
Last Web page update: 10/9/2017
0.11.1 (10/9/2017)—This version is mainly a maintenance
release in response to Apple's release of macOS 10.13 ("High Sierra"),
although there are a couple of unrelated improvements. Its specific
changes are:
The new Apple Filesystem (APFS) uses subvolumes, which appear as
subdirectories with UUIDs as names to the EFI and EFI programs such
as rEFInd. This fact means that the location of Apple's boot loader
has changed, from rEFInd's perspective, necessitating a code
update. This version provides that update.
As a follow-on to the preceding change, I discovered that compiling
rEFInd with GNU-EFI resulted in a failure to properly track some
files on APFS volumes. I don't know if this failure reflected a bug
in Apple's EFI, in GNU-EFI, or in rEFInd; but I changed the way
rEFInd tracks boot loader files internally to work around the
problem. Although I've tested this version on an unusually wide
number of computers, it's possible that this change will introduce
new bugs. Thus, if you upgrade and have problems with boot loaders
not being detected or not launching, dropping back to version 0.11.0
(省略されました)