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 upConsider restoring dom0 home backup to /home/subdir instead of /home #2271
Comments
andrewdavidwong
added
C: core
task
labels
Aug 27, 2016
andrewdavidwong
added this to the Release 4.0 milestone
Aug 27, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
entr0py
Aug 27, 2016
+1
- backup existing /home to /home.original
- backup restored /home to /home.restored
- put one of these versions in /home
Recently had an issue with KDE Window Rules not being restored properly. Having the config files handy makes troubleshooting much easier than having to dig through the backup files.
entr0py
commented
Aug 27, 2016
|
+1
Recently had an issue with KDE Window Rules not being restored properly. Having the config files handy makes troubleshooting much easier than having to dig through the backup files. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
commented
Sep 23, 2016
|
This is a great idea. Better from a security standpoint, too. |
andrewdavidwong
added
C: qubes-manager
P: major
labels
Jan 14, 2017
andrewdavidwong
referenced this issue
Jan 14, 2017
Closed
Do no restore (some of) the Dom0 home dir on backup restore #1106
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Feb 27, 2018
Member
Done by @tasket here: QubesOS/qubes-core-admin-client@30dd7ac
Dom0 home is restored into sub directory backup-restore-<timestamp> instead of home directly.
|
Done by @tasket here: QubesOS/qubes-core-admin-client@30dd7ac |
andrewdavidwong commentedAug 27, 2016
•
edited
Edited 1 time
-
andrewdavidwong
edited Aug 27, 2016 (most recent)
Currently, when restoring a dom0 home backup, the existing contents of dom0's
/homeare moved to a subdirectory, then the contents of the backup are restored directly do dom0's/home.This makes it convenient to restore a same-machine backup, since all backed up settings are automatically applied, but it makes it inconvenient to restore a cross-machine backup for the same reason (all the backed up settings are automatically applied). For example, if I create a backup on my desktop computer, which has multiple monitors and no power-saving requirements, then restore that backup on my laptop, which has a single monitor and stringent power-saving requirements, the display and power settings of the desktop get automatically applied on the laptop, and I have to manually undo/move everything. (I can't simply exclude dom0's home from the restore, because it contains some files and scripts that I need.)
TL;DR: In general, it seems better to allow the user to have explicit control over which files and settings get applied rather than assuming that the user always wants the contents of the backup to take precedence over the user's existing files in dom0's
/home.(If the concern is that restoring for backups would become more inconvenient with this change, then one possibility is to provide the user with a choice. "Which set of files do you want us to move to into a subdirectory: the existing ones, or the ones in the backup?")