sig_cloud/diskimage-builder
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Correct statement about ramdisk and tmpfs.

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

Change-Id: Ib28b1c47f9f2bf1a3ba7138ab790b2ef6e11e06d
This commit is contained in:
Robert Collins 2014-07-16 20:26:18 +12:00 committed by Steve Kowalik
parent d78421642b
commit 0651c8f3f1
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@ -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