location of binaries and libraries of new wifi tools
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.
Signature · 5 lines
Mierswa, Daniel
If you still don't like it, that's ok: that's why I'm boss. I simply
know better than you do.
--- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22Quoted 10 lines · Daniel Mierswa
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_supplicantand 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. But then you have to ask yourself, why are you using a network mounted /usr over wifi? That seems odd. Somebody turns on a microwave or starts to use a cordless phone and you're hosed.
Dan
Quoted 12 lines · Dan Williams
Quoted 10 lines · Daniel Mierswa
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_supplicantand 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.
Quoted 4 lines
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)
Quoted 6 lines · Dan Williams
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. But then you have to ask yourself, why are you using a network mounted /usr over wifi? That seems odd. Somebody turns on a microwave or starts to use a cordless phone and you're hosed.
Right, point taken. But why should there be a non-working binary in /sbin if you don't have /usr mounted. Couldn't we just stick all the tools in /usr/{s,}bin then?
Signature · 5 lines
Mierswa, Daniel
If you still don't like it, that's ok: that's why I'm boss. I simply
know better than you do.
--- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22Quoted 10 lines · Daniel Mierswa
Quoted 6 lines · Dan Williams
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. But then you have to ask yourself, why are you using a network mounted /usr over wifi? That seems odd. Somebody turns on a microwave or starts to use a cordless phone and you're hosed.
Right, point taken. But why should there be a non-working binary in /sbin if you don't have /usr mounted. Couldn't we just stick all the tools in
/usr/{s,}binthen?
So right now the libs I see from /usr/ that our new wireless tools may use is libnl and openssl (libgcrypt goes into /lib/ at least on my box), iw is already on /usr/sbin/ and crda can be moved to /usr/sbin/ if that makes everything peachy but just please note the udev rule will change location, which should be fine, it is just noted.
Luis