hgkamath

The below logs come from a vdisk ventoy-boot of Fedora-37. In order to know what the status is in the initramfs, breaked at pre-mount ``` [root@fedora ~]$ uname -a Linux...

In this comment, I document - What is native booting - The usefulness of live iso/vdisk multibooting solutions. The reasons for using ventoy - Why being able to mount the...

### THE ANTI-VENTOY IDEA Here-in, I document an idea that just came to me. An alternate way to achieve the same effect of mounting host partition without needing to patch...

> The idea is just how Ventoy did to support persistence. possibly yes, except that this is the blocks of the whole remaining partition stitched together with zero-block-sections that take...

I first used qemu in windows to confirm that image is bootable, did some dnf package updates within, updated linux kernel inside to 6.1.11-200, re-applied vtoyboot-1.0.25 and then confirmed that...

I think I found out what the bug might be. Notice that the two files ``` 08/11/2022 07:01 PM 32,768 m01_lnx.raw.vlnk.img 02/10/2023 10:07 AM 49,861,885,952 m02_lnx.raw.img.vtoy ``` appear one after...

Confirming: yes 1. First I rename the file to break vtoy-vlnk ``` PS H:\> Rename-Item .\m01_lnx.raw.img.vtoy m01_Zlnx.raw.img.vtoy PS H:\> dir H:\m01_Zlnx.raw.img.vtoy Directory: H:\ Mode LastWriteTime Length Name ---- ------------- ------...

Confirming: yes on USB flash-drive as well - I created the same vtoy-vlnk in the USB folder ```L:\transcend``` to the image in ```H:\``` , named it ```m01_lnx.raw.vlnk.img``` - I also...

TLDR: This comment is about secureboot investigation. I don't think secureboot is the issue The thing is the EFI parition on the main SSD, is different from the EFI partition...

I inserted a ```rd.break=pre-mount``` kernel boot option to kernel conf ```6.1.11-200.fc37.x86_64.conf``` in ```/boot/loader/entries``` . Rebooted while secureboot still disabled. Then I copied ```/tmp/vtoy.log``` off initramfs ``` [root@fedora gana]# cat /mnt/a12/gana/tmp/vtoy.log...