Quoting Ben Hutchings (ben@decadent.org.uk): > By the same token, we don't need iproute2 if there is no GUI tool that > invokes it. See how silly that argument is? The point is not saying that iw is useless. My point is that I don't think that solving this problem (if there is one) should be done by adding iw to a *desktop* task. > iw is the standard Linux command for configuring wireless interfaces. > But you are quite unlikely to have them on a server, otherwise I would > suggest it should be priority standard. > > crda is definitely required for wireless interfaces, but it is normally > invoked via a udev hook rather than from a shell or GUI front-end. Unless some other solution exists, isn't it better to use the *laptop* task for these?
Attachment:
signature.asc
Description: Digital signature