On Tue, Nov 26, 2019 at 3:30 PM <[email protected]> wrote: > I just looked and I do not have any of those files anywhere on my system > (did the find command). >
Aah, my tree was not up-to-date. Looks like Waldek removed Multiboot support: commit 2a34f9f2acb582b8351c3ca7cac0ac2ad18dfe2a Author: Waldemar Kozaczuk <[email protected]> Date: Wed Jul 24 17:54:56 2019 -0400 Remove obsolete loader.bin build artifact and related source files At some point long time ago the loader.bin artifact was added as a way to boot OSv on multiboot bootloaders. Unfortunately it got abandoned with time, then resurrected with the commit e44133273ebdbb305b045b6a74c347a96cab9943 to allow OSv boot on hyperkit in multiboot mode which never became fully functional. Given that now we have Linux-compatible vmlinuz.bin artifact generated than can be used to boot OSv on hyperkit, there is no need to keep this arifact around - the boot process and all kinds of its variation are complex enough. Signed-off-by: Waldemar Kozaczuk <[email protected]> But, GRUB should be able to boot to "vmlinuz.bin" if it's really compatible with Linux kernel. - Pekka -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osv-dev/CAGUyND-1%2BJ0WjwV_Vv0zVVKET0Eu%3Da57_vYkg%3DuH-%3D0S1Zctvw%40mail.gmail.com.
