Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign up[GUI improvement] Qubes VM Manager StandaloneVM: keep the original TemplateVM OS name #2592
Comments
Wikinaut
changed the title from
[GUI improvement] Qubes VM Manager StandaloneVM: keep the original TemplateVM name
to
[GUI improvement] Qubes VM Manager StandaloneVM: keep the original TemplateVM OS name
Jan 19, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jan 19, 2017
Member
That's bad idea - since StandaloneVM is not really bound to its original template, it can easily desynchronize - for example when you update to the next distribution (like debian-9 StandaloneVM created of debian-8 or even older VM), or even morph it to a differend distribution (like kali).
In the future, VM description field may be used for such thing: #899
|
That's bad idea - since StandaloneVM is not really bound to its original template, it can easily desynchronize - for example when you update to the next distribution (like debian-9 StandaloneVM created of debian-8 or even older VM), or even morph it to a differend distribution (like kali). In the future, VM description field may be used for such thing: #899 |
marmarek
closed this
Jan 19, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Wikinaut
Jan 19, 2017
It was just and only meant as a reminder to the user what the original OS was.
Wikinaut
commented
Jan 19, 2017
|
It was just and only meant as a reminder to the user what the original OS was. |
Wikinaut commentedJan 19, 2017
Qubes OS version (e.g.,
R3.2):3.2
When I set up a StandaloneVM, let's say based on
debian-9, this information is overwritten with the string"StandaloneVM"when the SVM is created.I want to suggest that the original TemplateVM name is kept, e.g.
"Standalone VM (based on debian-9)"or so.