Linux bluetooth development
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Support for stored link keys
Date: Thu, 28 Apr 2005 19:28:20 +0100	[thread overview]
Message-ID: <1114712900.12012.365.camel@baythorne.infradead.org> (raw)
In-Reply-To: <1114094787.32265.11.camel@pegasus>

On Thu, 2005-04-21 at 16:46 +0200, Marcel Holtmann wrote:
> Another thing is if we should use /var/lib64/bluetooth on 64-bit
> platforms? What is the deal for the /var directory on these
> architectures?

Only arch-specific binary stuff which is 64-bit should go in lib64.
Since none of that should be in /var anyway, I think there is
no /var/lib64.


-- 
dwmw2




-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2005-04-28 18:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 14:46 [Bluez-devel] Support for stored link keys Marcel Holtmann
2005-04-21 15:55 ` Mitja Pufic
2005-04-21 16:07   ` Marcel Holtmann
2005-04-21 16:34     ` Mitja Pufic
2005-04-21 16:45       ` Marcel Holtmann
2005-04-22 22:26         ` Scott W Gifford
2005-04-22 22:55           ` Henryk Plötz
2005-04-23  0:00             ` Marcel Holtmann
2005-04-24 18:12         ` Fred Schaettgen
2005-04-21 16:37     ` Mitja Pufic
2005-04-28 18:28 ` David Woodhouse [this message]
2005-04-29  9:37   ` Marcel Holtmann

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=1114712900.12012.365.camel@baythorne.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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