mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-11-27 23:21:06 -05:00
manual fixes
Manual fixes after the conversion tool.
This commit is contained in:
Marek Marczykowski-Górecki
parent
4a3b08fd7d
commit
bbd0337e91
26 changed files with 388 additions and 1613 deletions
|
|
@ -179,7 +179,7 @@ RPMs will appear in qubes-src/linux-kernel/pkgs/fc20/x86_64:
|
|||
|
||||
|
||||
Useful :doc:`QubesBuilder </developer/building/qubes-builder>` commands
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
1. ``make check`` - will check if all the code was committed into
|
||||
|
|
|
|||
|
|
@ -208,7 +208,7 @@ the source less readable and more difficult to work with for
|
|||
localization and automation purposes. Here are examples of several types
|
||||
of alerts and their recommended icons:
|
||||
|
||||
.. code:: bash
|
||||
.. code::
|
||||
|
||||
<div class="alert alert-success" role="alert">
|
||||
<i class="fa fa-check-circle"></i>
|
||||
|
|
|
|||
|
|
@ -92,7 +92,7 @@ and therefore one of the most important things to do well.
|
|||
|
||||
Below is the application template:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: markdown
|
||||
|
||||
# Introduction
|
||||
|
||||
|
|
@ -136,7 +136,7 @@ incomplete. If you are interested in submitting a proposal based on
|
|||
these ideas, you should contact the :ref:`qubes-devel mailing list <introduction/support:qubes-devel>` and associated GitHub issue to learn
|
||||
more about the idea.
|
||||
|
||||
.. code:: bash
|
||||
.. code:: markdown
|
||||
|
||||
### Adding a Proposal
|
||||
|
||||
|
|
|
|||
|
|
@ -224,7 +224,7 @@ satisfy the following criteria:
|
|||
|
||||
- The videos are suitable for embedding in appropriate places in the
|
||||
Qubes documentation. (E.g., a video on how to update Qubes OS should
|
||||
be appropriate for appearing on the :doc:`:doc:`how to update </user/how-to-guides/how-to-update>`` page.)
|
||||
be appropriate for appearing on the :doc:`how to update </user/how-to-guides/how-to-update>` page.)
|
||||
|
||||
- Where possible, the videos should strive to be version-independent.
|
||||
(For example, a video explaining the template system should still be
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ How to edit the documentation
|
|||
=============================
|
||||
|
||||
|
||||
*Also see the* :doc:`documentation style guide </developer/general/documentation-style-guide>` *.*
|
||||
*Also see the* :doc:`documentation style guide </developer/general/documentation-style-guide>`.
|
||||
|
||||
Qubes OS documentation pages are stored as plain text Markdown files in
|
||||
the `qubes-doc <https://github.com/QubesOS/qubes-doc>`__ repository. By
|
||||
|
|
@ -186,7 +186,7 @@ function the way they should when the website is rendered. They are not
|
|||
further analyzed in an attempt to determine whether they are malicious.
|
||||
|
||||
Once a pull request passes review, the reviewer should add a signed
|
||||
comment stating, “Passed review as of ``<LATEST_COMMIT>``” (or similar).
|
||||
comment stating, “Passed review as of ``<LATEST_COMMIT>`` ” (or similar).
|
||||
The documentation maintainer then verifies that the pull request is
|
||||
mechanically sound (no merge conflicts, broken links, ANSI escapes,
|
||||
etc.). If so, the documentation maintainer then merges the pull request,
|
||||
|
|
|
|||
|
|
@ -3,12 +3,6 @@ Qubes R3.0 release notes
|
|||
========================
|
||||
|
||||
|
||||
Qubes R3.0 Release Notes
|
||||
------------------------
|
||||
|
||||
|
||||
|
||||
|
||||
This Qubes OS release is dedicated to the memory of Caspar Bowden.
|
||||
|
||||
New features since 2.0
|
||||
|
|
|
|||
|
|
@ -776,27 +776,35 @@ Policy admin API
|
|||
There is also an API to view and update :doc:`Qubes RPC policy files </developer/services/qrexec>` in dom0. All of the following calls have dom0 as
|
||||
destination:
|
||||
|
||||
+------------------+----------+------------------+------------------+
|
||||
| call | argument | inside | return |
|
||||
+==================+==========+==================+==================+
|
||||
| ``policy.List`` | - | - | ``<name1> |
|
||||
| ``polic | | | \n<name2>\n...`` |
|
||||
| y.include.List`` | | | |
|
||||
+------------------+----------+------------------+------------------+
|
||||
| ``policy.Get`` | name | - | ``<tok |
|
||||
| ``poli | | | en>\n<content>`` |
|
||||
| cy.include.Get`` | | | |
|
||||
+------------------+----------+------------------+------------------+
|
||||
| `` | name | ``<tok | - |
|
||||
| policy.Replace`` | | en>\n<content>`` | |
|
||||
| ``policy.i | | | |
|
||||
| nclude.Replace`` | | | |
|
||||
+------------------+----------+------------------+------------------+
|
||||
| ` | name | ``<token>`` | - |
|
||||
| `policy.Remove`` | | | |
|
||||
| ``policy. | | | |
|
||||
| include.Remove`` | | | |
|
||||
+------------------+----------+------------------+------------------+
|
||||
.. list-table:: i
|
||||
:widths: 15 8 8 15
|
||||
:align: left
|
||||
:header-rows: 1
|
||||
|
||||
* - call
|
||||
- argument
|
||||
- inside
|
||||
- return
|
||||
* - | ``policy.List``
|
||||
| ``policy.include.List``
|
||||
- `-`
|
||||
- `-`
|
||||
- | ``<name1>\n<name2>...``
|
||||
* - | ``policy.Get``
|
||||
| ``policy.include.Get``
|
||||
- name
|
||||
- `-`
|
||||
- | ``<token>\n<content>``
|
||||
* - | ``policy.Get``
|
||||
| ``policy.include.Get``
|
||||
- name
|
||||
- | ``<token>\n<content>``
|
||||
- `-`
|
||||
* - | ``policy.Remove``
|
||||
| ``policy.include.Remove``
|
||||
- name
|
||||
- ``<token>``
|
||||
- `-`
|
||||
|
||||
The ``policy.*`` calls refer to main policy files
|
||||
(``/etc/qubes/policy.d/``), and the ``policy.include.*`` calls refer to
|
||||
|
|
|
|||
|
|
@ -61,10 +61,10 @@ qubes-dom0-update). Note that we assume that this script might get
|
|||
compromised and fetch maliciously compromised downloads – this is not a
|
||||
problem as Dom0 verifies digital signatures on updates later. The
|
||||
downloaded rpm files are placed in a
|
||||
``/var/lib/qubes/dom0-updates`` directory on UpdateVM
|
||||
``/var/lib/qubes/dom0-updates`` directory on UpdateVM
|
||||
filesystem (again, they might get compromised while being kept there,
|
||||
still this isn’t a problem). This directory is passed to yum using the
|
||||
``–installroot=`` option.
|
||||
``–installroot=`` option.
|
||||
|
||||
Once updates are downloaded, the update script that runs in UpdateVM
|
||||
requests an RPM service
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Components residing in the same domain (``qrexec-client-vm`` to
|
|||
``qrexec-agent``, ``qrexec-client`` to ``qrexec-daemon``) use local
|
||||
sockets as the underlying transport medium. Components in separate
|
||||
domains (``qrexec-daemon`` to ``qrexec-agent``, data channel between
|
||||
``qrexec-agent``s) use vchan links. Because of `vchan limitation <https://github.com/qubesos/qubes-issues/issues/951>`__, it
|
||||
``qrexec-agent``) use vchan links. Because of `vchan limitation <https://github.com/qubesos/qubes-issues/issues/951>`__, it
|
||||
is not possible to establish qrexec connection back to the source
|
||||
domain.
|
||||
|
||||
|
|
@ -185,7 +185,7 @@ dom0: request execution of ``cmd`` in domX
|
|||
with ``qrexec-agent`` later.)
|
||||
``qrexec-client`` translates that request into a ``MSG_EXEC_CMDLINE``
|
||||
message sent to ``qrexec-daemon``, with ``connect_domain`` set to 0
|
||||
(connect to **dom0**) and `connect_port also set to 0 (allocate a
|
||||
(connect to **dom0**) and ``connect_port`` also set to 0 (allocate a
|
||||
port).
|
||||
|
||||
- **dom0**: ``qrexec-daemon`` allocates a free port (in this case 513),
|
||||
|
|
|
|||
|
|
@ -367,7 +367,6 @@ particular service argument.
|
|||
|
||||
See `below <#rpc-service-with-argument-file-reader>`__ for an example of
|
||||
an RPC service using an argument.
|
||||
<!-- TODO document "Yes to All" authorization if it is reintroduced -->
|
||||
|
||||
Qubes RPC examples
|
||||
------------------
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load diff
Loading…
Add table
Add a link
Reference in a new issue