Yeah, seems sensible to me, although I can't test this at the moment - I'm on mobile.
Search Criteria
Package Details: ventoy-bin 1.1.05-1
Package Actions
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: | 383 |
Popularity: | 5.36 |
First Submitted: | 2020-05-19 06:14 (UTC) |
Last Updated: | 2025-02-24 18:30 (UTC) |
Dependencies (7)
- bash (bash-devel-gitAUR, bash-gitAUR)
- dosfstools (dosfstools-gitAUR)
- util-linux (util-linux-aesAUR, util-linux-selinuxAUR)
- xz (xz-gitAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR) (optional) – GTK3 GUI
- polkit (polkit-gitAUR, polkit-consolekitAUR) (optional) – run GUI from application menu
- qt5-base (qt5-base-gitAUR, qt5-base-headlessAUR) (optional) – Qt5 GUI
Required by (0)
Sources (10)
Latest Comments
« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 18 Next › Last »
Kr1ss commented on 2021-05-03 08:23 (UTC)
DuckSoft commented on 2021-05-03 08:17 (UTC)
@solstice Hi thanks for pointing that out.
I noticed that both exfat-utils
and exfatprogs
offers mkfs.exfat
. However, only exfat-utils
offers mkexfatfs
, where mkfs.exfat
is symlinked to mkexfatfs
. So I guess a better solution would be symlink Ventoy's mkexfatfs
to system /usr/bin/mkfs.exfat
?
What do you guys think?
solsticedhiver commented on 2021-05-02 18:47 (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.
FirstAirBender commented on 2021-03-31 04:38 (UTC)
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
Kr1ss commented on 2021-03-30 03:15 (UTC)
Thanks @FirstAirBender, the image location should now be fixed and the image will be created in the directory where you run ventoy-persistent
.
FirstAirBender commented on 2021-03-29 19:46 (UTC)
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
saverio commented on 2021-03-28 16:21 (UTC)
Thanks a lot for this utility, it's very useful!
Kr1ss commented on 2021-03-28 12:50 (UTC)
the spelling in the release assets is correct...
Yes, it was me who made that mistake. Non-native english speaker as well 8)
Kr1ss commented on 2021-03-28 12:14 (UTC)
Yes, I'd rather use the correct form.
Pinned Comments