PM: Add stock policy_manager.conf file.
The idea is that this file can be provided by a board-specific
package. To make it easy for such developers to figure out what they
can tweak, provide a helpful, well-documented configuration file.
Another CL will modify the update_engine ebuild so that it gets
installed (in /etc) along with the other files needed.
BUG=chromium:352739
TEST=None
Change-Id: I3d1045dbb9f5fd5d3ba31ef43c50addcf824fc96
Reviewed-on: https://chromium-review.googlesource.com/196700
Reviewed-by: Gilad Arnold <garnold@chromium.org>
Commit-Queue: David Zeuthen <zeuthen@chromium.org>
Tested-by: David Zeuthen <zeuthen@chromium.org>
diff --git a/policy_manager/policy_manager.conf b/policy_manager/policy_manager.conf
new file mode 100644
index 0000000..9215971
--- /dev/null
+++ b/policy_manager/policy_manager.conf
@@ -0,0 +1,18 @@
+# Configuration file for the policy-manager component of update_engine.
+#
+# Normally this file is loaded from /etc/policy_manager.conf. If
+# running update_engine in developer mode (and only if running in
+# developer mode), we attempt to load
+#
+# /mnt/stateful_partition/etc/policy_manager.conf
+#
+# and use it if it exists. If it doesn't exist, we fall back to
+# /etc/policy_manager.conf.
+#
+# Note: changes to this file are not automatically applied. Use the
+# command "restart update-engine" from a root shell to make your
+# changes take effect.
+
+# Set to true if the device supports the concept of OOBE
+# (Out-Of-the-Box-Experience), false if it doesn't.
+is_oobe_enabled=true