On Sat, Jan 31, 2015 at 05:51:57PM +0100, Denys Vlasenko wrote > > "mdev --help" says: > > If /dev/mdev.log file exists, debug log will be appended to it. > > Please create an empty /dev/mdev.log file before you run > "mdev -s" or install mdev as hotplug helper. > Reboot, send me the resulting log file, and entire /etc/mdev.conf.
That required a bit of digging on my part. At first I was getting
nothing in /dev/log when I did "mdev -s", even after rebuilding busybox
with the debug and syslog flags and rebooting. I looked into the
/etc/init.d/mdev script, and noticed the following function which is
executed *BEFORE* "mdev -s"...
seed_dev()
{
# copy over any persistent things
if [ -d /lib/mdev/devices ] ; then
cp -RPp /lib/mdev/devices/* /dev 2>/dev/null
fi
}
I created /lib/mdev/devices/ and a zero-byte mdev.log file in it,
rebooted, and finally got some output. Apparently "mdev -s" is not
equivalant to rebooting, as far as mdev.log is concerned. File-attached
are mdev.conf.gz and mdev.log.gz (from the boot process). They're
gzipped to save space on the mailing list. This is from the 64-bit
Gentoo machine.
--
Walter Dnes <[email protected]>
mdev.conf.gz
Description: Binary data
mdev.log.gz
Description: Binary data
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
