DragonFly BSD
DragonFly commits List (threaded) for 2005-05
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: cvs commit: src/sys/i386/i386 nexus.c src/sys/i386/include atomic.h src/sys/kern kern_poll.c lwkt_serialize.c src/sys/net if.c if_var.h rtsock.c src/sbin/ifconfig ifconfig.c src/sys/dev/netif/dc if_dc.c src/sys/dev/netif/em if_em.c if_em.h ...

From: Joerg Sonnenberger <joerg@xxxxxxxxxxxxxxxxx>
Date: Wed, 25 May 2005 10:41:43 +0200
Mail-followup-to: commits@crater.dragonflybsd.org

On Wed, May 25, 2005 at 01:13:58AM -0700, Matthew Dillon wrote:
>    Polling is an interface capability in FreeBSD, and it works totally
>    differently from any other standard network interface operation.  It
>    requires reading multiple manual pages and getting help from the lists
>    to even make it work as expected, something I'd like to avoid in 
>    DragonFly.  It is totally non-intuitive.  The design is aweful.

It works already that way. "ifconfig rl0 polling". That's all.
The only reason it is hard to find is that the man pages are outdated.
It is more similiar to e.g. vlan support than to broadcast. Actually
this is a good example of how they differ.

The reason we have IFF_CANTCHANGE is because the interface flags are
already a mix of administrative and internal flags, this makes it
only worse.


[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]