Bug#499537: might conflict with aircrack-ng?

[Kel Modderman <kel@otaku42.de>]

On Saturday 20 September 2008 06:49:20 Johannes Berg wrote:
> > On a side note, iwconfig is currently installed to /sbin (and it doesn't
> > link with anything on /usr/), as I understand it is there so that it may be
> > used to configure a network device early in boot so that a network filesystem
> > may be mounted (which might be /usr/). iw seems to make iwconfig redundant in
> > the future. Currently iw links to /usr/lib/libnl.so.X, but if libnl was changed
> > to reside in /lib sometime in the future, I can imagine some people picketing
> > to have iw moved from /usr/bin/ to /bin or /sbin, what is your take on this?
> > 
> > Note that i personally think mounting critical network filesystems over
> > wireless to be crazy.
> 
> :)
> 
> If you really want to go there... I'm thinking /usr/bin since I don't
> see it as that critical right now, but if anybody complains it can be
> changed I guess. I don't like sbin that much because it's not in the
> default $PATH, and the tool most definitely _is_ useful even for users
> who can only read. Even iwconfig/iwlist is, in my opinion, misplaced in
> sbin.

Yep. I think either /usr/bin or /bin is most appropriate, but I just have this
feeling that someone will want their wifi to get /usr/ mounted sometime (this
is Debian, they want to do this crazy stuff all the time), which means that
using /bin now would cause less headaches in the future (when everyones scripts
are using absolute paths to /usr/bin/iw already...).

If that is a realistic scenario, it would leave the choice of the Debian iw
maintainer to a) say that use case is not possible, and stick to his guns, or
b) move iw to /bin and thus possibly diverge from what the rest of the
distro's, and you as upstream, are doing.

Thanks, Kel.