Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Apr 1998 01:44:55 +0200
From:      Eivind Eklund <eivind@yes.no>
To:        Peter Hawkins <peter@hilink.com.au>, cvs-committers@FreeBSD.ORG
Subject:   Re: cvs commit: CVSROOT avail
Message-ID:  <19980417014455.02651@follo.net>
In-Reply-To: <199804162158.OAA06012@freefall.freebsd.org>; from Jordan K. Hubbard on Thu, Apr 16, 1998 at 02:58:28PM -0700
References:  <199804162158.OAA06012@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 16, 1998 at 02:58:28PM -0700, Jordan K. Hubbard wrote:
> jkh         1998/04/16 14:58:27 PDT
> 
>   Modified files:
>     .                    avail 
>   Log:
>   Add Peter Hawkins <peter@hilink.com.au> to committers.  Welcome aboard,
>   Peter!  Erm.  I think that's enough committers for right now though - we're
>   growing too fast, ack! :)

Welcome aboard, Peter, 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 emergency, Cc:
to root@freebsd.org.  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 'easy-import' script on freefall).

Besides Peter Wemm, there are other officers you'll get to know:
    Satoshi Asami <asami@FreeBSD.ORG>
	A lean, mean ports-machine.  This guy owns the docking
	machinery (bsd.port.mk) which you are not allowed to touch
	without permission, and have ultimate authority over all
	modifcations to docking setups (ports).  Touch them when he's
	declared a hands-off, and you'll get your commit privileges
	suspended faster than you can say 'ports-freeze'.

    Jordan K Hubbard <jkh@FreeBSD.ORG>
	The usual takeoff-manager (release-engineer).  When you forget
	to merge good, wholesome changes from -current (HEAD) to
	-stable (at the moment RELENG_2_2 - not some magic number), it
	is Jordan who is most likely to get the extra work.  So
	remember to merge - he's overworked enough as it is.
	Jordan is also the guy who is constantly forgetting to set up
	forward files for new committers, so you'd probably be well of
	logging into hub.freebsd.org and setting /var/forward/tepish
	to point to where you want your mail to land.  There's
	probably some letters from your sweetheart waiting for you
	on hub already..

    Bruce Evans <bde@FreeBSD.ORG>
	Perfection police.  When you do a commit that could have been
	done better, Bruce will be there.  Even though it can be
	extremely annoying to be reminded of your own imperfections at
	all the in-opportune moments, Bruce is a good guy too.

    Garret Wollman <wollman@FreeBSD.ORG>
	If you speak some obscure network internals, and you think
	FreeBSD has a lithp somewhere, then Garret is likely a good
	person to know about - he's responsible for the overall state
	of FreeBSD networking internals.

... and some important 
    Steve Price <steve@FreeBSD.ORG>
	Steve is unofficial maintainer of /can - oh, typo - /bin, I
	mean.  If you're going to do something large to /bin (like
	merging everything from NetBSD or OpenBSD), you might be will
	of coordinating with Steve.  He's also Problem Report-meister.

    Brian Somers <brian@FreeBSD.ORG>
	Official maintainer of /usr/bin/ppp and LPD.  He's ten times
	as efficient as god on changing PPP, so if you intend to help
	out there, be prepared to feel quite inadequate as he end up
	doing everything.

(Anybody that feel left out - speak up.  I've just included the people
that I thought were likely to need their roles explained - no
significance attached).

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 thepish@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 Put 'ssh-agent sh ~/.xsession-real' in ~/.xsession after having
    copied your old .xsession to .xsession-real.
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.  No commiter has ever screwed up.  :-)


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.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980417014455.02651>