On Sat, 2008-09-20 at 06:34 +1000, Kel Modderman wrote: > Indeed, I added a Conflicts: aircrack-ng to the debian/control file because > of this when preparing the package this afternoon. What aircrack-ng is doing > makes iw look bad for breaking policy: > > Section 2.5 Priorities > "Note that optional packages should not conflict with each other." Heh. > Once the bastard iw is removed from aircrack-ng, the Conflicts field can have a > version conditional added to it. Right. > 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. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part