aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
blob: 5552f6709bf91bc3a6afd5da5eee5ac44aae16f7 (plain) (blame)
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
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
<!--
     The FreeBSD Documentation Project

     $FreeBSD$
-->

<appendix id="mirrors">
  <title>Obtaining &os;</title>

  <sect1 id="mirrors-cdrom">
    <title>CDROM and DVD Publishers</title>

    <sect2>
      <title>Retail Boxed Products</title>

      <para>&os; is available as a boxed product (&os; CDs,
	additional software, and printed documentation) from several
	retailers:</para>

      <itemizedlist>
	<listitem>
	  <address>
	    <otheraddr>CompUSA</otheraddr>
	    WWW: <otheraddr><ulink url="http://www.compusa.com/"></ulink></otheraddr>
	  </address>
	</listitem>

	<listitem>
	  <address>
	    <otheraddr>Frys Electronics</otheraddr>
	    WWW: <otheraddr><ulink url="http://www.frys.com/"></ulink></otheraddr>
	  </address>
	</listitem>
      </itemizedlist>
    </sect2>

    <sect2>
      <title>CD and DVD Sets</title>

      <para>&os; CD and DVD sets are available from many online
	retailers:</para>

    <itemizedlist>
      <listitem>
        <address>
	  <otheraddr>&os; Mall, Inc.</otheraddr>
	  <street>700 Harvest Park Ste F</street>
	  <city>Brentwood</city>, <state>CA</state>  <postcode>94513</postcode>
	  <country>USA</country>
	  Phone: <phone>+1 925 240-6652</phone>
	  Fax: <fax>+1 925 674-0821</fax>
	  Email: <email>info@freebsdmall.com</email>
	  WWW: <otheraddr><ulink url="http://www.freebsdmall.com/"></ulink></otheraddr>
        </address>
      </listitem>

      <listitem>
	<address>
	  <otheraddr>Dr. Hinner EDV</otheraddr>
	  <street>St. Augustinus-Str. 10</street>
	  <postcode>D-81825</postcode> <city>M&uuml;nchen</city>
	  <country>Germany</country>
	  Phone: <phone>(089) 428 419</phone>
	  WWW: <otheraddr><ulink url="http://www.hinner.de/linux/freebsd.html"></ulink></otheraddr>
        </address>
      </listitem>

      <listitem>
	<address>
	  <otheraddr>Ikarios</otheraddr>
	  <street>22-24 rue Voltaire</street>
	  <postcode>92000</postcode> <city>Nanterre</city>
	  <country>France</country>
	  WWW: <otheraddr><ulink url="http://ikarios.com/form/#freebsd"></ulink></otheraddr>
        </address>
      </listitem>

      <listitem>
	<address>
	  <otheraddr>JMC Software</otheraddr>
	  <country>Ireland</country>
	  Phone: <phone>353 1 6291282</phone>
	  WWW: <otheraddr><ulink url="http://www.thelinuxmall.com"></ulink></otheraddr>
	</address>
      </listitem>

      <listitem>
	<address>
	  <otheraddr>The Linux Emporium</otheraddr>
	  <street>Hilliard House, Lester Way</street>
	  <city>Wallingford</city>
	  <postcode>OX10 9TA</postcode>
	  <country>United Kingdom</country>
	  Phone: <phone>+44 1491 837010</phone>
	  Fax: <fax>+44 1491 837016</fax>
	  WWW: <otheraddr><ulink url="http://www.linuxemporium.co.uk/products/bsd/"></ulink></otheraddr>
        </address>
      </listitem>

      <listitem>
	<address>
	  <otheraddr>Linux+ DVD Magazine</otheraddr>
	  <street>Lewartowskiego 6</street>
	  <city>Warsaw</city>
	  <postcode>00-190</postcode>
	  <country>Poland</country>
	  Phone: <phone>+48 22 860 18 18</phone>
	  Email: <email>editors@lpmagazine.org</email>
	  WWW: <otheraddr><ulink url="http://www.lpmagazine.org/"></ulink></otheraddr>
	</address>
      </listitem>

      <listitem>
	<address>
	  <otheraddr>Linux System Labs Australia</otheraddr>
	  <street>21 Ray Drive</street>
	  <city>Balwyn North</city>
	  <postcode>VIC - 3104</postcode>
	  <country>Australia</country>
	  Phone: <phone>+61 3 9857 5918</phone>
	  Fax: <fax>+61 3 9857 8974</fax>
	  WWW: <otheraddr><ulink url="http://www.lsl.com.au"></ulink></otheraddr>
        </address>
      </listitem>

      <listitem>
	<address>
	  <otheraddr>LinuxCenter.Ru</otheraddr>
	  <street>Galernaya Street, 55</street>
	  <city>Saint-Petersburg</city>
	  <postcode>190000</postcode>
	  <country>Russia</country>
	  Phone: <phone>+7-812-3125208</phone>
	  Email: <email>info@linuxcenter.ru</email>
	  WWW: <otheraddr><ulink url="http://linuxcenter.ru/shop/freebsd"></ulink></otheraddr>
	</address>
      </listitem>

    </itemizedlist>
    </sect2>

    <sect2>
      <title>Distributors</title>

      <para>If you are a reseller and want to carry &os; CDROM products,
	please contact a distributor:</para>

      <itemizedlist>
	<listitem>
	  <address>
	    <otheraddr>Cylogistics</otheraddr>
	    <street>809B Cuesta Dr., #2149</street>
	    <city>Mountain View</city>, <state>CA</state> <postcode>94040</postcode>
	    <country>USA</country>
	    Phone: <phone>+1 650 694-4949</phone>
	    Fax: <fax>+1 650 694-4953</fax>
	    Email: <email>sales@cylogistics.com</email>
	    WWW: <otheraddr><ulink url="http://www.cylogistics.com/"></ulink></otheraddr>
	  </address>
	</listitem>

        <listitem>
	  <address>
	    <otheraddr>Ingram Micro</otheraddr>
	    <street>1600 E. St. Andrew Place</street>
	    <city>Santa Ana</city>, <state>CA</state>  <postcode>92705-4926</postcode>
	    <country>USA</country>
	    Phone: <phone>1 (800) 456-8000</phone>
	    WWW: <otheraddr><ulink url="http://www.ingrammicro.com/"></ulink></otheraddr>
          </address>
        </listitem>

	<listitem>
	  <address>
	    <otheraddr>Kudzu, LLC</otheraddr>
	    <street>7375 Washington Ave. S.</street>
	    <city>Edina</city>, <state>MN</state> <postcode>55439</postcode>
	    <country>USA</country>
	    Phone: <phone>+1 952 947-0822</phone>
	    Fax: <fax>+1 952 947-0876</fax>
	    Email: <email>sales@kudzuenterprises.com</email>
	  </address>
	</listitem>

	<listitem>
	  <address>
	    <otheraddr>LinuxCenter.Kz</otheraddr>
	    <city>Ust-Kamenogorsk</city>
	    <country>Kazakhstan</country>
	    Phone: <phone>+7-705-501-6001</phone>
	    Email: <email>info@linuxcenter.kz</email>
	    WWW: <otheraddr><ulink url="http://linuxcenter.kz/page.php?page=fr"></ulink></otheraddr>
	  </address>
	</listitem>

	<listitem>
	  <address>
	    <otheraddr>LinuxCenter.Ru</otheraddr>
	    <street>Galernaya Street, 55</street>
	    <city>Saint-Petersburg</city>
	    <postcode>190000</postcode>
	    <country>Russia</country>
	    Phone: <phone>+7-812-3125208</phone>
	    Email: <email>info@linuxcenter.ru</email>
	    WWW: <otheraddr><ulink url="http://linuxcenter.ru/freebsd"></ulink></otheraddr>
	  </address>
	</listitem>

	<listitem>
	  <address>
	    <otheraddr>Navarre Corp</otheraddr>
	    <street>7400 49th Ave South</street>
	    <city>New Hope</city>, <state>MN</state> <postcode>55428</postcode>
	    <country>USA</country>
	    Phone: <phone>+1 763 535-8333</phone>
	    Fax: <fax>+1 763 535-0341</fax>
	    WWW: <otheraddr><ulink url="http://www.navarre.com/"></ulink></otheraddr>
	  </address>
	</listitem>
      </itemizedlist>
    </sect2>
  </sect1>

  <sect1 id="mirrors-ftp">
    <title>FTP Sites</title>

    <para>The official sources for &os; are available via anonymous FTP
      from a worldwide set of mirror sites.  The site
      <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/"></ulink> is well
      connected and allows a large number of connections to it, but
      you are probably better off finding a <quote>closer</quote>
      mirror site (especially if you decide to set up some sort of
      mirror site).</para>

    <para>The <ulink
	url="http://mirrorlist.FreeBSD.org/">&os; mirror
	sites database</ulink> is more accurate than the mirror listing in the
      Handbook, as it gets its information from the DNS rather than relying on
      static lists of hosts.</para>

    <para>Additionally, &os; is available via anonymous FTP from the
      following mirror sites.  If you choose to obtain &os; via anonymous
      FTP, please try to use a site near you.  The mirror sites listed as
      <quote>Primary Mirror Sites</quote> typically have the entire &os; archive (all
      the currently available versions for each of the architectures) but
      you will probably have faster download times from a site that is
      in your country or region.  The regional sites carry the most recent
      versions for the most popular architecture(s) but might not carry
      the entire &os; archive.  All sites provide access via anonymous
      FTP but some sites also provide access via other methods.  The access
      methods available for each site are provided in parentheses
      after the hostname.</para>

    &chap.mirrors.ftp.inc;
  </sect1>

  <sect1 id="mirrors-bittorrent">
    <title>BitTorrent</title>

    <indexterm>
      <primary>BitTorrent</primary>
    </indexterm>

    <para>The ISO images for the basic release CDs are available via
      BitTorrent.  A collection of torrent files to download the
      images is available at <ulink
      url="http://torrents.freebsd.org:8080/">http://torrents.freebsd.org:8080</ulink></para>

    <para>The BitTorrent client software is available from the
      <filename role="package">net-p2p/py-bittorrent</filename> port,
      or a precompiled package.</para>

    <para>After downloading the ISO image with BitTorrent, you may
      burn it to CD or DVD media as described in <xref
      linkend="burncd">, burncd.</para>
  </sect1>

    <sect1 id="anoncvs">
      <title>Anonymous CVS</title>

      <sect2>
	<title><anchor id="anoncvs-intro">Introduction</title>

	<indexterm>
	  <primary>CVS</primary>
	  <secondary>anonymous</secondary>
	</indexterm>

	<para>Anonymous CVS (or, as it is otherwise known,
	  <emphasis>anoncvs</emphasis>) is a feature provided by the CVS
	  utilities bundled with &os; for synchronizing with a remote
	  CVS repository.  Among other things, it allows users of &os;
	  to perform, with no special privileges, read-only CVS operations
	  against one of the &os; project's official anoncvs servers.
	  To use it, one simply sets the <envar>CVSROOT</envar>
	  environment variable to point at the appropriate anoncvs server,
	  provides the well-known password <quote>anoncvs</quote> with the
	  <command>cvs login</command> command, and then uses the
	  &man.cvs.1; command to access it like any local
	  repository.</para>

	<note>
	  <para>The <command>cvs login</command> command, stores the passwords
	    that are used for authenticating to the CVS server in a file
	    called <filename>.cvspass</filename> in your
	    <envar>HOME</envar> directory.  If this file does not exist,
	    you might get an error when trying to use <command>cvs
	    login</command> for the first time.  Just make an empty
	    <filename>.cvspass</filename> file, and retry to login.</para>
	</note>

	<para>While it can also be said that the <link
	  linkend="cvsup">CVSup</link> and <emphasis>anoncvs</emphasis>
	  services both perform essentially the same function, there are
	  various trade-offs which can influence the user's choice of
	  synchronization methods.  In a nutshell,
	  <application>CVSup</application> is much more efficient in its
	  usage of network resources and is by far the most technically
	  sophisticated of the two, but at a price.  To use
	  <application>CVSup</application>, a special client must first be
	  installed and configured before any bits can be grabbed, and
	  then only in the fairly large chunks which
	  <application>CVSup</application> calls
	  <emphasis>collections</emphasis>.</para>

	<para><application>Anoncvs</application>, by contrast, can be used
	  to examine anything from an individual file to a specific
	  program (like <command>ls</command> or <command>grep</command>)
	  by referencing the CVS module name.  Of course,
	  <application>anoncvs</application> is also only good for
	  read-only operations on the CVS repository, so if it is your
	  intention to support local development in one repository shared
	  with the &os; project bits then
	  <application>CVSup</application> is really your only
	  option.</para>
      </sect2>

      <sect2>
	<title><anchor id="anoncvs-usage">Using Anonymous CVS</title>

	<para>Configuring &man.cvs.1; to use an Anonymous CVS repository
	  is a simple matter of setting the <envar>CVSROOT</envar>
	  environment variable to point to one of the &os; project's
	  <emphasis>anoncvs</emphasis> servers.  At the time of this
	  writing, the following servers are available:</para>

	<itemizedlist>
	  <listitem>
	    <para><emphasis>France</emphasis>:
	      :pserver:anoncvs@anoncvs.fr.FreeBSD.org:/home/ncvs
	      (pserver (password <quote>anoncvs</quote>), ssh (no password))
	    </para>
	  </listitem>
	  <listitem>
	    <para><emphasis>Japan</emphasis>:
	      :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs
	      (Use <command>cvs login</command> and enter the password
	      <quote>anoncvs</quote> when prompted.)</para>
	  </listitem>
	  <listitem>
	    <para><emphasis>Taiwan</emphasis>:
	      :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs
	      (pserver (use <command>cvs login</command> and enter any
	      password when prompted), ssh (no password))</para>

	      <programlisting>SSH2 HostKey: 1024 02:ed:1b:17:d6:97:2b:58:5e:5c:e2:da:3b:89:88:26 /etc/ssh/ssh_host_rsa_key.pub
SSH2 HostKey: 1024 e8:3b:29:7b:ca:9f:ac:e9:45:cb:c8:17:ae:9b:eb:55 /etc/ssh/ssh_host_dsa_key.pub</programlisting>
      
	  </listitem>
	  <listitem>
	    <para><emphasis>USA</emphasis>:
	      freebsdanoncvs@anoncvs.FreeBSD.org:/home/ncvs
	      (ssh only - no password)</para>

	    <programlisting>SSH HostKey: 1024 a1:e7:46:de:fb:56:ef:05:bc:73:aa:91:09:da:f7:f4 root@sanmateo.ecn.purdue.edu
SSH2 HostKey: 1024 52:02:38:1a:2f:a8:71:d3:f5:83:93:8d:aa:00:6f:65 ssh_host_dsa_key.pub</programlisting>

	  </listitem>
	  <listitem>
	    <para><emphasis>USA</emphasis>:
	      anoncvs@anoncvs1.FreeBSD.org:/home/ncvs (ssh2 only - no
	      password)</para>

	    <programlisting>SSH2 HostKey: 2048 53:1f:15:a3:72:5c:43:f6:44:0e:6a:e9:bb:f8:01:62 /etc/ssh/ssh_host_dsa_key.pub</programlisting>

	  </listitem>
	</itemizedlist>

	<para>Since CVS allows one to <quote>check out</quote> virtually
	  any version of the &os; sources that ever existed (or, in
	  some cases, will exist), you need to be
	  familiar with the revision (<option>-r</option>) flag to
	  &man.cvs.1; and what some of the permissible values for it in
	  the &os; Project repository are.</para>

	<para>There are two kinds of tags, revision tags and branch tags.
	  A revision tag refers to a specific revision.  Its meaning stays
	  the same from day to day.  A branch tag, on the other hand,
	  refers to the latest revision on a given line of development, at
	  any given time.  Because a branch tag does not refer to a
	  specific revision, it may mean something different tomorrow than
	  it means today.</para>

	<para><xref linkend="cvs-tags"> contains revision tags that users
 	  might be interested
	  in.  Again, none of these are valid for the Ports Collection
	  since the Ports Collection does not have multiple
	  branches of development.</para>

	<para>When you specify a branch tag, you normally receive the
	  latest versions of the files on that line of development.  If
	  you wish to receive some past version, you can do so by
	  specifying a date with the <option>-D date</option> flag.
	  See the &man.cvs.1; manual page for more details.</para>
      </sect2>

      <sect2>
	<title>Examples</title>

	<para>While it really is recommended that you read the manual page
	  for &man.cvs.1; thoroughly before doing anything, here are some
	  quick examples which essentially show how to use Anonymous
	  CVS:</para>

	<example>
	  <title>Checking Out Something from -CURRENT (&man.ls.1;):</title>

	  <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter any word for</emphasis> <quote>password</quote>.
&prompt.user; <userinput>cvs co ls</userinput>
	  </screen>
	</example>

	<example>
	  <title>Using SSH to check out the <filename>src/</filename>
	    tree:</title>
	  <screen>&prompt.user; <userinput>cvs -d freebsdanoncvs@anoncvs.FreeBSD.org:/home/ncvs co src</userinput>
The authenticity of host 'anoncvs.freebsd.org (128.46.156.46)' can't be established.
DSA key fingerprint is 52:02:38:1a:2f:a8:71:d3:f5:83:93:8d:aa:00:6f:65.
Are you sure you want to continue connecting (yes/no)? <userinput>yes</userinput>
Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known hosts.</screen>
	</example>

	<example>
	  <title>Checking Out the Version of &man.ls.1; in the 6-STABLE
	    Branch:</title>

	  <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter any word for</emphasis> <quote>password</quote>.
&prompt.user; <userinput>cvs co -rRELENG_6 ls</userinput>
	  </screen>
	</example>

	<example>
	  <title>Creating a List of Changes (as Unified Diffs) to &man.ls.1;</title>

	  <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter any word for</emphasis> <quote>password</quote>.
&prompt.user; <userinput>cvs rdiff -u -rRELENG_5_3_0_RELEASE -rRELENG_5_4_0_RELEASE ls</userinput>
	  </screen>
	</example>

	<example>
	  <title>Finding Out What Other Module Names Can Be Used:</title>

	  <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput>
<emphasis>At the prompt, enter any word for</emphasis> <quote>password</quote>.
&prompt.user; <userinput>cvs co modules</userinput>
&prompt.user; <userinput>more modules/modules</userinput>
	  </screen>
	</example>
      </sect2>

      <sect2>
	<title>Other Resources</title>

	<para>The following additional resources may be helpful in learning
	  CVS:</para>

	<itemizedlist>
	  <listitem>
	    <para><ulink 
		url="http://users.csc.calpoly.edu/~gfisher/classes/205/handouts/cvs-basics.html">CVS Tutorial</ulink> from California 
		Polytechnic State University.</para>
	  </listitem>

	  <listitem>
	    <para><ulink url="http://ximbiot.com/cvs/wiki/">CVS Home</ulink>,
	      the CVS development and support community.</para>
	  </listitem>

	  <listitem>
	    <para><ulink
		url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVSweb</ulink> is
	      the &os; Project web interface for CVS.</para>
	  </listitem>
	</itemizedlist>
      </sect2>
    </sect1>
    
    
  <sect1 id="ctm">
    <title>Using CTM</title>

      <indexterm>
	<primary>CTM</primary>
      </indexterm>

      <para><application>CTM</application> is a method for keeping a
	remote directory tree in sync with a central one.  It has been
	developed for usage with &os;'s source trees, though other
	people may find it useful for other purposes as time goes by.
	Little, if any, documentation currently exists at this time on the
	process of creating deltas, so contact the &a.ctm-users.name; mailing list for more
	information and if you wish to use <application>CTM</application>
	for other things.</para>

      <sect2>
	<title>Why Should I Use <application>CTM</application>?</title>

	<para><application>CTM</application> will give you a local copy of
	  the &os; source trees.  There are a number of
	  <quote>flavors</quote> of the tree available.  Whether you wish
	  to track the entire CVS tree or just one of the branches,
	  <application>CTM</application> can provide you the information.
	  If you are an active developer on &os;, but have lousy or
	  non-existent TCP/IP connectivity, or simply wish to have the
	  changes automatically sent to you,
	  <application>CTM</application> was made for you.  You will need
	  to obtain up to three deltas per day for the most  active
	  branches.  However, you should consider having them sent by
	  automatic email.  The sizes of the updates are always kept as
	  small as possible.  This is typically less than 5K, with an
	  occasional (one in ten) being 10-50K and every now and then a
	  large 100K+ or more coming around.</para>

	<para>You will also need to make yourself aware of the various
	  caveats related to working directly from the development sources
	  rather than a pre-packaged release.  This is particularly true
	  if you choose the <quote>current</quote> sources.  It is
	  recommended that you read <link linkend="current">Staying
	  current with &os;</link>.</para>
      </sect2>

      <sect2>
	<title>What Do I Need to Use
	  <application>CTM</application>?</title>

	<para>You will need two things: The <application>CTM</application>
	  program, and the initial deltas to feed it (to get up to
	  <quote>current</quote> levels).</para>
	    
	<para>The <application>CTM</application> program has been part of
	  &os; ever since version 2.0 was released, and lives in
	  <filename>/usr/src/usr.sbin/ctm</filename> if you have a copy
	  of the source available.</para>

	<para>The <quote>deltas</quote> you feed
	  <application>CTM</application> can be had two ways, FTP or
	  email.  If you have general FTP access to the Internet then the
	  following FTP sites support access to
	  <application>CTM</application>:</para>

	<para><ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/"></ulink></para>

	<para>or see section <link
	  linkend="mirrors-ctm">mirrors</link>.</para>

	<para>FTP the relevant directory and fetch the
	  <filename>README</filename> file, starting from there.</para>

	<para>If you wish to get your deltas via email:</para>

	<para>Subscribe to one of the
	  <application>CTM</application> distribution lists.
	  &a.ctm-cvs-cur.name; supports the entire CVS tree.
	  &a.ctm-src-cur.name; supports the head of the development
	  branch.  &a.ctm-src-4.name; supports the 4.X release
	  branch, etc..  (If you do not know how to subscribe yourself
	  to a list, click on the list name above or go to
	  &a.mailman.lists.link; and click on the list that you
	  wish to subscribe to.  The list page should contain all of
	  the necessary subscription instructions.)</para>

	<para>When you begin receiving your <application>CTM</application>
	  updates in the mail, you may use the
	  <command>ctm_rmail</command> program to unpack and apply them.
	  You can actually use the <command>ctm_rmail</command> program
	  directly from a entry in <filename>/etc/aliases</filename> if
	  you want to have the process run in a fully automated fashion.
	  Check the <command>ctm_rmail</command> manual page for more
	  details.</para>

	<note>
	  <para>No matter what method you use to get the
	    <application>CTM</application> deltas, you should subscribe to
	    the &a.ctm-announce.name; mailing list.  In
	    the future, this will be the only place where announcements
	    concerning the operations of the
	    <application>CTM</application> system will be posted.  Click
	    on the list name above and follow the instructions
	    to subscribe to the
	    list.</para>
	</note>
      </sect2>

      <sect2>
	<title>Using <application>CTM</application> for the First
	  Time</title>

	<para>Before you can start using <application>CTM</application>
	  deltas, you will need to get to a starting point for the deltas
	  produced subsequently to it.</para>

	<para>First you should determine what you already have.  Everyone
	  can start from an <quote>empty</quote> directory.  You must use
	  an initial <quote>Empty</quote> delta to start off your
	  <application>CTM</application> supported tree.  At some point it
	  is intended that one of these <quote>started</quote> deltas be
	  distributed on the CD for your convenience, however, this does
	  not currently happen.</para>

	<para>Since the trees are many tens of megabytes, you should
	  prefer to start from something already at hand.  If you have a
	  -RELEASE CD, you can copy or extract an initial source from it.
	  This will save a significant transfer of data.</para>

	<para>You can recognize these <quote>starter</quote> deltas by the
	  <literal>X</literal> appended to the number
	  (<filename>src-cur.3210XEmpty.gz</filename> for instance).  The
	  designation following the <literal>X</literal> corresponds to
	  the origin of your initial <quote>seed</quote>.
	  <filename>Empty</filename> is an empty directory.  As a rule a
	  base transition from <literal>Empty</literal> is produced
	  every 100 deltas.  By the way, they are large! 70 to 80
	  Megabytes of <command>gzip</command>'d data is common for the
	  <filename>XEmpty</filename> deltas.</para>

	<para>Once you have picked a base delta to start from, you will also
	  need all deltas with higher numbers following it.</para>
      </sect2>

      <sect2>
	<title>Using <application>CTM</application> in Your Daily
	  Life</title>

	<para>To apply the deltas, simply say:</para>

	<screen>&prompt.root; <userinput>cd /where/ever/you/want/the/stuff</userinput>
&prompt.root; <userinput>ctm -v -v /where/you/store/your/deltas/src-xxx.*</userinput></screen>

	<para><application>CTM</application> understands deltas which have
	  been put through <command>gzip</command>, so you do not need to
	  <command>gunzip</command> them first, this saves disk space.</para>

	<para>Unless it feels very secure about the entire process,
	  <application>CTM</application> will not touch your tree.  To
	  verify a delta you can also use the <option>-c</option> flag and
	  <application>CTM</application> will not actually touch your
	  tree; it will merely verify the integrity of the delta and see
	  if it would apply cleanly to your current tree.</para>

	<para>There are other options to <application>CTM</application>
	  as well, see the manual pages or look in the sources for more
	  information.</para>

	<para>That is really all there is to it.  Every time you get a new
	  delta, just run it through <application>CTM</application> to
	  keep your sources up to date.</para>

	<para>Do not remove the deltas if they are hard to download again.
	  You just might want to keep them around in case something bad
	  happens.  Even if you only have floppy disks, consider using
	  <command>fdwrite</command> to make a copy.</para>
      </sect2>

      <sect2>
	<title>Keeping Your Local Changes</title>

	<para>As a developer one would like to experiment with and change
	  files in the source tree.  <application>CTM</application>
	  supports local modifications in a limited way: before checking
	  for the presence of a file <filename>foo</filename>, it first
	  looks for <filename>foo.ctm</filename>.  If this file exists,
	  <application>CTM</application> will operate on it instead of
	  <filename>foo</filename>.</para>

	<para>This behavior gives us a simple way to maintain local
	  changes:  simply copy the files you plan to modify to the
	  corresponding file names with a <filename>.ctm</filename>
	  suffix.  Then you can freely hack  the code, while <application>CTM</application> keeps the
	  <filename>.ctm</filename> file up-to-date.</para>
      </sect2>

      <sect2>
	<title>Other Interesting <application>CTM</application> Options</title>

	<sect3>
	  <title>Finding Out Exactly What Would Be Touched by an
	    Update</title>

	  <para>You can determine the list of changes that
	    <application>CTM</application> will make on your source
	    repository using the <option>-l</option> option to
	    <application>CTM</application>.</para>

	  <para>This is useful if you would like to keep logs of the
	    changes, pre- or post- process the modified files in any
	    manner, or just are feeling a tad paranoid.</para>
	</sect3>

	<sect3>
	  <title>Making Backups Before Updating</title>

	  <para>Sometimes you may want to backup all the files that would
	    be changed by a <application>CTM</application> update.</para>

	  <para>Specifying the <option>-B backup-file</option> option
	    causes <application>CTM</application> to backup all files that
	    would be touched by a given <application>CTM</application>
	    delta to <filename>backup-file</filename>.</para>
	</sect3>

	<sect3>
	  <title>Restricting the Files Touched by an Update</title>

	  <para>Sometimes you would be interested in restricting the scope
	    of a given <application>CTM</application> update, or may be
	    interested in extracting just a few files from a sequence of
	    deltas.</para>

	  <para>You can control the list of files that
	    <application>CTM</application> would operate on by specifying
	    filtering regular expressions using the <option>-e</option>
	    and <option>-x</option> options.</para>

	  <para>For example, to extract an up-to-date copy of
	    <filename>lib/libc/Makefile</filename> from your collection of
	    saved <application>CTM</application> deltas, run the commands:</para>

	  <screen>&prompt.root; <userinput>cd /where/ever/you/want/to/extract/it/</userinput>
&prompt.root; <userinput>ctm -e '^lib/libc/Makefile' ~ctm/src-xxx.*</userinput></screen>

	  <para>For every file specified in a
	    <application>CTM</application> delta, the <option>-e</option>
	    and <option>-x</option> options are applied in the order given
	    on the command line.  The file is processed by
	    <application>CTM</application> only if it is marked as
	    eligible after all the <option>-e</option> and
	    <option>-x</option> options are applied to it.</para>
	</sect3>
      </sect2>

      <sect2>
	<title>Future Plans for <application>CTM</application></title>

	<para>Tons of them:</para>

	<itemizedlist>
	  <listitem>
	    <para>Use some kind of authentication into the <application>CTM</application> system, so
	      as to allow detection of spoofed <application>CTM</application> updates.</para>
	  </listitem>

	  <listitem>
	    <para>Clean up the options to <application>CTM</application>,
	      they became confusing and counter intuitive.</para>
	  </listitem>
	</itemizedlist>
      </sect2>

      <sect2>
	<title>Miscellaneous Stuff</title>

	<para>There is a sequence of deltas for the
	  <literal>ports</literal> collection too, but interest has not
	  been all that high yet.</para>
      </sect2>

    <sect2 id="mirrors-ctm">
      <title>CTM Mirrors</title>
      
    <para><link linkend="ctm">CTM</link>/&os; is available via anonymous
      FTP from the following mirror sites.  If you choose to obtain <application>CTM</application> via
      anonymous FTP, please try to use a site near you.</para>

    <para>In case of problems, please contact the &a.ctm-users.name;
      mailing list.</para>

    <variablelist>
      <varlistentry>
	<term>California, Bay Area, official source</term>

	<listitem>
	  <itemizedlist>
	    <listitem>
	      <para><ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CTM/"></ulink></para>
	    </listitem>
	  </itemizedlist>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>South Africa, backup server for old deltas</term>

	<listitem>
	  <itemizedlist>
	    <listitem>
	      <para><ulink url="ftp://ftp.za.FreeBSD.org/pub/FreeBSD/CTM/"></ulink></para>
	    </listitem>
	  </itemizedlist>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>Taiwan/R.O.C.</term>

	<listitem>
	  <itemizedlist>
	    <listitem>
	      <para><ulink url="ftp://ctm.tw.FreeBSD.org/pub/FreeBSD/development/CTM/"></ulink></para>
	    </listitem>

	    <listitem>
	      <para><ulink url="ftp://ctm2.tw.FreeBSD.org/pub/FreeBSD/development/CTM/"></ulink></para>
	    </listitem>

	    <listitem>
	      <para><ulink url="ftp://ctm3.tw.FreeBSD.org/pub/FreeBSD/development/CTM/"></ulink></para>
	    </listitem>
	  </itemizedlist>
	</listitem>
      </varlistentry>
    </variablelist>

    <para>If you did not find a mirror near to you or the mirror is
      incomplete, try to use a search engine such as
      <ulink url="http://www.alltheweb.com/">alltheweb</ulink>.</para>
  </sect2></sect1>

  <sect1 id="cvsup">
    <title>Using CVSup</title>
    
    <sect2 id="cvsup-intro">
      <title>Introduction</title>
      
      <para><application>CVSup</application> is a software package for
	distributing and updating source trees from a master CVS
	repository on a remote server host.  The &os; sources are
	maintained in a CVS repository on a central development machine
	in California.  With <application>CVSup</application>, &os;
	users can easily keep their own source trees up to date.</para>
      
      <para><application>CVSup</application> uses the so-called
	<emphasis>pull</emphasis> model of updating.  Under the pull
	model, each client asks the server for updates, if and when they
	are wanted.  The server waits passively for update requests from
	its clients.  Thus all updates are instigated by the client.
	The server never sends unsolicited updates.  Users must either
	run the <application>CVSup</application> client manually to get
	an update, or they must set up a <command>cron</command> job to
	run it automatically on a regular basis.</para>
      
      <para>The term <application>CVSup</application>, capitalized just
	so, refers to the entire software package.  Its main components
	are the client <command>cvsup</command> which runs on each
	user's machine, and the server <command>cvsupd</command> which
	runs at each of the &os; mirror sites.</para>

      <para>As you read the &os; documentation and mailing lists, you
	may see references to <application>sup</application>.
	<application>Sup</application> was the predecessor of
	<application>CVSup</application>, and it served a similar
	purpose.  <application>CVSup</application> is used much in the
	same way as sup and, in fact, uses configuration files which are
	backward-compatible with <command>sup</command>'s.
	<application>Sup</application> is no longer used in the &os;
	project, because <application>CVSup</application> is both faster
	and more flexible.</para>

      <note>
	<para>The <application>csup</application> utility is a rewrite of the
	  <application>CVSup</application> software in C.  Its biggest
	  advantage is, that it is faster and does not depend on the
	  Modula-3 language, thus you do not need to install it as a
	  requirement.  Moreover, if you are using &os; 6.2 or later,
	  you can use it out-of-the-box, since it is included in the base
	  system.  Older &os; versions do not have &man.csup.1; in their
	  base system but you can easily install the
	  <filename role="package">net/csup</filename> port, or a precompiled
	  package.  The <application>csup</application> utility does not
	  support CVS mode, though.  If you want to mirror complete
	  repositories, you will still need to use
	  <application>CVSup</application>.  If you decided to use
	  <application>csup</application>, just skip the steps on the
	  installation of <application>CVSup</application> and
	  substitute the references of <application>CVSup</application> with
	  <application>csup</application> while following the remainder of
	  this article.</para>
      </note>
    </sect2>

    <sect2 id="cvsup-install">
      <title>Installation</title>
      
      <para>The easiest way to install <application>CVSup</application>
	is to use the precompiled <filename role="package">net/cvsup</filename> package
	from the &os; <link linkend="ports">packages collection</link>.
	If you prefer to build <application>CVSup</application> from
	source, you can use the <filename role="package">net/cvsup</filename>
	port instead.  But be forewarned: the
	<filename role="package">net/cvsup</filename> port depends on the Modula-3
	system, which takes a substantial amount of time and
	disk space to download and build.</para>

	<note>
	  <para>If you are going to be using
	  <application>CVSup</application> on a machine which will not have
	  <application>&xfree86;</application> or <application>&xorg;</application> installed, such as a server, be
	  sure to use the port which does not include the
	  <application>CVSup</application> <acronym>GUI</acronym>,
	  <filename role="package">net/cvsup-without-gui</filename>.</para>
	</note>

      <para>If you want to install <application>csup</application> on
	&os; 6.1 or earlier, you can use the precompiled
	<filename role="package">net/csup</filename> package
	from the &os; <link linkend="ports">packages collection</link>.
	If you prefer to build <application>csup</application> from source,
	you can use the <filename role="package">net/csup</filename>
	port instead.</para>
    </sect2>

    <sect2 id="cvsup-config">
      <title>CVSup Configuration</title>
      
      <para><application>CVSup</application>'s operation is controlled
	by a configuration file called the <filename>supfile</filename>.
	There are some sample <filename>supfiles</filename> in the
	directory <ulink type="html"
	  url="file://localhost/usr/share/examples/cvsup/"><filename>/usr/share/examples/cvsup/</filename></ulink>.</para>
      
      <para>The information in a <filename>supfile</filename> answers
	the following questions for <application>CVSup</application>:</para>
      
      <itemizedlist>
	<listitem>
	  <para><link linkend="cvsup-config-files">Which files do you
	      want to receive?</link></para>
	</listitem>
	
	<listitem>
	  <para><link linkend="cvsup-config-vers">Which versions of them
	      do you want?</link></para>
	</listitem>
	
	<listitem>
	  <para><link linkend="cvsup-config-where">Where do you want to
	      get them from?</link></para>
	</listitem>
	
	<listitem>
	  <para><link linkend="cvsup-config-dest">Where do you want to
	      put them on your own machine?</link></para>
	</listitem>
	
	<listitem>
	  <para><link linkend="cvsup-config-status">Where do you want to
	      put your status files?</link></para>
	</listitem>
      </itemizedlist>

      <para>In the following sections, we will construct a typical
	<filename>supfile</filename> by answering each of these
	questions in turn.  First, we describe the overall structure of
	a <filename>supfile</filename>.</para>

      <para>A <filename>supfile</filename> is a text file.  Comments
	begin with <literal>#</literal> and extend to the end of the
	line.  Lines that are blank and lines that contain only
	comments are ignored.</para>
      
      <para>Each remaining line describes a set of files that the user
	wishes to receive.  The line begins with the name of a
	<quote>collection</quote>, a logical grouping of files defined by
	the server. The name of the collection tells the server which
	files you want.  After the collection name come zero or more
	fields, separated by white space.  These fields answer the
	questions listed above.  There are two types of fields: flag
	fields and value fields.  A flag field consists of a keyword
	standing alone, e.g., <literal>delete</literal> or
	<literal>compress</literal>.  A value field also begins with a
	keyword, but the keyword is followed without intervening white
	space by <literal>=</literal> and a second word.  For example,
	<literal>release=cvs</literal> is a value field.</para>
      
      <para>A <filename>supfile</filename> typically specifies more than
	one collection to receive.  One way to structure a
	<filename>supfile</filename> is to specify all of the relevant
	fields explicitly for each collection.  However, that tends to
	make the <filename>supfile</filename> lines quite long, and it
	is inconvenient because most fields are the same for all of the
	collections in a <filename>supfile</filename>.
	<application>CVSup</application> provides a defaulting mechanism
	to avoid these problems.  Lines beginning with the special
	pseudo-collection name <literal>*default</literal> can be used
	to set flags and values which will be used as defaults for the
	subsequent collections in the <filename>supfile</filename>.  A
	default value can be overridden for an individual collection, by
	specifying a different value with the collection itself.
	Defaults can also be changed or augmented in mid-supfile by
	additional <literal>*default</literal> lines.</para>

      <para>With this background, we will now proceed to construct a
	<filename>supfile</filename> for receiving and updating the main
	source tree of <link
	  linkend="current">&os;-CURRENT</link>.</para>

      <itemizedlist>
	<listitem>
	  <para><anchor id="cvsup-config-files">Which files do you want
	    to receive?</para>
	  
	  <para>The files available via <application>CVSup</application>
	    are organized into named groups called
	    <quote>collections</quote>.  The collections that are
	    available are described in the <link
	      linkend="cvsup-collec">following section</link>.  In this
	    example, we
	    wish to receive the entire main source tree for the &os;
	    system.  There is a single large collection
	    <literal>src-all</literal> which will give us all of that.
	    As a first step toward constructing our
	    <filename>supfile</filename>, we
	    simply list the collections, one per line (in this case,
	    only one line):</para>

	  <programlisting>src-all</programlisting>
	</listitem>

	<listitem>
	  <para><anchor id="cvsup-config-vers">Which version(s) of them
	    do you want?</para>

	  <para>With <application>CVSup</application>, you can receive
	    virtually any version of the sources that ever existed.
	    That is possible because the
	    <application>cvsupd</application> server works directly from
	    the CVS repository, which contains all of the versions.  You
	    specify which one of them you want using the
	    <literal>tag=</literal> and <option>date=</option> value
	    fields.</para>
	  
	  <warning>
	    <para>Be very careful to specify any <literal>tag=</literal>
	      fields correctly.  Some tags are valid only for certain
	      collections of files.  If you specify an incorrect or
	      misspelled tag, <application>CVSup</application>
	      will delete files which you probably
	      do not want deleted.  In particular, use <emphasis>only
	      </emphasis> <literal>tag=.</literal> for the
	      <literal>ports-*</literal> collections.</para>
	  </warning>

	  <para>The <literal>tag=</literal> field names a symbolic tag
	    in the repository.  There are two kinds of tags, revision
	    tags and branch tags.  A revision tag refers to a specific
	    revision.  Its meaning stays the same from day to day.  A
	    branch tag, on the other hand, refers to the latest revision
	    on a given line of development, at any given time.  Because
	    a branch tag does not refer to a specific revision, it may
	    mean something different tomorrow than it means
	    today.</para>
	  
	  <para><xref linkend="cvs-tags"> contains branch tags that
	    users might be interested in.  When specifying a tag in
	    <application>CVSup</application>'s configuration file, it
	    must be preceded with <literal>tag=</literal>
	    (<literal>RELENG_4</literal> will become
	    <literal>tag=RELENG_4</literal>).
	    Keep in mind that only the <literal>tag=.</literal> is
	    relevant for the Ports Collection.</para>

	  <warning>
	    <para>Be very careful to type the tag name exactly as shown.
	      <application>CVSup</application> cannot distinguish
	      between valid and invalid tags.  If you misspell the tag,
	      <application>CVSup</application> will behave as though you
	      had specified a valid tag which happens to refer to no
	      files at all.  It will delete your existing sources in
	      that case.</para>
	  </warning>

	  <para>When you specify a branch tag, you normally receive the
	    latest versions of the files on that line of development.
	    If you wish to receive some past version, you can do so by
	    specifying a date with the <option>date=</option> value
	    field. The &man.cvsup.1; manual page explains how to do
	    that.</para>

	  <para>For our example, we wish to receive &os;-CURRENT.  We
	    add this line at the beginning of our
	    <filename>supfile</filename>:</para>
	  
	  <programlisting>*default tag=.</programlisting>

	  <para>There is an important special case that comes into play
	    if you specify neither a <literal>tag=</literal> field nor a
	    <literal>date=</literal> field.  In that case, you receive
	    the actual RCS files directly from the server's CVS
	    repository, rather than receiving a particular version.
	    Developers generally prefer this mode of operation.  By
	    maintaining a copy of the repository itself on their
	    systems, they gain the ability to browse the revision
	    histories and examine past versions of files.  This gain is
	    achieved at a large cost in terms of disk space,
	    however.</para>
	</listitem>

	<listitem>
	  <para><anchor id="cvsup-config-where">Where do you want to get
	    them from?</para>
	  
	  <para>We use the <literal>host=</literal> field to tell
	    <command>cvsup</command> where to obtain its updates.  Any
	    of the <link linkend="cvsup-mirrors">CVSup mirror
	      sites</link> will do, though you should try to select one
	    that is close to you in cyberspace.  In this example we will
	    use a fictional &os; distribution site,
	    <hostid role="fqdn">cvsup99.FreeBSD.org</hostid>:</para>

	  <programlisting>*default host=cvsup99.FreeBSD.org</programlisting>
	  
	  <para>You will need to change the host to one that actually
	    exists before running <application>CVSup</application>.
	    On any particular run of
	    <command>cvsup</command>, you can override the host  setting
	    on the command line, with <option>-h
	      <replaceable>hostname</replaceable></option>.</para>
	</listitem>
	
	<listitem>
	  <para><anchor id="cvsup-config-dest">Where do you want to put
	    them on your own machine?</para>
	  
	  <para>The <literal>prefix=</literal> field tells
	    <command>cvsup</command> where to put the files it receives.
	    In this example, we will put the source files directly into
	    our main source tree, <filename>/usr/src</filename>.  The
	    <filename>src</filename> directory is already implicit in
	    the collections we have chosen to receive, so this is the
	    correct specification:</para>
	  
	  <programlisting>*default prefix=/usr</programlisting>
	</listitem>

	<listitem>
	  <para><anchor id="cvsup-config-status">Where should
	    <command>cvsup</command> maintain its status files?</para>

	  <para>The <application>CVSup</application> client maintains
	    certain status files in what
	    is called the <quote>base</quote> directory.  These files
	    help <application>CVSup</application> to work more
	    efficiently, by keeping track of which updates you have
	    already received.  We will use the standard base directory,
	    <filename>/var/db</filename>:</para>

	  <programlisting>*default base=/var/db</programlisting>

	  <para>If your base directory does not already exist, now would
	    be a good time to create it.  The <command>cvsup</command>
	    client will refuse to run if the base directory does not
	    exist.</para>
	</listitem>

	<listitem>
	  <para>Miscellaneous <filename>supfile</filename>
	    settings:</para>
	  
	  <para>There is one more line of boiler plate that normally
	    needs to be present in the
	    <filename>supfile</filename>:</para>

	  <programlisting>*default release=cvs delete use-rel-suffix compress</programlisting>

	  <para><literal>release=cvs</literal> indicates that the server
	    should get its information out of the main &os; CVS
	    repository.  This is virtually always the case, but there
	    are other possibilities which are beyond the scope of this
	    discussion.</para>
	  
	  <para><literal>delete</literal> gives
	    <application>CVSup</application> permission to delete files.
	    You should always specify this, so that
	    <application>CVSup</application> can keep your source tree
	    fully up-to-date.  <application>CVSup</application> is
	    careful to delete only those files for which it is
	    responsible.  Any extra files you happen to have will be
	    left strictly alone.</para>
	  
	  <para><literal>use-rel-suffix</literal> is ... arcane.  If you
	    really want to know about it, see the &man.cvsup.1; manual
	    page.  Otherwise, just specify it and do not worry about
	    it.</para>

	  <para><literal>compress</literal> enables the use of
	    gzip-style compression on the communication channel.  If
	    your network link is T1 speed or faster, you probably should
	    not use compression.  Otherwise, it helps
	    substantially.</para>
	</listitem>

	<listitem>
	  <para>Putting it all together:</para>

	  <para>Here is the entire <filename>supfile</filename> for our
	    example:</para>

	  <programlisting>*default tag=.
*default host=cvsup99.FreeBSD.org
*default prefix=/usr
*default base=/var/db
*default release=cvs delete use-rel-suffix compress

src-all</programlisting>
	</listitem>
      </itemizedlist>
      <sect3 id="cvsup-refuse-file">
       <title>The <filename>refuse</filename> File</title>

       <para>As mentioned above, <application>CVSup</application> uses
       a <emphasis>pull method</emphasis>. Basically, this means that
       you connect to the <application>CVSup</application> server, and
       it says, <quote>Here is what you can download from
       me...</quote>, and your client responds <quote>OK, I will take
       this, this, this, and this.</quote> In the default
       configuration, the <application>CVSup</application> client will
       take every file associated with the collection and tag you
       chose in the configuration file. However, this is not always
       what you want, especially if you are synching the <filename>doc</filename>, <filename>ports</filename>, or
       <filename>www</filename> trees &mdash; most people cannot read four or five
       languages, and therefore they do not need to download the
       language-specific files. If you are
       <application>CVSup</application>ing the Ports Collection, you
       can get around this by specifying each collection individually
       (e.g., <emphasis>ports-astrology</emphasis>,
       <emphasis>ports-biology</emphasis>, etc instead of simply
       saying <emphasis>ports-all</emphasis>). However, since the <filename>doc</filename>
       and <filename>www</filename> trees do not have language-specific collections, you
       must use one of <application>CVSup</application>'s many nifty
       features: the <filename>refuse</filename> file.</para>

       <para>The <filename>refuse</filename> file essentially tells
       <application>CVSup</application> that it should not take every
       single file from a collection; in other words, it tells the
       client to <emphasis>refuse</emphasis> certain files from the
       server. The <filename>refuse</filename> file can be found (or, if you do not yet
       have one, should be placed) in
       <filename><replaceable>base</replaceable>/sup/</filename>.
       <replaceable>base</replaceable> is defined in your <filename>supfile</filename>;
       our defined <replaceable>base</replaceable> is
       <filename>/var/db</filename>, 
       which means that by default the <filename>refuse</filename> file is
       <filename>/var/db/sup/refuse</filename>.</para>

       <para>The <filename>refuse</filename> file has a very simple format; it simply
       contains the names of files or directories that you do not wish
       to download.  For example, if you cannot speak any languages other
       than English and some German, and you do not feel the need to read
       the German translation of documentation, you can put the following in your
       <filename>refuse</filename> file:</para>

       <screen>doc/bn_*
doc/da_*
doc/de_*
doc/el_*
doc/es_*
doc/fr_*
doc/hu_*
doc/it_*
doc/ja_*
doc/mn_*
doc/nl_*
doc/no_*
doc/pl_*
doc/pt_*
doc/ru_*
doc/sr_*
doc/tr_*
doc/zh_*</screen>

       <para>and so forth for the other languages (you can find the
       full list by browsing the <ulink
       url="http://www.FreeBSD.org/cgi/cvsweb.cgi/">&os;
       CVS repository</ulink>).</para>

       <para>With this very useful feature, those users who are on
       slow links or pay by the minute for their Internet connection
       will be able to save valuable time as they will no longer need
       to download files that they will never use. For more
       information on <filename>refuse</filename> files and other neat
       features of <application>CVSup</application>, please view its
       manual page.</para> 
      </sect3>
    </sect2>
    
    <sect2>
      <title>Running <application>CVSup</application></title>
      
      <para>You are now ready to try an update.  The command line for
	doing this is quite simple:</para>

      <screen>&prompt.root; <userinput>cvsup <replaceable>supfile</replaceable></userinput></screen>

      <para>where <filename><replaceable>supfile</replaceable></filename>
	is of course the name of the <filename>supfile</filename> you have just created. 
	Assuming you are running under X11, <command>cvsup</command>
	will display a GUI window with some buttons to do the usual
	things.  Press the <guibutton>go</guibutton> button, and watch it
	run.</para>
      
      <para>Since you are updating your actual
	<filename>/usr/src</filename> tree in this example, you will
	need to run the program as <username>root</username> so that
	<command>cvsup</command> has the permissions it needs to update
	your files.  Having just created your configuration file, and
	having never used this program before, that might
	understandably make you nervous. There is an easy way to do a
	trial run without touching your precious files.  Just create an
	empty directory somewhere convenient, and name it as an extra
	argument on the command line:</para>

      <screen>&prompt.root; <userinput>mkdir /var/tmp/dest</userinput>
&prompt.root; <userinput>cvsup supfile /var/tmp/dest</userinput></screen>
      
      <para>The directory you specify will be used as the destination
	directory for all file updates.
	<application>CVSup</application> will examine your usual files
	in <filename>/usr/src</filename>, but it will not modify or
	delete any of them.  Any file updates will instead land in
	<filename>/var/tmp/dest/usr/src</filename>.
	<application>CVSup</application> will also leave its base
	directory status files untouched when run this way.  The new
	versions of those files will be written into the specified
	directory.  As long as you have read access to
	<filename>/usr/src</filename>, you do not even need to be
	<username>root</username> to perform this kind of trial run.</para>
      
      <para>If you are not running X11 or if you just do not like GUIs,
	you should add a couple of options to the command line when you
	run <command>cvsup</command>:</para>
      
      <screen>&prompt.root; <userinput>cvsup -g -L 2 <replaceable>supfile</replaceable></userinput></screen>
	    
      <para>The <option>-g</option> tells
	<application>CVSup</application> not to use its GUI.  This is
	automatic if you are not running X11, but otherwise you have to
	specify it.</para>
      
      <para>The <option>-L 2</option> tells 
	<application>CVSup</application> to print out the
	details of all the file updates it is doing.  There are three
	levels of verbosity, from <option>-L 0</option> to
	<option>-L 2</option>.  The default is 0, which means total
	silence except for error messages.</para>
      
      <para>There are plenty of other options available.  For a brief
	list of them, type <command>cvsup -H</command>.  For more
	detailed descriptions, see the manual page.</para>

      <para>Once you are satisfied with the way updates are working, you
	can arrange for regular runs of <application>CVSup</application>
	using &man.cron.8;.
	Obviously, you should not let <application>CVSup</application>
	use its GUI when running it from &man.cron.8;.</para>
    </sect2>

    <sect2 id="cvsup-collec">
      <title><application>CVSup</application> File Collections</title>
	    
      <para>The file collections available via
	<application>CVSup</application> are organized hierarchically.
	There are a few large collections, and they are divided into
	smaller sub-collections.  Receiving a large collection is
	equivalent to receiving each of its sub-collections.  The
	hierarchical relationships among collections are reflected by
	the use of indentation in the list below.</para>
      
      <para>The most commonly used collections are
	<literal>src-all</literal>, and
	<literal>ports-all</literal>.  The other collections are used
	only by small groups of people for specialized purposes, and
	some mirror sites may not carry all of them.</para>
      
      <variablelist>
	<varlistentry>
	  <term><literal>cvs-all release=cvs</literal></term>
	  
	  <listitem>
	    <para>The main &os; CVS repository, including the
	      cryptography code.</para>
	    
	    <variablelist>
	      <varlistentry>
		<term><literal>distrib release=cvs</literal></term>
		
		<listitem>
		  <para>Files related to the distribution and mirroring
		    of &os;.</para>
		</listitem>
	      </varlistentry>
	      
	      <varlistentry>
		<term><literal>doc-all release=cvs</literal></term>
		<listitem>
		  <para>Sources for the &os; Handbook and other
		    documentation.  This does not include files for
		    the &os; web site.</para>
		</listitem>
	      </varlistentry>

	      <varlistentry>
		<term><literal>ports-all release=cvs</literal></term>

		<listitem>
		  <para>The &os; Ports Collection.</para>

		  <important id="cvsup-collec-pbase-warn">
		    <para>If you do not want to update the whole of
		      <literal>ports-all</literal> (the whole ports tree),
		      but use one of the subcollections listed below,
		      make sure that you <emphasis>always</emphasis> update
		      the <literal>ports-base</literal> subcollection!
		      Whenever something changes in the ports build
		      infrastructure represented by
		      <literal>ports-base</literal>, it is virtually certain
		      that those changes will be used by <quote>real</quote>
		      ports real soon.  Thus, if you only update the
		      <quote>real</quote> ports and they use some of the new
		      features, there is a very high chance that their build
		      will fail with some mysterious error message.  The
		      <emphasis>very first</emphasis> thing to do in this
		      case is to make sure that your
		      <literal>ports-base</literal> subcollection is up to
		      date.</para>
		  </important>

		  <important id="cvsup-collec-index-warn">
		    <para>If you are going to be building your own local
		      copy of <filename>ports/INDEX</filename>, you
		      <emphasis>must</emphasis> accept 
		      <literal>ports-all</literal> (the whole ports tree).
		      Building <filename>ports/INDEX</filename> with
		      a partial tree is not supported.  See the
		      <ulink url="&url.books.faq;/applications.html#MAKE-INDEX">
		      FAQ</ulink>.</para>
		  </important>

		  <variablelist>
		    <varlistentry>
		      <term><literal>ports-accessibility
			  release=cvs</literal></term>

		      <listitem>
			<para>Software to help disabled users.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-arabic
			  release=cvs</literal></term>

		      <listitem>
			<para>Arabic language support.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-archivers
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Archiving tools.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-astro
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Astronomical ports.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-audio
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Sound support.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-base
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>The Ports Collection build infrastructure -
			  various files located in the
			  <filename>Mk/</filename> and
			  <filename>Tools/</filename> subdirectories of
			  <filename>/usr/ports</filename>.</para>

			<note>
			  <para>Please see the <link
			    linkend="cvsup-collec-pbase-warn">important
			    warning above</link>: you should
			    <emphasis>always</emphasis> update this
			    subcollection, whenever you update any part of
			    the &os; Ports Collection!</para>
			</note>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-benchmarks
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Benchmarks.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-biology
			  release=cvs</literal></term>

		      <listitem>
			<para>Biology.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-cad
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Computer aided design tools.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-chinese
			  release=cvs</literal></term>
			
		      <listitem>
			<para>Chinese language support.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-comms
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Communication software.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-converters
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>character code converters.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-databases
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Databases.</para>
		      </listitem>
		    </varlistentry>
		    
		    <varlistentry>
		      <term><literal>ports-deskutils
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Things that used to be on the desktop
			  before computers were invented.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-devel
			  release=cvs</literal></term>

		      <listitem>
			<para>Development utilities.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-dns
			  release=cvs</literal></term>

		      <listitem>
			<para>DNS related software.</para>
		      </listitem>
		    </varlistentry>
		    
		    <varlistentry>
		      <term><literal>ports-editors
			  release=cvs</literal></term>

		      <listitem>
			<para>Editors.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-emulators
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Emulators for other operating
			  systems.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-finance
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Monetary, financial and related applications.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-ftp
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>FTP client and server utilities.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-games
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Games.</para>
		      </listitem>
		    </varlistentry>
		    
		    <varlistentry>
		      <term><literal>ports-german
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>German language support.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-graphics
			  release=cvs</literal></term>

		      <listitem>
			<para>Graphics utilities.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-hebrew
			  release=cvs</literal></term>

		      <listitem>
			<para>Hebrew language support.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-hungarian
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Hungarian language support.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-irc
			  release=cvs</literal></term>

		      <listitem>
			<para>Internet Relay Chat utilities.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-japanese
			  release=cvs</literal></term>

		      <listitem>
			<para>Japanese language support.</para>
		      </listitem>
		    </varlistentry>
		    
		    <varlistentry>
		      <term><literal>ports-java
			  release=cvs</literal></term>

		      <listitem>
			<para>&java; utilities.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-korean
			  release=cvs</literal></term>

		      <listitem>
			<para>Korean language support.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-lang
			  release=cvs</literal></term>

		      <listitem>
			<para>Programming languages.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-mail
			  release=cvs</literal></term>

		      <listitem>
			<para>Mail software.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-math
			  release=cvs</literal></term>

		      <listitem>
			<para>Numerical computation software.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-mbone
			  release=cvs</literal></term>

		      <listitem>
			<para>MBone applications.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-misc
			  release=cvs</literal></term>

		      <listitem>
			<para>Miscellaneous utilities.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-multimedia
			  release=cvs</literal></term>

		      <listitem>
			<para>Multimedia software.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-net
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Networking software.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-net-im
			  release=cvs</literal></term>

		      <listitem>
			<para>Instant messaging software.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-net-mgmt
			  release=cvs</literal></term>

		      <listitem>
			<para>Network management software.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-net-p2p
			  release=cvs</literal></term>

		      <listitem>
			<para>Peer to peer networking.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-news
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>USENET news software.</para>
		      </listitem>
		    </varlistentry>
		    
		    <varlistentry>
		      <term><literal>ports-palm
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Software support for <trademark class="trade">Palm</trademark>
			  series.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-polish
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Polish language support.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-ports-mgmt
			  release=cvs</literal></term>

		      <listitem>
			<para>Utilities to manage ports and packages.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-portuguese
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Portuguese language support.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-print
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Printing software.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-russian
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Russian language support.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-science
			  release=cvs</literal></term>

		      <listitem>
			<para>Science.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-security
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Security utilities.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-shells
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Command line shells.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-sysutils
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>System utilities.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-textproc
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>text processing utilities (does not
			  include desktop publishing).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-ukrainian
			  release=cvs</literal></term>

		      <listitem>
			<para>Ukrainian language support.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-vietnamese
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Vietnamese language support.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-www
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Software related to the World Wide
			  Web.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-x11
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Ports to support the X window
			  system.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-x11-clocks
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>X11 clocks.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-x11-drivers
			  release=cvs</literal></term>

		      <listitem>
			<para>X11 drivers.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-x11-fm
			  release=cvs</literal></term>

		      <listitem>
			<para>X11 file managers.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-x11-fonts
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>X11 fonts and font utilities.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-x11-toolkits
			  release=cvs</literal></term>

		      <listitem>
			<para>X11 toolkits.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-x11-servers
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>X11 servers.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-x11-themes
			  release=cvs</literal></term>

		      <listitem>
			<para>X11 themes.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>ports-x11-wm
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>X11 window managers.</para>
		      </listitem>
		    </varlistentry>
		  </variablelist>
		</listitem>
	      </varlistentry>

	      <varlistentry>
		<term><literal>projects-all release=cvs</literal></term>
		<listitem>
		  <para>Sources for the &os; projects repository.</para>
		</listitem>
	      </varlistentry>

	      <varlistentry>
		<term><literal>src-all release=cvs</literal></term>
		
		<listitem>
		  <para>The main &os; sources, including the
		    cryptography code.</para>

		  <variablelist>
		    <varlistentry>
		      <term><literal>src-base
			  release=cvs</literal></term>

		      <listitem>
			<para>Miscellaneous files at the top of
			  <filename>/usr/src</filename>.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-bin
			  release=cvs</literal></term>

		      <listitem>
			<para>User utilities that may be needed in
			  single-user mode
			  (<filename>/usr/src/bin</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-cddl
			  release=cvs</literal></term>

		      <listitem>
			<para>Utilities and libraries covered by the
			  CDDL license
			  (<filename>/usr/src/cddl</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-contrib
			  release=cvs</literal></term>

		      <listitem>
			<para>Utilities and libraries from outside the
			  &os; project, used relatively unmodified
			  (<filename>/usr/src/contrib</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-crypto release=cvs</literal></term>

		      <listitem>
			<para>Cryptography utilities and libraries from
			  outside the &os; project, used relatively
			  unmodified
			  (<filename>/usr/src/crypto</filename>).</para>
			  </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-eBones release=cvs</literal></term>
		
		      <listitem>
			<para>Kerberos and DES
			  (<filename>/usr/src/eBones</filename>).  Not
			  used in current releases of &os;.</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-etc
			  release=cvs</literal></term>

		      <listitem>
			<para>System configuration files
			  (<filename>/usr/src/etc</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-games
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Games
			  (<filename>/usr/src/games</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-gnu
			  release=cvs</literal></term>

		      <listitem>
			<para>Utilities covered by the GNU Public
			  License (<filename>/usr/src/gnu</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-include
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Header files
			  (<filename>/usr/src/include</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-kerberos5
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Kerberos5 security package
			  (<filename>/usr/src/kerberos5</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-kerberosIV
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>KerberosIV security package
			  (<filename>/usr/src/kerberosIV</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-lib
			  release=cvs</literal></term>

		      <listitem>
			<para>Libraries
			  (<filename>/usr/src/lib</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-libexec
			  release=cvs</literal></term>

		      <listitem>
			<para>System programs normally executed by other
			  programs
			  (<filename>/usr/src/libexec</filename>).</para>
		      </listitem>
		    </varlistentry>
		    
		    <varlistentry>
		      <term><literal>src-release
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Files required to produce a &os;
			  release
			  (<filename>/usr/src/release</filename>).</para>
		      </listitem>
		    </varlistentry>
		    
		    <varlistentry>
		      <term><literal>src-rescue
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>Statically linked programs for emergency
			   recovery; see &man.rescue.8;
			  (<filename>/usr/src/rescue</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-sbin release=cvs</literal></term>

		      <listitem>
			<para>System utilities for single-user mode
			  (<filename>/usr/src/sbin</filename>).</para>
		      </listitem>
		    </varlistentry>
		    
		    <varlistentry>
		      <term><literal>src-secure
			  release=cvs</literal></term>

		      <listitem>
			<para>Cryptographic libraries and commands
			  (<filename>/usr/src/secure</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-share
			  release=cvs</literal></term>

		      <listitem>
			<para>Files that can be shared across multiple
			  systems
			  (<filename>/usr/src/share</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-sys
			  release=cvs</literal></term>

		      <listitem>
			<para>The kernel
			  (<filename>/usr/src/sys</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-sys-crypto
			release=cvs</literal></term>
		
		      <listitem>
			<para>Kernel cryptography code
			  (<filename>/usr/src/sys/crypto</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-tools
			  release=cvs</literal></term>

		      <listitem>
			<para>Various tools for the maintenance of
			  &os;
			  (<filename>/usr/src/tools</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-usrbin
			  release=cvs</literal></term>

		      <listitem>
			<para>User utilities
			  (<filename>/usr/src/usr.bin</filename>).</para>
		      </listitem>
		    </varlistentry>

		    <varlistentry>
		      <term><literal>src-usrsbin
			  release=cvs</literal></term>
		      
		      <listitem>
			<para>System utilities
			  (<filename>/usr/src/usr.sbin</filename>).</para>
		      </listitem>
		    </varlistentry>
		  </variablelist>
		</listitem>
	      </varlistentry>
	      
	      <varlistentry>
		<term><literal>www release=cvs</literal></term>
		
		<listitem>
		  <para>The sources for the &os; WWW site.</para>
		</listitem>
	      </varlistentry>
	    </variablelist>
	  </listitem>
	</varlistentry>
	
	<varlistentry>
	  <term><literal>distrib release=self</literal></term>

	  <listitem>
	    <para>The <application>CVSup</application> server's own 
	      configuration files.  Used by <application>CVSup</application>
	      mirror sites.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term><literal>gnats release=current</literal></term>

	  <listitem>
	    <para>The GNATS bug-tracking database.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term><literal>mail-archive release=current</literal></term>
	  
	  <listitem>
	    <para>&os; mailing list archive.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term><literal>www release=current</literal></term>

	  <listitem>
	    <para>The pre-processed &os; WWW site files (not the
	      source files).  Used by WWW mirror sites.</para>
	  </listitem>
	</varlistentry>
      </variablelist>
    </sect2>

    <sect2>
      <title>For More Information</title>

      <para>For the <application>CVSup</application> FAQ and other 
	information about <application>CVSup</application>, see
	<ulink url="http://www.cvsup.org">The
	  CVSup Home Page</ulink>.</para>

      <para>Most &os;-related discussion of
	<application>CVSup</application> takes place on the
	&a.hackers;.  New versions of the software are announced there,
	as well as on the &a.announce;.</para>

      <para>For questions or bug reports about
	<application>CVSup</application> take a look at the
	<ulink url="http://www.cvsup.org/faq.html#bugreports">
	CVSup FAQ</ulink>.</para>
    </sect2>

    <sect2 id="cvsup-mirrors">
    <title>CVSup Sites</title>

    <para><link linkend="cvsup">CVSup</link> servers for &os; are running
      at the following sites:</para>

    &chap.mirrors.cvsup.inc;
    </sect2>
  </sect1>
  
  <sect1 id="cvs-tags">
    <title>CVS Tags</title>

    <para>When obtaining or updating sources using
      <application>cvs</application> or
      <application>CVSup</application>, a revision tag must be specified.
      A revision tag refers to either a particular line of &os;
      development, or a specific point in time.  The first type are called
      <quote>branch tags</quote>, and the second type are called
      <quote>release tags</quote>.</para>

    <sect2>
      <title>Branch Tags</title>

      <para>All of these, with the exception of <literal>HEAD</literal> (which
	is always a valid tag), only apply to the <filename>src/</filename>
	tree.  The <filename>ports/</filename>, <filename>doc/</filename>, and
	<filename>www/</filename> trees are not branched.</para>

    <variablelist>
      <varlistentry>
	<term>HEAD</term>

	<listitem>
	  <para>Symbolic name for the main line, or &os;-CURRENT.
	    Also the default when no revision is specified.</para>

	  <para>In <application>CVSup</application>, this tag is represented
	    by a <literal>.</literal> (not punctuation, but a literal
	    <literal>.</literal> character).</para>

	  <note>
	    <para>In CVS, this is the default when no revision tag is
	      specified.  It is usually <emphasis>not</emphasis>
	      a good idea to checkout or update to CURRENT sources
	      on a STABLE machine, unless that is your intent.</para>
	  </note>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_8</term>

	<listitem>
	  <para>The line of development for &os;-8.X, also known
	    as &os; 8-STABLE</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_8_0</term>

	<listitem>
	  <para>The release branch for &os;-8.0, used only for
	    security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_7</term>

	<listitem>
	  <para>The line of development for &os;-7.X, also known
	    as &os; 7-STABLE</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_7_3</term>

	<listitem>
	  <para>The release branch for &os;-7.3, used only for
	    security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_7_2</term>

	<listitem>
	  <para>The release branch for &os;-7.2, used only for
	    security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_7_1</term>

	<listitem>
	  <para>The release branch for &os;-7.1, used only for
	    security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_7_0</term>

	<listitem>
	  <para>The release branch for &os;-7.0, used only for
	    security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_6</term>

	<listitem>
	  <para>The line of development for &os;-6.X, also known
	    as &os; 6-STABLE</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_6_4</term>

	<listitem>
	  <para>The release branch for &os;-6.4, used only for
	    security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_6_3</term>

	<listitem>
	  <para>The release branch for &os;-6.3, used only for
	    security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_6_2</term>

	<listitem>
	  <para>The release branch for &os;-6.2, used only for
	    security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_6_1</term>

	<listitem>
	  <para>The release branch for &os;-6.1, used only for
	    security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_6_0</term>

	<listitem>
	  <para>The release branch for &os;-6.0, used only for
	    security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5</term>

	<listitem>
	  <para>The line of development for &os;-5.X, also known
	    as &os; 5-STABLE.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_5</term>

	<listitem>
	  <para>The release branch for &os;-5.5, used only 
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_4</term>

	<listitem>
	  <para>The release branch for &os;-5.4, used only 
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_3</term>

	<listitem>
	  <para>The release branch for &os;-5.3, used only 
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_2</term>

	<listitem>
	  <para>The release branch for &os;-5.2 and &os;-5.2.1, used only 
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_1</term>

	<listitem>
	  <para>The release branch for &os;-5.1, used only 
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_0</term>

	<listitem>
	  <para>The release branch for &os;-5.0, used only 
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4</term>

	<listitem>
	  <para>The line of development for &os;-4.X, also known
	    as &os; 4-STABLE.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_11</term>

	<listitem>
	  <para>The release branch for &os;-4.11, used only
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_10</term>

	<listitem>
	  <para>The release branch for &os;-4.10, used only 
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_9</term>

	<listitem>
	  <para>The release branch for &os;-4.9, used only 
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_8</term>

	<listitem>
	  <para>The release branch for &os;-4.8, used only 
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_7</term>

	<listitem>
	  <para>The release branch for &os;-4.7, used only 
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_6</term>

	<listitem>
	  <para>The release branch for &os;-4.6 and &os;-4.6.2,
            used only for security advisories and other
            critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_5</term>

	<listitem>
	  <para>The release branch for &os;-4.5, used only
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_4</term>

	<listitem>
	  <para>The release branch for &os;-4.4, used only
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_3</term>

	<listitem>
	  <para>The release branch for &os;-4.3, used only
	    for security advisories and other critical fixes.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_3</term>

	<listitem>
	  <para>The line of development for &os;-3.X, also known
	    as 3.X-STABLE.</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_2_2</term>

	<listitem>
	  <para>The line of development for &os;-2.2.X, also known
	    as 2.2-STABLE.  This branch is mostly obsolete.</para>
	</listitem>
      </varlistentry>
    </variablelist>
    </sect2>

    <sect2>
      <title>Release Tags</title>

      <para>These tags refer to a specific point in time when a particular
	version	of &os; was released.  The release engineering process is
	documented in more detail by the
	<ulink url="&url.base;/releng/">Release Engineering
	  Information</ulink> and
        <ulink url="&url.articles.releng;/release-proc.html">Release
	  Process</ulink> documents.
	The <filename class="directory">src</filename> tree uses tag names that
	start with <literal>RELENG_</literal> tags.
	The <filename class="directory">ports</filename> and
	<filename class="directory">doc</filename> trees use tags whose names
	begin with <literal>RELEASE</literal> tags.
	Finally, the <filename class="directory">www</filename> tree is not
	tagged with any special name for releases.</para>

    <variablelist>
      <varlistentry>
	<term>RELENG_8_0_0_RELEASE</term>

	<listitem>
	  <para>&os; 8.0</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_7_2_0_RELEASE</term>

	<listitem>
	  <para>&os; 7.2</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_7_1_0_RELEASE</term>

	<listitem>
	  <para>&os; 7.1</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_7_0_0_RELEASE</term>

	<listitem>
	  <para>&os; 7.0</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_6_4_0_RELEASE</term>

	<listitem>
	  <para>&os; 6.4</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_6_3_0_RELEASE</term>

	<listitem>
	  <para>&os; 6.3</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_6_2_0_RELEASE</term>

	<listitem>
	  <para>&os; 6.2</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_6_1_0_RELEASE</term>

	<listitem>
	  <para>&os; 6.1</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_6_0_0_RELEASE</term>

	<listitem>
	  <para>&os; 6.0</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_5_0_RELEASE</term>

	<listitem>
	  <para>&os; 5.5</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_4_0_RELEASE</term>

	<listitem>
	  <para>&os; 5.4</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_11_0_RELEASE</term>

	<listitem>
	  <para>&os; 4.11</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_3_0_RELEASE</term>

	<listitem>
	  <para>&os; 5.3</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_10_0_RELEASE</term>

	<listitem>
	  <para>&os; 4.10</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_2_1_RELEASE</term>

	<listitem>
	  <para>&os; 5.2.1</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_2_0_RELEASE</term>

	<listitem>
	  <para>&os; 5.2</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_9_0_RELEASE</term>

	<listitem>
	  <para>&os; 4.9</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_1_0_RELEASE</term>

	<listitem>
	  <para>&os; 5.1</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_8_0_RELEASE</term>

	<listitem>
	  <para>&os; 4.8</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_5_0_0_RELEASE</term>

	<listitem>
	  <para>&os; 5.0</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_7_0_RELEASE</term>

	<listitem>
	  <para>&os; 4.7</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_6_2_RELEASE</term>

	<listitem>
	  <para>&os; 4.6.2</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_6_1_RELEASE</term>

	<listitem>
	  <para>&os; 4.6.1</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_6_0_RELEASE</term>

	<listitem>
	  <para>&os; 4.6</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_5_0_RELEASE</term>

	<listitem>
	  <para>&os; 4.5</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_4_0_RELEASE</term>

	<listitem>
	  <para>&os; 4.4</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_3_0_RELEASE</term>

	<listitem>
	  <para>&os; 4.3</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_2_0_RELEASE</term>

	<listitem>
	  <para>&os; 4.2</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_1_1_RELEASE</term>

	<listitem>
	  <para>&os; 4.1.1</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_1_0_RELEASE</term>

	<listitem>
	  <para>&os; 4.1</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_4_0_0_RELEASE</term>

	<listitem>
	  <para>&os; 4.0</para>
	</listitem>
      </varlistentry>
	  
      <varlistentry>
	<term>RELENG_3_5_0_RELEASE</term>

	<listitem>
	  <para>&os;-3.5</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_3_4_0_RELEASE</term>

	<listitem>
	  <para>&os;-3.4</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_3_3_0_RELEASE</term>

	<listitem>
	  <para>&os;-3.3</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_3_2_0_RELEASE</term>

	<listitem>
	  <para>&os;-3.2</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_3_1_0_RELEASE</term>

	<listitem>
	  <para>&os;-3.1</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_3_0_0_RELEASE</term>

	<listitem>
	  <para>&os;-3.0</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_2_2_8_RELEASE</term>

	<listitem>
	  <para>&os;-2.2.8</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_2_2_7_RELEASE</term>

	<listitem>
	  <para>&os;-2.2.7</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_2_2_6_RELEASE</term>

	<listitem>
	  <para>&os;-2.2.6</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_2_2_5_RELEASE</term>

	<listitem>
	  <para>&os;-2.2.5</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_2_2_2_RELEASE</term>

	<listitem>
	  <para>&os;-2.2.2</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_2_2_1_RELEASE</term>

	<listitem>
	  <para>&os;-2.2.1</para>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>RELENG_2_2_0_RELEASE</term>

	<listitem>
	  <para>&os;-2.2.0</para>
	</listitem>
      </varlistentry>
    </variablelist>
    </sect2>
  </sect1>

  <sect1 id="mirrors-afs">
    <title>AFS Sites</title>

    <para>AFS servers for &os; are running at the following sites:</para>

    <variablelist>
      <varlistentry>
	<term>Sweden</term>

	<listitem>
	  <para>The path to the files are:
  	    <filename>/afs/stacken.kth.se/ftp/pub/FreeBSD/</filename></para>

	  <programlisting>stacken.kth.se         # Stacken Computer Club, KTH, Sweden
130.237.234.43         #hot.stacken.kth.se
130.237.237.230        #fishburger.stacken.kth.se
130.237.234.3          #milko.stacken.kth.se</programlisting>

	  <para>Maintainer <email>ftp@stacken.kth.se</email></para>
	</listitem>
      </varlistentry>
    </variablelist>
  </sect1>

  <sect1 id="mirrors-rsync">
    <title>rsync Sites</title>

    <para>The following sites make &os; available through the rsync
      protocol.  The <application>rsync</application> utility works in
      much the same way as the &man.rcp.1; command,
      but has more options and uses the rsync remote-update protocol
      which transfers only the differences between two sets of files,
      thus greatly speeding up the synchronization over the network.  
      This is most useful if you are a mirror site for the
      &os; FTP server, or the CVS repository.  The
      <application>rsync</application> suite is available for many
      operating systems, on &os;, see the
      <filename role="package">net/rsync</filename>
      port or use the package.</para>

    <variablelist>
      <varlistentry>
	<term>Czech Republic</term>

	<listitem>
	  <para>rsync://ftp.cz.FreeBSD.org/</para>

	  <para>Available collections:</para>
	  <itemizedlist>
	    <listitem><para>ftp: A partial mirror of the &os; FTP
	      server.</para></listitem>
	    <listitem><para>&os;: A full mirror of the &os; FTP
	      server.</para></listitem>
	  </itemizedlist>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>Netherlands</term>

	<listitem>
	  <para>rsync://ftp.nl.FreeBSD.org/</para>

	  <para>Available collections:</para>
	  <itemizedlist>
	    <listitem><para>&os;: A full mirror of the
	      &os; FTP server.</para></listitem>
	  </itemizedlist>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>Russia</term>

	<listitem>
	  <para>rsync://ftp.mtu.ru/</para>

	  <para>Available collections:</para>
	  <itemizedlist>
	    <listitem><para>&os;: A full mirror of the &os; FTP
	      server.</para></listitem>
	    <listitem><para>&os;-gnats: The GNATS bug-tracking
	      database.</para></listitem>
	    <listitem><para>&os;-Archive: The mirror of &os; Archive FTP
	      server.</para></listitem>
	  </itemizedlist>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>Taiwan</term>

	<listitem>
	  <para>rsync://ftp.tw.FreeBSD.org/</para>
	  <para>rsync://ftp2.tw.FreeBSD.org/</para>
	  <para>rsync://ftp6.tw.FreeBSD.org/</para>

	  <para>Available collections:</para>
	  <itemizedlist>
	    <listitem><para>&os;: A full mirror of the &os; FTP
	      server.</para></listitem>
	  </itemizedlist>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>United Kingdom</term>

	<listitem>
	  <para>rsync://rsync.mirrorservice.org/</para>

	  <para>Available collections:</para>
	  <itemizedlist>
	    <listitem><para>sites/ftp.freebsd.org: A full mirror of the
	      &os; FTP server.</para></listitem>
	  </itemizedlist>
	</listitem>
      </varlistentry>

      <varlistentry>
	<term>United States of America</term>

	<listitem>
	  <para>rsync://ftp-master.FreeBSD.org/</para>

	  <para>This server may only be used by &os; primary mirror
	    sites.</para>
	  <para>Available collections:</para>
	  <itemizedlist>
	    <listitem><para>&os;: The master archive of the &os;
	      FTP server.</para></listitem>
	    <listitem><para>acl: The &os; master ACL
	      list.</para></listitem>  
	  </itemizedlist>

	  <para>rsync://ftp13.FreeBSD.org/</para>

	  <para>Available collections:</para>
	  <itemizedlist>
	    <listitem><para>&os;: A full mirror of the &os; FTP
	      server.</para></listitem>
	  </itemizedlist>
	</listitem>
      </varlistentry>
    </variablelist>
  </sect1>  
</appendix>

<!--
     Local Variables:
     mode: sgml
     sgml-declaration: "../appendix.decl"
     sgml-indent-data: t
     sgml-omittag: nil
     sgml-always-quote-attributes: t
     sgml-parent-document: ("../book.sgml" "part" "appendix")
     End:
-->