Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Nov 2009 01:52:30 +0100
From:      Polytropon <>
To:        "Ronald F. Guilmette" <>
Subject:   Re: BTX Loader crashes -- Help wanted
Message-ID:  <>
In-Reply-To: <>
References:  <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Fri, 20 Nov 2009 15:48:34 -0800, "Ronald F. Guilmette" <> wrote:
> But I have one question.  The author sez to do this:
>    dd if=8.0-BETA1-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync
> I just want to know what the effect of conv=sync and why it might be
> necessary.

According to "man dd":

     bs=n     Set both input and output block size to n bytes, superseding the
              ibs and obs operands.  If no conversion values other than
              noerror, notrunc or sync are specified, then each input block is
              copied to the output as a single block without any aggregation
              of short blocks.

in conjunction with

     conv=value[,value ...]
              Where value is one of the symbols from the following list.

              sync     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.

it appears that the data is ensured to be "properly
aligned" with a possibly different block size on the
source or target media. As far as I remember, not
giving the bs= argument would result in a default
block size of 512 bytes which may - but don't ask
me why - lead to a non-functioning target USB stick.

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

Want to link to this message? Use this URL: <>