eb05d5b190
I think (but am not absolutely certain) that things behave as follows: - The non-zsys initramfs script expects canmount=noauto for the root filesystem. It then mounts the active one (e.g. in the case of clones) manually, overriding that. - zsys manages the canmount attribute. I am sure that when the system boots with zsys, the initial datasets, which were created with canmount=noauto, have canmount=on. Therefore, there seems to be no reason to set canmount=noauto for the zsys scenario, and I have removed it. This simplifies the instructions and may avoid issues like #73. Signed-off-by: Richard Laager <rlaager@wiktel.com> Fixes #73
.. image:: docs/_static/img/logo/480px-Open-ZFS-Secondary-Logo-Colour-halfsize.png .. highlight:: sh OpenZFS Documentation ===================== Public link: https://openzfs.github.io/openzfs-docs/ Building Locally ---------------- Install Prerequisites ~~~~~~~~~~~~~~~~~~~~~ The dependencies are available via pip:: # For Debian based distros sudo apt install python3-pip # For RPM-based distros sudo yum install python3-pip pip3 install -r docs/requirements.txt # Add ~/.local/bin to your $PATH, e.g. by adding this to ~/.bashrc: PATH=$HOME/.local/bin:$PATH Build ~~~~~ :: cd docs make html # HTML files will be generated in: _build/html