Finit hangs after mounting filesystems from /etc/fstab

[ComputerKing12]

I'm working on a custom distro, and I decided to use finit as the init system. I feel like I'm just missing something, but I'm not sure what. Shown below is an image of finit hanging. I have also attached my /etc/fstab, /etc/finit.conf, a log of the vm's entire lifecycle, and the config.h that was used to build finit. Also, if there are any additional files you'd like to see, I'd be happy to upload them. If you know what I'm missing, please let me know.
Thanks

fstab.txt
finit.conf.txt
log.txt
config.h.txt

[troglobit]

Since you are using yet unreleased software from the master branch, could you tell me which hash you are using? (We had a regression recently that upended things for many.)

Enable finit.debug to get some more output, see https://github.com/troglobit/finit/blob/master/doc/cmdline.md.

[troglobit]

If you can dump it all in this thread, that would be great. I don't have any I other storage to offer, unfortunately.

I won't be able to look at it until tomorrow though, so no panic.

[troglobit]

Oh, would be great if you could detail your qemu line, there are quite a few possibilities, which have tripped up many before.

[ComputerKing12]

Apologies it took so long. I had gotten caught up in a few things, and github wouldn't let me upload the rootfs, since it was over 25mb (in actuality, it is 5gb compressed, and 16gb uncompressed). My qemu launch command is as follows: qemu-system-x86_64 -nographic -kernel bzImage -drive file=rootfs.img -m 1024 -append "root=/dev/sda console=ttyS0 init=/sbin/finit" |& tee log.txt. Hope this helps. Thank you again
Google Drive - rootfs
bzImage.zip

[troglobit]

Thanks, this made it really easy to reproduce!

I mounted the rootfs and added this to your /etc/finit.conf:

tty [12345789] console noclear nologin

Starting up again I now had a root shell and could probe it further. Calling initctl showed acpid as waiting on syslogd, so I modified finit.conf as follows and called initctl reload:

runlevel 2
log size=100k count=4

service [S12345] env:-/etc/conf.d/syslog syslogd -n            -- Syslog daemon
service [S12345] <pid/syslogd> env:-/etc/conf.d/klogd klogd -n -- Kernel log daemon
service [2345] <pid/syslogd> log acpid -f                      -- ACPI daemon        
tty [12345789] console noclear nologin

Now both acpid and klogd failed to start. So I started poking around a bit and realized that a lot of what I usually expect to be available on a Finit system was missing:

• /lib/plugins/*
• /etc/finit.d/*

The finit.d/ directory is not mandatory, Finit works fine with just finit.conf. However, to get the dependency handling to work, the pidfile.so plugin must be loaded, otherwise no pid conditions can be asserted. You can of course use the bare minimum of Finit, without any plugins, but if you try to start a system without synchronization then you're a bit on your own.

I must say I'm not really sure what you expected would happen? I'm sorry to say this, but have you looked at the contrib/ section in the repository or read any of the documentation? For reference you can have a look at some of the examples build around Buildroot that I've published:

• https://github.com/troglobit/myLinux
• https://github.com/troglobit/br2-finit-demo, which uses:
  • https://github.com/troglobit/br2-ext-finit
  • https://github.com/troglobit/finit-skel

I really recommend the br2-finit-demo it's fairly straight forward to build and get with running. Having a working reference when setting up your own system is always handy. A walk-through is available here: https://troglobit.com/post/2022-12-26-buildroot-demo-of-finit/

Good Luck!

Tip: add -M q35,accel=kvm -cpu host -enable-kvm to your qemu-system line to speed it up a bit.

[ComputerKing12]

Thank you for your time and assistance. I had looked through the documentation and contrib folder, but there was no mention of exactly what was required. I'll poke through the resources you posted. Thank you again

EDIT: Glad it was user error and not a bug

EDIT 2: I did enable build-static with configure, and I'm curious if that caused pidfile.so to not be built?

[troglobit]

I've tried to make the build instructions as clear as possible, but I guess there's always room for improvement.

Hmm, yeah you're right. When building a static Finit the pidfile plugin should be built-in. Sorry, but the static build should probably be marked as deprecated, and then removed in v5. I've never used it myself, and was pushed by a very vocal user 5-10 years back. I should know better than try to support use-cases I have no way of testing myself 😞

I recommend going with a dynamic build, doing a proper "make install" and setting up your system .conf file(s) with help from the contrib section.