quibble icon indicating copy to clipboard operation
quibble copied to clipboard

Filesystem loop device EFI drivers

Open joshumax opened this issue 5 years ago • 1 comments

I'm not quite sure if this is the best place to put this, but I figured the issues page is probably a good bet.

I did something similar to this for a project called UbWI (Ubuntu Windows Installer, like Wubi but the other way around). However, instead of writing a clean re-implementation of the Windows EFI bootloader blobs, I opted for a much-more cumbersome method of injecting hooks at known offsets using a separate EFI application, then wrapping file IO commands to a custom loop device driver which exposed an NTFS image file from an ext4 partition as a distinct virtual "disk" to bootstrap the NT kernel. While the kernel driver portion of the project is still a work in project, stage 1 worked well enough to kickstart ntoskrnl until it panicked.

Do you have anything like this in the works for quibble? If not, what is your stance on adding it? For reference, I'd be happy to re-license my existing EFI work under the LGPL.

joshumax avatar Feb 14 '20 10:02 joshumax

IIRC you can already do that with the UEFI fork of grub4dos and SVBus virtual disk driver, no?

http://reboot.pro/index.php?showtopic=22400 http://wuyou.net/forum.php?mod=viewthread&tid=422652 https://sourceforge.net/projects/svbus/

driver1998 avatar Apr 14 '21 02:04 driver1998