mirror of
https://github.com/pbatard/rufus.git
synced 2026-07-09 06:55:39 +00:00
8b2a5b8514* Can GRUB *EVER* produce a release archive that is not *UTTERLY BROKEN*??? https://lists.gnu.org/archive/html/grub-devel/2026-01/msg00043.html * Also set version to rufus-next.
26 lines
No EOL
1.4 KiB
Text
26 lines
No EOL
1.4 KiB
Text
This directory contains the Grub 2.0 boot records that are used by Rufus
|
|
|
|
* boot.img and core.img were created from https://ftp.gnu.org/gnu/grub/grub-2.14.tar.xz
|
|
with https://github.com/gentoo/gentoo/raw/d51cbeb087dbbe979ff29af645f32071cce2834d/sys-boot/grub/files/grub-2.14-revert-image-base.patch
|
|
applied (since GRUB are apparently unable to perform BASIC testing of their releases)
|
|
on a Debian 13 x64 system using the commands:
|
|
patch -p1 < grub-2.14-revert-image-base.patch
|
|
./autogen.sh
|
|
# --enable-boot-time for Manjaro Linux
|
|
./configure --disable-nls --enable-boot-time
|
|
make -j4
|
|
cd grub-core
|
|
../grub-mkimage -v -O i386-pc -d. -p\(hd0,msdos1\)/boot/grub biosdisk fat exfat ext2 ntfs ntfscomp part_msdos -o core.img
|
|
|
|
* boot.img has been modified to nop the jump @ 0x66 as per grub2's setup.c comments:
|
|
/* If DEST_DRIVE is a hard disk, enable the workaround, which is
|
|
for buggy BIOSes which don't pass boot drive correctly. Instead,
|
|
they pass 0x00 or 0x01 even when booted from 0x80. */
|
|
|
|
* Note that, for convenience reasons, the content of boot.img is *not* the one that
|
|
Rufus processes when writing the MBR.
|
|
Instead, the byte array from src/ms-sys/inc/mbr_grub2.h (whose content is identical)
|
|
is what Rufus uses. If you modify these files, be mindful that you may also need
|
|
to update the array in mbr_grub2.h.
|
|
|
|
* For details, see src/format.c, src/msys/br.c and src/msys/inc/mbr_grub2.h. |