-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
changes to partition structure from #305 #331
Comments
cc @ajeddeloh since you have been looking at combined bios/uefi images since that might have some implications on our final partition layout. |
Please find the filesystem with |
yeah I switched to that last night, need to add some extra logic in there just in case there is another disk attached to the system with a FS with that label, but it should work. |
Please label both the partitions and filesystems so they can be accessed as I don't know if we every consensus on the
|
I don't think anaconda sets partlabels. I only see the
|
This issue was mostly an FYI in case anyone noticed anything alarming that needed to be addressed. I'll close it out since there isn't really any work to be done and we can follow up on the partition structure in #334 |
In #305 we switched to using
reqpart --add-boot
in our kickstart files.This notably gives us an extra partition that we didn't have before and also gives us an ext4 formatted /boot partition. Before people start hardcoding in these assumptions (i.e. some early installer work POC assumes 1st partition is boot partition) we should strive to get closer to what we have laid out in the design document: https://github.com/coreos/fedora-coreos-tracker/blob/master/Design.md#summary-1
The text was updated successfully, but these errors were encountered: