[root@fedora vtoyboot-1.0.31]# sh vtoyboot.sh

**********************************************
      vtoyboot 1.0.31
      longpanda admin@ventoy.net
      https://www.ventoy.net
**********************************************

Current system use dracut as initramfs tool
mkdir: cannot create directory ‘/lib/dracut/modules.d/99ventoy’: Read-only file system
cp: cannot create regular file '/bin/vtoydump': Read-only file system
cp: cannot create regular file '/bin/vtoypartx': Read-only file system
cp: cannot create regular file '/bin/vtoytool': Read-only file system
./distros/dracut/vtoy.sh: line 43: /bin/vtoydmpatch: Read-only file system
cp: cannot create regular file '/lib/dracut/modules.d/99ventoy/': Not a directory
cp: cannot create regular file '/lib/dracut/modules.d/99ventoy/': Not a directory
updating the initramfs, please wait ...
dracut: Can't write to /boot/efi/31ea8b02de6a4ab88ac6604f693cd2df/6.5.6-300.fc39.x86_64: Directory /boot/efi/31ea8b02de6a4ab88ac6604f693cd2df/6.5.6-300.fc39.x86_64 does not exist or is not accessible.
grub mkconfig ...
PROBE_PATH=/usr/sbin/grub2-probe EDITENV_PATH=/usr/bin/grub2-editenv MKCONFIG_PATH=/usr/sbin/grub2-mkconfig
cp: cannot create regular file '/usr/sbin/grub2-probe-bk': Read-only file system
rm: cannot remove '/usr/sbin/grub2-probe': Read-only file system
cp: cannot remove '/usr/sbin/grub2-probe': Read-only file system
chmod: changing permissions of '/usr/sbin/grub2-probe': Read-only file system
chmod: cannot access '/usr/sbin/grub2-probe-bk': No such file or directory
cp: cannot create regular file '/usr/bin/grub2-editenv-bk': Read-only file system
rm: cannot remove '/usr/bin/grub2-editenv': Read-only file system
cp: cannot remove '/usr/bin/grub2-editenv': Read-only file system
chmod: changing permissions of '/usr/bin/grub2-editenv': Read-only file system
chmod: cannot access '/usr/bin/grub2-editenv-bk': No such file or directory
/usr/sbin/grub2-mkconfig -o /boot/loader.0/grub.cfg
Generating grub configuration file ...
Adding boot menu entry for UEFI Firmware Settings ...
done

vtoyboot process successfully finished.