Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
A warning statement is included below the Linux instruction as follows: The image must be written to the whole-disk device and not a partition, e.g. /dev/sdb and not /dev/sdb1.
I would like to ask why the copy operation is performed on the entire hard disk space. Will the file system be changed and all data originally on the hard disk deleted after this operation?
Thanks for any help.
Last edited by Free_Alan on 2024-03-20 05:45, edited 1 time in total.
Free_Alan wrote: ↑2024-03-19 09:27
I would like to ask why the copy operation is performed on the entire hard disk space.
Because it's a hybrid bootable disk image, so it includes partition table, boot sector(s), and filesystems. That's how disk images generally work.
A cp to a block device node is roughly equivalent to a dd to the same, and writes directly to the raw disk or partition.
Free_Alan wrote: ↑2024-03-19 09:27Will the file system be changed and all data originally on the hard disk deleted after this operation?
Of course. As the wiki states:
Be aware, that the methods described here will destroy anything already on the device!
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.
FWIW, I would not use the cp command, but would instead do "dd if=debian.iso of=/dev/sdx bs=512" since cp is meant for filesystem operations, not raw devices.
kent_dorfman766 wrote: ↑2024-03-19 11:35
FWIW, I would not use the cp command, but would instead do "dd if=debian.iso of=/dev/sdx bs=512" since cp is meant for filesystem operations, not raw devices.