On Sat, Mar 29, 2014 at 2:42 AM, David Miller <davem@xxxxxxxxxxxxx> wrote: > From: Tom Gundersen <teg@xxxxxxx> > Date: Fri, 28 Mar 2014 23:39:57 +0100 > >> You mean coordinate with each other in userspace? If so, I still don't >> see how this can ever be anything else than fragile. It will depend on >> each userspace component actually opting in to whatever scheme we >> devise, and does so correctly. > > Isn't that essentially what dbus is? > > A way for seperate userland components to coordinate their > activities? The protocol is not the problem. The issue is that this information only exists reliably in the kernel, so we need to get it from there somehow. > I just simply don't like all of these ramdom keys getting > added all over the place to guide udev behavior wrt. some > other entity. Well, in this case udev is sort of doing a bit of the kernel's work, and it needs some information from the kernel to do it reliably. Another approach would be for the kernel to just assign predictable interface names to devices to begin with and we would never have to touch them. You have all the information so that would be relatively easy. The issue I see with that is that there are several ways to generate predictable names, and the user may want to chose between them, so this is arguably policy that should not be in the kernel. If you don't think that's a problem, I'd be happy to submit a patch to move all this logic from udev to the kernel, just let me know how you see it. Cheers, Tom -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
