Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #228994

Re: Size of initrd

From <tomas@tuxteam.de>
Newsgroups linux.debian.user
Subject Re: Size of initrd
Date 2020-11-24 10:20 +0100
Message-ID <BeCEp-V8-1@gated-at.bofh.it> (permalink)
References <BdHd7-7WI-5@gated-at.bofh.it> <BdIiR-nY-1@gated-at.bofh.it> <BebXz-1uF-1@gated-at.bofh.it> <BecqB-1TO-1@gated-at.bofh.it> <BetB7-3KM-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Mon, Nov 23, 2020 at 06:30:46PM -0500, Stefan Monnier wrote:
> > Use unmkinitramfs. It appears you've only looked at the first archive,
> > the early one, which gets the kernel into shape. The second, main one
> > is the big one.
> 
> OK, for those interested I tracked it down: indeed the machine with the
> larger initrd had MODULES=most instead of MODULES=dep.

My unqualified guess was modules, since that's the really fat part
of that cake.

> It took me some effort to figure out that it was actually
> LZMA-compressed as I had specified (the first CPIO archive, containing
> the intel microcode blob isn't, but the second is) [...]

I feel somewhat guilty, because my "solution" implied (as I thought at
the time) that initramfs is /just/ one cpio archive. I've been corrected
in the meantime.

Sorry for that. I know it's a sleazy way of learning -- spewing out some
nonsense, being corrected and caching that for the next time.

Your extra time was the collateral damage. I owe you a beer -- post-Covid.

Cheers
 - t

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Size of initrd Stefan Monnier <monnier@iro.umontreal.ca> - 2020-11-21 21:00 +0100
  Re: Size of initrd <tomas@tuxteam.de> - 2020-11-21 22:10 +0100
    Re: Size of initrd Stefan Monnier <monnier@iro.umontreal.ca> - 2020-11-23 05:50 +0100
      Re: Size of initrd David Wright <deblis@lionunicorn.co.uk> - 2020-11-23 06:20 +0100
        Re: Size of initrd Stefan Monnier <monnier@iro.umontreal.ca> - 2020-11-24 00:40 +0100
          Re: Size of initrd <tomas@tuxteam.de> - 2020-11-24 10:20 +0100
            Re: Size of initrd Greg Wooledge <wooledg@eeg.ccf.org> - 2020-11-24 14:00 +0100
              Re: Size of initrd Curt <curty@free.fr> - 2020-11-24 15:40 +0100
            Re: Size of initrd Stefan Monnier <monnier@iro.umontreal.ca> - 2020-11-24 16:00 +0100
      Re: initrd inspection (was: Size of initrd) Felix Miata <mrmazda@earthlink.net> - 2020-11-23 07:40 +0100
        Re: initrd inspection (was: Size of initrd) <tomas@tuxteam.de> - 2020-11-23 09:50 +0100
          Re: initrd inspection Sven Hartge <sven@svenhartge.de> - 2020-11-23 12:30 +0100
            Re: initrd inspection <tomas@tuxteam.de> - 2020-11-23 13:00 +0100
              Re: initrd inspection Stefan Monnier <monnier@iro.umontreal.ca> - 2020-11-24 00:40 +0100
    Re: Size of initrd Curt <curty@free.fr> - 2020-11-23 14:00 +0100
      Re: Size of initrd Curt <curty@free.fr> - 2020-11-23 14:30 +0100
      Re: initrd inspection (was: Size of initrd) Felix Miata <mrmazda@earthlink.net> - 2020-11-23 18:30 +0100
    Re: Size of initrd Greg Wooledge <wooledg@eeg.ccf.org> - 2020-11-23 14:20 +0100
      Re: Size of initrd <tomas@tuxteam.de> - 2020-11-23 16:20 +0100
  Re: Size of initrd David Wright <deblis@lionunicorn.co.uk> - 2020-11-21 22:40 +0100
  Re: Size of initrd Andy Smith <andy@strugglers.net> - 2020-11-21 22:50 +0100
    Re: Size of initrd David Wright <deblis@lionunicorn.co.uk> - 2020-11-22 00:10 +0100

csiph-web