On Sat, Aug 31, 2024 at 01:31:28PM +0200, to...@tuxteam.de wrote:
I plug in a USB stick (which will get completely overwritten),
check from the logs what its device name is (/dev/sdX),
then, as root, execute:
# dd bs=1M if=debian…amd64-netinst.iso of=/dev/sdX
# sync
and wait for the prompt after the sync command.
My recommendation is to add "oflag=sync status=progress" to that "dd"
command above.
Having bothched some sticks with the above method (that "sync" can take
a *long* time with big images).
Do *not* use oflag=sync, it will unnecessarily slow things down with no
advantage. Instead, if you really want to make sure things make it to
disk, use oflag=fdatasync, which will prevent dd from exiting until
everything has been written to disk, but without writing blocks one at a
time.
In general the recommended "cp" mechanism (followed by sync) is better
for most uses as it's a much simpler command line and much harder to
screw up with typos. dd has quite a lot of cargo cult voodoo around it,
but it's the best tool for a very small and specialized set of cases.
(It's in the muscle memory of a lot of older users, but that's no
reason we need to impose it on new users.)
On Sat, Aug 31, 2024 at 09:59:47PM -0500, David Wright wrote:
On Sat 31 Aug 2024 at 14:09:45 (-0400), Lee wrote:
On Sat, Aug 31, 2024 at 1:31 AM John Conover wrote:
>
> What does a "debian ... amd64-netinst.iso" do
> with an .iso?
>
> Can it be coverted to a USB. How?
https://www.debian.org/releases/bookworm/amd64/ch04s03.en.html
# cp debian.iso /dev/sdX
The disadvantage of this method is how to check the USB has a good copy.
I don't understand why it would be any harder or easier to check that
there's a good copy with cp vs some other tool, so this seems like
strange advice.
