From 4b625ee6667bfaacabc98263f035b63b28fe1d2a Mon Sep 17 00:00:00 2001 From: qubedmaiska Date: Wed, 15 Jan 2025 15:29:39 -0500 Subject: [PATCH] Rearranged hyperlinked words --- developer/system/template-implementation.md | 2 +- user/how-to-guides/how-to-use-devices.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/developer/system/template-implementation.md b/developer/system/template-implementation.md index 4feb91fb..1cc840a6 100644 --- a/developer/system/template-implementation.md +++ b/developer/system/template-implementation.md @@ -27,7 +27,7 @@ This is mounted as /rw and here is placed all VM private data. This includes: - */usr/local* – which is symlink to /rw/usrlocal - some config files (/rw/config) called by qubes core scripts (ex /rw/config/rc.local) -**Note:** Whenever a TemplateBasedVM is created, the contents of the `/home` directory of its parent TemplateVM [are *not* copied to the child TemplateBasedVM's `/home`](/doc/templates/#inheritance-and-persistence). The child TemplateBasedVM's `/home` is independent from its parent TemplateVM's `/home`, which means that any changes to the parent TemplateVM's `/home` will not affect the child TemplateBasedVM's `/home`. Once a TemplateBasedVM has been created, any changes in its `/home`, `/usr/local`, or `/rw/config` directories will be persistent across reboots, which means that any files stored there will still be available after restarting the TemplateBasedVM. No changes in any other directories in TemplateBasedVMs persist in this manner. If you would like to make changes in other directories which *do* persist in this manner, you must make those changes in the parent TemplateVM. +**Note:** Whenever a TemplateBasedVM is created, the contents of the `/home` directory of its parent TemplateVM [are *not* copied to the child TemplateBasedVM's](/doc/templates/#inheritance-and-persistence) `/home`. The child TemplateBasedVM's `/home` is independent from its parent TemplateVM's `/home`, which means that any changes to the parent TemplateVM's `/home` will not affect the child TemplateBasedVM's `/home`. Once a TemplateBasedVM has been created, any changes in its `/home`, `/usr/local`, or `/rw/config` directories will be persistent across reboots, which means that any files stored there will still be available after restarting the TemplateBasedVM. No changes in any other directories in TemplateBasedVMs persist in this manner. If you would like to make changes in other directories which *do* persist in this manner, you must make those changes in the parent TemplateVM. ### modules.img (xvdd) diff --git a/user/how-to-guides/how-to-use-devices.md b/user/how-to-guides/how-to-use-devices.md index c8d2c0eb..66269c41 100644 --- a/user/how-to-guides/how-to-use-devices.md +++ b/user/how-to-guides/how-to-use-devices.md @@ -65,7 +65,7 @@ A list of VMs appears, one showing the eject symbol: ![eject icon](/attachment/d Only `mic` should be attached to more than one running VM. You may *assign* a device to more than one VM (using the `--persistent` option), however, only one of them can be started at the same time. -But be careful: There is a [bug in `qvm-device block` or `qvm-block`](https://github.com/QubesOS/qubes-issues/issues/4692) which will allow you to *attach* a block device to two running VMs. +But be careful: There is a [bug in](https://github.com/QubesOS/qubes-issues/issues/4692) `qvm-device block` or `qvm-block` which will allow you to *attach* a block device to two running VMs. Don't do that!