mirror of
https://github.com/pbatard/rufus.git
synced 2024-08-14 23:57:05 +00:00
3a0f7d3813
* As was *ENTIRELY PREDICTIBLE*, the lack of timely releases from the GRUB project has resulted in distro maintainers (Ubuntu, Fedora, etc.) taking matters in their own hand and applying patches on top of their 2.06 version. However, these patches result in 2.06 bootloaders that are incompatible with 2.06 modules that don't have the same patches applied. Especially this now results in the infamous "452: out of range pointer" error message when using patched modules with unpatched bootloader or unpatched modules with patched bootloaders. * Making this issue worse, we also have distro maintainers who won't add a suffix to their GRUB version, AS ONE SHOULD DO WHEN ONE APPLIES TONS OF PATCHES ON TOP OF A PROJECT'S SOURCE, and MISreport their non 2.06 GRUB as "2.06", and, because we can't detect what patches are needed from modules themselves (unlike what is the case for grub_debug_is_enabled), we have no way of telling incompatible GRUB 2.06 binaries from one another. * As a result, we have no choice but to append a sanitized version of the ISO label to the GRUB version, as a means to differentiate between incompatible versions, and tweak our existing bootloader download mechanism to *ATTEMPT* to download a compatible 'core.img' from our server... where we will have to waste a lot of time adding new binaries and symlinks to try to make all these GRUB "2.06" based images work, and will probably miss quite few with the end results that users who are just trying to install Linux will be left stranded. * Again, I have to point out how the end result of regular users wanting to try Linux and being unable to do so is the *DIRECT* result of the GRUB project maintainers having sat on a 2-year influx of CONTINUOUS patches, and thinking that "Release Early, Release Often" is only a gimmick, and not something that should apply to their project, even as they have been warned before, by yours truly, that *NOT* releasing on a timely basis is causing actual grievances... That's because, had the GRUB maintainers released on a timely basis (at least once a year) Fedora and Ubuntu would be using vanilla GRUB 2.07 with the memory patches, and we wouldn't be trying to mix that with old GRUB 2.06 binaries. * For more on this, see #2233, noting that we will need to apply a compatibility breaking change during the 4.1 release, to revert the patches we applied to the default 2.06 'core.img' in pbatard/rufus-web@320b800592. |
||
---|---|---|
.. | ||
bled | ||
ext2fs | ||
getopt | ||
libcdio | ||
ms-sys | ||
msvc-missing | ||
syslinux | ||
.editorconfig | ||
badblocks.c | ||
badblocks.h | ||
checksum.c | ||
cpu.c | ||
cpu.h | ||
db.h | ||
dev.c | ||
dev.h | ||
dos.c | ||
dos.h | ||
dos_locale.c | ||
drive.c | ||
drive.h | ||
format.c | ||
format.h | ||
format_ext.c | ||
format_fat32.c | ||
gpt_types.h | ||
hdd_vs_ufd.h | ||
icon.c | ||
iso.c | ||
license.h | ||
localization.c | ||
localization.h | ||
localization_data.h | ||
localization_data.sh | ||
Makefile.am | ||
Makefile.in | ||
mbr_types.h | ||
missing.h | ||
msapi_utf8.h | ||
net.c | ||
parser.c | ||
pki.c | ||
process.c | ||
process.h | ||
re.c | ||
re.h | ||
registry.h | ||
resource.h | ||
rufus.c | ||
rufus.h | ||
rufus.manifest | ||
rufus.rc | ||
settings.h | ||
smart.c | ||
smart.h | ||
stdfn.c | ||
stdio.c | ||
stdlg.c | ||
syslinux.c | ||
ui.c | ||
ui.h | ||
ui_data.h | ||
vhd.c | ||
vhd.h | ||
winio.h | ||
wue.c | ||
wue.h |