Hello
I wanted to try aarch64 image, but I had a small issue.
When I used arm-installer, it triggered an error and did not complete, I discovered that vg name is fedora, but this is also the same name for my laptop...
Perhaps adding aarch64 on the name could reduce the risk of conflicts "fedora_aarch64", it could also be a release number such as F28 "fedora_F28" or both "fedora_F28_aarch64" :)
By the way, probably a stupid question, what are the differences between armhfp and aarch64 builds ?
Fox
I wanted to try aarch64 image, but I had a small issue.
When I used arm-installer, it triggered an error and did not complete, I discovered that vg name is fedora, but this is also the same name for my laptop...
Perhaps adding aarch64 on the name could reduce the risk of conflicts "fedora_aarch64", it could also be a release number such as F28 "fedora_F28" or both "fedora_F28_aarch64" :)
We use the same setup across all architectures, also by putting a version in there it's obsolete as soon as someone upgrades to a newer versions as opposed to clean install every release.
By the way, probably a stupid question, what are the differences between armhfp and aarch64 builds ?
armhfp is 32 bit ARMv7 with hard floating point, aarch64 is 64 bit.
Ok it makes sense :)
So I'll have to rename my local vg from "fedora" to something else. I just fear that my laptop won't boot again after that ...
Thanks