Tails no longer recommending balenaEtcher
-
i think it depends on the image you get - for archlinux you can simply cat (or dd) the file onto a usb stick and it works perfectly fine, bootable. but i think i have seen an image at some point where it didn't work, but i don't recall what it was.
-
Eh, I prefer being able to specify block sizes, to maximize the throughput.
-
Why use a fancy GUI tool when good old
dddoes the trick -
Completely aside from the blob issue mentioned, the Tails team has recommended against using a multiboot utility like Ventoy to install Tails. Ventoy works fine for basically any other operating system (again, aside from the blob issue), just not Tails, which is what this post is about.
-
WSL2 has relatively easy (a few powershell commands iirc) device mounting, provided you aren't trying to mount
or the windows install drive (not necessarily the same). -
Rufus is great! I worked with the maintainer to fix a bug in hardware they didn't have and it was a very pleasant experience.
-
It won't depend. I think it's because back in the day we never had an easy way to force boot a device, if a device wasn't flagged as bootable it wouldn't boot
-
I used to use the fedora media writer but the RPi imager software is so easy I switched
-
pvfor life. -
cat is the tool of distinguished gentlemen
-
Thanks for trying.
I'm not against terminal, but I'd just have to look up commands every time that I rarely use.
-
for Windows
-
Balenaetcher has, for me at least, failed to write to USBs for the last 3 years or so that I've tried to use it - meanwhile random iso writers from flatpak have been more reliable for me. Very obnoxious that so many iso related sites recommend it. Rufus, kicks tons of ass, if for whatever reason you're still on windows.
Also on most distros I've tried, the disk utility has some sort of right click or context menu that gets you a 'restore disk image' button that works great as well.
-
dd status=progresscan also tell you how far along the operation is. -
Or gnome disks, which also adds an "open with 'write to drive'" option to isos and images
-
From what I could gather, they're taken from Fedora and OpenSUSE. They're signed blobs for secure boot support.
-
I used it because that's what the instructions on the Linux Mint website for creating a bootable USB stick from Windows say to do.
I have no clue what "electron wrapper", "dd", or "rufus" are. I'm trying to learn more, but can't learn it all in one day.
-
Meh i find it slow.
-
Not using Ventoy in 2025?
-
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)
