I have an embedded system running a slim installation of Buildroot Linux with kernel 3.10.105. Apparently most commands come from BusyBox here, and it seems those do not always implement the full functionality of the regular counterparts... I wonder whether more presistent logging is simply not implemented here, either, or maybe this can be configured?
So if I execute htop, I see that syslogd and klogd are running. I can see recent kernel messages in the file /var/log/messages. There is no kern.log in that log folder, though. All that's in there is: messages, resolv.conf, sshd, and then folders: dbus, subsys.
I'd like to inspect, after reboot, the kern.log (or whatever equivalent file) to see what happened before the system froze when using a certain driver.
Can I do this with the BusyBox tools?
EDIT: Some notes due to comments:
Configuration: when I type syslogd --help, it mentions that "this version of syslogd ignores /etc/syslog.conf". And according to htop, it runs with the option -n, which according to this help output means "run in foreground". The only option that a file parameter is: -O FILE, and it says the default is /var/log/messages, so it's the "live" file.