(Illustration by Gaich Muramatsu)
Hi, My apologies for using a lot of list bandwith in the last few days. :-/ I'm trying to use Coda for home directories, but if logging into Coda using clog username, there's a chicken and the egg problem with putting that into the user's .bashrc (because that lives in the home directory, which is in Coda, which cannot be accessed until the user has logged in). Is there an official method of working around this? I'd prefer not to have 2 separate lots of home directories, one for startup and one for actual data. Also, home directories would need to remain accessible to users' accounts between logins, so their cron jobs can run with access to their files. How can this be achieved? The next question that arises is how to authenticate Coda from a centralized user database, so as to make it transparently fit with the rest of the system (authenticating via NIS, or LDAP/Kerberos). I have seen references to both NIS and Kerberos being used in the list archives, but I've yet to find any documentation that explains how to set it up. Is there such a piece of documentation somewhere that somebody could point me at, please? Many thanks. GordanReceived on 2008-01-31 06:27:13