/qubes-issues

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

qvm-* tools cleanup #421

Closed
marmarek opened this Issue Mar 8, 2015 · 4 comments

Comments

Assignees

@marmarek marmarek

Labels
Projects
None yet
Milestone
  Release 1
2 participants
@marmarek @rootkovska
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 18 Jan 2012 10:01 UTC

  • use qvm-pref also for the per-system settings (default template, etc)
  • move remaining functionality from qvm-* tools to the utils pkg
  • wiki docs for qvm-tools

Migrated-From: https://wiki.qubes-os.org/ticket/421

@marmarek marmarek assigned rootkovska Mar 8, 2015

@marmarek marmarek added this to the Release 1 milestone Mar 8, 2015

@marmarek marmarek added bug C: core P: major labels Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 30 Jan 2012 21:59 UTC
BTW, we should keep in mind that the 'qvm-' prefix was introduced to mean 'Qubes Virtual Machine', and so qvm-* tools should operate on the VMs, and not on the global system settings. So, e.g. qvm-set-default-netvm is really a bad name. I think we should keep qvm-run, qvm-prefs, etc, and then merge all the system-wide commands into qubes-prefs.
Member

marmarek commented Mar 8, 2015

Comment by joanna on 30 Jan 2012 21:59 UTC
BTW, we should keep in mind that the 'qvm-' prefix was introduced to mean 'Qubes Virtual Machine', and so qvm-* tools should operate on the VMs, and not on the global system settings. So, e.g. qvm-set-default-netvm is really a bad name. I think we should keep qvm-run, qvm-prefs, etc, and then merge all the system-wide commands into qubes-prefs.
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by marmarek on 7 Feb 2012 15:20 UTC
Member

marmarek commented Mar 8, 2015

Modified by marmarek on 7 Feb 2012 15:20 UTC

@marmarek marmarek assigned marmarek and unassigned rootkovska Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 10 Feb 2012 10:02 UTC
Most of cleanup done:

  • per-system tools renamed to qubes-*
  • most of qvm-* functionality moved to qubesutils package (so now qubes-manager can use it easily)

TODO:

  • perhaps move some other qvm-* to qubesutils (qvm-grow-private?)
  • docs (man pages and/or wiki)
Member

marmarek commented Mar 8, 2015

Comment by marmarek on 10 Feb 2012 10:02 UTC
Most of cleanup done:

  • per-system tools renamed to qubes-*
  • most of qvm-* functionality moved to qubesutils package (so now qubes-manager can use it easily)

TODO:

  • perhaps move some other qvm-* to qubesutils (qvm-grow-private?)
  • docs (man pages and/or wiki)
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 8 Mar 2012 23:33 UTC
qvm-tools documentation is now tracked by #479. Closing this one.
Member

marmarek commented Mar 8, 2015

Comment by joanna on 8 Mar 2012 23:33 UTC
qvm-tools documentation is now tracked by #479. Closing this one.

@marmarek marmarek closed this Mar 8, 2015

@andrewdavidwong andrewdavidwong referenced this issue May 23, 2016

Open

Create qvm-* (domU) man pages #2020

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