Getting the message from the kernel
Posted Jul 3, 2007 17:45 UTC (Tue) by Blaisorblade
Parent article: Getting the message from the kernel
I was thinking to an entirely different approach altogether: communicating with hal and dbus important messages.
Most printk are for debugging purposes (for instance):
[22156.206781] sd 6:0:0:0: Attached scsi removable disk sdb
[22156.207067] Device driver target6:0:1 lacks bus and class support for being resumed.
[...repeated for all partitions...]
[22156.215831] usb-storage: device scan complete
[22261.183379] usb 1-3: USB disconnect, address 8
"Interface is up / down " messages are already told to the user via tons of graphical applets.
What instead is important and is not told are, for instance, I/O errors, on internal or external media. On Windows, such messages pop up from the systray. The same should happen on a Linux desktop.
Such messages would be just a selection, and creating unique IDs for them (and adding the message in userspace) would be a task for userspace developers at that point.
to post comments)