Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases Wiki Activity

TemplateImplementation changed

Browse Source
This commit is contained in:
Marek Marczykowski-Górecki 2011-04-11 20:21:31 +00:00
parent 9e1fc4ca6e
commit 2c1b57c927
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
TemplateImplementation.md
View File

@ -37,14 +37,14 @@ When TemplateVM is stopped, the xen script removes root-cow.img and creates a ne
Snapshot device in AppVM Snapshot device in AppVM
------------------------ ------------------------
Root device is exposed to AppVM in read-only mode. The only place where AppVM can write something is: Root device is exposed to AppVM in read-only mode. AppVM can write only in:
- private.img - persistent storage (mounted in /rw) used for /home, /usr/local and maybe more in future versions - private.img - persistent storage (mounted in /rw) used for /home, /usr/local - in future versions, its use may be extended
- volatile.img - temporary storage, which is discarded after AppVM restart - volatile.img - temporary storage, which is discarded after an AppVM restart
The volatile.img is divided into two partitions: volatile.img is divided into two partitions:
1. changes to root device 1. changes to root device
2. swap partition 2. swap partition
Inside of AppVM, root device is wrapped by snapshot with first partition of volatile.img. Thanks to this AppVM can write anything to its filesystem (but this changes will be discarded after restart). Inside of an AppVM, the root device is wrapped by the snapshot in the first partition of volatile.img. Therefore, the AppVM can write anything to its filesystem - however, such changes will be discarded after a restart.