This kind of errors don't happen that often anymore nowadays, thanks to wide 
use of usb pens. As nobody came up with a solution which would be ready-to-go 
for more than 2 years I'm closing this with "won't" fix.

* Michael Gebetsroither <bts@bts.grml.org> [20071222 12:14]:

> dmesg -n <right loglevel>
> doesn't help either?

Hm?! How is this supposed to help us? I'd like to "grep for Squashfs
errors in syslog" and display it immediately on all available
consoles (including X terminals as well) without any user
interaction. (On the other side I don't want to flood the user with
any other messages of course.)

thx && regards,
-mika-

dmesg -n <right loglevel>
doesn't help either?

Yeah, I was aware of that. My problem is, that syslog-ng does not provide a way 
of including seperate configuration files. So looks like we have to add that 
snippet to the official syslog-ng configuration. :-/

thx && regards,
-mika-

it should be enough to adjust the kernel loglevel to our needs ;).

but netherless something like this should do it for syslog-ng to all users:
destination allusers { usertty("*"); };

Gebi: do you have any templates for syslog-ng you think might match the needs 
of http://bts.grml.org/grml/issue330 ?

regards,
-mika-

If we notice:

SQUASHFS error: sb_bread failed reading block ...
SQUASHFS error: Unable to read page, block ..., size ....

or:

loop0: read i/o error, sector ...

inside the syslog we should write a warning to all consoles so the user is 
notified about the broken CD-ROM.