On 04/19/2018 10:00 AM, awokd wrote:
On Thu, April 19, 2018 5:45 am, Jan Hustak wrote:
I guess there's a cognitive aspect to it as well, not related to
security as such. I have over 2300 packages installed on my main Debian
notebook, many of them not needed anymore. Cleaning them out is a tedious
job I never get to. If I had a VM/filesystem with "only packages needed
for Project X", things would be more orderly. I don't need Qubes OS for
that, of course, but it's an issue I seek to address in addition to
security. Sorry if I'm straying off topic.
It's not off topic. I've said before I'd keep using Qubes even if it
provided no additional security over any other Linux distributions (but it
does a lot) merely for the convenience/flexibility it provides! In your
case then, you might want a workflow something like:
1- Clone one of the stock templates to create a base template with common
packages
2- Clone as needed for project X, install specific packages
3- Make Project X AppVM based on the new template
4- Delete project specific VMs when done
If you can figure out a union of common packages (hopefully less than
2300!) then you could skip step #2 some of the time and base #3 on #1.
Yes, this is exactly what I'm thinking about. It does mean having 2 VMs
per project but that's a trivial cost.
jh
--
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/2ccd2211-8046-2113-f117-d8fd927f59e4%40journey.sk.
For more options, visit https://groups.google.com/d/optout.
