summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2010-07-08 20:52:54 -0400
committerScott Moser <smoser@ubuntu.com>2010-07-08 20:52:54 -0400
commitb5c3659c29db2177665ff6c1c10587bc1d8eba1f (patch)
tree92a4f6af85468321c9ef6a7d62e033f4d91dc3f3 /doc
parentd96186bc66b86639e9f9257aa288256e11e44ad5 (diff)
downloadvyos-cloud-init-b5c3659c29db2177665ff6c1c10587bc1d8eba1f.tar.gz
vyos-cloud-init-b5c3659c29db2177665ff6c1c10587bc1d8eba1f.zip
add 'nobootwait' to the default options for fstab entries
It just seems like for cloud instances, getting /etc/fstab written incorrectly with the result of non-booting system is worth avoiding.
Diffstat (limited to 'doc')
-rw-r--r--doc/examples/cloud-config.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/examples/cloud-config.txt b/doc/examples/cloud-config.txt
index e036feba..ed1ef47f 100644
--- a/doc/examples/cloud-config.txt
+++ b/doc/examples/cloud-config.txt
@@ -102,7 +102,7 @@ packages:
# written to /etc/fstab.
# - '/dev' can be ommitted for device names that begin with: xvd, sd, hd, vd
# - if an entry does not have all 6 fields, they will be filled in
-# from the following: [ None, None, "auto", "defaults", "0", "0" ]
+# from the following: [ None, None, "auto", "defaults,nobootwait", "0", "0" ]
#
# Note, that you should set 'nobootwait' (see man fstab) for volumes that may
# not be attached at instance boot (or reboot)