Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\.6\s+NET\]\s+Device\s+name\s+changing\s+via\s+rtnetlink\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\.6\s+NET\]\s+Device\s+name\s+changing\s+via\s+rtnetlink\s*$/: 40 ]

Total 40 documents matching your query.

21. [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: Thomas Graf <tgraf@xxxxxxx>; Date: Fri, 10 Sep 2004 15:36:37 +0200; Allows changing of device name via rtnetlink. Last bit needed to do full link configuration via rtnetlink. Signed-off-by: Thomas Graf <tgraf@xxxxxxx> diff -Nru linux-2.6.9-rc1-bk15.orig/include/linux; /archives/netdev/2004-09/msg01753.html (10,459 bytes)
22. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: YOSHIFUJI Hideaki / <yoshfuji@xxxxxxxxxxxxxx>; Date: Fri, 10 Sep 2004 23:00:38 +0900 (JST); Please use sizeof(ifname) instead. -- Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@xxxxxxxxxxxxxx> GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA; /archives/netdev/2004-09/msg01755.html (9,798 bytes)
23. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: Thomas Graf <tgraf@xxxxxxx>; Date: Fri, 10 Sep 2004 16:28:04 +0200; * YOSHIFUJI Hideaki / ?$B5HF#1QL@ <20040910.230038.322907649.yoshfuji@xxxxxxxxxxxxxx> 2004-09-10 23:00 Thanks for the hint. Allows changing of device name via rtnetlink. Last bit needed to do full li; /archives/netdev/2004-09/msg01756.html (12,132 bytes)
24. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: YOSHIFUJI Hideaki / <yoshfuji@xxxxxxxxxxxxxx>; Date: Fri, 10 Sep 2004 23:31:57 +0900 (JST); Thanks. Ack. Signed-off-by: Hideaki YOSHIFUJI <yoshfuji@xxxxxxxxxxxxxx> --yoshfuji; /archives/netdev/2004-09/msg01757.html (10,249 bytes)
25. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx>; Date: Fri, 10 Sep 2004 12:50:03 -0700; This does not work, because you don't return the new name to user space. If the new name is a pattern, such as "eth%d" or "wlan%d", you absolutely need to return the new instanciated device name to u; /archives/netdev/2004-09/msg01760.html (11,146 bytes)
26. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: Thomas Graf <tgraf@xxxxxxx>; Date: Fri, 10 Sep 2004 22:06:44 +0200; * Jean Tourrilhes <20040910195003.GA13912@xxxxxxxxxxxxxxxxxx> 2004-09-10 12:50 The ifindex stays the same, therefore the user space application can simply dump the link list and fetch the new interfa; /archives/netdev/2004-09/msg01761.html (10,380 bytes)
27. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx>; Date: Fri, 10 Sep 2004 13:13:02 -0700; It's so simple to return the new name, so why not do it ? There is no need to make applications more complex. What do you mean, break the RFC ? Jean; /archives/netdev/2004-09/msg01762.html (11,607 bytes)
28. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: Thomas Graf <tgraf@xxxxxxx>; Date: Fri, 10 Sep 2004 22:22:35 +0200; * Jean Tourrilhes <20040910201302.GA16556@xxxxxxxxxxxxxxxxxx> 2004-09-10 13:13 Oh, I didn't realize that, can you enlighten me? I can think of 2 ways implementing this: 2) Implement NETDEV_CHANGE, I; /archives/netdev/2004-09/msg01763.html (11,864 bytes)
29. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx>; Date: Fri, 10 Sep 2004 13:32:03 -0700; Do you have any info on NETDEV_CHANGE, I've got a potential use for it. (By the way, there are other ways to do it, but if NETDEV_CHANGE is the proposed standard, I might as well use it). Jean; /archives/netdev/2004-09/msg01765.html (11,553 bytes)
30. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 10 Sep 2004 16:31:41 -0400; This is what he needs. Essentially NETDEV_CHANGE will generate a netlink event. cheers, jamal; /archives/netdev/2004-09/msg01766.html (10,852 bytes)
31. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: Thomas Graf <tgraf@xxxxxxx>; Date: Fri, 10 Sep 2004 22:43:48 +0200; * Jean Tourrilhes <20040910203203.GA17078@xxxxxxxxxxxxxxxxxx> 2004-09-10 13:32 Currently call_netdevice_notifiers is called and sends out a RTM_NEWLINK message with the new interface name to everyone; /archives/netdev/2004-09/msg01767.html (11,438 bytes)
32. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 10 Sep 2004 18:58:02 -0400; I missed the RTM_NEWLINK part. It is easier to just keep it that way and make sure it is well documented as so. It may not be trivial (as an example all the inetdev name attributes change - look at i; /archives/netdev/2004-09/msg01779.html (12,369 bytes)
33. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxxxxx>; Date: Fri, 10 Sep 2004 16:04:34 -0700; For now I'm going to apply Thomas's name changing patch (with the sizeof() fix suggested by Yoshifuji), and we can enhance it later.; /archives/netdev/2004-09/msg01782.html (10,868 bytes)
34. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: Thomas Graf <tgraf@xxxxxxx>; Date: Sat, 11 Sep 2004 01:17:26 +0200; * jamal <1094857082.1041.19.camel@xxxxxxxxxxxxxxxx> 2004-09-10 18:58 I agree, most applications will hold a cache of all links, like iproute2 is doing, and just update the cache. There is one remaini; /archives/netdev/2004-09/msg01783.html (12,614 bytes)
35. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 10 Sep 2004 22:01:10 -0400; notify via ioctls is still needed. Are you changing MTU and NAME at the same time? Valid to receive the two updates i would think in that case. cheers, jamal; /archives/netdev/2004-09/msg01790.html (11,534 bytes)
36. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: Thomas Graf <tgraf@xxxxxxx>; Date: Sat, 11 Sep 2004 15:44:09 +0200; * jamal <1094868070.1042.77.camel@xxxxxxxxxxxxxxxx> 2004-09-10 22:01 Possibly, I change everything the user requests me to do. That's not the problem, the problem is that you may receive more updates; /archives/netdev/2004-09/msg01797.html (13,768 bytes)
37. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 11 Sep 2004 15:59:53 -0400; Ok, this doesnt sound right. Not necessary to send all those updates. do_setlink was doing the right thing before your patch. It was announcing the change of addresses (broadcast, etc). You introduce; /archives/netdev/2004-09/msg01806.html (13,344 bytes)
38. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: Thomas Graf <tgraf@xxxxxxx>; Date: Sun, 12 Sep 2004 00:06:14 +0200; * jamal <1094932793.2344.82.camel@xxxxxxxxxxxxxxxx> 2004-09-11 15:59 OK, however I'd prefer to invert the concept. See patch below. This would send out the following updates: ififlags - NETDEV_(UP|DO; /archives/netdev/2004-09/msg01809.html (13,942 bytes)
39. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 12 Sep 2004 13:27:29 -0400; Guess it wont make difference in number of lines of code, so fine. This one is sort of grey area. Sigh. In any case, i think that this is ok for now. So patch should go in - we can revisit the whole; /archives/netdev/2004-09/msg01824.html (14,174 bytes)
40. Re: [PATCH 2.6 NET] Device name changing via rtnetlink (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxxxxx>; Date: Sun, 12 Sep 2004 17:20:43 -0700; Done.; /archives/netdev/2004-09/msg01852.html (10,939 bytes)

Current List: 21 - 40
Page: [1] [2]