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

I have successfully installed coda running on a Debian server and
laptop.  Running through the documentation helped me get a working root
volume and two other volumes, a private volume for storage of group wide
information that all privileged users will have access to, and my own
$HOME directory for my laptop.  Everything works great as long as I am
connected to the network when I startup and issue a clog as my user.

However, my question is, how do I go about being able to use my coda
HOME directory when I startup disconnected from the network.  I am not
able to use clog to successfully get a token in that case and thus am
not able to gain access to my HOME directory.  I am able to login to the
laptop, but I get dumped into the root (/) directory as my HOME
directory (my HOME directory is a symlink from /home/<user> ->
/coda/domain.name/users/<user>).  There are references to having a coda
volume as a users HOME directory but not any examples (that I've found
in the documentation or the mailing lists), so I subscribed to the
mailing list to ask whether this is even feasible or not.  I can't
imagine how to get a clog token from the authentication server after
logging in when I have to login in order to issue clog as my user.  :)

I did find pam_kcoda.so and downloaded and installed that tarball.  I
set it up according to the example in the README, but it doesn't seem to
have any effect, even when fully connected.  I am still logged into the
/ directory initially, but then after a clog and successful
authentication and logout, when I log back in, I am able to successfully
use my coda directory as my HOME directory (which I am doing now to
write this e-mail).

Thanks for any tips/pointers.  I've even had the idea of setting up a
local auth2 server on the laptop with just the groups and users
information to allow the primary user of the laptop(s) to login to their
respective laptop and clog to their localhost, etc. to be able to use
hoard'ed/cached copies of their HOME directory files.

Thanks again.
- --
Jason A. Pattie
pattieja_at_xperienceinc.com
Xperience, Inc. (http://www.xperienceinc.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFABs3YuYsUrHkpYtARAv6rAJ0XlvWnjbqpkCcxEHWg/04nrToz+wCeLdaA
vciMBHNiLRCK1+sd1T6uHc4=
=PkHu
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.