using read-only fs for ~/.gnupg ?

[Aaron D. Turner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I was wondering if anyone could give me any suggestions for setting up my
~/.gnupg dir on a read-only fs?  I'm using the --no-random-seed-file
option, but I'm still getting attempts to create temp files in the
directory.  So far, I haven't been able to determine any negative effects
of this, but it is a little worrisome.

Here's an example:
gpg: failed to create temporary file `/home/aturner/.gnupg/.#lk0x80da800.lager.1544': Read-only file system
gpg: fatal: /home/aturner/.gnupg/trustdb.gpg: can't create lock
secmem usage: 1632/1632 bytes in 3/3 blocks of pool 1632/16384

Thanks.

- -- 
Aaron D. Turner  Security Architect, OneSecure  http://www.onesecure.com/
aturner@onesecure.com  work: 408-992-8045  cell: 408-314-9874
pub  1024D/1B57EB4D 2000-09-27 Aaron D. Turner <aturner@onesecure.com>
     Key fingerprint = F90C BFB4 4404 5504 295D  4435 578B 1DD5 1B57 EB4D
All emails by me are PGP signed; an invalid signature indicates a forgery.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Public key 0x1B57EB4D at: http://www.keyserver.net/en/
Filter: gpg4pine 4.1 (http://azzie.robotics.net)

iEYEARECAAYFAjvQYO8ACgkQV4sd1RtX601juQCcCePYKwcmsf108P9JSYg8VVX+
3HAAn01InDUbj5W//pA3apylVkYb1/Vk
=rQbW
-----END PGP SIGNATURE-----