Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-28 Thread Ronald F. Guilmette
In message 5153a2fd.8020...@sneakertech.com, you wrote: Why exactly is the bs=10240 is there? Wouldn't the default of 512 do just as well? Modern systems can read and write far more than 512 bytes per operation. Sticking with 512 would work perfectly fine, but you'd be imposing

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-28 Thread Quartz
I have filed the following PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=177431 Er, don't take my word for law: I have *no* idea if 1M is a good idea for most systems, I'm not even sure if it's optimal for mine. I did a single test with three random values at different orders of magnitude

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-28 Thread Steve O'Hara-Smith
On Thu, 28 Mar 2013 04:27:43 -0400 Quartz qua...@sneakertech.com wrote: I have filed the following PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=177431 Er, don't take my word for law: I have *no* idea if 1M is a good idea for most systems, I'm not even sure if it's optimal for mine.

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-28 Thread Ronald F. Guilmette
In message 5153feff.4090...@sneakertech.com, you wrote: I have filed the following PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=177431 Er, don't take my word for law: I didn't. I won't. I have *no* idea if 1M is a good idea Any size which is an exact multiple of the physical block

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-28 Thread Arthur Chance
On 03/28/13 10:32, Ronald F. Guilmette wrote: In message 5153feff.4090...@sneakertech.com, you wrote: I have filed the following PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=177431 Er, don't take my word for law: I didn't. I won't. I have *no* idea if 1M is a good idea Any size

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-28 Thread Ronald F. Guilmette
In message 51543b7a.4030...@qeng-ho.org, Arthur Chance free...@qeng-ho.org wrote: On 03/28/13 10:32, Ronald F. Guilmette wrote: It is possible, I would guess, that dd may notice the EOF occuring before it has filled up an entire input buffer, and then just quit at that point, _without_

Copying memstick image to a USB (flash/thumb) drive

2013-03-27 Thread Ronald F. Guilmette
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:

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-27 Thread Dan Nelson
In the last episode (Mar 27), Ronald F. Guilmette said: 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

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-27 Thread Daniel O'Callaghan
On 28/03/2013 8:10 AM, Ronald F. Guilmette wrote: Question: Why exactly is conv=sync is there? I found this on http://www.mkssoftware.com/docs/man1/dd.1.asp If you specified conv=sync and this input block is smaller than the specified input block size, dd pads it to the specified

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-27 Thread Quartz
Why exactly is the bs=10240 is there? Wouldn't the default of 512 do just as well? Modern systems can read and write far more than 512 bytes per operation. Sticking with 512 would work perfectly fine, but you'd be imposing an unnecessary bottleneck and the copy would be a lot