From owner-freebsd-questions@FreeBSD.ORG  Wed Mar 27 21:19:43 2013
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id E915C129
 for <freebsd-questions@freebsd.org>; Wed, 27 Mar 2013 21:19:43 +0000 (UTC)
 (envelope-from rfg@tristatelogic.com)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com
 [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id CC104169
 for <freebsd-questions@freebsd.org>; Wed, 27 Mar 2013 21:19:42 +0000 (UTC)
Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1])
 by segfault.tristatelogic.com (Postfix) with ESMTP id DD1533AE43
 for <freebsd-questions@freebsd.org>; Wed, 27 Mar 2013 14:10:21 -0700 (PDT)
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
To: freebsd-questions@freebsd.org
Subject: Copying memstick image to a USB (flash/thumb) drive
Date: Wed, 27 Mar 2013 14:10:21 -0700
Message-ID: <6148.1364418621@server1.tristatelogic.com>
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2013 21:19:44 -0000


I've never used any FreeBSD memstick image before, but now I have reason
to do so.

I'm reading the instructions for creating a bootable memstick that are
located on this page:

  http://www.freebsd.org/releases/9.1R/announce.html

which include the following example of how to perform the copy:

  # dd if=FreeBSD-9.1-RELEASE-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync

Question:

   Why exactly is "conv=sync" is there?

   Also, in practice what does it actually do?  (I've used dd plenty in my
   lifetime, but never found any reason to use conv= at all.  I always
   thought that it was... mostly... just an archaic leftover from the days
   when some big iron used EBCDIC that needed to get converted to ASCII
   or vise versa.)

   The dd man page describes the "sync" type of "conversion" thusly:
   "Pad every input block to the input buffer size.  Spaces are used for
   pad bytes if a block oriented conversion value is specified, otherwise
   NUL bytes are used."  Ummm... ok.  WTF is a "block oriented conversion
   value"?  How would I know if I had specified one?

Question:

    Why exactly is the "bs=10240" is there?  Wouldn't the default of 512
    do just as well?


Regards,
rfg