I am shocked by this - the quote in below is very concerning:
“However, in 2024, the situation changed: balenaEtcher started sharing the file name of the image and the model of the USB stick with the Balena company and possibly with third parties.”
Can’t see myself using this software anymore…
You must log in or register to comment.
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 124 users / day
- 1.05K users / week
- 1.3K users / month
- 4.58K users / 6 months
- 1 subscriber
- 3.36K Posts
- 85.3K Comments
- Modlog
Is no one aware of Fedora Media Writer? It’s FOSS and the most trustworthy ISO burning software in existence. It’s only issue is that its named as if it is written only for producing Fedora bootable media. It works for everything.
Opensuse has one too. And dd exists for the brave or the foolish
The article at the end mentions they suggest dd as alternative for MacOS (due to Unix user space). It seems the balena -> rufus decision is about the easiest-onramp Mac+Win-portable option, for those uncomfortable dropping to low-level device-writing CLI tools in their current system.
Side-note: Last time I was on a friend’s Windows I installed dd simply enough both as mingw-w64 (native compiled) and under Cygwin. So for Windows users who are comfortable using dd it only requires a minor step. When I once used WSL devices were accessible too, but that was WSL1 (containerized), whereas WSL2 (virtualized) probably makes device-mapping complex(?) enough to not be worth it there.
WSL2 has relatively easy (a few powershell commands iirc) device mounting, provided you aren’t trying to mount C: or the windows install drive (not necessarily the same).
Thanks, that’s good to know, but for raw-writing a bootable image to a device do you (or anyone reading) know if there are also straightforward powershell commands for mapping devices at the block level? (as opposed to mounting at filesystem level)
I dunno… I just use dd.
cat works perfectly fine too 👌
Eh, I prefer being able to specify block sizes, to maximize the throughput.
Seeing progress, too
Meh i find it slow.
Or gnome disks, which also adds an “open with ‘write to drive’” option to isos and images