Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #238063
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Updating kernels impossible when /boot is getting full |
| Date | 2021-08-02 23:30 +0200 |
| Message-ID | <CHNFv-fm-1@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <CHsB3-3Bu-3@gated-at.bofh.it> <CHKHD-6VA-1@gated-at.bofh.it> <CHL10-733-1@gated-at.bofh.it> <CHM6J-7Ez-9@gated-at.bofh.it> <CHM6J-7Ez-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 8/2/21 12:47 PM, Greg Wooledge wrote: > On Mon, Aug 02, 2021 at 12:43:27PM -0700, David Christensen wrote: >> I'd rather not install dracut. > > Me too. So why not use lsinitramfs -l ? Why keep reinventing the wheel? > > unicorn:~$ lsinitramfs -l /boot/initrd.img-5.10.0-8-amd64 | head -12 > drwxr-xr-x 2 root root 0 Apr 25 08:00 kernel > drwxr-xr-x 2 root root 0 Apr 25 08:00 kernel/x86 > drwxr-xr-x 2 root root 0 Apr 25 08:00 kernel/x86/microcode > drwxr-xr-x 2 root root 0 Apr 25 08:00 kernel/x86/microcode/.enuineIntel.align.0123456789abc > -rw-r--r-- 1 root root 4609024 Apr 25 08:00 kernel/x86/microcode/GenuineIntel.bin > drwxr-xr-x 7 root root 0 Aug 2 14:37 . > lrwxrwxrwx 1 root root 7 Aug 2 14:37 bin -> usr/bin > drwxr-xr-x 3 root root 0 Aug 2 14:37 conf > -rw-r--r-- 1 root root 16 Aug 2 14:37 conf/arch.conf > drwxr-xr-x 2 root root 0 Aug 2 14:37 conf/conf.d > -rw-r--r-- 1 root root 49 Jan 11 2018 conf/conf.d/resume > -rw-r--r-- 1 root root 1365 Sep 13 2020 conf/initramfs.conf > > No dracut needed. Did you not make a post that lsinitrd.sh and lsinitramfs produced different output? https://lists.debian.org/debian-user/2021/08/msg00057.html They seem to produce the same output on my machine. So, yes, lsinitramfs(8) is preferable: $ lsinitramfs -l /boot/initrd.img-4.19.0-17-amd64 | sort -k 9 > initrd.img-4.19.0-17-amd64.lsinitramfs $ diff -s initrd.img-4.19.0-17-amd64.txt initrd.img-4.19.0-17-amd64.lsinitramfs Files initrd.img-4.19.0-17-amd64.txt and initrd.img-4.19.0-17-amd64.lsinitramfs are identical David
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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