Any issues with changing template for sys-usb?

47 views
Skip to first unread message

Stumpy

unread,
Jun 8, 2019, 9:19:00 AM6/8/19
to Qubes users
I have a sys-usb that is currently based on fedora but i need to run a
package on debian.
Should it be a problem if i install the package on debian, temporarily
switch the template to debian, use the app when i need, then switch back?

awokd

unread,
Jun 8, 2019, 12:38:42 PM6/8/19
to qubes...@googlegroups.com
Stumpy wrote on 6/8/19 1:18 PM:
Shouldn't be a problem, but you could also just leave it on Debian.

Stumpy

unread,
Jun 9, 2019, 1:42:29 PM6/9/19
to awokd, qubes...@googlegroups.com
Thanks, will give it a try then

Jon deps

unread,
Jun 16, 2019, 1:48:21 PM6/16/19
to qubes...@googlegroups.com
just messes up your app shortcuts, then one has to fix them if one
uses them ; course you can just use qvm-run

what is the application?

jules....@gmail.com

unread,
Jun 16, 2019, 1:54:10 PM6/16/19
to qubes-users
I wanted to do the same to move the template sys-usb was based on, but you need to stop sys-usb to do it which in the case of a Deskop computer make you without keyboard and mousse ...

awokd

unread,
Jun 16, 2019, 2:16:59 PM6/16/19
to qubes...@googlegroups.com
jules....@gmail.com:
You could temporarily remove rd.qubes.hide_all_usb from your xen.cfg.
This exposes dom0 to your USB controllers, so unplug everything except
keyboard & mouse. Reboot, and verify you have keyboard after shutting
down sys-usb. Make the changes you need and verify sys-usb starts
normally. Add rd.qubes.hide_all_usb back to xen.cfg.

I believe the above is relatively low risk, anyone have a better
approach? You could also script the template change, but I wouldn't be
confident enough to attempt it...

unman

unread,
Jun 16, 2019, 7:49:29 PM6/16/19
to qubes...@googlegroups.com
How about?

#!/bin/bash
qvm-shutdown sys-usb
qvm-prefs sys-usb template debian-9
qvm-start sys-usb
sleep 3m
qvm-shutdown sys-usb
qvm-prefs sys-usb template fedora-30
qvm-start sys-usb

Just long enough to check all works fine and then switches back.
If all's fine, delete the last 4 lines.

If worried about races, pepper in a few more sleeps.

scurge1tl

unread,
Jun 17, 2019, 1:34:15 AM6/17/19
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512



unman:
Nice one. Where should I normally put the #!/bin/bash scripts in dom0?
Is it ok to use /usr/bin or is it better to leave it for
package-managed executables and have an another /bin?
Thank you.

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEExlmPb5HoPUTt+CQT44JZDAWK6UwFAl0HJkFfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM2
NTk4RjZGOTFFODNENDRFREY4MjQxM0UzODI1OTBDMDU4QUU5NEMACgkQ44JZDAWK
6Uz5TBAAsgsmgiB1LtVqdIsTdwO4SPwrieAhl6jqECOZSZl8Q4+bUc5lZJvzF313
PwqND0izsXFGE5ewiAWK2pc7MVHlsh0sn85wQS/ivSTrvymaTQcT/lY3SONEkQn+
0uZfrxSf6aQpVHRSbZI/kNcld2hg3u/0nUjzdx9fmjLgclWyaL9CBmQr+80p6BI2
ob8zNn23P5Uj+AvsN/VPVK9ZclDwSZy+qzy7NTPD4SBskwO4pFmYTrMmuYmpvTM3
COwqeju8onuXFCCOUujXkwXWF+eC67/zgfnwJnKWFvAe8FIpADDbBQmWrCKLYXGX
JAuTWYOgVLRzJM7inv4qdp8mYkeIBtQhFq+9t1bA9uKTwC0rhRsyL6jEoN1K4MQo
lA511PCQSjFFYRrjvdTU4RAQo8aEuBKCEMtmUZusPMmwQwbpvM4Uzwh2h6vxcdd6
X4xZ96tQ7T/lQZbOuf47xIa8aBRWE65/lFtfHxZRZkOgz3A0Y7aI40zpjZyOaigc
ZAkUOJ5I9CB7Ptf5WyiSXxy6laP+dPejgw1SI6KH3nj52Eg9SckRQ9TxgKGzbkFc
bCZIRQZucNtX3M0jmIv8DLnfo5TcWHUNePPyybNU/xy9pQNlBTBr8WIiXfleHWBT
yJ/c6p+xlL57ZK18boIOHzQW020uaxEca/5BV8YXCWkgVvkM2Fo=
=PSXa
-----END PGP SIGNATURE-----
0xC1F4E83AF470A4ED.asc

awokd

unread,
Jun 17, 2019, 8:28:08 AM6/17/19
to qubes...@googlegroups.com
scurge1tl:

> Nice one. Where should I normally put the #!/bin/bash scripts in dom0?
> Is it ok to use /usr/bin or is it better to leave it for
> package-managed executables and have an another /bin?
> Thank you.

I put dom0 user scripts in ~. The #!/bin/bash at the top is a directive
for what shell the script should use when it executes.
Reply all
Reply to author
Forward
0 new messages