Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image
On Sun, Apr 11, 2021 at 10:45:27PM +0200, Ben Hutchings wrote:
> Control: reassign -1 initramfs-tools
> Control: tag -1 - wontfix
> Control: forcemerge 789067 -1
>
> On Sat, 2021-04-10 at 15:36 -0700, Josh Triplett wrote:
> > On Sat, Apr 10, 2021 at 11:23:53PM +0200, Bastian Blank wrote:
> > > On Sat, Apr 10, 2021 at 02:11:06PM -0700, Josh Triplett wrote:
> > > > For cloud instances and VMs, it's helpful to be able to use ip=dhcp as a
> > > > minimal network configuration. Enabling this option will do nothing
> > > > unless the kernel command line includes ip=dhcp.
> > >
> > > We don't support initramfs-less boot.
> >
> > Whether you have an initramfs or not is orthogonal to DHCP
> > configuration. The kernel's built-in DHCP configuration works even if
> > you're not using a network filesystem as the root filesystem.
>
> The initramfs is supposed to take responsibility for handling all of
> the legacy boot parameters. Moving this to initramfs-tools and merging
> it with the existing bug there.
That wouldn't actually solve the issue as reported. I was hoping
specifically for the in-kernel support.
I'd like to use this on a cloud instance that uses ext4 on NVMe, and
thus doesn't currently need an initramfs.
Reply to: