Hi Alina, > > you argue command line tools against kernel exposed API. > > I use the command line syntax to explain the kernel API. and that is just plain wrong to begin with. If you want a one command do everything, then do that in userspace and not inside a kernel API. > > Both have > > nothing to do with each other on that level. > > Most commands are mapped 1:1. And the API easier to understand if it is so. That just happen to be this way right now. It doesn't have to stay that way and if it would, that would be actually be stupid. > > If you don't like the iw > > syntax then fix it and provide a command that does all three task for > > you. No need to mess with the kernel interface for that. > > I think now, provide a high-level command besides the low-level commands is a good idea. We need it for the old wext interface anyway. Then wext can only call this command and don't need own intelligence. So than it's only a foolish wrapper, like it should. >From my point of view, WEXT can die right now. Just doing something to make WEXT happy is wrong. If you want something like that then do it in userspace. I just don't see the need here for an extra kernel API. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
