It is desirable to have finer control on install and uninstall of vtoyboot.
One wants
1) Most importantly, a way to clear all traces of vtoyboot and restore root-filesystem and initramfs to as before
2) More control over whether the files/scripts for dm_patch feature is installed. (This is more stronger that not setting VTOY_LINUX_REMOUNT in plugson/ventoy-grub2-cmdline)
3) Manual step-by-step removal instructions:
For the time being, a description of what needs to be manually, like which files to delete, what config files to edit, and command to enter so that it regenerate a fresh pristine initramfs.
./vtoyboot.sh --install all as is presently
./vtoyboot.sh --install no-dm_patch install only the script but not dmpatch
./vtoyboot.sh --uninstall dm_patch clean the system of the dm_patch, user will take responsibility of creating a dm-device
./vtoyboot.sh --uninstall all not a trace left, machine/OS/initramfs restored to pristine state.
Q) Is it sufficient to manually delete these files? Any other file/config missing?
tbh, I am leaning towards not using vtoyboot for host partition mounting and going with the creating a dm-device for mounting host partition as mentioned in https://github.com/ventoy/Ventoy/issues/2234 & #62. A non-patching approach seems to be the secure way that does not do kernel-taint.
Apparently the taint is recorded even if patch fails to load. Value of /proc/sys/kernel/tainted will be 0 for untainted kernels.
It is desirable to have finer control on install and uninstall of vtoyboot.
One wants 1) Most importantly, a way to clear all traces of vtoyboot and restore root-filesystem and initramfs to as before 2) More control over whether the files/scripts for dm_patch feature is installed. (This is more stronger that not setting
VTOY_LINUX_REMOUNT
in plugson/ventoy-grub2-cmdline) 3) Manual step-by-step removal instructions: For the time being, a description of what needs to be manually, like which files to delete, what config files to edit, and command to enter so that it regenerate a fresh pristine initramfs../vtoyboot.sh --install all
as is presently./vtoyboot.sh --install no-dm_patch
install only the script but not dmpatch./vtoyboot.sh --uninstall dm_patch
clean the system of the dm_patch, user will take responsibility of creating a dm-device./vtoyboot.sh --uninstall all
not a trace left, machine/OS/initramfs restored to pristine state.Files:
command to rebuild initramfs on fedora
Q) Is it sufficient to manually delete these files? Any other file/config missing?
tbh, I am leaning towards not using vtoyboot for host partition mounting and going with the creating a dm-device for mounting host partition as mentioned in https://github.com/ventoy/Ventoy/issues/2234 & #62. A non-patching approach seems to be the secure way that does not do kernel-taint.
Apparently the taint is recorded even if patch fails to load. Value of
/proc/sys/kernel/tainted
will be0
for untainted kernels.ps. The need for an uninstaller has mentioned as a sub-requirement in an issue (#2) from 2 yrs ago (Jan 4, 2021)