Bryan Kadzban wrote:
> These operations (creating the socket and bind()ing it) will generate
> their own log messages, but they'll be put into the log when udevd
> starts up, not later. So you may have to change the logging level in
> the config file (...if that's even possible anymore)
Yup. You
Hi Stef,
Stef Bon wrote:
> Nov 1 09:08:56 localhost udevd[920]: get_netlink_msg: unable to receive
> kernel netlink message: Socket operation on non-socket
> Nov 1 09:08:56 localhost udevd[920]: get_ctrl_msg: unable to receive user
> udevd message: Socket operation on non-socket
I don't have a
Alexander E. Patrakov wrote:
> This is a non-issue. Both are processed, and in this particular case it
> doesn't matter which of the files is examined first.
Ah ok, no problem then.
It would be 'cleaner' to give it another number IMHO.
OT: Why 26 anyway? What's the thought behind this? (I'm curi
Hi,
I'm working my way through the LFS-6.2-stable book and found this:
In section 7.13.1 (Creating stable names for network interfaces); the
reader is told to create a udev rule for the network card by doing:
cat > /etc/udev/rules.d/26-network.rules << EOF
I found that there is a udev rule '26-
