BH> These messages remain in the kernel log buffer and should be copied
BH> by the log daemon later.
Ah ha, I can reproduce the messages via
/etc/init.d/udev restart
and indeed they also end up in the /var/log/ files.
(They are complaining about some things in /etc/udev/rules.d/*, but that
is besides the point (that they don't get logged at boot.))
So then I rebooted (regular boot,
/proc/cmdline:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-686 root=/dev/sda1 ro quiet panic=15)
There those udev warnings go zipping by.
And now that everything is up and running in multi-user mode, I check
the logs, and ah ha, the only warnings that were logged are the ones
from when I did /etc/init.d/udev restart. There are none corresponding
to the time right after reboot. Nor say several hours off due to
timezone settings or anything.
(I don't believe "quiet" above means less will go to the logs than goes
to the screen.)
10:49 log# find -mtime -1 -type f|xargs egrep -h SYSFS\|reboot|colrm 77|sort -u
Dec 21 10:43:10 jidanni3 udevd[15039]: SYSFS{}= will be removed in a future
Dec 21 10:45:14 jidanni3 shutdown[15063]: shutting down for system reboot
Dec 21 10:45:58 jidanni3 /usr/sbin/cron[1178]: (CRON) INFO (Running @reboot
Maybe some logging is being done, but it is at that time ending up on a
tmpfs that one sees in /etc/init.d/udev, that gets mounted over with
something else, but that is over my head.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
