From 0651c8f3f1143d469433aa7818aefbb626d9e487 Mon Sep 17 00:00:00 2001
From: Robert Collins <rbtcollins@hp.com>
Date: Wed, 16 Jul 2014 20:26:18 +1200
Subject: [PATCH] Correct statement about ramdisk and tmpfs.

This has been wrong since we moved ramdisk creation into the chroot.

Change-Id: Ib28b1c47f9f2bf1a3ba7138ab790b2ef6e11e06d
---
 README.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 771af7367..56c703b8e 100644
--- a/README.md
+++ b/README.md
@@ -85,10 +85,11 @@ Requirements
 If you have 4GB of available physical RAM\*, or more, diskimage-builder will
 create a tmpfs mount to build the image in. This will improve image build time
 by building in RAM. This can be disabled completely by passing --no-tmpfs to
-disk-image-create. ramdisk-image-create does not use a tmpfs mount. If tmpfs
-is not used, you will need enough room in /tmp to store two uncompressed
-cloud images. If you do have tmpfs, you will still need /tmp space for one
-uncompressed cloud image and about 20% of that for working files.
+disk-image-create. ramdisk-image-create builds a regular image and then within
+that does ramdisk creation. If tmpfs is not used, you will need enough room in
+/tmp to store two uncompressed cloud images. If you do have tmpfs, you will
+still need /tmp space for one uncompressed cloud image and about 20% of that
+for working files.
 
 \* As reported by /proc/meminfo MemTotal