Just a heads-up for anyone else reading this thread who may want to try this
too and is not aware of this pitfall, a warning before trying. Any mistakes
done in the scripts can make the template unable to start applications. For
example even if it can boot-up, applications may not start.
So
On Wednesday, January 24, 2018 at 8:32:24 PM UTC+1, Chris Laprise wrote:
> On 01/24/2018 10:55 AM, Yuraeitha wrote:
>
> >
> > All 3 suggestions are you guys brought up are really intriguig, I'm pretty
> > excited about this, these ideas are excellent, even better than I hoped for.
> >
> > I'm
On 01/24/2018 10:55 AM, Yuraeitha wrote:
All 3 suggestions are you guys brought up are really intriguig, I'm pretty
excited about this, these ideas are excellent, even better than I hoped for.
I'm using Qubes 4, so I assume I can't give the beta setup a try until or if it
becomes available
On Tuesday, January 23, 2018 at 4:21:56 PM UTC+1, Alex Dubois wrote:
> On Monday, 22 January 2018 21:36:46 UTC, Yuraeitha wrote:
> > The purpose is to narrow down access to an AppVM based on /dev/xvdb,
> > keeping more of the AppVM in the read-only /dev/xvda template partition.
> >
> > For
On 01/22/2018 04:36 PM, Yuraeitha wrote:
The purpose is to narrow down access to an AppVM based on /dev/xvdb, keeping
more of the AppVM in the read-only /dev/xvda template partition.
For example, to make an AppVM which only preserves bookmarks in /dev/xvdb that
normally keeps /rw /home and
