Date: Fri, 27 Feb 1998 10:13:02 +0100 From: Eivind Eklund <eivind@yes.no> To: "Jordan K. Hubbard" <jkh@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-CVSROOT@FreeBSD.ORG Subject: Re: cvs commit: CVSROOT avail Message-ID: <19980227101302.39170@follo.net> In-Reply-To: <199802261914.LAA27102@freefall.freebsd.org>; from Jordan K. Hubbard on Thu, Feb 26, 1998 at 11:14:39AM -0800 References: <199802261914.LAA27102@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 26, 1998 at 11:14:39AM -0800, Jordan K. Hubbard wrote:
> jkh 1998/02/26 11:14:39 PST
>
> Modified files:
> . avail
> Log:
> Please welcome Nik Clayton to the FreeBSD Docs project!
Wild cheers erupt! (... We want docs! ... We want docs! ... We want
docs! ... from the audience)
Welcome aboard, Nik, and thanks for going with FreeBSD Spacetours.
Your CVS-meister will be Peter Wemm <peter@freebsd.org> - take any
repository-related problems with him. Patching the hull yourself (AKA
writing directly to the repository) is strictly not allowed without
prior permission; this include all cases. In case of emergence, Cc:
to root. Be aware of the severe implications of running a blow-torch
('cvs import') in the ship - it might sometimes be necessary, but we
really recommend using Joergs new blowtorch with safety features (the
'easyimport' script on freefall).
For your convenience, we repeat some of the magic tricks of using CVS
with SSH below:
1. Always use ssh public key authentication with agents to work
against freefall. This is (a) secure and (b) extremely convenient.
Details below.
2. Set your CVS_RSH=ssh
3. Store your local CVS-repository in /home/ncvs, as freefall hasn't
got a /home/FreeBSD alias, so you can't store the repository
anywhere intuitive. (Well, OpenBSD doesn't implement
/home/OpenBSD, either - they're worse...)
4. Set alias lcvs='cvs -d /home/ncvs'
5. Set alias fcvs='cvs -d nik@freefall.freebsd.org:/home/ncvs'
Now, use lcvs to checkout/diff/update locally, and when you want to
commit to freefall, use fcvs commit in the same directory. Remember:
Doing a 'lcvs diff' before you commit is usually a good idea.
6. (Vary depending on preferences only)
echo 'diff -u' > ~/.cvsrc'
echo 'update -Pd' >> ~/.cvsrc'
will give you unified diffs and pruned updates with directories.
You'll probably want these two options.
Now, for the ssh-setup (if you haven't done this already):
1.1 Run your window-manager as 'ssh-agent afterstep' (if you're
running afterstep; replace to taste). If you're not running a
window-manager, run your shell through ssh-agent.
1.2 Generate an ssh private/public key pair by running 'ssh-genkey'
1.3 Copy the public part of the key (~/.ssh/identity.pub) to
freefall:/home/nik/.ssh/authorized_keys
Now, when you want to get ready for authentication, run
1.3 'ssh-add' to add your private key to the authentication agent.
Take particular note of the neat X-display if you run 'ssh-add <
/dev/null' - I have this in my startup. (I am in a fairly secure
environment, and I lock my display any time I leave my machine).
After having stored your key in the authentication-agent (step 1.3
above), just ssh to the places you've added your identity.pub to -
you'll be authenticaten through your agent, no passwords. The same
goes for secure remote `cvs commit's.
Oh, and when you fix the fact that somebody else have delivered a
report of a leak in the ship or a suggestion for an improvement[1],
you can run 'edit-pr <pr-number>' on freefall to close it.
Relax now - the impending takeoff will be at your hands, but it will
_not_ include any mutilated bodies on the ground (AKA world-breakages)
or bodies falling from the sky (AKA release-breakages). Everything
will be just fine. :-)
Starship Mate Eivind signing off.
[1] Both are known as Problem Reports, or PRs for short - this is
because they give the committers extra problems.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980227101302.39170>