Location: Buenos Aires, Argentina.
@@ -406,258 +529,17 @@ Problems with a server should be reported to the maintainer of the server in question. -
Getting crypto sources through -cvs(1)
--IMPORTANT NOTE: -There are a few issues relating to cryptographic software that everyone -should be aware of: -
-
-
- The OpenBSD sources are from Canada.
-As
-
- researched by a Canadian individual
-and as
-
- described in the Export Control list of Canada
-it is legal to export crypto software from Canada to the world.
-
-
- However, if you are outside the USA or Canada, you should not
-fetch the cryptographic sections of the OpenBSD sources from an
-anoncvs server located in the USA. The files in question are...
-
-
-
- src/kerberosIV/* -
- src/kerberosV/* -
- src/lib/libdes/* -
- src/lib/libc/crypt/crypt.c -
- src/lib/libc/crypt/morecrypt.c -
- src/sys/crypto -
- src/sys/netinet -
- src/usr.sbin/afs/src/rxkad/* -
- XF4/xc-mit/lib/Xdmcp/Wraphelp.c -
- XF4/xc-old/lib/Xdmcp/Wraphelp.c -
- XF4/xc/lib/Xdmcp/Wraphelp.c -
Example usages for cvs(1) -
- -
-NOTICE: If you want to update a branch (such as a patch branch)
-to current, you would add the -A
-flag to cvs, but this flag is of little use otherwise. Some older
-versions of the OpenBSD documentation recommended use of this flag
-in many examples. We no longer recommend this flag unless absolutely necessary.
-
-
-A sample use of an anoncvs server would be: -
-$ cd /tmp -$ cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs get src/sys/arch/sparc - [copies the files from the repository to your machine] -$ cd src/sys/arch/sparc -$ cvs log locore.s - [shows the commit log for the chosen file] -$ cvs diff -bc -r1.1 -r1.5 locore.s - [shows the changes between revisions 1.1 and rev 1.5] -- -
-$ cvs -d :pserver:anoncvs@anoncvs.ca.openbsd.org:/cvs login -(Logging in to anoncvs@anoncvs1.ca.openbsd.org) -CVS password: anoncvs - [This writes a line to ~/.cvspass (filename over-ridden by CVS_PASSFILE).] - [An example line from my ~/.cvspass after typing 'blah' for the above ] - [password is: ] - [:pserver:anoncvs@anoncvs5.usa.openbsd.org:/cvs Au'yc ] - [After logging in ONCE every other use of the above CVSROOT will work. ] -$ cvs -d :pserver:anoncvs@anoncvs.ca.openbsd.org:/cvs get ksrc-i386 ksrc-common - [Allows you to retrieve ONLY that necessary to rebuild an i386 kernel. ] -- -
-Here is how someone using anoncvs regularly would update his -source tree: -
- First, start out by `get'-ing an initial tree:
-
-
(If you are following current): -
- # cd /usr - # cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -P src -
- -(If you are following the patch branch for 5.1): -
- # cd /usr - # cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_5_1 -P src -
- - - Anytime afterwards, to `update' this tree:
-
(If you are following current): -
- # cd /usr/src - # cvs -q up -Pd -
- -(If you are following the patch branch for 5.1): -
- # cd /usr/src - # cvs -q up -rOPENBSD_5_1 -Pd -
- -Every time you ran this it would synchronize your /usr/src tree. It would -not destroy any of your local changes, rather it would attempt to merge -changes in. - --
- NOTE:
-If you are updating a source tree that you initially fetched
-from a different server, or from a CD, you must
-add the -d anoncvs@anoncvs.ca.openbsd.org:/cvs options to cvs.
-
- # cd /usr/src - # cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs -q up -Pd -
-
-To use ports, -it is similar to src: -
-
-
(If you are following current): -
- # cd /usr - # cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -P ports -
-(If you are following the patch branch for 5.1): -
- # cd /usr - # cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_5_1 -P ports -
- - Anytime afterwards, to `update' this tree:
-
(If you are following current): -
- # cd /usr/ports - # cvs -q up -Pd -
-(If you are following the patch branch for 5.1): -
- # cd /usr/ports - # cvs -q up -rOPENBSD_5_1 -Pd -
-
-To make a diff of a locally patched module (here cd.c) to include with -a bug report: -
- # cd /usr - # cvs diff -u src/sys/scsi/cd.c > /tmp/patch -- -
-The -cvs(1) man page -(included with the CVS sources) has much more -information about how CVS can be used. - -
-Warning: -When using cvs you should take care that your current directory is either -the root of the tree you are referencing or in a separate place such as /tmp. -Some commands such as "get" can create an arbitrary sub-tree in the current -directory, and a subsequent update will recursively flesh out this sub-tree. - -
-The anoncvs service gives fledgling developers a chance to learn CVS -operation and get thoroughly involved in the development process -before getting "commit" access -- as a result of showing useful -skills and high quality results they will naturally later be given -developer access. As well, people providing patches can create -their "diff"s relative to the CVS tree, which will ease integration. - - -
Use rsh(1) or ssh(1)?
- -CVS supports three access methods between the CVS server and the CVS -client: - --
-
- ssh: Secure Shell can be used to access the anonymous CVS servers. -This is the recommended way of doing so, as it is encrypted. - -
- rsh: Remote Shell can be used on some of the servers for users -who don't have access to ssh. - -
- pserver: pserver is primarily useful for users who are behind -firewalls that block the other two connections. -
-NOTE: For users wishing to use rsh, you must first set the -CVS_RSH environment variable to point to the rsh(1) program: - -
-
-
- For Korn/Bourne shells:
-
- $ export CVS_RSH=/usr/bin/rsh -
- - For csh/tcsh:
-
- % setenv CVS_RSH /usr/bin/rsh -
-
-By default, OpenBSD's CVS client uses ssh ("secure shell": -OpenSSH) to talk to the CVS server. - -
-Many of the CVS sites no longer support rsh or pserver for security reasons. -Local -problems like firewalls or imperfect protocol emulators such as slirp may -also hinder rsh usage. However, if rsh is desired, one must set the -CVS_RSH environment variable to point to rsh -(typically /usr/bin/rsh). - -
If local policy prevents outgoing connections to ssh's default port of 22, -port 2022 may be used in its place. Note, however, that not all anoncvs -servers accept ssh connections on this port. Furthermore, most anoncvs servers -no longer accept the none cipher, as it is disabled in -recent versions of ssh for security reasons. Also, do not be tempted -to turn on compression: CVS already compresses. - -
-One could specify something like the following in the -$HOME/.ssh/config configuration file to avoid the pitfalls -and restrictions mentioned above: +some servers permit connections on an alternative port (typically 2022). +These are noted in the list above. +To use a different port, reconfigure your ssh client by adding a "Host" +entry to $HOME/.ssh/config, e.g.:
- Host anoncvs.ca.openbsd.org - Compression no - Port 2022 + Host anoncvs.ca.openbsd.org + Port 2022-
-CVS is a little noisy starting up; to quiet it a bit you may want to -do this: - -
- $ export CVS_CLIENT_PORT=-1 --
Setting up an anoncvs mirror
@@ -674,7 +556,7 @@ document which describes the setup of anoncvs servers is available. -Final notes
+Final notes
After upgrading your source tree, you should read the comments at the top of /usr/src/Makefile before attempting a build. Also, you should build a new kernel before @@ -692,7 +574,7 @@
www@openbsd.org
-$OpenBSD: anoncvs.html,v 1.369 2012/06/06 15:53:33 sthen Exp $ +
$OpenBSD: anoncvs.html,v 1.370 2012/09/08 21:07:47 rpe Exp $