Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

What's with the Ventoy hate. Every linux distro can be installed with Ventoy except for SuSe ones


SuSE doesn't ship ventoy and the installer does boot and work just fine. It's likely a bug in ventoy. SuSE doesn't test that and why would they?

Perhaps ventoy doesn't like SuSE.


there were some pretty deep shenanigans in ventoy not too long ago.

https://hackertimes.com/item?id=44810281

This was pretty wild too: https://github.com/ventoy/PXE/issues/106 that's where they installed a self-signed EV cert in the trust store.


It silently messes with the kernel boot flags which breaks the boot process If you do get it to work it silently adds extra broken repos which make it impossible to install packages.

Why would any distro want to support a tool that intentionally breaks things? Ventoy could just boot ISOs without messing with them and everything would work fine, but the developers insist on injecting garbage.


> If you do get it to work it silently adds extra broken repos which make it impossible to install packages.

This is not true.

I use it extensively and have done for more than 4 years now. It adds nothing at all to the installed OS. It doesn't care about the installed OS: I have successfully installed Linux, FreeBSD, Windows, even FreeDOS from Ventoy.



You have misunderstood what these reports are saying.

You claimed "Ventoy adds repos". It does not. It is incapable of doing anything of the kind. It does not run on the installed system. It does not modify the boot media in any way. This is demonstrable and verifiable.

When booted from Ventoy, openSUSE apparently adds the installation media as a repository.

This is not some disaster or horrible hack. This is normal behaviour for Debian, for example.

That means that something in the openSUSE installer is misinterpreting boot parameters.

This is a openSUSE bug, not a Ventoy bug.

SUSE, though, has an institutional habit of blaming problems on others, or denying that problems exist. I know this for a fact from my own personal direct experience: I worked at SUSE from 2017 to 2021.

You are misreading bug reports, wrongly deducing things that did not happen, and mis-attributing blame. The fault here is yours, and secondarily SUSE's. It is not Ventoy's.


> You claimed "Ventoy adds repos". It does not. It is incapable of doing anything of the kind. It does not run on the installed system. It does not modify the boot media in any way. This is demonstrable and verifiable.

It literally adds an rdinit to the kernel boot line that hijacks the boot process and messes with it in a shell script. This is demonstrable and verifiable: https://github.com/ventoy/Ventoy/blob/master/IMG/cpio/ventoy...


It adds a parameter to the kernel boot line. That is not adding a repository. It is not doing what you claim it does.

I am not putting any pressure on you. If you don't want to use it, then don't.

I find it hugely useful, have been using it for about 10 years now on dozens of machines and hundreds of distros and OSes, and it's saved me not just hours but days and weeks of work, effort, and time wasted writing files to USB keys.

All I am asking you to do is not tell lies about it.


Fine, the repository gets added because ventoy hijacks the boot process and messes with it, it does not directly add it. The problem is still the same and it would still be a problem even if it didn't break anything: It should not be hijacking the boot process, there's absolutely no good reason for it.


I’ve had trouble installing proxmox with ventoy, I had to install debian and then proxmox as a package. AFAIK there isn’t really an alternative to ventoy?


I like the iODD virtual disc drives, I have an ST400 that has been pretty reliable aside from complaining when the iso files are too "fragmented".


You really shouldn't trust ventoy.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: