Johannes Berg wrote: > On Tue, 2007-04-10 at 12:46 +0200, Patrick McHardy wrote: > > >>The main advantage that we don't get more weird sysfs/proc/ioctl based >>interfaces > > > Please don't put me into a corner I don't want to be in ;) The new > wireless stuff was completely designed using netlink. The sysfs > interface to these two specific things was a concession since it used to > exist before and we don't really have a fully functional userspace tool > yet.
I know :) It was a few month ago when I noticed the new bonding sysfs interface when I first thought that we really need this. >> and use the same interface that is used for all other network >>configuration, which f.e. will allow to add support for all software >>devices to iproute without much effort, so you don't need 30 different >>tools for configuring the different software device types anymore. >>Additionally we get atomic setup/dumps and extensibility. > > > I don't think wireless can get away without a new tool. So much stuff > there. Look at > http://git.kernel.org/?p=linux/kernel/git/linville/wireless-dev.git;a=blob;f=include/linux/nl80211.h;hb=HEAD Maybe not wireless, but bonding, briding, vlan, etun, possibly more. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
