I’ve been incredibly skeptical of Linux gaming for a long time now. But more than that I’ve been fed up with windows. I finally bit the bullet and bought some new ssd’s. Burned a bazzite iso and booted from the thumb drive. Honestly? The setup was flawless. The only thing I could see a non-technical person struggling with is burning images and booting from a drive. If a shop starts selling pre-builts with Linux configured for gaming then this might actually be the year of the Linux desktop
Now excuse me I’m gonna go play Arx Fatalis
Read closely and you’ll notice they used a thumb drive.
People usually refer to the act of copying the data directly onto the device as something other than “copying” to differentiate from copying the ISO as a file to a filesystem on the drive.
I’m honestly okay with the term “burn” being used here. It’s not correct, but it’s the same general operation. I usually say I’m “dd-ing an image onto the USB,” but that’s because I’m a Linux nerd and use
dd
for this.This is also one of those weird things: Why do people use
dd
for this?It doesn’t do anything special, it just does a plain old
read()
/write()
loop on regular-ass UNIX files. Its actual purpose is to do character set conversions while doing so.You can just
cp image.iso /dev/sda
or evencat image.iso > /dev/sda
. (The latter only works in a privileged shell because it’s the shell whichopen()
s the device file.)Idk about
cp
, but I can set block size and whatnot indd
, which seems to get better write performance. But maybe that’s a non-issue these days.Ya basically. Anytime I’m applying x to y hardware I’ll use “burn” or “flash” interchangeably. Something to indicate it’s overriding what’s there rather than just a fs cp.