Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

system-reinstall-bootc clobbers /boot/dtb on aarch64

未关闭
#2,568 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
linux, rust

调研方向

Start with the system-reinstall-bootc command and the bootc-destructive-cleanup.service it triggers, and find where they remove files under /boot. Reproduce on an aarch64 system or test setup that has /boot/dtb, then check whether the directory is deleted. Done means /boot/dtb survives reinstall on aarch64 without breaking the kernel removal step, which the maintainers still need to agree on.

由索引模型根据 Issue 内容生成。

描述

This came up over in https://gitlab.com/redhat/centos-stream/rpms/bootc/-/merge_requests/121

On aarch64 there's devicetree things located under /boot/dtb. When we do a system-reinstall-bootc, that gets wiped. At the very least it causes one of our tests to fail because bootc-destructive-cleanup.service fails when removing the kernel (xref https://gitlab.com/redhat/centos-stream/rpms/grubby/-/merge_requests/36), but in the more general sense I wanted to raise this here to track it.

At least on an aarch64 instance on the fedora testing farm ranch... it doesn't seem to cause any real issues. The system reboots fine and seems functional without /boot/dtb at all. But I'm concerned that we're probably being too heavy-handed here and some subset of systems is going to break because of this.

主要语言
Rust
星标
2.3k
派生
230
平均合并
2 天 20 小时
30 天内合并 PR
52

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

bootc-dev/bootc 的其他 Issue

查看 bootc-dev/bootc 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。