All Qubes OS Project documentation pages are stored as plain text files in this dedicated repository. By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the Web.
Go to file
rafaelreis-r b6afa9270c
Update custom-install.md
1 - Inform the user how to return to installation @ step 8;
2 - Clarify the need to choose a FS and format prior to assigning the mount points (option is greyed out until you do).  @ step 9
3 - Guide the user on navigating the quirky behaviour of Anaconda on that part - You have to first check the box, then choose FS, then enter mount point, from bottom to top, which is not really friendly. @ step 9

Future TODO: Include details for GPT / UEFI disks. Boot mount point and FS are different, as well as the disk initialization part with fdisk (step 2).
2019-11-07 11:54:11 -03:00
_dev _dev: add explanation 2018-04-18 21:16:59 +02:00
developer Merge branch 'qrexec-rewrite-phase-3-internals' of https://github.com/pierwill/qubes-doc into pierwill-qrexec-rewrite-phase-3-internals 2019-10-29 00:32:25 -05:00
external fix merge conflicts 2019-10-29 11:41:52 +01:00
introduction Remove link to retired unofficial forum 2019-10-23 21:34:49 -05:00
project-security Recommend using gpg2 with keyserver options instead of gpg 2019-10-23 01:05:50 -05:00
user Update custom-install.md 2019-11-07 11:54:11 -03:00
.travis.yml travis: update ruby version 2018-03-18 23:24:54 +01:00
CONTRIBUTING.md Fix link 2017-04-04 21:52:06 -07:00
doc.md Fix Incorrect index 2019-09-04 11:32:09 +00:00
README.md Fix typo 2016-03-22 22:52:54 +00:00

Qubes OS Documentation

Canonical URL: https://www.qubes-os.org/doc/

All Qubes OS Project documentation pages are stored as plain text files in this dedicated repository. By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the Web.

For more information about the documentation, including how to contribute, please see the Documentation Guidelines.