On Wed, 07.09.05 11:15, Stephen Hemminger ([EMAIL PROTECTED]) wrote: > > This how I think ifplugd should work, it should not poll it > should just use libnetlink and read for the next message. > > The RUNNING flag works for wireless and non-wireless devices. > If there is a driver it doesn't work on than that is a bug in > the device driver and should be fixed ASAP, not worked around > in user space.
I know how this "should" work. I already wrote that in my previous mail you apperently didn't bother to read. Unfortunately monitoring IFF_RUNNING currently doesn't work with many drivers. And even if it would work with all drivers in modern 2.6 kernels I am not keen on breaking compatibility with 2.4 or even early 2.6 drivers. A hard dependency on kernel 2.6.13 in ifplugd would be plain stupid. Even more "modern" software like HAL monitors like beat with MII ioctls. I will not reiterating the reasons why I implemented ifplugd the way I did, consider reading my previous mail instead. Thank you! Lennart -- Lennart Poettering; lennart [at] poettering [dot] de ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.de/lennart/ - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
