From: Joshua Lock <joshua.g.lock@intel.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: [PATCH] wic/help.py: document requirements for valid fstab generation
Date: Mon, 11 Jan 2016 13:33:51 +0000 [thread overview]
Message-ID: <1452519231-13332-1-git-send-email-joshua.g.lock@intel.com> (raw)
Without one of the --ondrive, --ondisk or --use-uuid options for a
partition with a mountpoint specified the automatically generated
fstab entry will be invalid.
[YOCTO #8844]
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
---
scripts/lib/wic/help.py | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/scripts/lib/wic/help.py b/scripts/lib/wic/help.py
index be334e7..f5587bb 100644
--- a/scripts/lib/wic/help.py
+++ b/scripts/lib/wic/help.py
@@ -629,6 +629,13 @@ DESCRIPTION
If a <mountpoint> is not specified the partition will be created
but will not be mounted.
+ Partitions with a <mountpoint> specified will be automatically mounted.
+ This is achieved by wic adding entries to the fstab during image
+ generation. In order for a valid fstab to be generated one of the
+ --ondrive, --ondisk or --use-uuid partition options must be used for
+ each partition that specifies a mountpoint.
+
+
The following are supported 'part' options:
--size: The minimum partition size. Specify an integer value
--
2.5.0
next reply other threads:[~2016-01-11 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 13:33 Joshua Lock [this message]
2016-01-18 8:08 ` [PATCH] wic/help.py: document requirements for valid fstab generation Ed Bartosh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1452519231-13332-1-git-send-email-joshua.g.lock@intel.com \
--to=joshua.g.lock@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox