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


Groups > linux.debian.user > #238022

Re: listing initrd content

From The Wanderer <wanderer@fastmail.fm>
Newsgroups linux.debian.user
Subject Re: listing initrd content
Date 2021-08-02 14:10 +0200
Message-ID <CHEVA-3q2-13@gated-at.bofh.it> (permalink)
References (3 earlier) <CHs81-3nG-1@gated-at.bofh.it> <CHyGu-7TC-1@gated-at.bofh.it> <CHEiS-2WN-3@gated-at.bofh.it> <CHECf-34a-13@gated-at.bofh.it> <CHELU-37q-3@gated-at.bofh.it>
Organization This space intentionally left blank.

Show all headers | View raw


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

On 2021-08-02 at 07:51, Greg Wooledge wrote:

> On Mon, Aug 02, 2021 at 07:41:03AM -0400, The Wanderer wrote:
>
>> On 2021-08-02 at 07:25, Greg Wooledge wrote:
>> 
>> > unicorn:~$ lsinitrd /boot/initrd.img-5.10.0-8-amd64 | wc -l
>> > 1646
>> > unicorn:~$ lsinitramfs /boot/initrd.img-5.10.0-8-amd64 | wc -l
>> > 1635
>> > 
>> > Curious.
>> 
>> Try a diff between the lsinit* outputs? I don't have dracut-core
>> installed, or I'd run the test myself just out of curiosity.
> 
> I didn't have it either; I installed it specifically to test this thing.
> Unfortunately, installing it also brought in "cryptsetup" and related
> packages, which modified the initrd images.  Because of that, I don't
> recommend this test for anyone else.

dracut-core has cryptsetup in Recommends:, so that could be avoided with
--no-install-recommends. Maybe try removing dracut-core, 'apt-get
autoremove' / 'apt-get remove $(deborphan)' etc. till nothing new is
removed, then install dracut-core again without Recommends and see if
that improves things any?

That's a bigger and more drastic operation than it sounded like when I
started writing out the steps, though, so maybe not worth bothering with.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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


Thread

Updating kernels impossible when /boot is getting full Ilkka Huotari <ilkkah@gmail.com> - 2021-08-01 06:40 +0200
  Re: Updating kernels impossible when /boot is getting full Paul Duncan <paul.d@soi-team.org> - 2021-08-01 12:00 +0200
  Re: Updating kernels impossible when /boot is getting full Stefan Monnier <monnier@iro.umontreal.ca> - 2021-08-01 17:40 +0200
  Re: Updating kernels impossible when /boot is getting full David Christensen <dpchrist@holgerdanske.com> - 2021-08-01 21:50 +0200
    Re: Updating kernels impossible when /boot is getting full Greg Wooledge <greg@wooledge.org> - 2021-08-01 22:10 +0200
      Re: Updating kernels impossible when /boot is getting full Hans <hans.ullrich@loop.de> - 2021-08-01 22:30 +0200
      Re: Updating kernels impossible when /boot is getting full David Christensen <dpchrist@holgerdanske.com> - 2021-08-02 00:30 +0200
        Re: Updating kernels impossible when /boot is getting full Greg Wooledge <greg@wooledge.org> - 2021-08-02 01:00 +0200
          Re: Updating kernels impossible when /boot is getting full Darac Marjal <mailinglist@darac.org.uk> - 2021-08-02 17:20 +0200
          Re: Updating kernels impossible when /boot is getting full David Christensen <dpchrist@holgerdanske.com> - 2021-08-02 20:20 +0200
            Re: Updating kernels impossible when /boot is getting full Greg Wooledge <greg@wooledge.org> - 2021-08-02 20:40 +0200
              Re: Updating kernels impossible when /boot is getting full Greg Wooledge <greg@wooledge.org> - 2021-08-02 21:50 +0200
                Re: Updating kernels impossible when /boot is getting full David Christensen <dpchrist@holgerdanske.com> - 2021-08-02 23:30 +0200
              Re: Updating kernels impossible when /boot is getting full David Christensen <dpchrist@holgerdanske.com> - 2021-08-02 21:50 +0200
        Re: listing initrd content (was: Updating kernels impossible...) Felix Miata <mrmazda@earthlink.net> - 2021-08-02 07:30 +0200
          Re: listing initrd content (was: Updating kernels impossible...) Greg Wooledge <greg@wooledge.org> - 2021-08-02 13:30 +0200
            Re: listing initrd content The Wanderer <wanderer@fastmail.fm> - 2021-08-02 13:50 +0200
              Re: listing initrd content Greg Wooledge <greg@wooledge.org> - 2021-08-02 14:00 +0200
                Re: listing initrd content The Wanderer <wanderer@fastmail.fm> - 2021-08-02 14:10 +0200
                Re: listing initrd content David Wright <deblis@lionunicorn.co.uk> - 2021-08-02 17:50 +0200
                Re: listing initrd content Greg Wooledge <greg@wooledge.org> - 2021-08-02 18:00 +0200
                Re: listing initrd content David <bouncingcats@gmail.com> - 2021-08-02 18:10 +0200
                Re: listing initrd content David Wright <deblis@lionunicorn.co.uk> - 2021-08-02 21:00 +0200
                Re: listing initrd content David <bouncingcats@gmail.com> - 2021-08-03 12:00 +0200
      Re: Updating kernels impossible when /boot is getting full Teemu Likonen <tlikonen@iki.fi> - 2021-08-02 07:10 +0200
        Re: Updating kernels impossible when /boot is getting full David Wright <deblis@lionunicorn.co.uk> - 2021-08-02 18:00 +0200

csiph-web