[Buildroot] Possible conflict with systemd and e2fsprogs?
dom at digineo.de
Mon Apr 29 09:01:11 UTC 2019
On 4/27/19 11:47 PM, Arnout Vandecappelle wrote:
> I've tried to reproduce in qemu, but it works fine there. This is the defconfig
> I used:
In 2019.02.x, I can only find max. 4.19, do I need master?
> and this is the qemu command to launch:
> qemu-system-arm -M vexpress-a9 \
> -drive "file=output/images/rootfs.ext2,if=sd,format=raw" \
> -append "root=/dev/mmcblk0 rootfstype=ext4 rootwait ro console=ttyAMA0" \
> -net nic,model=lan9118 -net user -dtb output/images/vexpress-v2p-ca9.dtb \
> -serial stdio -kernel output/images/zImage
EXT4-fs (mmcblk0): mounted filesystem with ordered data mode. Opts:
VFS: Mounted root (ext4 filesystem) readonly on device 179:0.
Freeing unused kernel memory: 1024K
Run /sbin/init as init process
FATAL: kernel too old
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
(obvious error is obvious :-))
>>> package/systemd/Config.in does select BR2_PACKAGE_UTIL_LINUX_FSCK precisely for
>>> this reason...
>>> I'm adding Carlos (who added that) in Cc, maybe he has something to say about it.
>>> If it now needs the fsck from e2fsprogs, then it is getting a little tricky to
>>> do the right thing. We'd have to revert the dependency between e2fsprogs fsck
>>> and util-linux fsck.
>> I don't think systemd needs e2fsprog's fsck. *I* need e2fsprogs, but only for
>> its resize2fs (nevertheless, it also installs /sbin/fsck.ext4). However, systemd
>> finds /sbin/fsck.ext4, and proceeds to execute /sbin/fsck.
>> My current working theory is that /sbin/fsck then in turn calls out to
>> /sbin/fsck.ext4. As far as I can tell, /sbin/fsck originates from util-linux,
>> while /sbin/fsck.* come from e2fsprogs.
> Yes indeed. And all that is exactly how it's supposed to work. So I don't
> really understand why it doesn't work for you.
I will investigate further.
More information about the buildroot