| Git Clone URL: | https://aur.archlinux.org/ventoy-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | ventoy-bin |
| Description: | A new bootable USB solution |
| Upstream URL: | http://www.ventoy.net |
| Keywords: | boot image iso multiboot usb |
| Licenses: | GPL-3.0-or-later |
| Conflicts: | ventoy |
| Provides: | ventoy |
| Submitter: | DuckSoft |
| Maintainer: | DuckSoft (KokaKiwi, yochananmarqos, Kr1ss) |
| Last Packager: | yochananmarqos |
| Votes: | 380 |
| Popularity: | 8.12 |
| First Submitted: | 2020-05-19 06:14 (UTC) |
| Last Updated: | 2025-02-24 18:30 (UTC) |
exfatprogs package provides exfat-utils so ventoy-bin package installs fine but breaks later when running ventoy:
./tool/VentoyWorker.sh: line 284: mkexfatfs : command not found
It would be fine if one can use exfatprogs instead of exfat-utils because gparted rely on exfatprogs. Otherwise, find a way to warn about the possible problem.
Thank you.
In that case, you might as well just make it a link to /opt/ventoy/CreatePersistentImg.sh.
ln -s /opt/ventoy/CreatePersistentImg.sh /usr/bin/ventoy-persistent
Thanks @FirstAirBender, the image location should now be fixed and the image will be created in the directory where you run ventoy-persistent.
Why does the ventoy-persistent script create the persistence data inside /opt/ventoy? This is contrary to what is said in the documentation. The file should be created in the current directory.
Just sudo /opt/ventoy/CreatePersistentImg.sh ... is all I needed to create the persistence file
Thanks a lot for this utility, it's very useful!
the spelling in the release assets is correct...
Yes, it was me who made that mistake. Non-native english speaker as well 8)
Yes, I'd rather use the correct form.
@C0rn3j wow i didn't even notice that... i am not a native speaker :(
so let's go with ventoy-persistent?
UPDATES: double checked that the spelling in the release assets is correct...
so no problem, just move on :)
Yes correct ! Thx @C0rn3j. :)
Pinned Comments