Skip to content
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

WIP: Ensure that /boot partition is not required #5340

Closed
wants to merge 1 commit into from

Conversation

KKoukiou
Copy link
Contributor

In the general case, if we have a single operating system, there's no need to create the /boot partition as long as our hardware is recent. New machines don't have the old restrictions that required the creation of the /boot partition.

This new attribute will be used in the front-end to guide the users who are doing manual mount point assignment.

Relevant to: rhbz#2234640

In the general case, if we have a single operating system, there's no
need to create the /boot partition as long as our hardware is recent.
New machines don't have the old restrictions that required the creation of the /boot partition.

This new attribute will be used in the front-end to guide the users who
are doing manual mount point assignment.

Relevant to: rhbz#2234640
@KKoukiou
Copy link
Contributor Author

KKoukiou commented Nov 23, 2023

@vojtechtrefny I am trying to approach the request on making /boot recommened - not required when not needed. I will need some guidance on this, I am not much familiar with this and also I am not sure how to find which platforms actually require the /boot seperate.

I just found the method; def _execute_reqpart(self, storage, data): in the custom partitioning, which does the logic I am trying to reinvent. I guess I need someone with better knowledge of the backend than me here.

@vojtechtrefny
Copy link
Contributor

also I am not sure how to find which platforms actually require the /boot seperate.

Requirement for the separate /boot is not based on platform, but on storage on which / is located. Separate /boot is needed if / is on a device which is encrypted or on LVM*. There are also limits for MD RAID levels and metadata versions and some special cases for network storage (separate /boot on a local disk is needed for non-iBFT iSCSI).

*) These limits are partially self-imposed, GRUB2 does support booting from an encrypted device or LVM volume, but there are some problems with that and we don't want to support it.

@KKoukiou KKoukiou closed this Nov 30, 2023
@KKoukiou KKoukiou deleted the bz-2234640 branch November 30, 2023 10:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants