mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-12-28 00:39:30 -05:00
9e48ca78cc
Generally modifying storage volume/pool settings require removing and creating the object again. This is not only API limitation, but most of them really need the object to be recreated (for example storage pool have most settings related to physical location of the data). But some properties are safe to change. This applies to `revisions_to_keep` (both storage pool and volume). Introduce appropriate API methods for this. Put property name in API call name, because argument is already used. And also because we don't plan to be too flexible here - we may need to add one or two more mutable properties, but definitely we don't want to allow any of them (as explained above). The same applies to `persistent` option of device. There, in theory detach+attach should be enough at all times, but in practice domain may use the device (for example system being started from it - QubesOS/qubes-issues#3055). |
||
|---|---|---|
| .. | ||
| admin-api.md | ||
| dom0-secure-updates.md | ||
| dvm-impl.md | ||
| qfilecopy.md | ||
| qfileexchgd.md | ||
| qmemman.md | ||
| qrexec2.md | ||
| qrexec3.md | ||