New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

document that dom0 never updates templates #1616

Closed
adrelanos opened this Issue Jan 13, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@adrelanos
Member

adrelanos commented Jan 13, 2016

Templates are intentionally never upgraded on qubes-dom0-update because then all user modifications to the template would be lost. I don't think this is documented somewhere yet? The usual way to update the templates is from within the templates. And if someone wants intentionally get rid of users changes and install a newer template version, the old one has to be uninstalled using yum first.

@marmarek marmarek added this to the Documentation/website milestone Jan 13, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 13, 2016

Member

Wondering where should it be mentioned. Perhaps here: https://www.qubes-os.org/doc/templates/
or maybe here: https://www.qubes-os.org/doc/software-update-vm/
Where would you look for such information?

Member

marmarek commented Jan 13, 2016

Wondering where should it be mentioned. Perhaps here: https://www.qubes-os.org/doc/templates/
or maybe here: https://www.qubes-os.org/doc/software-update-vm/
Where would you look for such information?

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Jan 13, 2016

Member

Both links are the same.

Member

adrelanos commented Jan 13, 2016

Both links are the same.

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Jan 13, 2016

Member

Anyhow. That page could do.

Not sure if people would find it. But I would primarily use it to direct users to it once the topic comes up somewhere. Better to have a good canonical documentation than investing time to reciting it.

Member

adrelanos commented Jan 13, 2016

Anyhow. That page could do.

Not sure if people would find it. But I would primarily use it to direct users to it once the topic comes up somewhere. Better to have a good canonical documentation than investing time to reciting it.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 13, 2016

Member

Both links are the same.

Oops, comment fixed.

Member

marmarek commented Jan 13, 2016

Both links are the same.

Oops, comment fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment