[Bug 2098659] [NEW] Please support hostonly mode with full portability

Benjamin Drung 2098659 at bugs.launchpad.net
Mon Feb 17 11:30:22 UTC 2025


Public bug reported:

In Ubuntu, initramfs-tools builds portable initrds by default. We want
that user can replace hardware (e.g. the graphics card, keyboard) and
still be able to boot. Taking a disk from one machine, plug it into a
different machine, and boot should work out of the box.

We currently use `--hostonly --hostonly-mode=sloppy` (see bug #2084809).

Upstream bug: https://github.com/dracut-ng/dracut-ng/issues/748

Proposed solution:

* Rename `hostonly_cmdline` to `include_cmdline`. Deprecate the former name.
* Introduce `mode="{generic|hostonly|strict}"` where generic matches `hostonly=no`, hostonly matches `hostonly=yes hostonly_mode=sloppy`, strict matches `hostonly=yes hostonly_mode=strict`
* Add `include_system_configs={yes|no}` to decouple this behavior the mode.

** Affects: dracut
     Importance: Unknown
         Status: Unknown

** Affects: dracut (Ubuntu)
     Importance: Medium
         Status: Triaged

** Bug watch added: github.com/dracut-ng/dracut-ng/issues #748
   https://github.com/dracut-ng/dracut-ng/issues/748

** Also affects: dracut via
   https://github.com/dracut-ng/dracut-ng/issues/748
   Importance: Unknown
       Status: Unknown

** Changed in: dracut (Ubuntu)
       Status: New => Triaged

** Changed in: dracut (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dracut in Ubuntu.
Matching subscriptions: dracut
https://bugs.launchpad.net/bugs/2098659

Title:
  Please support hostonly mode with full portability

Status in Dracut:
  Unknown
Status in dracut package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu, initramfs-tools builds portable initrds by default. We want
  that user can replace hardware (e.g. the graphics card, keyboard) and
  still be able to boot. Taking a disk from one machine, plug it into a
  different machine, and boot should work out of the box.

  We currently use `--hostonly --hostonly-mode=sloppy` (see bug
  #2084809).

  Upstream bug: https://github.com/dracut-ng/dracut-ng/issues/748

  Proposed solution:

  * Rename `hostonly_cmdline` to `include_cmdline`. Deprecate the former name.
  * Introduce `mode="{generic|hostonly|strict}"` where generic matches `hostonly=no`, hostonly matches `hostonly=yes hostonly_mode=sloppy`, strict matches `hostonly=yes hostonly_mode=strict`
  * Add `include_system_configs={yes|no}` to decouple this behavior the mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dracut/+bug/2098659/+subscriptions




More information about the foundations-bugs mailing list