On Fri, Feb 06, 2009 at 11:41:11PM -0500, Dan Williams wrote: > On Fri, 2009-02-06 at 23:58 +0100, Daniel Mierswa wrote: > > Hey list, I was wondering where to put binaries for the new > > wireless-stack based tools. Most default installations put libnl, crypto > > and gcrypt into /usr. Applications like iw, wpa_supplicant and crda need > > those to run, yet they do not link statically. So if the default > > location for the new binaries is /sbin or /bin and the libraries it > > links against are default installed somewhere into /usr things will > > break. I wonder now what to do for consistency. Either statically link > > libraries that are default installed into /usr, put those libs into /lib > > or install the binaries into /usr aswell. I'd appreciate any comments on > > that. :) Thanks and have a nice weekend. > > Stuff in /bin or /sbin can certainly link to stuff in /usr without > breaking. The only time it breaks is when you're using network > mounted /usr and you need the wireless stack to boot the machine and > mount /usr. Which is a tradeoff to make. But when you decide mounting /usr using wireless networks is not viable you shoiuld just move the tools to /usr/bin & /usr/sbin instead. Having tools in /bin and & /sbin that need libraries from /usr/lib is not a good idea as it violates the basic assumptions (and doesn't actually help anything over having the tools in /usr/bin & /usr/sbin) -- 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
