Bug#561764: Bug#561229: Bug#561764: some warnings fly off screen and are not saved in any file

2009-12-21 Thread Jonas Smedegaard
On Mon, Dec 21, 2009 at 09:46:57AM +0100, Bernd Zeimetz wrote: jida...@jidanni.org wrote: OK, via $ zcat /boot/initrd.img-2.6.32-trunk-686|strings|less I think I found one of the messages I saw: SYSFS{}= will be removed in a future udev version which is in /sbin/udevadm ... bug #561229 perhaps.

Bug#561764: Bug#561229: Bug#561764: some warnings fly off screen and are not saved in any file

2009-12-21 Thread Bernd Zeimetz
jida...@jidanni.org wrote: > OK, via > $ zcat /boot/initrd.img-2.6.32-trunk-686|strings|less > I think I found one of the messages I saw: > SYSFS{}= will be removed in a future udev version > which is in /sbin/udevadm ... bug #561229 perhaps. What the hell does a bug in gpsd udev rules have to do

Bug#561764: some warnings fly off screen and are not saved in any file

2009-12-20 Thread jidanni
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 bes

Bug#561764: some warnings fly off screen and are not saved in any file

2009-12-20 Thread Ben Hutchings
On Mon, 2009-12-21 at 04:07 +0800, jida...@jidanni.org wrote: > > "BH" == Ben Hutchings writes: > > BH> Early kernel messages should be copied into /var/log/messages by the log > BH> daemon. Maybe you need to turn up the log level. If you think this is > BH> not a configuration error, pleas

Bug#561764: some warnings fly off screen and are not saved in any file

2009-12-20 Thread jidanni
> "BH" == Ben Hutchings writes: BH> Early kernel messages should be copied into /var/log/messages by the log BH> daemon. Maybe you need to turn up the log level. If you think this is BH> not a configuration error, please reassign to the log daemon's package BH> (rsyslog is the default). Al

Bug#561764: some warnings fly off screen and are not saved in any file

2009-12-20 Thread Robert Hancock
On 12/20/2009 11:39 AM, jida...@jidanni.org wrote: OK, via $ zcat /boot/initrd.img-2.6.32-trunk-686|strings|less I think I found one of the messages I saw: SYSFS{}= will be removed in a future udev version which is in /sbin/udevadm ... bug #561229 perhaps. However, what I'm saying is "how bad it

Bug#561764: some warnings fly off screen and are not saved in any file

2009-12-20 Thread Ben Hutchings
On Mon, 2009-12-21 at 01:39 +0800, jida...@jidanni.org wrote: > OK, via > $ zcat /boot/initrd.img-2.6.32-trunk-686|strings|less > I think I found one of the messages I saw: > SYSFS{}= will be removed in a future udev version > which is in /sbin/udevadm ... bug #561229 perhaps. > > However, what I'

Bug#561229: Bug#561764: some warnings fly off screen and are not saved in any file

2009-12-20 Thread jidanni
OK, via $ zcat /boot/initrd.img-2.6.32-trunk-686|strings|less I think I found one of the messages I saw: SYSFS{}= will be removed in a future udev version which is in /sbin/udevadm ... bug #561229 perhaps. However, what I'm saying is "how bad it is that there be any messages that fly off the scree

Bug#561764: some warnings fly off screen and are not saved in any file

2009-12-19 Thread jidanni
Package: linux-2.6 Version: 2.6.32-2 Severity: wishlist X-debbugs-cc: linux-ker...@vger.kernel.org There is some warning about SYS... being DEPRECATED or something like that. I can't tell as it flies off the screen at boot and is not kept in any /var/log file. I don't even know what to google for