On Fri, Nov 06, 2015 at 01:38:42PM +0000, Steve McIntyre wrote:
>
> Since the move to systemd as the default init system, the initramfs
> will attempt to fsck and mount both / and /usr (where applicable). To
> aid this, initramfs-tools will copy necessary filesystem tools into
> the initramfs when it is generated.
>
> To make this work well, all filesystem tools packages for filesystems
> that are likely to be used for / and/or /usr should call
> "update-initramfs -u" in their postinst. This will
>
> (a) ensure that necesssary fsck tools are included in the initramfs
> generated by debian-installer (see #801961 for an example failure
> here); and
> (b) ensure that bug fixes to fsck tools get included immediately in
> the initramfs
>
> I've checked your package and I don't see any update-initramfs
> calls. Please add one. If you'd like help doing that, I can supply a
> patch - just ask!
I'm confused. I've just tried running "update-initramfs -u" using
initramfs-tools and I'm not seeing any fsck tools. In fact, I'm not
seeing much of anything:
# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.5.0-00039-ge2bd7c0
# cpio -it < /boot/initrd.img-4.5.0-00039-ge2bd7c0
kernel
kernel/x86
kernel/x86/microcode
kernel/x86/microcode/GenuineIntel.bin
44 blocks
This is on a debian testing system using systemd. What am I missing?
If it matters, I'm not using Debian's heavyweight kernel building
instead, but instead am building kernels from upstream using "make
deb-pkg".
- Ted
