Distributor Notes 分销商说明
Dracut Module Dracut 模块
The distribution specific integration is responsible for ensuring that the ignition dracut module is included in the initramfs when necessary. This can be achieved by adding it as dependency of the dracut module containing the distribution integration, or by installing a dracut configuration file.
分发特定的集成负责确保在需要时将点火 dracut 模块包含在 initramfs 中。这可以通过将其添加为包含分发集成的 dracut 模块的依赖项来实现，或者通过安装一个 dracut 配置文件。
Kernel Arguments 内核参数
When Ignition is updating kernel arguments it will call out to a binary (defined in internal/distro/distro.go and overridable at build-time via overriding the github.com/coreos/ignition/v2/internal/distro.kargsCmd build flag). Ignition expects that the binary accepts --should-exist & --should-not-exist parameters. Should exist operations should append the argument if missing and should not exist should NOT fail if the argument is not present. The binary should also reboot the system if necessary.
当 Ignition 更新内核参数时，它将调用一个二进制文件（在 internal/distro/distro.go 中定义，并可以通过覆盖 github.com/coreos/ignition/v2/internal/distro.kargsCmd 构建标志来在构建时进行覆盖）。Ignition 期望该二进制文件接受 --should-exist 和 --should-not-exist 参数。如果存在操作应该在参数丢失时追加参数，如果不存在则不应在参数不存在时失败。该二进制文件还应在必要时重新启动系统。
As an example of the binary implementation look at examples/ignition-kargs-helper.
作为二进制实现示例，请查看 examples/ignition-kargs-helper 。
If your implementation of Ignition doesn’t intend to ship kargs functionality the ignition-kargs.service unit should be disabled.
如果您的 Ignition 实现不打算提供 kargs 功能，则应禁用 ignition-kargs.service 单元。