From d6135c84a4c001683c58d6e555181f4faaaea0a7 Mon Sep 17 00:00:00 2001 From: Jonas Vautherin Date: Sat, 11 Feb 2023 01:08:16 +0100 Subject: [PATCH 1/2] Minor improvement in template-implementation Link to doc/templates/#inheritance-and-persistence when mentioning that the contents of the /home directory is not copied from the base template. --- developer/system/template-implementation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer/system/template-implementation.md b/developer/system/template-implementation.md index e4cc5303..eb248dbd 100644 --- a/developer/system/template-implementation.md +++ b/developer/system/template-implementation.md @@ -25,7 +25,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`. 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 `/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. ## modules.img (xvdd) From f4fb9c2306e85f0401e6e7f83c081e09c7942a94 Mon Sep 17 00:00:00 2001 From: Andrew David Wong Date: Fri, 10 Feb 2023 22:47:23 -0800 Subject: [PATCH 2/2] Fix URL --- developer/system/template-implementation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer/system/template-implementation.md b/developer/system/template-implementation.md index eb248dbd..c5efd1f7 100644 --- a/developer/system/template-implementation.md +++ b/developer/system/template-implementation.md @@ -25,7 +25,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 `/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. ## modules.img (xvdd)