BJ> Received.....  See routed netmail reply.  Once I get reconfigured, 
 BJ> see direct netmail reply.

 BS> See that.

Good....

 BJ> While you sent me the info, I now have dug through the sourceforge 
 BJ> documentation and I think I am now configured with proper 
 BJ> authenication between sourceforge and my development system.....  It 
 BJ> can take up to six hours to get thata part setup 
 BS> on source forge.....  

 BS> well:

 BS> export CVS_RSH=ssh
 BS> export CVSROOT=....
 BS> cvs login
 BS> cvs commit dir/

Didn't catch the two export lines.....  CVS_RSH line now in my .bash.rc,
and I've made an attempt at the CVSROOT line that seems to be working with
my account.  Still requests a password on the cvs login -- must be to cvs
and not the SSH password question, because a cvs co maximus is running with
out the password request....

Hmmm....  I'm getting an invalid root path on the CVS chechkout, but it
seems to be proceeding to work correctly.....  Wonder what I've got setup
incorrectly?  I recall something I hit the first time running CVS may be
the issue.....

The six hours is to get the SSH stuff loaded across all the source forge
machines.  I manually forced what was needed to the shell machine, but that
doesn't help the other machines.....  Without that I believe I get hit with
too many prompts for my password....

I'll need to discuss the changes with you.  You're doing a few things I
wasn't expecting....  And one or two files that are "different' seem
to be just white space changes.....

 BJ> Have you thought about registering as a developer on SourceForge?

 BS> I'm a registered developer, i've also worked on some 
 BS> projects, but wes haven't give me the rights to commit to the project.

Ok....  Any reason we shouldn't ask Wes to add you as a developer in the
SourceForge project?  I cann't since I only asked Scott for developer
access and didn't ask for admin permission on the project when I contacted
him for access.....

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01