[email protected]: > Thank you, this worked fine(For future duckduckgoers, I did this on fedora > in the end, I now feel it makes more sense because the disk usage of the > template is not avoidable, by having extra templates its just weighing your > disk down). However I have one last parting question, once I reboot > sys-net, I lose my driver and have to install it again. I have a feeling > that I should install the driver in the template to keep persistence, is > this correct? What is the qubes way to do this? > I should have thought of that! Probably the easiest thing to do in your case is to create a new qube, choosing the Standalone copied from template and check the "provides network" box. This behaves as a regular VM, so you can make any changes you need and they will stay. Once you have it set up, uncheck auto-start on sys-net, add auto-start to your new qube, and set sys-firewall Qube Settings to use it. Also change anything pointing to sys-net in Qubes Global Settings. Qubes Update will see it in the list for updates.
-- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/89c3040d-5aad-7018-5318-c53edd1845bf%40danwin1210.me.
