Subject: Re: [Bluez-devel] Support for stored link keys
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
In-Reply-To: <1114712900.12012.365.camel@baythorne.infradead.org>
References: <1114094787.32265.11.camel@pegasus>
	 <1114712900.12012.365.camel@baythorne.infradead.org>
Content-Type: text/plain
Message-Id: <1114767430.8836.34.camel@pegasus>
Mime-Version: 1.0
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Reply-To: bluez-devel@lists.sourceforge.net
Date: Fri, 29 Apr 2005 11:37:10 +0200

Hi David,

> > 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.

so using /var/lib/bluetooth or ${localstatedir}/lib/bluetooth is okay
for storing the link keys and other information?

Regards

Marcel


-------------------------------------------------------
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