After it completed, I updated it and began reinstalling my apps. Then I realized during reboots, I wasn’t asked for the disk encryption key. I went to disks and the option for changing the password is greyed out. Is there a way to enable disk encryption now? Or do I have to reflash again?
If i have to reflash again, what did I miss the first time around?
One note, when I got to the point during the reflash, when I installed the battery, the light went solid yellow not red. The script continued running so I figured it wasn’t a problem.
Yes. One represents the encrypted partition, the other is the logical volume that represents the decrypted encrypted partition. Its just a way to show what sort of partition (filesystem, etc) the encrypted partition is when its decrypted.
You can clone fork the repo, create your own branch, edit the page and send a merge request to the original repo.
I’ve got the feeling that I should remember a reason why the documentation isn’t updated, yet. I believe that there is missing the part that would re-encrypt the luks partition of the downloaded image to not use the ecryption key of the downloaded image in production (that would make the target phone decryptable to any person with access to the downloaded image - no matter how much one would change the passphrase protecting the encryption key).
But it is just a uncertain feeling that this really is the reason. We’d have to look over the installation process to make sure what the status is.
Sorry, I mixed up terminology: I wrote ‘clone’, but meant ‘fork’. You need to fork the repository, then use your own fork to do the changes and then you can commit a merge request.
Once you’ll have your own fork updated (preferably in a dedicated branch for this patch) you can start the merge request easily through the web interface of source.puri.sm .
guru@c720-r368166:~ $ git fork git@source.puri.sm:Librem5/developer.puri.sm.git
git: 'fork' is not a git command. See 'git --help'.
The most similar command is
fsck
guru@c720-r368166:~ $ git --help | grep -i fork
guru@c720-r368166:~ $ git --help | grep -i branch
branch List, create, or delete branches
switch Switch branches
pull Fetch from and integrate with another repository or a local branch
guru@c720-r368166:~ $
perhaps you mean pull?
Is there a tutorial or even rules to use git within Purism?