From: Christoph Hellwig <hch@infradead.org>
To: Dan Williams <dcbw@redhat.com>
Cc: Daniel Mierswa <impulze@impulze.org>, linux-wireless@vger.kernel.org
Subject: Re: location of binaries and libraries of new wifi tools
Date: Sat, 7 Feb 2009 02:29:35 -0500 [thread overview]
Message-ID: <20090207072935.GA27869@infradead.org> (raw)
In-Reply-To: <1233981671.3652.6.camel@localhost>
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)
next prev parent reply other threads:[~2009-02-07 7:29 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
2009-02-07 7:29 ` Christoph Hellwig [this message]
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=20090207072935.GA27869@infradead.org \
--to=hch@infradead.org \
--cc=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).