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

Enforce /boot as separate partition on Silverblue #2848

Conversation

VladimirSlavik
Copy link
Contributor

@VladimirSlavik VladimirSlavik commented Sep 10, 2020

Resolves: rhbz#1862784

Many thanks to Vendy who told me what needs changing!

@VladimirSlavik VladimirSlavik added master Please, use the `f39` label instead. f33 labels Sep 10, 2020
Copy link
Contributor

@poncovka poncovka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thanks!

Copy link
Member

@jkonecny12 jkonecny12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me!

@poncovka poncovka added the blocked Don't merge this pull request! label Sep 11, 2020
@poncovka
Copy link
Contributor

It might be fixed in ostree.

@bam80
Copy link
Contributor

bam80 commented Sep 11, 2020

I'm not happy with enforcing /boot as mount point. It's a serious drawback. So +1 for ostree solution or whatever..

@VladimirSlavik
Copy link
Contributor Author

Jenkins, test this please.

@VladimirSlavik
Copy link
Contributor Author

@cgwalters is this actually needed? @cmurf pointed in the BZ to ostreedev/ostree#2149 as possible fix...

@cgwalters
Copy link
Contributor

Yes, it shouldn't be required anymore but it isn't heavily tested either yet.

@VladimirSlavik
Copy link
Contributor Author

Thanks! I read that as: Ostree handles /boot on / now, and this PR is not needed anymore. Is that correct for rawhide, f33, both, or neither?

@VladimirSlavik VladimirSlavik deleted the f33-silverblue-enforce-separate-boot branch October 18, 2022 10:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Don't merge this pull request! f33 master Please, use the `f39` label instead.
Development

Successfully merging this pull request may close these issues.

5 participants