On Thu, Apr 15, 2010 at 04:12:11PM -0700, Xin LI wrote: > Hi, > > On Thu, Apr 15, 2010 at 2:59 PM, Jonathan Chen <j...@chen.org.nz> wrote: > > ?? ??$ /compat/i386/sbin/ifconfig > > ?? ??: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> > > ?? ?? ?? ??inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255 > > ?? ?? ?? ??inet 192.168.1.11 netmask 0xffffffff broadcast 192.168.1.11 > > ?? ?? ?? ??inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255 > > ?? ?? ?? ??inet 192.168.2.10 netmask 0xffffffff broadcast 192.168.2.10 > > ?? ?? ?? ??inet 192.168.2.12 netmask 0xffffffff broadcast 192.168.2.12 > > ?? ?? ?? ??inet 127.0.0.1 netmask 0xff000000 > > ?? ??ifconfig: ioctl(SIOCGIFINFO_IN6): Device not configured > > > > Why is the output from the 32-bit ifconfig severely mangled? > > My understanding is that 32-bit management tools like ifconfig is not > supported on 64-bit FreeBSD. Someone has to sit down and write a > compatibility layer for translating back and forth :(
Ah. The reason I ask is because wine's (32-bit) network-i/f iteration code is breaking when running under amd64. It uses code similar to ifconfig's to determine available network interfaces. I didn't expect the read-only interface would break when crossing the 32 to 64 barrier. Thanks for the analysis. -- Jonathan Chen <j...@chen.org.nz> ---------------------------------------------------------------------- "In mathematics you don't understand things. You just get used to them." - Johann von Neumann _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"