| TxLogicGuy | A few days ago I asked a question about how to capture console messages from 'udevd --debug'. I found the solution and would post it here, but it probably wouldn't be very readable without posting it as a formatted code listing. How can I do that? (I'm very new to libera.chat.) | 02:24 |
|---|---|---|
| kveremitz | use a pastebin? link here? | 02:59 |
| kveremitz | vivien: you may still find blueness (Anthony) on IRC .. | 03:03 |
| kveremitz | he's generally pretty helpful | 03:04 |
| TxLogicGuy | ok, here is how I captured the messages from 'udevd --debug' | 04:04 |
| TxLogicGuy | https://pastebin.com/zumqigQ5 | 04:05 |
| TxLogicGuy | When I look through the debug messages I see a lot of messages like this one: | 04:14 |
| TxLogicGuy | no db file to read /run/udev/data/+bus:acpi: No such file or directory | 04:14 |
| TxLogicGuy | When I look at the /run/udev/data directory I see that indeed there is no file named "+bus:acpi:" | 04:15 |
| TxLogicGuy | Where do these files in /run/udev/data come from? /run is a tmpfs file system. These files must be created by the kernel or udev, or something, during boot. Should there be a file named "+bus:acpi:"? Or, is udev looking in vain for a file that it doesn't need to be looking for? | 04:18 |
| TxLogicGuy | Maybe the final ":" isn't part of the name. Anyway, there is no "+bus:acpi" either. | 04:27 |
| bb|hcb | TxLogicGuy: The files under /run/udev/data must be created by udev. The kernel never creates files in user filesystems by itself. About +bus:acpi:, I see nothing like that in the default rules. Maybe you have some custom rule, that references it? On a running sysmtem I see many +acpi: (no bus:) | 18:38 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!