Re: [libvirt] [PATCH] portability: handle ifreq differences in virnetdev

2013-05-02 Thread Roman Bogorodskiy
Eric Blake wrote: > From: Roman Bogorodskiy > > FreeBSD (and maybe other BSDs) have different member > names in struct ifreq when compared to Linux, such as: > > - uses ifr_data instead of ifr_newname for setting >interface names > - uses ifr_index instead of ifr_ifindex for interface >

[libvirt] [PATCH] portability: handle ifreq differences in virnetdev

2013-04-30 Thread Eric Blake
From: Roman Bogorodskiy FreeBSD (and maybe other BSDs) have different member names in struct ifreq when compared to Linux, such as: - uses ifr_data instead of ifr_newname for setting interface names - uses ifr_index instead of ifr_ifindex for interface index Also, add a check for SIOCGI

Re: [libvirt] [PATCH] portability: handle ifreq differences in virnetdev

2013-04-30 Thread Eric Blake
On 04/29/2013 11:48 AM, Eric Blake wrote: > On 04/27/2013 09:50 AM, Roman Bogorodskiy wrote: >> FreeBSD (and maybe other BSDs) have different member >> names in struct ifreq when compared to Linux, such as: >> >> - uses ifr_data instead of ifr_newname for setting >>interface names >> - uses i

Re: [libvirt] [PATCH] portability: handle ifreq differences in virnetdev

2013-04-29 Thread Eric Blake
On 04/27/2013 09:50 AM, Roman Bogorodskiy wrote: > FreeBSD (and maybe other BSDs) have different member > names in struct ifreq when compared to Linux, such as: > > - uses ifr_data instead of ifr_newname for setting >interface names > - uses ifr_index instead of ifr_ifindex for interface >

[libvirt] [PATCH] portability: handle ifreq differences in virnetdev

2013-04-27 Thread Roman Bogorodskiy
FreeBSD (and maybe other BSDs) have different member names in struct ifreq when compared to Linux, such as: - uses ifr_data instead of ifr_newname for setting interface names - uses ifr_index instead of ifr_ifindex for interface index Also, add a check for SIOCGIFHWADDR for virNetDevValid