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 ...
joerg at britannica.bec.de
Wed May 25 09:01:17 PDT 2005
On Wed, May 25, 2005 at 08:24:25AM -0700, Matthew Dillon wrote:
> However, the ifconfig changes stay. I did change 'poll' to 'polling',
> but I've left it an IF flag rather then a capability because, frankly,
> using the capabilities bits to control an active operation is just plain
> a bad idea. The IFF flags should be used to control an active operation,
> not the capability bits.
Another important point is that the user doesn't mess with most of
the IFF flags at all (UP, DEBUG, LOOPBACK, NOARP and PROMISC to be
precise) and of those IFF_UP is the capability equivalent of
IFF_RUNNING. So this isn't really a good argument why IFF is better.
More information about the Commits