Apologies, this is not a bug but a suggestion to incorporate a post-boot export of the system dmesg. On other OSes I've used, the dmesg output from the system boot is written to a static file under e.g. /var/log/dmesg.boot and is useful for analyzing real dmesg/boot output prior to the kernel writing the dmesg "(buffer?)" full of garbage for device errors and filesystem debugging, etc. which tends to overwrite the useful information a user might seek after booting the system. Reproducible: Didn't try Steps to Reproduce: Non-reproducable. Actual Results: After having more than a few days uptime, my system dmesg is worth nothing in terms of hardware boot message analysis and is usually filled with hardware debugging information.
Created attachment 38899 [details] Initial patch to include a log of dmesg
I write a script to write a log in /var/log/dmesg I requiere after local to load all modules and see the log
Hi. Firstly, you didn't attached a patch, but the init script itself. Also, adding this into the consolefont init script is pretty random and not the right way to fix this. bootmisc might be a better bet. Want to have another go at this?
bootmisc sounds like a good idea ... perhaps as the last command in the start() function in the if [ "${BOOT}" = "yes" ] block of code
updated the bootmisc script like i described to run `dmesg > /var/log/dmesg`
