Anton Hvornum

I don't dare to touch this one until we get the last few glitches patched and sorted out. As I know this will cause some major disruptions in the code...

This is one of our goals, to support https://github.com/archlinux/archinstall/issues/1072. However, it would require quite of a lot of testing so it doesn't break setups some where. And if that is...

Currently archinstall is pretty dumb when it comes to "detecting" `/boot` or in your case `/efi`. All archinstall does currently is to make sure a partition is mounted at `/mnt/archinstall`...

I'm holding off on this one until I figure out why it doesn't work. It implements the manual steps taken to get the issue fixed - but for some reason...

This is technically already supported. If you create a separate home partition under ext4, and only select that one to be encrypted, i think you're good to go. Not tested...

`pacman -Sy archlinux-keyring` and then `pacman -S git python-pip`. This happens every now and then sadly. easiest way is what dyland said :)

Nicely spotted!

@wc7086 let me run a test just to verify, if that's the case I'll re-open and submit a quick PR.

Thank you @wc7086 for poking me. There's some weird issue with the forked process returning `\r\n`. And adding `newline="\n"` doesn't solve the issue. I'll get a PR going tomorrow. 

USB drives as the install medium is still a bit in it's early days for archinstall. But we'll make sure to fix this.