How to become a HOL developer

To become a HOL developer, go to the project web site and sign-on as a new user by clicking on "New User via SSL" at the top left of the page. You will need to choose a name and password (name "my_name" and password "my_password" are used in what follows).

You should then email one of the project administrators requesting developer status. Currently the administrators are Michael Norrish ( and Konrad Slind (

When you have been authorised as a developer, you should login to Source forge

This will create your home directory. You should see something like this

 bass% slogin's password: my_password

 Warning: Remote host denied X11 forwarding.
 Creating home directory '/home/users/m/mj/my_name'.
 Linux usw-pr-cvs1 2.2.18pre11-va2.0-servers4 #1 SMP Thu Mar 29 20:48:12 PST 2001 i686 unknown

 Most of the programs included with the Debian GNU/Linux system are
 freely redistributable; the exact distribution terms for each program
 are described in the individual files in /usr/doc/*/copyright

 Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
 permitted by applicable law.

 Welcome to

 This is a restricted Shell Account
 You cannot execute anything here.

 Connection to closed.

If this fails with a message like

  The RSA1 host key for has changed,
  and the key for the according IP address
  is unknown. This could either mean that
  DNS SPOOFING is happening or the IP address for the host
  and its host key have changed at the same time.
  Someone could be eavesdropping on you right now (man-in-the-middle attack)!
  It is also possible that the RSA1 host key has just been changed.
  The fingerprint for the RSA1 key sent by the remote host is
  Please contact your system administrator.
  Add correct host key in /home/my_name/.ssh/known_hosts to get rid of this message.
  Offending key in /home/my_name/.ssh/known_hosts:9
  RSA1 host key for has changed and you have requested strict checkin

then you need to edit ~/.ssh/known_hosts (consult local system administrators for details).

Once you have created your home directory at SourceForge, you should be able to download hol98 by executing

 export CVS_RSH=ssh 
 cvs -z3 co hol98


> ... I want to check in some changes, but I get
> > cvs [server aborted]: "commit" requires write access to the
> > repository cvs commit: saving log message in /tmp/cvskmY8xG
> Is it me? What do I do?
I'd say you've checked your copy of the repository out anonymously,
rather than as a developer.

You need to follow the instructions on the lower half of the page 

or Mike's log at

If you get the following kind of message from SourceForge 

> Connection refused
> cvs [commit aborted]: end of file from server (consult above messages ...)

when attempting a cvs command then you need to do 

   export CVS_RSH=ssh

That's for bash. If you're using another shell, you'll have to find out
what the equivalent invocation is and execute it. 

> When I try to save my work to the cvs repository I often get
>     scrod% cvs ci
>     cvs commit: Examining .
>     cvs commit: Examining doc
> Connection refused
>     cvs [commit aborted]: end of file from server 
>     (consult above messages if any)
> If I try again later it usually works. This happens when others are
> able to use SourceForge without problems (i.e. I don't think it is due
> to SF being down).

I think it may be symptomatic of not having the CVS_RSH environment
variable correctly set to be ssh1.

No, ssh1 is a CLism (I think), and it is not even consistent on all CL
machines (eg. bass doesn't have one).  The correct fix is dependent on
the actual ssh implementation/instalation.  With OpenSSH (got my
recommondation) fix is to tweak your setup in .ssh/config (or
/etc/ssh/_ssh_config for site-wide configuration).  To be concrete, in
my .ssh/config I have the following line:

Protocol 1,2

at the top.  This might even be the correct fix for other ssh
implementations (I think it is).  But it *might* cause trouble if you
want to connect to a ssh using ssh protocol 2 (don't know because I
haven't needed that).

> should I fix
>  export CVS_RSH=ssh 
> to be
>  export CVS_RSH=ssh1
> in 


> [maybe with a comment saying use "ssh1" when that is the version being used]

But it might be there as a CL (machine) specific advice.