On Mon, Nov 7, 2022 at 9:50 AM James Wabi wrote:
>
> Thanks vladimir, sadly it did not work. What i did was to include the memmap
> line like this on boot/grub/grub.cfg
>
>
> # This Menu entry brought to you courtesy of
> https://www.pendrivelinux.com/install-grub2-on-usb-from-ubuntu-linux/
> se
Hi Sudhakar!
On Fri, Nov 25, 2022 at 10:52:39AM +0530, sudhakar wrote:
>Hi Steve,
>
>It seems invalid Commit id which you reported. It should be
>4bd9877f62166b7e369773ab92fe24a39f6515f8
>did you applied below patch and tested? Could you please confirm that.
>
>fs/f2fs: Do not read past the end of
Changes from v1:
- Rebased against latest GRUB
- Validated patches against coding guidelines
- Clarified comments
Note: If you are interested in testing this series, I have jolted down some
guidelines at:
https://gist.github.com/pbatard/0deddbd71eefc35a3ed0b08e12a9e7e3
--
In order to add file system transposition support for UEFI, i.e. the ability
to copy the content of an ISO9660 grub-mkrescue ISO image onto user-formatted
media, and have that boot on UEFI systems, the first thing we need to do is
add support for the file systems that are natively handled by UEFI.
The final piece needed to add UEFI file system transposition support is to
ensure the boot media can be located regardless of how the boot partition
was instantiated. Especially, we do not want to be reliant on brittle
partition UUIDs, as these only work if a boot media is duplicated at the
block l
To enable file system transposition support for UEFI, we also must ensure that
there exists a copy of the EFI bootloaders, that are currently embedded in the
efi.img for xorriso, at their expected UEFI location on the ISO9660 file system.
This is accomplished by removing the use of a temporary dir
