mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-10-12 02:20:40 -04:00
Change again some languages
Thanks to @tokideveloper !!!
This commit is contained in:
parent
978efb3514
commit
3ba7a492f0
10 changed files with 12 additions and 12 deletions
|
@ -129,7 +129,7 @@ If you’re submitting a patch via GitHub (or a similar Git server), please sign
|
|||
|
||||
You may also find it convenient to have an alias for verifying the tag on the latest commit:
|
||||
|
||||
.. code:: console
|
||||
.. code:: ini
|
||||
|
||||
vtag = !git tag -v `git describe`
|
||||
|
||||
|
|
|
@ -220,7 +220,7 @@ This step is optional, but very helpful. Put these scripts somewhere in your ``$
|
|||
|
||||
``qtb-iterate``:
|
||||
|
||||
.. code:: console
|
||||
.. code:: bash
|
||||
|
||||
#!/bin/sh
|
||||
|
||||
|
@ -247,7 +247,7 @@ I (woju) have those two git hooks. They ensure tests are passing (or are marked
|
|||
|
||||
``core-admin/.git/hooks/pre-commit``: (you may retain also the default hook, here omitted for readability)
|
||||
|
||||
.. code:: console
|
||||
.. code:: bash
|
||||
|
||||
#!/bin/sh
|
||||
|
||||
|
@ -258,7 +258,7 @@ I (woju) have those two git hooks. They ensure tests are passing (or are marked
|
|||
|
||||
``core-admin/.git/hooks/pre-push``:
|
||||
|
||||
.. code:: console
|
||||
.. code:: bash
|
||||
|
||||
#!/bin/sh
|
||||
|
||||
|
|
|
@ -129,7 +129,7 @@ History and rationale
|
|||
|
||||
On 2013-01-05, Joanna Rutkowska announced the qubes-secpack and explained its rationale in an `email <https://groups.google.com/d/msg/qubes-devel/twkOEaMLtNI/lZyGx6_jFCEJ>`__ to the Qubes mailing lists:
|
||||
|
||||
.. code:: console
|
||||
.. code:: text
|
||||
|
||||
Hello,
|
||||
|
||||
|
|
|
@ -458,7 +458,7 @@ Now, our goal is to perform the same verification steps as we did with the origi
|
|||
|
||||
This command reads exactly the number of bytes of your Qubes ISO (obtained with ``stat -c %s /path/to/iso``) from the USB drive and pipes them into ``sha256sum``. The output should look something like this:
|
||||
|
||||
.. code:: console
|
||||
.. code:: output
|
||||
|
||||
0e68dd3347b68618d9e5f3ddb580bf7ecdd2166747630859b3582803f1ca8801 -
|
||||
5523+0 records in
|
||||
|
|
|
@ -402,7 +402,7 @@ Virtual Machine Formulae
|
|||
|
||||
You can use these formulae to download, install, and configure qubes in Qubes. These formulae use pillar data to define default qube names and configuration details. The default settings can be overridden in the pillar data located in:
|
||||
|
||||
.. code:: yaml
|
||||
.. code:: text
|
||||
|
||||
/srv/pillar/base/qvm/init.sls
|
||||
|
||||
|
|
|
@ -43,7 +43,7 @@ Clipboard automatic policy enforcement
|
|||
|
||||
The Qubes clipboard :doc:`RPC policy </user/advanced-topics/rpc-policy>` is configurable in:
|
||||
|
||||
.. code:: console
|
||||
.. code:: text
|
||||
|
||||
/etc/qubes-rpc/policy/qubes.ClipboardPaste
|
||||
|
||||
|
|
|
@ -31,7 +31,7 @@ You can always put a window into fullscreen mode in Xfce4 using the trusted wind
|
|||
|
||||
As an alternative to the Xfce4 method, you can enable fullscreen mode for select VMs by creating the following entry in the ``/etc/qubes/guid.conf`` file in dom0:
|
||||
|
||||
.. code:: console
|
||||
.. code:: text
|
||||
|
||||
VM: {
|
||||
personal: {
|
||||
|
|
|
@ -397,7 +397,7 @@ Verify the rules on the sys-net firewall correctly match the packets you want by
|
|||
|
||||
In this example, we can see 7 packets in the forward rule, and 3 packets in the dnat rule:
|
||||
|
||||
.. code:: console
|
||||
.. code:: output
|
||||
|
||||
chain custom-forward {
|
||||
iifname ens6 ip saddr 192.168.x.y/24 ip daddr 10.137.1.z tcp dport 443 ct state new,established,related counter packets 7 bytes 448 accept
|
||||
|
|
|
@ -340,7 +340,7 @@ These parameters are set for the following reasons:
|
|||
- Given the higher than usual memory requirements of Windows, you may get a ``Not enough memory to start domain 'WindowsNew'`` error. In that case try to shutdown unneeded VMs to free memory before starting the Windows VM.
|
||||
At this point you may open a tab in dom0 for debugging, in case something goes amiss:
|
||||
|
||||
.. code:: doscon
|
||||
.. code:: console
|
||||
|
||||
tailf /var/log/qubes/vm-WindowsNew.log \
|
||||
/var/log/xen/console/hypervisor.log \
|
||||
|
|
|
@ -52,7 +52,7 @@ In dom0, the ``qvm-appmenus`` tool allows the user to see the list of available
|
|||
|
||||
To change the whitelist shown in app menu, you need to provide a list of the desktop entries. Each line contains a desktop entry name, with its ``.desktop`` extension, like this:
|
||||
|
||||
.. code:: console
|
||||
.. code:: text
|
||||
|
||||
qubes-open-file-manager.desktop
|
||||
qubes-run-terminal.desktop
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue