clean up and refine all the docs in git

Break the long lines, remove the deprecated content, etc.

BTW, other minor changes include:
* move the cmdln completion scripts to more proper places
* file permission checking

Change-Id: I063d99119156b45279a387c24280723ae70f4eb2
Signed-off-by: Jianfeng Ding <jian-feng.ding@intel.com>

4 files changed, 67 insertions, 43 deletions

diff --git a/doc/FAQ.rst b/doc/FAQ.rst
new file mode 100644
index 0000000..e52baa3
--- /dev/null
+++ b/doc/FAQ.rst
@@ -0,0 +1,58 @@
+FAQ
+===
+
+Q: When creating an image, MIC shows:
+   "Error <creator>: URLGrabber error: http://.../.../repos/oss/ia32/packages/repodata/repomd.xml"
+
+A: Perhaps your network has some issues, or your proxy doesn't work.
+   Try another proxy or find out the network issue.
+
+Q: MIC complains "ERROR: found 1 resolver problem, abort!"
+
+A: This is not an issue of MIC, it's caused by the repo you used.
+   Make sure the packages in the repo you used have proper dependencies.
+
+Q: I used '-A i586' to create an i586 image, but it showed
+   "nothing provided ....". What's wrong with it?
+
+A: Use '-A i686'. i586 is lower than i686, so many packages will be missing
+   from the installation.
+
+Q: Error shows: "uninstallable providers: somepackageA"
+
+A: It's caused by the missing package in the repo. To find it out, modify the
+   "%packages" section with only one item 'somepackageA' in kickstart file,
+   then you can root cause what's the missing dependency.
+
+Q: MIC shows in the log:
+   "file /usr/share/whatever conflicts between attempted installs of somepackageA and somepackageB"
+
+A: There are conflicts between some packages in the repo you used, but this
+   is not an issue with MIC. Please make sure you are using a proper repo.
+
+Q: Error shows: Command 'modprobe' is not available.
+
+A: In some distributions, when you use sudo, the PATH variable will be changed
+   and you will lose some important paths. Run 'export PATH=/sbin:$PATH'
+   before running MIC.
+
+Q: MIC lost some packages which are specified in '--includepkgs'/'--excludepkgs'
+
+A: Assume you want to include/exclude some packages in one repo, you will use
+   '--includepkgs'/'--excludepkgs' option in the according repo command line,
+   but you should list these packages to %packages section too, otherwise they
+   will not take any effect.
+
+Q: How does mic select packages? And how to set the priority of a repo?
+
+A: In general, mic will select a higher version if two or more available in
+   all repos, if the version is the same, a higher release number is
+   prefferred. But if you assign a priority to one repo, mic will prefer to
+   select packages from the repo with higher priority, even in case a higher
+   version is available in the repo with a lower priority. Actually the
+   default priority for a repo is 99, the range of a repo priority is 1~99,
+   the larger number has the lower priority.
+   An example is given:
+     "repo --name=base --baseurl=http://whateverurl --prioirity=1"
+
+
diff --git a/doc/KNOWN_ISSUES b/doc/KNOWN_ISSUES
index 72e8b24..cf53eac 100644
--- a/doc/KNOWN_ISSUES
+++ b/doc/KNOWN_ISSUES
@@ -3,9 +3,11 @@ Known Issues
 
 ARM64 support
 -------------
-Currently mic only supports aarch64 (aka arm64) in native mode. To support
-aarch64 in mic, you should upgrade following packages manually:
-libzypp
-python-zypp
-qemu-arm-static
+Currently mic only supports aarch64 (ARM64) in native running mode because
+of current enabling status in Tizen repository. And the following packages
+need to be upgraded by using Tizen-tools repository:
+
+* libzypp
+* python-zypp
+* qemu-arm-static
 
diff --git a/doc/RELEASE_NOTES b/doc/RELEASE_NOTES
index 14b4b5f..f9d849a 100644
--- a/doc/RELEASE_NOTES
+++ b/doc/RELEASE_NOTES
@@ -1,5 +1,5 @@
- MIC Image Creator 0.21 Release Notes
-===========================================================
+MIC Image Creator 0.21 Release Notes
+====================================
 Released August 28 2013
 
 This release note documents the changes included in the new release. And
diff --git a/doc/faq.rst b/doc/faq.rst
deleted file mode 100644
index 314b4e4..0000000
--- a/doc/faq.rst
+++ /dev/null
@@ -1,36 +0,0 @@
-FAQ
-===
-
-Q: When creating an image, MIC shows "Error <creator>: URLGrabber error: http://www.example.com/latest/repos/oss/ia32/packages/repodata/repomd.xml"
-
-A: Perhaps your network has some issues, or your proxy doesn't work. Try another proxy or find out the network issue.
-
-Q: MIC complains "ERROR: found 1 resolver problem, abort!"
-
-A: This is not an issue of MIC, it's caused by the repo you used. Make sure the packages in the repo you used have proper dependencies.
-
-Q: I used '-A i586' to create an i586 image, but it showed "nothing provided ....". What's wrong with it?
-
-A: Use '-A i686'. i586 is lower than i686, so many packages will be missing from the installation.
-
-Q: Error shows: "uninstallable providers: somepackageA"
-
-A: It's caused by the missing package in the repo. To find it out, modify the %packages section with only one item 'somepackageA' in kickstart file, then you can root cause what's the missing dependency.
-
-Q: MIC shows in the log: "file /usr/share/whatever conflicts between attempted installs of somepackageA and somepackageB"
-
-A: There are conflicts between some packages in the repo you used, but this is not an issue with MIC. Please make sure you are using a proper repo.
-
-Q: Error shows: Command 'modprobe' is not available.
-
-A: In some distributions, when you use sudo, the PATH variable will be changed and you will lose some important paths. Run 'export PATH=/sbin:$PATH' before running MIC.
-
-Q: MIC lost some packages which are specified in '--includepkgs'/'--excludepkgs'
-
-A: Assume you want to include/exclude some packages in one repo, you will use '--includepkgs'/'--excludepkgs' option in the according repo command line, but you should list these packages to %packages section too, otherwise they will not take any effect.
-
-Q: How does mic select packages? And how to set the priority of a repo?
-
-A: In general, mic will select a higher version if two or more available in all repos, if the version is the same, a higher release number is prefferred. But if you assign a priority to one repo, mic will prefer to select packages from the repo with higher priority, even in case a higher version is available in the repo with a lower priority. Actually the default priority for a repo is 99, the range of a repo priority is 1~99, the larger number has the lower priority. An example is given: 'repo --name=base --baseurl=http://whateverurl --prioirity=1'.
-
-