This is only going to bite people installing from one USB stick to another.  USB-connected drives wouldn&#39;t be affected, because they report an actual serial number from the disk; it&#39;s just USB sticks that often do not, since they are cheap.  I may be missing the correct scenario here, but it appears what you are describing is not likely to happen.<br>
<br><div class="gmail_quote">On Sun, Oct 16, 2011 at 10:36 PM, Juan Francisco Cantero Hurtado <span dir="ltr">&lt;<a href="mailto:iam@juanfra.info">iam@juanfra.info</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Sun, Oct 16, 2011 at 11:29:27PM +0000, Justin C. Sherrill (via DragonFly issue tracker) wrote:<br>
&gt;<br>
&gt; Why are you installing from one USB stick to another?  The original image is<br>
&gt; bootable.  You can copy the initial image onto both.  I realize that&#39;s not<br>
&gt; the original task you were trying to do, but it would have less problems.<br>
&gt;<br>
<br>
I know. I was only testing the speed of my usb stick with hammer and<br>
I discovered the bug. My steps are only a example :)<br>
<br>
Some users install the operating systems in usb disks and they will<br>
have this problem. No only a bootable OS like in the usb images, I mean<br>
people with a real systems (tens of GB) in usb disks.<br>
<br>
SATA, IDE and SCSI disks have a unique identifier, the serial number.<br>
The USB disks need also a unique identifier.<br>
<br>
</blockquote></div><br>
