About Qubes Doc & persistance in appvm

Hi world!

I’ve noticed some mistakes (in my opinion) in the Qubes Documentation related to bind-dirs configuration ( How to make any file persistent (bind-dirs) — Qubes OS Documentation ). Here is my suggestion:

In the Appvm you want to persiste configuration files/folders (between reboots):

  1. Prepare destination:
    sudo mkdir -p /rw/bind-dirs
    sudo mkdir -p /rw/config/qubes-bind-dirs.d

  2. Add what has to be persisted to your will (e.g. bluetooth configurations):

sudo <your_fav_editor> /rw/config/qubes-bind-dirs.d/50_bluetooth.conf
    binds+=( '/var/lib/bluetooth' )
    binds+=( '/usr/lib/bluetooth' )
    binds+=( '/etc/bluetooth' )
  1. Then activate persistance:
    sudo /usr/lib/qubes/init/bind-dirs.sh

That’s all folks!

EDIT: proper documentation is here: How to make any file persistent (bind-dirs) — Qubes OS Documentation

What did you improve? :face_with_monocle:

Not to create dirs in /rw/bind_dirs… or else you’ll loose your config files, plus nothing about init
Steps 5 to 8.

In the docs it is stated that /rw/bind-dirs is created automatically - which is true.

The bind-dirs.sh is mentioned 11 times. The manual execution as well as the implicit execution by the methods of a restart is also mentioned.

Did you make your own modifications without completing step 1-8 and therefore made non persistent changes?

Thanks for the feedback. Note that the link you provided is not an official one. You might be able copy your changes in /rw/bind-dirs? Take a look at the “Limitations” section.

@balder86, @parulin,
You both are right: I’m not referring to the proper documentation… Anyway, I’m using successfully what I provide (it works fine this way, modulo “limitations”).
Thanks.