Summary: | sysctl set /proc system before udev rename the interfaces | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matteo Contri <linux> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | VERIFIED NEEDINFO | ||
Severity: | minor | CC: | gregkh |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 104535 |
Description
Matteo Contri
2005-08-30 09:28:10 UTC
doubtful sysctl is run long after udev is started sysctl simply sets values in /proc/sys/net/ so something else is likely going on Yeah, sysctl happens _way_ after udev runs at startup. What is probably happening is your module is getting loaded for your device, and that is racing with the sysctl stuff, right? get back to us Sorry guys, but i completely forget this issue! I cannot test anymore on the machine because now is on production: it's a lovely outgoing load balancer... But i tried with my workstation. Greg Kroah-Hartman was right, the problem is that the configuration for the device was create by the kernel when the interface goes up (then at network initialization) but the sysctl was already started. Now i know a little bit more of Linux... and thank you Gentoo devs! |