Wait up to 3 seconds for the data volume to initialize

When storage hardware takes too long to initialize, the disk is not
available at the time automount runs so the persistent boot2docker
volume never gets mounted.  By adding a `waitusb` option to the kernel
command line, we can pause the init sequence and allow the hardware
initialization and discovery to complete.

`waitusb=3:LABEL=boot2docker-data` will cause Tiny Core Linux to pause
until a volume with the `boot2docker-data` label is availalbe or 3
seconds have passed.
1.0.1 Docker release update
Merge pull request #401 from sykesm/waitusb-for-data

Wait up to 3 seconds for the data volume to initialize
Merge pull request #403 from SvenDowideit/pre-1.0.1

1.0.1 Docker release update
Support NFS back

https://github.com/boot2docker/boot2docker/pull/337
Do not delete sunrpc
Add CONFIG_NFS_V4_1 and CONFIG_NFSD_TCP
Change m to y for CONFIG_NFSD
prepare for next release
it seems that 3 seconds is not enough time for Hyper-V to have the disk ready (Closes #406) - trying 10 for now
Merge pull request #416 from SvenDowideit/pr_out_it_seems_that_3_seconds_is_not_enough_time_for_hyper_v_to_have_the_disk_ready_closes_406_trying_10_for_now

it seems that 3 seconds is not enough time for Hyper-V to have the disk ready (Closes #406) - trying 10 for now
Merge pull request #349 from YungSang/nfs

Support NFS back
Merge pull request #415 from SvenDowideit/pr_out_prepare_for_next_release

prepare for next release
update to 3.15.3 Linux kernel
add retry to kernel curl, my net was up and down like mad
change the build instructions to be more like what I actually do
the 3.15.3 .config we built with
Merge pull request #419 from SvenDowideit/update-to-3.15.3-linux-kernel

Update to 3.15.3 linux kernel
Clarify cifs volume sharing

I wanted to mention that using --volumes-from how you get the shared container available in other containers. 

Docker-DCO-1.1-Signed-off-by: Michael Neale michael.neale@gmail.com (github: michaelneale)
Merge pull request #421 from michaelneale/master

Clarify cifs volume sharing docs