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 upStandalone AppVMs with own root.img #98
Comments
marmarek
assigned
rootkovska
Mar 8, 2015
marmarek
added this to the Release 1 Beta 1 milestone
Mar 8, 2015
marmarek
added
enhancement
C: core
P: major
labels
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Mar 8, 2015
Member
Comment by joanna on 15 Mar 2011 00:49 UTC
Perhps the --standalone switch would be more readable?
|
Comment by joanna on 15 Mar 2011 00:49 UTC |
marmarek
changed the title from
Independent AppVMs with own root.img
to
Standalone AppVMs with own root.img
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Modified by joanna on 15 Mar 2011 00:50 UTC |
marmarek
assigned
marmarek
and unassigned
rootkovska
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Modified by marmarek on 17 Mar 2011 00:43 UTC |
marmarek
closed this
Mar 8, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedMar 8, 2015
Reported by joanna on 14 Mar 2011 21:37 UTC
Currently, in order to have a totally independent and updateable AppVM, the user must: 1) clone the template, 2) make the template unupdatble, 3) create the AppVM based on this template.
This is useful if one wishes to have several AppVMs based on the custom template, but a total overkill if one wishes to have just one, independently updateable AppVM.
So, I think it would be useful to allow creation of 'independent' AppVMs, i.e. with own root.img, not based on any other template. Something like this:
Migrated-From: https://wiki.qubes-os.org/ticket/98