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

config/network/firewall.md: needs some rework/clarifications.

未关闭
#512 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
48/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
停滞
领域
documentation

调研方向

打开 config/network/firewall.md,比较当前标题为“Applying rules at boot”和“Applying rules at runtime”的章节。明确说明这些是在启动时和运行时加载规则的替代方式,解释为什么优先使用 core-services/rc.local,并记录使用 sv 或 nftables/iptables 命令重新加载的方法;更新后的章节标题和说明应消除歧义。

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

描述

bug enhancement help wanted

We currently have here two sections "Applying rules at boot" and "Applying rules at runtime" both are ambiguous.
Both of them work at boot and at runtime, they are two alternative methods, with the one "Applying rules at boot" being clearly the better solution because they don't need a fake service and they make sure firewall rules are loaded before network services are up.

  • Change the headlines for "Applying rules at X".
  • Make clear that they are two ways of loading rules at boot and at runtime, make clear that core-services/rc.local is superior.
  • Document how to reload rules with the fake service, sv can be used and with the better core-services or rc.local method the nftables (or iptables) command can be used.
主要语言
CSS
星标
217
派生
212
平均合并
2 天 21 小时
30 天内合并 PR
1

贡献指南

打开贡献指南

从这里开始

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

void-linux/void-docs 的其他 Issue

查看 void-linux/void-docs 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

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