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 example, to make an AppVM which only preserves bookmarks in /dev/xvdb > that normally keeps /rw /home and /usr files, where everything else is swept > away upon restarting the AppVM. There are other use-cases than for bookmarks, > whatever project one may have in mind. > > For those who may need the reference, the Qubes partition read-only and > write-access scheme is explained here > https://www.qubes-os.org/doc/template-implementation/ Essentially the > /dev/xvda is like the template, and /dev/xvdb is like the AppVM. > > It may possibly be a bit difficult to split up the path to the firefox files, > away from the remaining /home files, and further splitting up the firefox > files to only preserve the bookmarks and not the remaining firefox files. > This presumably complicates everything, however similar approaches can be > seen with /dev/xvdc which holds any modified read-only /dev/xvda files, which > are then discarded upon shutting down the AppVM. The other example is how the > Whonix AppVM is handled, which only preserves a few things, like bookmarks, > and erases everything else. However the Whonix approach while similar, is > fundamentally different too, since this process is being handled inside the > VM, and not outside the VM. > > So the question is, can the borderline between which Linux paths are saved in > the read-only partition /dev/xvda and the write-access to /dev/xvdb, be > changed in any specific pre-installed template? And further, can everything > be moved back to /dev/xvda, without removing firefox folder from the > /dev/xvdb, or better yet, only allowing edits to the bookmarks directory only > while keeping the remaining firefox folder in /dev/xvda? > > Whould splitting of files here require using a similar approach like the one > used with /dev/xvda and /dev/xvdc for system-files? Can this be done with > current means in Qubes? > > Ideas or suggestions on if this is feasible or maybe even undesirable for any > unseen reason?
Could you have a process to backup your bookmarks in /home/user (i.e. every 10 min) And have a process on start-up to load them up? If you are OK to create the bookmarks elsewhere you could create them in a "bookmark vault" and get them pushed on start-up (from Dom0, start bookmark vault, start browsing VM, initiate transfer of bookmarks from vault to browsign) -- 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/5d2f9f89-3bdd-4ae7-a966-7859c5d2a6ab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.