this post was submitted on 06 Dec 2024
67 points (98.6% liked)
Linux Gaming
15493 readers
444 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME
away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.