[haiku-development] Re: Failing to mount anyboot boot image
- From: Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 2 Sep 2016 16:00:15 +0200
Am 02/09/2016 um 14:31 schrieb Jessica Hamilton:
Hmm, setting gBootVolume.SetBool(BOOT_VOLUME_BOOTED_FROM_IMAGE, true);
in UEFI side seemed to fix it. Weird, but I'll accept that :p
As you can see in [1], Haiku will always try to mount a volume with the
write_overlay when the boot volume is read-only.
So if the above works for you, then it will probably doesn't boot from
the volume you would like it to boot. In any case, it deserves some
investigation.
Why can't you just add the write_overlay to your boot device/image?
Doesn't it just use the packagefs?
In any case, one could retry without write_overlay if that one isn't
available in the kernel, however, you would lose the live desktop
feature of the CD (or at least cripple its experience).
Bye,
Axel.
[1]
http://xref.plausible.coop/source/xref/haiku/src/system/kernel/fs/vfs_boot.cpp#491
Other related posts:
