The boot process is logged to /var/log/messages
Everything is logged upto the point
>>loading modules. The individual modules may log information which is not displayed on the command line, and whilst the modules are listed on the command line, no entry is made in the /var/log/messages that a module has been loaded.
An entry should be made for each module that loading is attempted for. If that module also logs information, so be it.
you've opted not to post a lot of information that every bug report should have
please consult the documentation:
in particular, you need to include `emerge --info`, and in this case your /etc/rc.conf as well as /etc/conf.d/rc should be posted as attachments
Created attachment 149047 [details]
Image of the boot process
Created attachment 149049 [details]
corresponds to the image
Created attachment 149050 [details]
Created attachment 149052 [details]
ok, you have some misconceptions here that i'll clear up
/var/log/messages is for kernel and system logging only. it is not for logging of anything that gets sent to the console while booting.
the module output that you've posted in the image is from the initrd, not baselayout or anything else. it comes from the tiny image that genkernel created before the root filesystem even gets mounted. we most likely wont be adding logging support for the initrd. if we do, that is something to take up with the genkernel people, not baselayout.
logging of the console is done via the bootlog option (which ironically you havent turned on in your /etc/conf.d/rc). but this is only for once the userspace init process has taken over (and thus baselayout/openrc). those messages are also logged to a different place, not via the standard system log daemons. there is also the problem that the dev file system and the system logger are not even available at the time things start.
The initrd is logged in full. This must be cached until the file system is available, or it has it's own write mechanism. Either way, the genkernel people log the lot! Even though the message were produced before system logger was available.
I noticed the /etc/conf.d/rc boot logging option after you requested it. I havn't changed it so 'No' must be the default. I'll have a play and turn it on, but I would have thought the default was YES.
'logged to a different place' - where?
Given that the modules that are not being listed are for the disk drives, would this still be in initrd and so this should be assigned to genkernel?
Let me check the boot logging option. I will reassign accordingly.
the boot logging requires an external package ... that is why it is not enabled by default, nor does it list the filename (as the location is controlled by the other package, not baselayout). it typically ends up as /var/log/boot.log iirc.
i dont know where the logging is stored as the log file you posted doesnt contain anything from genkernel.