[BioPython] backups boring but essential

Andrew Dalke dalke@bioreason.com
Mon, 20 Sep 1999 11:37:14 -0600

Ewan said:
> CVS effectively backs up the code over multiple locations. There are
> probably 5/6 active cvs repositories out there.

Which reminds me, how do I use CVS "transparently" from my
remote machine without having to give my password every time?

I set it up to use ssh as the connection method, as given in
(CVS_RSH is set to ssh) and I can do checkin/checkout/update,
but every time it wants to make a connection, I have to give it
my password.

This means I can't work inside emacs using its version control
submode, since it doesn't understand passwords.

Reading the man page shows that there is a .shosts file which
is the equivalent of .rhosts, but I can't make it work.

Here are some possible problems:
  * my client is a 1.x version, not 2.x as on the server
val> ssh -V
SSH Version 1.2.26 [mips-sgi-irix6.5], protocol version 1.5.
Standard version.  Does not use RSAREF.

As I understand it, ssh 2.x for commercial use requires some
sort of license.

  * connections are forwarded through a gateway, so it looks
like I'm coming from a different machine than I'm really at,

  * my primary machine isn't reverse DNS-able

  * identd isn't running on the gateway machine

  * I don't understand if there's anything I need to do with
respect the info at http://www.tac.nyc.ny.us/~kim/ssh/ and
creating keys.

  To be back on topic, since it's cumbersome to make the CVS
connection, I often end up working directly on biopython.org, and
hence there is no redundancy.