-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 2017-05-20 21:59, Todd Lasman wrote: > > On 05/20/2017 06:12 PM, Andrew David Wong wrote: >> On 2017-05-20 19:43, Todd Lasman wrote: >>> The dogma, as I understand it, is that it's safer to clone a >>> template, make changes to the clone, then base your AppVM's >>> off of that cloned template. > >>> - From the Qubes website: "It is highly recommended to clone >>> the original template, and make any changes in the clone >>> instead of the original template. The following command clones >>> the template. Replace your-new-clone with your desired >>> name..." > >>> My question is, why? It seems to me that if you ever needed >>> the original template back, you could just download it again >>> from the repository. Am I missing something? > >>> Todd > > >> The main reasons are that user customizations are not guaranteed >> to be preserved in RPM-managed templates, and they're harder to >> back up and restore. > > > > Hmm. Not sure I understand that logic. The cloned templates still > need to be managed and backed up, so where's the advantage? >
Being RPM-managed is different from being "managed" in a general sense. Cloned templates need to be managed in a general sense, but they do not need to be (and are not) RPM-managed. This is an advantage if they're extensively customized by the user, since any changes pushed to RPM-managed templates won't break the user customizations. Cloned templates are easier to back up and restore than RPM-managed templates. Trying to restore an RPM-managed on a Qubes machine with an existing RPM-managed template of the same kind can be very difficult. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJZIQtuAAoJENtN07w5UDAwAfoQAL2legUgVIjasmV9hGr4ZTL9 NLfd7Za5soKa1lPmnpvTaaOvesKwbTWl8J++zQ0tH9gpn4oeDQnzWmcNvOLaY7Ow x+k1shEC9VSBhY54CRRVlzKcL61Bfge0tqDqiWAoWknee7YYc81AyZlFeuJHVmO5 SBwFAUOENaHQZqbIAWNQnO1T/p3DKaTSldt4NHz1xl9ekLtFGQgGArg94PpRaNOX Gq6M/Mn1eOgVkACDUQgP98EuSAqVH3PWdOjVOs/gCKN9eqNmh+V2wcZoCp0mueQo +yiaz0kdNEIJtBSBVHfWN1271QSub0RSxDWU0A8fptfMASFkZWex7C1jxbTnXhWA 6+ZNG/UB7+JoEexMrapt0vycMGn7Cb97wCWDLeszPz0vitPAU9ei8x8nAFANzRQX +gYHxTYGZMthTZ/S6vr9Z+a116i3/ay1kOYOsf5CJLqO5M1Mwt8S2cab0a5HJDSD JfryBnu5HR2mQoej4IqYpMKhI9qqSonyrKOHSRyq+3dAjZxgZMZWzKaZXF7B+UuL goFzPTVUDv3QSRnPi00ZS2eIOt4vnRqr/eiDmSaZ4HoNnxn9lyLWIfdxpzm9O6Fp M7k1JXTJWNJZJU9Zmqypj2LFixZ77b4iCkbnkdHlA7vVdrpmclawT08MRTsjjY0i toEv/3e1Ezy5HzgViq+I =THST -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4d3630f2-b4b5-e558-6e12-62c77d8d92e3%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
