| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 56 online users.
» 0 Member(s) | 54 Guest(s)
Bing, Google
|
| Latest Threads |
Windows 10/11 setup Error...
Forum: Ventoy Discussion Forum
Last Post: Steve2926
Today, 08:29 AM
» Replies: 5
» Views: 284
|
Higher resolution on ISO'...
Forum: Ventoy Plugin Forum
Last Post: perfection
Today, 07:46 AM
» Replies: 3
» Views: 1,953
|
Problem with EasyOS
Forum: Ventoy Discussion Forum
Last Post: longpanda
Today, 01:33 AM
» Replies: 4
» Views: 415
|
can't move win10 or win11...
Forum: Ventoy Discussion Forum
Last Post: Steve2926
Yesterday, 11:01 PM
» Replies: 1
» Views: 37
|
Issue: ventoy-1.0.74, Sys...
Forum: Ventoy Plugin Forum
Last Post: Steve2926
Yesterday, 10:26 AM
» Replies: 1
» Views: 101
|
Windows 10 Installation i...
Forum: Ventoy Discussion Forum
Last Post: Steve2926
Yesterday, 10:15 AM
» Replies: 5
» Views: 275
|
Booting from Vhd or Vhdx ...
Forum: Ventoy Discussion Forum
Last Post: aboamir@gmail.com
05-17-2022, 05:36 PM
» Replies: 0
» Views: 102
|
Secureboot : Grub error "...
Forum: Ventoy Discussion Forum
Last Post: 2Torr
05-16-2022, 08:20 PM
» Replies: 3
» Views: 702
|
question about the source...
Forum: Ventoy Discussion Forum
Last Post: AlexBryansk
05-12-2022, 05:36 PM
» Replies: 1
» Views: 331
|
Help $OEM$
Forum: Ventoy Discussion Forum
Last Post: Cyberfox
05-10-2022, 02:12 PM
» Replies: 0
» Views: 205
|
|
|
| Linux updating shell script |
|
Posted by: johnca - 04-21-2022, 08:30 PM - Forum: Ventoy Discussion Forum
- No Replies
|
 |
Hello everyone.
Could we update the main scrip for terminal execution?
old scrip
Code: #!/bin/sh
OLDDIR=$(pwd)
if ! [ -f ./tool/ventoy_lib.sh ]; then
if [ -f ${0%Ventoy2Disk.sh}/tool/ventoy_lib.sh ]; then
cd ${0%Ventoy2Disk.sh}
fi
fi
if [ -f ./ventoy/version ]; then
curver=$(cat ./ventoy/version)
fi
if uname -m | egrep -q 'aarch64|arm64'; then
export TOOLDIR=aarch64
elif uname -m | egrep -q 'x86_64|amd64'; then
export TOOLDIR=x86_64
elif uname -m | egrep -q 'mips64'; then
export TOOLDIR=mips64el
else
export TOOLDIR=i386
fi
export PATH="./tool/$TOOLDIR:$PATH"
echo ''
echo '**********************************************'
echo " Ventoy: $curver $TOOLDIR"
echo " longpanda admin@ventoy.net"
echo " https://www.ventoy.net"
echo '**********************************************'
echo ''
if ! [ -f ./boot/boot.img ]; then
if [ -d ./grub ]; then
echo "Don't run Ventoy2Disk.sh here, please download the released install package, and run the script in it."
else
echo "Please run under the correct directory!"
fi
exit 1
fi
echo "############# Ventoy2Disk $* [$TOOLDIR] ################" >> ./log.txt
date >> ./log.txt
#decompress tool
echo "decompress tools" >> ./log.txt
cd ./tool/$TOOLDIR
ls *.xz > /dev/null 2>&1
if [ $? -eq 0 ]; then
[ -f ./xzcat ] && chmod +x ./xzcat
for file in $(ls *.xz); do
echo "decompress $file" >> ./log.txt
xzcat $file > ${file%.xz}
[ -f ./${file%.xz} ] && chmod +x ./${file%.xz}
[ -f ./$file ] && rm -f ./$file
done
fi
cd ../../
chmod +x -R ./tool/$TOOLDIR
if [ -f /bin/bash ]; then
/bin/bash ./tool/VentoyWorker.sh $*
else
ash ./tool/VentoyWorker.sh $*
fi
if [ -n "$OLDDIR" ]; then
CURDIR=$(pwd)
if [ "$CURDIR" != "$OLDDIR" ]; then
cd "$OLDDIR"
fi
fi
new scrip
Code: #!/bin/sh
OLDDIR=$(pwd)
if ! [ -f ./tool/ventoy_lib.sh ]; then
if [ -f ${0%Ventoy2Disk.sh}/tool/ventoy_lib.sh ]; then
cd ${0%Ventoy2Disk.sh}
fi
fi
if [ -f ./ventoy/version ]; then
curver=$(cat ./ventoy/version)
fi
if uname -m | egrep -q 'aarch64|arm64'; then
export TOOLDIR=aarch64
elif uname -m | egrep -q 'x86_64|amd64'; then
export TOOLDIR=x86_64
elif uname -m | egrep -q 'mips64'; then
export TOOLDIR=mips64el
else
export TOOLDIR=i386
fi
export PATH="./tool/$TOOLDIR:$PATH"
echo \
"
**********************************************
Ventoy: $curver $TOOLDIR
longpanda admin@ventoy.net
https://www.ventoy.net
**********************************************
$(lsblk)
==============================================
run: umount /dev/sdX*
if necesary
"
if ! [ -f ./boot/boot.img ]; then
if [ -d ./grub ]; then
echo "Don't run Ventoy2Disk.sh here, please download the released install package, and run the script in it."
else
echo "Please run under the correct directory!"
fi
exit 1
fi
echo "############# Ventoy2Disk $* [$TOOLDIR] ################" >> ./log.txt
date >> ./log.txt
#decompress tool
echo "decompress tools" >> ./log.txt
cd ./tool/$TOOLDIR
ls *.xz > /dev/null 2>&1
if [ $? -eq 0 ]; then
[ -f ./xzcat ] && chmod +x ./xzcat
for file in $(ls *.xz); do
echo "decompress $file" >> ./log.txt
xzcat $file > ${file%.xz}
[ -f ./${file%.xz} ] && chmod +x ./${file%.xz}
[ -f ./$file ] && rm -f ./$file
done
fi
cd ../../
chmod +x -R ./tool/$TOOLDIR
if [ -f /bin/bash ]; then
/bin/bash ./tool/VentoyWorker.sh $*
else
ash ./tool/VentoyWorker.sh $*
fi
if [ -n "$OLDDIR" ]; then
CURDIR=$(pwd)
if [ "$CURDIR" != "$OLDDIR" ]; then
cd "$OLDDIR"
fi
fi
|
|
|
| Ventoy Boot Conf Replace Plugin - improvement ? |
|
Posted by: fuse59 - 04-20-2022, 07:41 AM - Forum: Ventoy Plugin Forum
- Replies (1)
|
|
Hello !
Is it possible in a future version for the same linux iso to replace several files ?
Code: {
"conf_replace": [
{
"iso": "/iso/clonezilla-live-2.8.1-12-amd64.iso",
"org1": "/boot/grub/grub.cfg",
"new1": "/path/new-grub.cfg",
"org2": "/boot/grub/ocswp-grub2.png",
"new2": "/path/new-logo.png"
}
]
}
|
|
|
|
| Fichier ISO bootables |
|
Posted by: danfranjo - 04-13-2022, 01:56 PM - Forum: Ventoy Discussion Forum
- Replies (4)
|
|
Hello to all of you,
I am using Ventoy and I like it a lot
The question I have is that I have many ISO files that are either CSM bootable or UEFI bootable
Is there a way to convert an CSM bootable file to an UEFI bootable file and vice versa ?
Thanks in advance
|
|
|
|
| 自定义菜单插件的问题， |
|
Posted by: edpcnet - 04-12-2022, 04:56 AM - Forum: Ventoy Plugin Forum
- No Replies
|
 |
我是小白，请问各位大神，怎么把下面这段代码写进Ventoy的自定义菜单插件里去。
运行 绕过密码启动windows
map --mem /你的IMA放置目录/KONBOOT.ima (fd0)
地图 (hd0) (hd1)
地图 (hd1) (hd0)
地图——钩子
链式装载机 (fd0)+1
rootnoverify (fd0)
menuentry "我的自定义菜单" --class=custom {
echo '这是自定义菜单...'
sleep 1
}
submenu '我的自定义子菜单 -->' --class=customsub {
menuentry "我的自定义菜单2" --class= custom2 {
echo '这是自定义 menu2 ... '
sleep 1
}
menuentry '<-- 返回上一级菜单 [Esc]' --class=vtoyret VTOY_RET {
echo 'Return ...'
}
}
menuentry '<-- 返回到上一个菜单 [Esc]' --class=vtoyret VTOY_RET {
echo 'Return ...'
}
|
|
|
|
| [feature suggestion] Find files by path without setting in ventoy.json |
|
Posted by: calzlot - 04-09-2022, 11:41 AM - Forum: Ventoy Discussion Forum
- Replies (1)
|
|
Hello!
Venty has reached a maturity that allows to look beyond function and start polishing the usability. Thank you for the hard work! I wonder why nobody did that much sooner?
Here is one suggestion. Allow me to explain the background first.
Whether we throw our files all into one directory...
Code: /images-and-corresponding-files/
distro1-config.cfg
distro1-persistence.dat
distro1.iso
distro2-config.cfg
distro2-persistence.dat
distro2.iso
/ventoy/
ventoy.json # global settings file (distros and ventoy)
...or keep them sorted...
Code: /configs/
distro1-config.cfg
distro2-config.cfg
/images/
distro1.iso
distro2.iso
/persistence-files/
distro1-persistence.dat
distro2-persistence.dat
/ventoy/
ventoy.json # global settings file (distros and ventoy)
...or sort by distro...
Code: /distros/
distro1/
distro1-config.cfg
distro1.iso
distro1-persistence.dat
distro2/
distro2-config.cfg
distro2.iso
distro2-persistence.dat
/ventoy/
ventoy.json # global settings file (distros and ventoy)
... whenever we change a distro, we also have to
- rename the persistence file,
- rename the config file,
- and edit the names of persistence and config files in the global ventoy.jason.
That can be more elegant. Here's the suggestion, consisting of two steps:
- Yentoy is enabled to automatically accept all files that belong to an image, if they are in the same folder with that image. That means its corresponding .dat, .cfg, .md5/.sha1/.sha256/.sha512 files.
- And also, all image specific settings that are now in the global ventoy.json file could go into an image-specific config file in that folder.
To keep backward compatibility, ventoy then needs to first look for corresponding files in its global ventoy.json, so every user can continue to use their current settings. Only if ventoy does not find entries there for the selected image, it then looks inside the folder of the selected image, reads the config there (if one exists), and then loads the image and the other files there.
We then could group images and files like this:
Code: /distros/
distro1/
distro1-config.cfg
distro1-persistence.dat
distro1-v1.2.3.iso
distro1.json # only settings for distro1
distro2/
distro2-config.cfg
distro2-persistence.dat
distro2-v4.5.6.iso
distro2.json # only settings for distro2
/ventoy/
ventoy.json # only settings for ventoy itself
Then, if the image file is replaced, and we want the new image to keep its new name (e.g., when it contains a version number):- No corresponding files needs renaming. (Checksums have to be replaced anyway.)
- No edit necessary in global ventoy.json.
- No edit necessary in image-specific config file (if existent).
Removing an image now only requires that a directory is deleted. No editing ventoy.json necessary. (Of course, one could stay with the old way, and just leave ventoy.json untouched, if one loves the accumulating cruft.  )
The reasoning behind the idea is as follows.
A minor version change (e.g. v1.2.34 => 1.2.35) will rarely need a changed config (and maybe not even persistence?). For the case that it does, the ventoy documentation needs an extra sentence that alerts to unchanged .dat, .cfg, and .json in case of errors, and suggests moving them elsewhere for a test.
This will prove especially useful with images that do not change much over long times, and only add security fixes and minor changes (e.g. Clonezilla). They can use the same config for a long time, and we will not need to edit the .cfg name and ventoy.json with every minor update.
For the interested, related reading about the power of the lack of ease of use: "Beware Trivial Inconveniences"
|
|
|
|
| Secureboot : Grub error "shim_lock protocol not found" |
|
Posted by: vernetroyer - 04-08-2022, 06:10 AM - Forum: Ventoy Discussion Forum
- Replies (3)
|
|
When installing Ventoy on USB with GPT and SecureBoot, upon first boot I need to install keys, just as explained on the website.
The second boot however does start up Ventoy correctly, but when selecting SystemRescue 9.01, and Grub starts, I get the following Grub error:
shim_lock protocol not found, you need to load the kernel first
Rebooting with secure boot disabled does not give the error, and boots SystemRescue successfully.
Booting with secureboot gives a black (?) grub screen, booting without secureboot gives a green (?) grub screen.
Does anyone know a solution on how to solve this that it will work under SecureBoot?
|
|
|
|
|
