It came from exactly https://ftp.openbsd.org/pub/OpenBSD/6.6/...019.10.tgz because I pasted the URL into a text file then did a wget -i on it, I keep the little text files.
Wait a minute, the url you posted is https://cdn.openbsd.org/pub/OpenBSD/6.6/...019.10.tgz, why does it have amd64 and aarch64 in it? But I can try that one or at least do a cmp on them.
OK, they have different sha256 sums, I'll try it. The date on yours is Dec 31, 1969, the other one too. 682536 bytes on both.
No difference in how they act. But I did take a quick look at the dd man page because I never used the seek feature before. The offset is the number you enter times the output block size so 8 * 1024. I up-arrowed and copied and pasted the line into a file afterwards, it was
dd if=u-boot-sunxi-with-spl.bin of=/dev/sdb bs=1024 seek=8
I used the same thing this time. I'm used to the block size not being critical, but the offset is critical.
I didn't sha the actual files, just the tgz files they came out of, those are different. I see
622f71b6897412861e3ac11b5cdefcabdbf2b078d87216dfd5c6da1c1c1c852d on the amd one,
1e9a2a7c0678d791031bb78180404110833b48d421fd3c7d84dff985306cbfae on the other.
Wait a minute, the url you posted is https://cdn.openbsd.org/pub/OpenBSD/6.6/...019.10.tgz, why does it have amd64 and aarch64 in it? But I can try that one or at least do a cmp on them.
OK, they have different sha256 sums, I'll try it. The date on yours is Dec 31, 1969, the other one too. 682536 bytes on both.
No difference in how they act. But I did take a quick look at the dd man page because I never used the seek feature before. The offset is the number you enter times the output block size so 8 * 1024. I up-arrowed and copied and pasted the line into a file afterwards, it was
dd if=u-boot-sunxi-with-spl.bin of=/dev/sdb bs=1024 seek=8
I used the same thing this time. I'm used to the block size not being critical, but the offset is critical.
I didn't sha the actual files, just the tgz files they came out of, those are different. I see
622f71b6897412861e3ac11b5cdefcabdbf2b078d87216dfd5c6da1c1c1c852d on the amd one,
1e9a2a7c0678d791031bb78180404110833b48d421fd3c7d84dff985306cbfae on the other.
