On Thu, Jan 25, 2024 at 09:48:28AM +0100, Ahmad Fatoum wrote:
> Hello Michael,
> 
> On 22.01.24 16:57, Michael Olbrich wrote:
> > On Mon, Jan 22, 2024 at 04:01:36PM +0100, Ahmad Fatoum wrote:
> >> On 17.01.24 14:56, Michael Olbrich wrote:
> >>> -CONFIG_BLK_DEV_INITRD=y
> >>> -CONFIG_INITRAMFS_SOURCE=""
> >>> -# CONFIG_RD_GZIP is not set
> >>> -# CONFIG_RD_BZIP2 is not set
> >>> -# CONFIG_RD_LZMA is not set
> >>> -# CONFIG_RD_XZ is not set
> >>> -# CONFIG_RD_LZO is not set
> >>> -# CONFIG_RD_LZ4 is not set
> >>> -CONFIG_RD_ZSTD=y
> >>> +# CONFIG_BLK_DEV_INITRD is not set
> >>
> >> We want to keep CONFIG_BLK_DEV_INITRD, so DistroKit systems can easily
> >> boot common distros like Debian that ship with an initramfs.
> > 
> > I was not aware that this is a use-case for DistroKit. I'm not sure how
> > that is supposed to work but fine.
> 
> It was suggested by Jan IIRC. Maybe he can chime in.

Being able to boot a Debian system is something I like to do. Most of
the time I do that with a Debian kernel (so it's more important that
barebox has support for initrd), but still I think it valuable to be
able to boot into a Debian rootfs to quickly test things.

Even though it doesn't happen often (for me), it's still nice enough to
keep it enabled.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |