[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Updating kernels impossible when /boot is getting full



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


Reply to: