Question:
I dd-ed an iso file (it is a bit-for-bit copy/cloning), which resulted in
sdb1.
What is this sdb2 about, where did it come from ?
As Eric already explained, there's nothing strange about dd(1) here.
Nothing prevents you from running this command:
$ fdisk -l Downloads/archlinux-2014.10.01-dual.iso
I'm pretty sure that you'll see the same result as the
fdisk output from the target /dev/sdb.
For dd(1), it's all just data - byte per byte.
It's the interpretation of the data that makes the difference.
The kernel e.g. has to check if there's a partition table at the
beginning of a device, /dev/sdb in this case, and indeed there is one.
Therefore, it provides access to the partitions as sdb{1,2}.
Given you knew the offset of the file system in the second partition
of the ISO file, then you could also loop-mount it directly by using
the 'offset' and 'sizelimit' options of mount/losetup.
man losetup; man mount
Again, this all has not much to do with dd(1) and coreutils.
Have a nice day,
Berny