Re: listing initrd content

2021-08-03 Thread David
On Tue, 3 Aug 2021 at 02:03, David wrote: > On Tue, 3 Aug 2021 at 01:45, David Wright wrote: > As the warning says, it and /usr/bin/cryptroot-unlock will go away > if you uninstall 'cryptsetup-initramfs', which is pulled in by 'cryptsetup', > which describes itself as a transitional dummy packag

Re: listing initrd content

2021-08-02 Thread David Wright
On Tue 03 Aug 2021 at 02:03:57 (+1000), David wrote: > On Tue, 3 Aug 2021 at 01:45, David Wright wrote: > > > BTW I encrypt only /home and swap, and AFAICT my initrd.img doesn't > > contain crypt stuff except for /usr/bin/cryptroot-unlock (5686B). > > So I ignore a polite warning at every rebuild

Re: listing initrd content

2021-08-02 Thread David
On Tue, 3 Aug 2021 at 01:45, David Wright wrote: > BTW I encrypt only /home and swap, and AFAICT my initrd.img doesn't > contain crypt stuff except for /usr/bin/cryptroot-unlock (5686B). > So I ignore a polite warning at every rebuild: > > update-initramfs: Generating /boot/initrd.img-4.19.0-17

Re: listing initrd content

2021-08-02 Thread Greg Wooledge
On Mon, Aug 02, 2021 at 10:45:25AM -0500, David Wright wrote: > You posted here their precise sizes before you installed dracut. > What's the size of your new initrd.img—has dracut done its job? unicorn:~$ ls -l /boot/initrd* -rw-r--r-- 1 root root 30924690 Jan 29 2021 /boot/initrd.img-4.19.0-13-

Re: listing initrd content

2021-08-02 Thread David Wright
On Mon 02 Aug 2021 at 07:51:55 (-0400), 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.i

Re: listing initrd content

2021-08-02 Thread The Wanderer
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

Re: listing initrd content

2021-08-02 Thread Greg Wooledge
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 betw

Re: listing initrd content

2021-08-02 Thread The Wanderer
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 m

Re: listing initrd content (was: Updating kernels impossible...)

2021-08-02 Thread Greg Wooledge
On Mon, Aug 02, 2021 at 01:20:13AM -0400, Felix Miata wrote: > David Christensen composed on 2021-08-01 15:29 (UTC-0700): > > > 2021-08-01 14:10:24 root@dipsy /tmp/initrd.img-4.19.0-17-amd64 > > # gunzip -c /boot/initrd.img-4.19.0-17-amd64 | cpio -i -d -H newc > > --no-absolute-filenames > > 2467

Re: listing initrd content (was: Updating kernels impossible...)

2021-08-01 Thread Felix Miata
David Christensen composed on 2021-08-01 15:29 (UTC-0700): > 2021-08-01 14:10:24 root@dipsy /tmp/initrd.img-4.19.0-17-amd64 > # gunzip -c /boot/initrd.img-4.19.0-17-amd64 | cpio -i -d -H newc > --no-absolute-filenames > 246741 blocks