Changes to enable dev in stateful partition for usb and startup

Changes to enable dev in stateful partition for usb and startup

[sosa, 2010-03-11 03:21:42]

Modifies image_to_usb to compensate for change in build_image and ensure the
stateful partition gets carried over.

A couple other changes:
- file_copy was reporting wrong times as files aren't sync'd until after they
are closed.  Now image_to_usb reports much better metrics of how it's doing when
copying

Also mod'd chromeos_startup to check whether it should mnt /usr/local

[gauravsh, 2010-03-11 04:09:48]

http://codereview.chromium.org/848002/diff/1/4
File src/scripts/image_to_usb.sh (right):

http://codereview.chromium.org/848002/diff/1/4#newcode180
src/scripts/image_to_usb.sh:180: seek_bytes=$(( (${PART_SIZE}) + 512 ))
I am slightly confused by the calculation here. Isn't the stateful partition,
the first partition right after the MBR. Shouldn't the seek_bytes only be 512?

[sosa, 2010-03-11 18:56:14]

http://codereview.chromium.org/848002/diff/1/4
File src/scripts/image_to_usb.sh (right):

http://codereview.chromium.org/848002/diff/1/4#newcode180
src/scripts/image_to_usb.sh:180: seek_bytes=$(( (${PART_SIZE}) + 512 ))
You're right.  I didn't catch it becaues it didn't matter for testing as
chromeos-startup searches for "C-STATE" to determine which partition is the
stateful partition so it didn't matter if i was sdb2 rather than sdb1

On 2010/03/11 04:09:48, gauravsh wrote:
> I am slightly confused by the calculation here. Isn't the stateful partition,
> the first partition right after the MBR. Shouldn't the seek_bytes only be 512?

[gauravsh, 2010-03-11 19:12:18]

lgtm

[sosa, 2010-03-11 22:35:58]

I decided to add legacy support before pushing out this change (i.e.
image_to_usb now assumes you have a stateful partition, so we create it for
people who haven't run the new build_image before pushing to usb)

[gauravsh, 2010-03-11 22:54:19]

lgtm