From: Dan Williams <dcbw@redhat.com>
To: Daniel Mierswa <impulze@impulze.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: location of binaries and libraries of new wifi tools
Date: Fri, 06 Feb 2009 23:41:11 -0500 [thread overview]
Message-ID: <1233981671.3652.6.camel@localhost> (raw)
In-Reply-To: <498CC07F.3080800@impulze.org>
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. 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
next prev parent reply other threads:[~2009-02-07 4:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 22:58 location of binaries and libraries of new wifi tools Daniel Mierswa
2009-02-07 4:41 ` Dan Williams [this message]
2009-02-07 7:29 ` Christoph Hellwig
2009-02-07 8:15 ` Daniel Mierswa
2009-02-07 20:49 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1233981671.3652.6.camel@localhost \
--to=dcbw@redhat.com \
--cc=impulze@impulze.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).