-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathanoncvs.html
729 lines (648 loc) · 27.9 KB
/
anoncvs.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
<!-- DO NOT EDIT MANUALLY! See comments in www/build/mirrors.dat for details -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>OpenBSD AnonCVS</title>
<link rev="made" href="mailto:[email protected]">
<meta name="resource-type" content="document">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="description" content="How to get OpenBSD updates via Internet using Anonymous CVS">
<meta name="keywords" content="openbsd,anoncvs,updates">
<meta name="distribution" content="global">
<meta name="copyright" content="This document copyright 1996-2009 by OpenBSD.">
</head>
<body bgcolor="#ffffff" text="#000000">
<a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
<p>
<h2><font color="#e00000">Anonymous CVS</font></h2>
<hr>
<h3>Table Of Contents</h3>
<ul>
<li><a href="#anoncvs">What is Anonymous CVS?</a>
<li><a href="#CVS">What is CVS?</a>
<li><a href="#starting">Getting Started Using Anonymous CVS</a>
<li><a href="#using">Using CVS to Get and Update your Source Tree</a>
<li><a href="#CVSROOT">Available Anonymous CVS Servers</a>
<li><a href="#CRYPTO">Getting crypto sources through cvs(1)</a>
<li><a href="#EXAMPLE">Example usages for cvs(1)</a>
<li><a href="#WHICH">Use rsh(1) or ssh(1)?</a>
<li><a href="#SUP">Mirroring the CVS repository via sup(1)</a>
<li><a href="#MIRROR">Setting up an anoncvs mirror</a>
</ul>
<hr>
<h3><a name="anoncvs"><font color="#0000e0">What is Anonymous CVS?</font></a></h3>
<p>
Anonymous CVS is a method of keeping your local copy of the OpenBSD source
tree up to date with respect to changes made to current OpenBSD sources.
In addition to following the bleeding edge of development, it is
also possible to track the patches for errata of a release.
<p>
The major advantage of Anonymous CVS over other source code update
techniques is that it works directly against a central source code
repository or mirror. This means that you have the full set of CVS
commands available to control merging and updating your changes with
other source changes and for performing diffs, change histories
and other queries against the central repository.
<p>
The OpenBSD Project currently has four active and two historic
source repositories:
<ul>
<li><b>src</b> - Houses all source code for the OpenBSD Operating System.
<li><b>ports</b> - Houses the <a href="./ports.html">OpenBSD Ports</a>.
<li><b>www</b> - Houses all OpenBSD web pages. (Including this one).
<li><b>xenocara</b> - Houses OpenBSD's active X.org v7 source tree.
<li><b>X11</b> and <b>XF4</b> - Houses OpenBSD's adaptation of the
<a href="http://www.XFree86.org/">XFree86-3</a> and XFree86-4
source trees.
These are here just for historical purposes, most users will have
no reason to use this tree, it is no longer being used.
</ul>
<p>
To summarize, the real strength of using Anonymous CVS is that it is
a "tolerant" source code control system - it <strong>respects</strong>
changes that you have made to your local sources and makes <strong>
"best efforts"</strong> to update your entire source tree, rather than
leaving you a list of arcane problems that have to be resolved before
continuing.
<h3><a name="CVS"><font color="#0000e0">What is CVS?</font></a></h3>
<p>
<a href="http://ximbiot.com/cvs/">CVS</a> is the source code control
system used to <a href="why-cvs.html">manage the OpenBSD source
tree.</a>
It implements a central repository for all officially released source code
and changes, while permitting developers to maintain local copies of the
source code with their working changes.
There are two levels of source tree access:
<ul>
<li><b>Read-write access for developers:</b>
Developers who need to commit changes to the source tree must have an
account on the OpenBSD machines.
Getting this access will be a natural result of working on the sources
with other OpenBSD developers.
If someone does some good work and shows they can work with the team,
they will get an account.
<li><b>Read-only access for everyone:</b>
Anyone can access the read-only CVS repositories.
These copies of the read-write CVS repository are mirrored often.
</ul>
<p>
The major strength of CVS is that it has the ability to perform intelligent
merges of changes to the central repository with changes that you make to
your local copy. This means that if you make a change to a module and
perform an update, your changes are not "blown away", rather CVS makes
best efforts to merge the changes made to the central sources with changes
you've made to your local copy.
<p>
In the event that the changes can't be completely merged, CVS provides a
"soft fallback", providing you with annotated changes to your
local copy, preserving an unmodified copy of your version and continuing
to update any other source modules you requested.
<h3><a name="starting"><font color="#0000e0">Getting Started Using Anonymous
CVS</font></a></h3>
While you can download the entire source tree from an AnonCVS server,
you can often save a lot of time and bandwidth by "preloading" your
source tree with the source files from either the OpenBSD CD or from an
FTP server.
This is particularly true if you are running
<a href="stable.html"><i>-stable</i></a>, as relatively few files change
between the <i>-release</i> and <i>-stable</i>.
<p>
To extract the source tree from the CD to <i>/usr/src</i> (assuming the CD is
mounted on /mnt):
<pre>
# <b>cd /usr/src</b>
# <b>tar xzf /mnt/src.tar.gz</b>
# <b>cd /usr</b>
# <b>tar xzf /mnt/xenocara.tar.gz</b>
# <b>tar xzf /mnt/ports.tar.gz</b>
</pre>
The source files for download from the FTP servers are separated into two
files to minimize the time required to download for those wishing to work
with only one part of the tree. The two files are <tt>sys.tar.gz</tt>,
which contains the files used to create the kernel, and <tt>src.tar.gz</tt>
which contains all the other "userland" utilities.
In general, however, you will usually want both of them installed.
Assuming the downloaded files, <tt>src.tar.gz</tt>,
<tt>sys.tar.gz</tt> and <tt>xenocara.tar.gz</tt> are in <tt>/usr</tt>:
<pre>
# <b>cd /usr/src</b>
# <b>tar xzf ../sys.tar.gz</b>
# <b>tar xzf ../src.tar.gz</b>
# <b>cd /usr</b>
# <b>tar xzf xenocara.tar.gz</b>
# <b>tar xzf ports.tar.gz</b>
</pre>
<p>
Not all people will wish to unpack all the file sets, but as the system
must be kept in sync, you will generally need to set up all trees.
<p>
You can also just use cvs(1) to "<b>checkout</b>" the source repository
for you. This is discussed in the <a href="#using">next section</a>.
<p>
After this, <tt>/usr/src</tt> will be a nice checkout area where all
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&sektion=1&format=html">
cvs(1)</a> commands will work properly.
<h3><a name="using"><font color="#0000e0">Using CVS to get and update your
source tree</font></a></h3>
<p>
CVS was designed to be a simple way to retrieve and update your sources.
You must first decide whether you want to track <i>-current</i> or a
<a href="stable.html">patch branch</a>.
The current tree has all of the up to the minute changes,
whereas a patch branch contains a formal release plus the patches
from the <a href="errata.html">errata</a> and lesser issues already applied.
For more information on these "flavors" of OpenBSD, see
<a href="faq/faq5.html#Flavors">here</a>.
<p>Once you have decided which tree to follow, you must choose which Anonymous
CVS server you are going to use. A list of these servers is
<a href="#CVSROOT">below</a>.
<p>
Once you have chosen which <a href="#CVSROOT">Anonymous CVS Server</a> you will
use, you can start using cvs. For those of you
who have CDs you can start with the CVS checkout that is on the CD by using
the method <a href="#starting">above</a> to get the sources onto your system.
If you don't have a CD handy, use the method below to checkout the sources.
This method puts the OpenBSD source tree into <i>/usr/src</i>.
<pre>
# <b>cd /usr; cvs checkout -P src</b>
</pre>
<p>
The above will checkout the <i>current</i> source tree. Many of you will
only want the patch branch sources. To checkout a patch branch, you must
specify a tag along with your command. Example:
<pre>
# <b>cd /usr; cvs checkout -P -rOPENBSD_4_6 src</b>
</pre>
<p>
Or OPENBSD_4_5 for 4.5, etc.
<p> The OPENBSD_4_6 tag contains the release sources and
errata already applied.
<h3><a name="CVSROOT"><font color="#0000e0">Available Anonymous CVS Servers
</font></a></h3>
<p>
<em>Please see the note about <a href="#WHICH">ssh vs. rsh</a> below!</em>
<p>
<ul>
<li><strong>[email protected]:/cvs</strong><br>
Location: Paris, France.<br>
Maintained by <a href="mailto:[email protected]">Landry Breuil</a>.<br>
Protocols: ssh.<br>
Updated every 2 hours from anoncvs1.ca.openbsd.org.<br>
SSH fingerprints:<br>
(RSA1) 2048 28:ce:6b:61:76:d9:0e:6d:65:a1:5c:dd:e8:d7:57:42<br>
(RSA) 2048 89:2e:84:9e:0c:f9:8d:21:41:0e:c5:80:41:27:14:c1<br>
(DSA) 1024 7f:fb:68:2f:0f:c8:63:6c:0f:32:2c:03:d4:cd:0c:47<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: Stockholm University, Stockholm, Sweden.<br>
Maintained by <a href="mailto:[email protected]">Janne Johansson</a>.<br>
Protocols: ssh.<br>
Updated every 2 hours.<br>
SSH fingerprints:<br>
(RSA) 2048 98:e6:80:5d:95:bb:e2:15:5e:19:4d:a3:e4:d0:bc:2c<br>
(DSA) 2048 4c:d2:0a:90:b8:95:5d:37:3b:32:7b:77:5a:c5:ef:26<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Host also known as <strong>anoncvs.usa.openbsd.org, anoncvs4.usa.openbsd.org</strong>.<br>
Location: Internet Software Consortium, Redwood City, CA, USA.<br>
Maintained by <a href="mailto:[email protected]">Todd C. Miller</a>.<br>
Protocols: rsh, ssh, ssh port 2022, pserver.<br>
Updated every 2 hours.<br>
SSH fingerprints:<br>
(RSA1) 1024 64:de:26:16:c2:ff:1b:c7:24:ed:a4:4a:d7:2f:69:3e<br>
(RSA) 1024 49:67:9a:46:62:8a:3f:4e:b3:63:ca:d6:41:29:2a:2f<br>
(DSA) 1024 a7:75:49:77:f3:47:d1:3c:5e:65:84:84:3b:03:f1:33<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: National Center for Atmospheric Research, Boulder, CO, USA.<br>
Maintained by <a href="mailto:[email protected]">Todd C. Miller</a>.<br>
Protocols: rsh, ssh, ssh port 2022, pserver.<br>
Updated every 2 hours.<br>
SSH fingerprints:<br>
(RSA1) 2048 80:cd:f6:fc:4f:0e:cb:80:6a:d0:6a:5e:dd:9e:5d:0a<br>
(RSA) 2048 49:6f:4a:be:02:63:0d:c0:54:b0:57:f0:48:7f:ce:16<br>
(DSA) 1024 f9:ab:fc:60:a3:15:8f:9c:47:24:9e:92:15:78:0d:f3<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: Michigan Technological University, Houghton, Michigan, USA.<br>
Maintained by <a href="mailto:[email protected]">Chris Linn</a>.<br>
Protocols: ssh.<br>
Updated every 2 hours.<br>
SSH fingerprints:<br>
(RSA1) 2048 d7:91:a2:f4:d2:8d:81:7f:3c:44:91:8f:b5:b9:46:48 <br>
(RSA) 2048 de:f1:09:85:a0:db:60:97:d4:95:0d:07:80:4e:ee:68<br>
(DSA) 1024 78:05:5c:c7:ce:7e:6f:c8:6d:b7:e2:7e:ba:06:1c:40<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: Vienna, Austria.<br>
Maintained by <a href="mailto:[email protected]">Martin Reindl</a>.<br>
Protocols: ssh, ssh port 2022.<br>
Updated every 2 hours from anoncvs1.usa.openbsd.org.<br>
SSH fingerprints:<br>
(RSA) 2048 e4:a7:3a:ab:e1:a7:c8:eb:5c:f4:ff:38:95:6f:81:f2<br>
(DSA) 2048 66:03:a3:bc:46:85:f3:6c:4b:6b:e3:d4:f5:5f:a6:c4<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Host also known as <strong>anoncvs.ca.openbsd.org, openbsd.sunsite.ualberta.ca</strong>.<br>
Location: Edmonton, Canada.<br>
Maintained by <a href="mailto:[email protected]">Bob Beck</a>.<br>
Protocols: ssh, ssh port 2022.<br>
Updated every 2 hours.<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: Toronto, Canada.<br>
Maintained by <a href="mailto:[email protected]">Brad Smith</a>.<br>
Protocols: ssh, ssh port 2022.<br>
Updated hourly.<br>
<p>
<li><strong>[email protected]:/OpenBSD</strong><br>
Location: Elion, Tallinn, Estonia.<br>
Maintained by <a href="mailto:[email protected]">Rivo Nurges</a>.<br>
Protocols: ssh.<br>
Updated every 2 hours from cvsync.de.openbsd.org.<br>
SSH fingerprints:<br>
(RSA) 1024 e1:12:fb:6b:e5:c0:6a:b3:f8:ca:b1:4c:20:fb:5e:07<br>
(DSA) 1024 bb:5c:44:f4:d9:12:3b:22:08:a9:12:c5:0c:e7:db:49<br>
<p>
<li><strong>[email protected]:/cvs/openbsd</strong><br>
Location: Paris, France.<br>
Maintained by <a href="mailto:[email protected]">Frank Denis</a>.<br>
Protocols: ssh, ssh port 2022.<br>
Updated every 2 hours from anoncvs3.usa.openbsd.org.<br>
SSH fingerprints:<br>
(RSA1) 2048 4d:60:d8:ab:bc:c6:29:64:b4:45:1b:98:2b:fe:40:7e<br>
(RSA) 2048 01:f1:c4:25:c8:e3:0d:0e:7a:33:94:14:f4:9d:98:5f<br>
(DSA) 2048 73:36:41:46:fd:0a:67:df:e6:c1:4a:6b:02:61:f4:61<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: Nürnberg, Germany.<br>
Maintained by <a href="mailto:[email protected]">Armin Wolfermann</a>.<br>
Protocols: ssh.<br>
Updated every 3 hours.<br>
SSH fingerprints:<br>
(RSA) 1024 f2:73:d2:f6:e3:01:ef:ca:3b:e7:6c:80:b6:bd:bb:84<br>
(DSA) 1024 fb:33:05:62:96:20:cf:88:7e:10:cb:8d:91:72:57:32<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: Budapest, Hungary.<br>
Maintained by <a href="mailto:[email protected]">Robert Nagy</a>.<br>
Protocols: ssh.<br>
Updated every 3 hours from anoncvs.de.openbsd.org.<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Host also known as <strong>kankoromochi.econ.nagasaki-u.ac.jp</strong>.<br>
Location: Nagasaki University, Faculty of Economics, Nagasaki, Japan.<br>
Maintained by <a href="mailto:[email protected]">Suzuki Itoshi</a>.<br>
Protocols: ssh, pserver.<br>
Updated every 3 hours.<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: TVK, Cable TV and Internet Services, Taurage, Lithuania.<br>
Maintained by <a href="mailto:[email protected]">Donatas Budvytis</a>.<br>
Protocols: ssh.<br>
Updated every 3 hours from cvsup.no.openbsd.org.<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Host also known as <strong>cvs.inet.no</strong>.<br>
Location: Oslo, Norway.<br>
Maintained by <a href="mailto:[email protected]">Karl-Andre' Skevik</a>.<br>
Protocols: ssh, ssh port 2022.<br>
Updated every 4 hours.<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: Warsaw, Poland.<br>
Maintained by <a href="mailto:[email protected]">Piotr Klein</a>.<br>
Protocols: ssh.<br>
Updated every 3 hours.<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Host also known as <strong>nina.kerberos.si</strong>.<br>
Location: Ljubljana, Slovenia.<br>
Maintained by <a href="mailto:[email protected]">Mitja Muzenic</a>.<br>
Protocols: ssh.<br>
Updated every 2 hours.<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: Stockholm, Sweden.<br>
Maintained by <a href="mailto:[email protected]">Viktor Holmlund</a>.<br>
Protocols: ssh.<br>
Updated every 3 hours from rsync.de.openbsd.org.<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: Institute of Neuroinformatics, University of Zurich, Zurich, Switzerland.<br>
Maintained by <a href="mailto:[email protected]">Stephan A. Rickauer</a>.<br>
Protocols: ssh, ssh port 2022.<br>
Updated every 2 hours.<br>
SSH fingerprints:<br>
(RSA) 2048 d4:4e:3c:ed:9a:ba:5d:60:17:f8:46:32:a3:ef:3c:16<br>
(DSA) 1024 05:0b:6d:a2:6e:69:d8:a5:33:7d:19:a6:f6:a7:8b:c5<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: DePaul University, Chicago, IL, USA.<br>
Maintained by <a href="mailto:[email protected]">Eric Pancer</a>.<br>
Protocols: ssh, ssh port 2022, pserver.<br>
Updated every 2 hours.<br>
SSH fingerprints:<br>
(RSA1) 1024 5b:1c:cb:b7:5f:82:82:cc:af:13:21:a4:2c:c2:55:6b<br>
(RSA) 1024 18:0f:97:2a:cf:6c:7f:d4:ca:2b:bc:c8:b9:56:2b:86<br>
(DSA) 1024 65:cb:ce:7c:3e:29:5c:82:0b:9d:fa:b7:bb:e0:4b:47<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: Chicago, IL, USA.<br>
Maintained by <a href="mailto:[email protected]">Brian Brombacher</a>.<br>
Protocols: ssh, ssh port 2022, pserver.<br>
Updated every 3 hours from anoncvs3.usa.openbsd.org.<br>
SSH fingerprints:<br>
(RSA1) 2048 e4:22:93:81:84:e0:68:8c:0b:d5:1f:78:cd:6f:fa:c3<br>
(RSA) 2048 8f:42:bd:b0:a2:94:df:6b:af:1e:96:03:ea:68:03:d9<br>
(DSA) 1024 26:51:e8:b3:38:88:dc:a8:2a:98:59:86:ab:40:bb:a4<br>
<p>
<li><strong>[email protected]:/cvs</strong><br>
Location: Frontier Communications, Rochester, NY, USA.<br>
Maintained by <a href="mailto:[email protected]">jared r r spiegel</a>.<br>
Protocols: ssh.<br>
Updated every 4 hours from anoncvs.ca.openbsd.org.<br>
<p>
</ul>
<p>
<em>Note:</em> If your server is listed on here with inaccurate or
unknown information, please contact
<a href="mailto:[email protected]"><tt>[email protected]</tt></a>
<p>
You may want to use
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=traceroute&sektion=8&format=html">traceroute(8)</a>
to find out which server is nearest you.
Problems with a server should be reported to the <b>maintainer</b> of the
server in question.
<h3><a name="CRYPTO"><font color="#0000e0">Getting crypto sources through
cvs(1)</font></a></h3>
<p>
<strong>IMPORTANT NOTE:</strong>
There are a few issues relating to cryptographic software that everyone
should be aware of:
<ul>
<li>The OpenBSD sources are from Canada.
As
<a href="http://www.efc.ca/pages/doc/crypto-export.html">
researched by a Canadian individual</a>
and as
<a href="http://axion.physics.ubc.ca/ECL.html">
described in the Export Control list of Canada</a>
it is legal to export crypto software from Canada to the world.
<p>
<li>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...
<ul>
<li>src/kerberosIV/*
<li>src/kerberosV/*
<li>src/lib/libdes/*
<li>src/lib/libc/crypt/crypt.c
<li>src/lib/libc/crypt/morecrypt.c
<li>src/sys/crypto
<li>src/sys/netinet
<li>src/usr.sbin/afs/src/rxkad/*
<li>XF4/xc-mit/lib/Xdmcp/Wraphelp.c
<li>XF4/xc-old/lib/Xdmcp/Wraphelp.c
<li>XF4/xc/lib/Xdmcp/Wraphelp.c
</ul>
Because of US Dept. of Commerce policy,
crypto software may only be exported to Canada from the USA.
</ul>
<h3><a name="EXAMPLE"><font color="#0000e0">Example usages for cvs(1)</font>
</a></h3>
<p>
NOTICE: If you want to update a branch (such as a patch branch)
to <i>current</i>, you would add the <code>-A</code>
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.
<p>
A sample use of an anoncvs server would be:
<pre>
$ <strong>cd /tmp</strong>
$ <strong>cvs -d [email protected]:/cvs get src/sys/arch/sparc</strong>
[copies the files from the repository to your machine]
$ <strong>cd src/sys/arch/sparc</strong>
$ <strong>cvs log locore.s</strong>
[shows the commit log for the chosen file]
$ <strong>cvs diff -bc -r1.1 -r1.5 locore.s</strong>
[shows the changes between revisions 1.1 and rev 1.5]
</pre>
<p>
<a name="pserver">In order to use a cvs ``pserver'' (a direct TCP connection
instead of using ssh or rsh) you must login once:</a>
<pre>
$ <strong>cvs -d :pserver:[email protected]:/cvs login</strong>
(Logging in to [email protected])
CVS password: <strong>anoncvs</strong>
[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:[email protected]:/cvs Au'yc ]
[After logging in ONCE every other use of the above CVSROOT will work. ]
$ <strong>cvs -d :pserver:[email protected]:/cvs get ksrc-i386 ksrc-common</strong>
[Allows you to retrieve ONLY that necessary to rebuild an i386 kernel. ]
</pre>
<p>
Here is how someone using anoncvs regularly would update his
source tree:
<ul><li>First, start out by `get'-ing an initial tree:
<p> (If you are following <i>current</i>):
<pre>
# <strong>cd /usr</strong>
# <strong>cvs -qd [email protected]:/cvs get -P src</strong>
</pre>
<p> (If you are following the patch branch for 4.6):
<pre>
# <strong>cd /usr</strong>
# <strong>cvs -qd [email protected]:/cvs get -rOPENBSD_4_6 -P src</strong>
</pre>
<li> Anytime afterwards, to `update' this tree:
<p> (If you are following <i>current</i>):
<pre>
# <strong>cd /usr/src</strong>
# <strong>cvs -q up -Pd</strong>
</pre>
<p> (If you are following the patch branch for 4.6):
<pre>
# <strong>cd /usr/src</strong>
# <strong>cvs -q up -rOPENBSD_4_6 -Pd</strong>
</pre>
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.
<p>
<li> NOTE:
If you are updating a source tree that you initially fetched
from a different server, or from a CD, you <strong>must</strong>
add the <em>-d [email protected]:/cvs</em> options to cvs.
<pre>
# <strong>cd /usr/src</strong>
# <strong>cvs -d [email protected]:/cvs -q up -Pd</strong>
</pre>
</ul>
<p>
To <a name="ports">use</a> <a href="ports.html">ports</a>, it is similar to src:
<ul><li>
<p> (If you are following <i>current</i>):
<pre>
# <strong>cd /usr</strong>
# <strong>cvs -qd [email protected]:/cvs get -P ports</strong>
</pre>
<p> (If you are following the patch branch for 4.6):
<pre>
# <strong>cd /usr</strong>
# <strong>cvs -qd [email protected]:/cvs get -rOPENBSD_4_6 -P ports</strong>
</pre>
<li> Anytime afterwards, to `update' this tree:
<p> (If you are following <i>current</i>):
<pre>
# <strong>cd /usr/ports</strong>
# <strong>cvs -q up -Pd</strong>
</pre>
<p> (If you are following the patch branch for 4.6):
<pre>
# <strong>cd /usr/ports</strong>
# <strong>cvs -q up -rOPENBSD_4_6 -Pd</strong>
</pre>
</ul>
In the above example, <i>-q</i> is optional, only intended to minimize
cvs's output. For those who like to see screenfulls of output, it
can be omitted.
<p>
To make a diff of a locally patched module (here <i>cd.c</i>) to include with
a bug report:
<pre>
# <strong>cd /usr</strong>
# <strong>cvs diff -u src/sys/scsi/cd.c > /tmp/patch</strong>
</pre>
<p>
The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&sektion=1&format=html">
cvs(1) man page</a>
(included with the CVS sources) has much more
information about how CVS can be used.
<p>
<strong>Warning:</strong>
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.
<p>
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.
<h3><a name="WHICH"><font color="#0000e0">Use rsh(1) or ssh(1)?</font></a></h3>
CVS supports three access methods between the CVS server and the CVS
client:
<ul>
<li><b>ssh:</b> Secure Shell can be used to access the anonymous CVS servers.
This is the <i>recommended</i> way of doing so, as it is encrypted.
<li><b>rsh:</b> Remote Shell can be used on some of the servers for users
who don't have access to <a href="http://www.openssh.com/">ssh</a>.
<li><b>pserver:</b> pserver is primarily useful for users who are behind
firewalls that block the other two connections.
</ul>
<p>
<b>NOTE:</b> For users wishing to use rsh, you must first set the
<tt>CVS_RSH</tt> environment variable to point to the rsh(1) program:
<ul>
<li>For Korn/Bourne shells:
<pre>
$ <b>export CVS_RSH=/usr/bin/rsh</b>
</pre>
<li>For csh/tcsh:
<pre>
% <b>setenv CVS_RSH /usr/bin/rsh</b>
</pre>
</ul>
<p>
By default, OpenBSD's CVS client uses ssh ("secure shell":
<a href="http://www.openssh.com/">OpenSSH</a>) to talk to the CVS server.
<p>
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
<var>CVS_RSH</var> environment variable to point to rsh
(typically <strong>/usr/bin/rsh</strong>).
<p>
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 <strong>none</strong> 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.
<p>
One could specify something like the following in the
<strong>$HOME/.ssh/config</strong> configuration file to avoid the pitfalls
and restrictions mentioned above:
<pre>
Host anoncvs.ca.openbsd.org
Compression no
Port 2022
</pre>
<p>
CVS is a little noisy starting up; to quiet it a bit you may want to
do this:
<pre>
<strong>$ export CVS_CLIENT_PORT=-1</strong>
</pre>
<p>
<h3><a name="SUP"><font color="#0000e0">Mirroring the CVS repository via
sup(1)</font></a></h3>
<p>
Users wishing to mirror the OpenBSD CVS tree itself may now do so
from <em>anoncvs.usa.openbsd.org</em> or <em>anoncvs3.usa.openbsd.org</em>
(these are different machines). Note that this is the cvs tree,
<b>not</b> a checked out source tree. It is only useful if you
want to be able to do fast cvs operations (diff, annotate, etc) or
if you have multiple source trees and you only want to transfer new
data once (you can then checkout a tree from your local cvs mirror).
<p>
A sample supfile would be:
<pre>
cvs host=anoncvs.usa.openbsd.org hostbase=/ base=/home delete
</pre>
<p>
which would mirror the cvs tree into /home/cvs with the sup data
files ending up in /home/sup. The full OpenBSD cvs tree is currently
about 3.5GB in size, and will, of course continue to grow.
<h3><a name="MIRROR"><font color="#0000e0">Setting up an anoncvs mirror
</font></a></h3>
<p>
If you wish to setup a new anoncvs mirror site and make it available to
the general public, please contact the anoncvs
<a href="mailto:[email protected]">maintainer</a>.
Anoncvs mirrors currently require about 3.5GB of disk (and it will grow!),
and use up to 32MB of swap
per anoncvs user (assuming the user does a large operation; while smaller
operations use fewer resources, anoncvs still makes much more of an
impact than ftp or sup). Such anoncvs machines should have excellent
network connectivity for the area they are expected to serve. A
<a href="anoncvs.shar">document</a>
which describes the setup of anoncvs servers is available.
<h3><font color="#0000e0">Final notes</font></h3>
After upgrading your source tree, you should read the comments
at the top of <kbd>/usr/src/Makefile</kbd> before attempting
a build. Also, you should build a new kernel <strong>before</strong>
doing a <kbd>make build</kbd> if possible. In some cases it may be
necessary to rebuild and install the <kbd>config</kbd> utility before
you can build the kernel. If <kbd>config GENERIC</kbd> fails this
is probably the case.
<p>
It is important to note that upgrading from a release to the current tree
by rebuilding the sources can be rather difficult due to dependencies
that are often not obvious. Therefore, it is suggested that you first
install the latest snapshot before attempting a tree build from source.
<hr>
<a href="index.html"><img height="24" width="24" src="back.gif" border="0"
alt="OpenBSD"></a>
<a href="mailto:[email protected]">[email protected]</a>
<br><small>$OpenBSD: anoncvs.html,v 1.314 2010/03/17 16:08:42 otto Exp $
</small>
</body>
</html>