![]() With Linux kernel-5.15 guest-OS-es have both ExFAT and NTFS3 in-kernel support.This feature lets ventoy be useful for running live-images, and not just for installation-iso-s and repair-tool-iso-s. So for the purposes of this issue, let us assume that that this workaround is not the optimal. ![]() Ideally, one would like to keep Ventoy-bootable images and data-virtual-disk-images on the same partition. Making the size of either partition less reduces availability of space to one or the other. ex: If there is 50% usage on both partitions, it is somewhat constraining to have to decide where an image should go to. The reason this is not optimal is because it fragments the free-space between two partitions the Ventoy partition and the data partition, and one would want all the free-space on the disk consolidated together. One suggestion that is given is to just reserve some space after the VTOYEFI partition and create a new data partition sdb3, for writing etc. Present status: The partition /dev/sdb1 will be reported to be busy if attempted to be mounted. ![]() It's okay if this issue cannot be resolved any time soon.įeature Request: One should be able to mount the Ventoy partition read-write from within booted OS So filing this issue, so as to track ideas and progress of the implementation of the feature. ![]() I searched the github-issues to find if this issue with feature request has been already filed. I have read the thread on the Ventoy-forum and understood that this feature is still under consideration. This issue corresponds to the discussion forum thread. Image file download link (if applicable)įirstly, thank you for making such a useful utility. ![]() Seagate Image file checksum (if applicable) I have tried the latest release, but the bug still exist. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
August 2023
Categories |