I briefly looked into how to do a backup of the whole system, in case running thru a 3rd installation resulted in the encryption passphrase being messed up upon first login after finishing the install. I decided against it, not yet being familiar with how to do it properly. It will take some getting used to the compartmentalization. I'm very familiar with VMs, however Qubes is a layer above that and requires understanding the role each VM plays in securing the system.
So I simply reinstalled a 3rd time, doing everything the same as the 2nd time except I left the checkbox for encryption checked. I also had the network cable plugged in this time, but didn't explicitly configure networking. However I did see a few log entries that leads me to believe the network drivers were activated, tho other log entries seemed to indicate no network service was started. I see the installer uses tmux which I am familiar with. Between the vitual consoles and tmux windows I popped around during the installation and looked at mounted devices, watched the anaconda log etc. After installation was complete I created the user account and completed the install, then rebooted. This time when the system started and asked for the disk passphrase it accepted it and I then completed the post installation configuration. Now it trully is a matter of coming up to speed on how to do things "the Qubes way", such as backups and updating the kernel. There were no issues with the passphrase on this 3rd install attempt, and now I have a fully secure and encrypted system. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0a33a19a-35a3-435b-87d4-69e178c63a8d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
