This file is indexed.

/usr/share/doc/discover/guide.html is in libdiscover2 2.1.2-7ubuntu1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

   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
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5071
5072
5073
5074
5075
5076
5077
5078
5079
5080
5081
5082
5083
5084
5085
5086
5087
5088
5089
5090
5091
5092
5093
5094
5095
5096
5097
5098
5099
5100
5101
5102
5103
5104
5105
5106
5107
5108
5109
5110
5111
5112
5113
5114
5115
5116
5117
5118
5119
5120
5121
5122
5123
5124
5125
5126
5127
5128
5129
5130
5131
5132
5133
5134
5135
5136
5137
5138
5139
5140
5141
5142
5143
5144
5145
5146
5147
5148
5149
5150
5151
5152
5153
5154
5155
5156
5157
5158
5159
5160
5161
5162
5163
5164
5165
5166
5167
5168
5169
5170
5171
5172
5173
5174
5175
5176
5177
5178
5179
5180
5181
5182
5183
5184
5185
5186
5187
5188
5189
5190
5191
5192
5193
5194
5195
5196
5197
5198
5199
5200
5201
5202
5203
5204
5205
5206
5207
5208
5209
5210
5211
5212
5213
5214
5215
5216
5217
5218
5219
5220
5221
5222
5223
5224
5225
5226
5227
5228
5229
5230
5231
5232
5233
5234
5235
5236
5237
5238
5239
5240
5241
5242
5243
5244
5245
5246
5247
5248
5249
5250
5251
5252
5253
5254
5255
5256
5257
5258
5259
5260
5261
5262
5263
5264
5265
5266
5267
5268
5269
5270
5271
5272
5273
5274
5275
5276
5277
5278
5279
5280
5281
5282
5283
5284
5285
5286
5287
5288
5289
5290
5291
5292
5293
5294
5295
5296
5297
5298
5299
5300
5301
5302
5303
5304
5305
5306
5307
5308
5309
5310
5311
5312
5313
5314
5315
5316
5317
5318
5319
5320
5321
5322
5323
5324
5325
5326
5327
5328
5329
5330
5331
5332
5333
5334
5335
5336
5337
5338
5339
5340
5341
5342
5343
5344
5345
5346
5347
5348
5349
5350
5351
5352
5353
5354
5355
5356
5357
5358
5359
5360
5361
5362
5363
5364
5365
5366
5367
5368
5369
5370
5371
5372
5373
5374
5375
5376
5377
5378
5379
5380
5381
5382
5383
5384
5385
5386
5387
5388
5389
5390
5391
5392
5393
5394
5395
5396
5397
5398
5399
5400
5401
5402
5403
5404
5405
5406
5407
5408
5409
5410
5411
5412
5413
5414
5415
5416
5417
5418
5419
5420
5421
5422
5423
5424
5425
5426
5427
5428
5429
5430
5431
5432
5433
5434
5435
5436
5437
5438
5439
5440
5441
5442
5443
5444
5445
5446
5447
5448
5449
5450
5451
5452
5453
5454
5455
5456
5457
5458
5459
5460
5461
5462
5463
5464
5465
5466
5467
5468
5469
5470
5471
5472
5473
5474
5475
5476
5477
5478
5479
5480
5481
5482
5483
5484
5485
5486
5487
5488
5489
5490
5491
5492
5493
5494
5495
5496
5497
5498
5499
5500
5501
5502
5503
5504
5505
5506
5507
5508
5509
5510
5511
5512
5513
5514
5515
5516
5517
5518
5519
5520
5521
5522
5523
5524
5525
5526
5527
5528
5529
5530
5531
5532
5533
5534
5535
5536
5537
5538
5539
5540
5541
5542
5543
5544
5545
5546
5547
5548
5549
5550
5551
5552
5553
5554
5555
5556
5557
5558
5559
5560
5561
5562
5563
5564
5565
5566
5567
5568
5569
5570
5571
5572
5573
5574
5575
5576
5577
5578
5579
5580
5581
5582
5583
5584
5585
5586
5587
5588
5589
5590
5591
5592
5593
5594
5595
5596
5597
5598
5599
5600
5601
5602
5603
5604
5605
5606
5607
5608
5609
5610
5611
5612
5613
5614
5615
5616
5617
5618
5619
5620
5621
5622
5623
5624
5625
5626
5627
5628
5629
5630
5631
5632
5633
5634
5635
5636
5637
5638
5639
5640
5641
5642
5643
5644
5645
5646
5647
5648
5649
5650
5651
5652
5653
5654
5655
5656
5657
5658
5659
5660
5661
5662
5663
5664
5665
5666
5667
5668
5669
5670
5671
5672
5673
5674
5675
5676
5677
5678
5679
5680
5681
5682
5683
5684
5685
5686
5687
5688
5689
5690
5691
5692
5693
5694
5695
5696
5697
5698
5699
5700
5701
5702
5703
5704
5705
5706
5707
5708
5709
5710
5711
5712
5713
5714
5715
5716
5717
5718
5719
5720
5721
5722
5723
5724
5725
5726
5727
5728
5729
5730
5731
5732
5733
5734
5735
5736
5737
5738
5739
5740
5741
5742
5743
5744
5745
5746
5747
5748
5749
5750
5751
5752
5753
5754
5755
5756
5757
5758
5759
5760
5761
5762
5763
5764
5765
5766
5767
5768
5769
5770
5771
5772
5773
5774
5775
5776
5777
5778
5779
5780
5781
5782
5783
5784
5785
5786
5787
5788
5789
5790
5791
5792
5793
5794
5795
5796
5797
5798
5799
5800
5801
5802
5803
5804
5805
5806
5807
5808
5809
5810
5811
5812
5813
5814
5815
5816
5817
5818
5819
5820
5821
5822
5823
5824
5825
5826
5827
5828
5829
5830
5831
5832
5833
5834
5835
5836
5837
5838
5839
5840
5841
5842
5843
5844
5845
5846
5847
5848
5849
5850
5851
5852
5853
5854
5855
5856
5857
5858
5859
5860
5861
5862
5863
5864
5865
5866
5867
5868
5869
5870
5871
5872
5873
5874
5875
5876
5877
5878
5879
5880
5881
5882
5883
5884
5885
5886
5887
5888
5889
5890
5891
5892
5893
5894
5895
5896
5897
5898
5899
5900
5901
5902
5903
5904
5905
5906
5907
5908
5909
5910
5911
5912
5913
5914
5915
5916
5917
5918
5919
5920
5921
5922
5923
5924
5925
5926
5927
5928
5929
5930
5931
5932
5933
5934
5935
5936
5937
5938
5939
5940
5941
5942
5943
5944
5945
5946
5947
5948
5949
5950
5951
5952
5953
5954
5955
5956
5957
5958
5959
5960
5961
5962
5963
5964
5965
5966
5967
5968
5969
5970
5971
5972
5973
5974
5975
5976
5977
5978
5979
5980
5981
5982
5983
5984
5985
5986
5987
5988
5989
5990
5991
5992
5993
5994
5995
5996
5997
5998
5999
6000
6001
6002
6003
6004
6005
6006
6007
6008
6009
6010
6011
6012
6013
6014
6015
6016
6017
6018
6019
6020
6021
6022
6023
6024
6025
6026
6027
6028
6029
6030
6031
6032
6033
6034
6035
6036
6037
6038
6039
6040
6041
6042
6043
6044
6045
6046
6047
6048
6049
6050
6051
6052
6053
6054
6055
6056
6057
6058
6059
6060
6061
6062
6063
6064
6065
6066
6067
6068
6069
6070
6071
6072
6073
6074
6075
6076
6077
6078
6079
6080
6081
6082
6083
6084
6085
6086
6087
6088
6089
6090
6091
6092
6093
6094
6095
6096
6097
6098
6099
6100
6101
6102
6103
6104
6105
6106
6107
6108
6109
6110
6111
6112
6113
6114
6115
6116
6117
6118
6119
6120
6121
6122
6123
6124
6125
6126
6127
6128
6129
6130
6131
6132
6133
6134
6135
6136
6137
6138
6139
6140
6141
6142
6143
6144
6145
6146
6147
6148
6149
6150
6151
6152
6153
6154
6155
6156
6157
6158
6159
6160
6161
6162
6163
6164
6165
6166
6167
6168
6169
6170
6171
6172
6173
6174
6175
6176
6177
6178
6179
6180
6181
6182
6183
6184
6185
6186
6187
6188
6189
6190
6191
6192
6193
6194
6195
6196
6197
6198
6199
6200
6201
6202
6203
6204
6205
6206
6207
6208
6209
6210
6211
6212
6213
6214
6215
6216
6217
6218
6219
6220
6221
6222
6223
6224
6225
6226
6227
6228
6229
6230
6231
6232
6233
6234
6235
6236
6237
6238
6239
6240
6241
6242
6243
6244
6245
6246
6247
6248
6249
6250
6251
6252
6253
6254
6255
6256
6257
6258
6259
6260
6261
6262
6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
6273
6274
6275
6276
6277
6278
6279
6280
6281
6282
6283
6284
6285
6286
6287
6288
6289
6290
6291
6292
6293
6294
6295
6296
6297
6298
6299
6300
6301
6302
6303
6304
6305
6306
6307
6308
6309
6310
6311
6312
6313
6314
6315
6316
6317
6318
6319
6320
6321
6322
6323
6324
6325
6326
6327
6328
6329
6330
6331
6332
6333
6334
6335
6336
6337
6338
6339
6340
6341
6342
6343
6344
6345
6346
6347
6348
6349
6350
6351
6352
6353
6354
6355
6356
6357
6358
6359
6360
6361
6362
6363
6364
6365
6366
6367
6368
6369
6370
6371
6372
6373
6374
6375
6376
6377
6378
6379
6380
6381
6382
6383
6384
6385
6386
6387
6388
6389
6390
6391
6392
6393
6394
6395
6396
6397
6398
6399
6400
6401
6402
6403
6404
6405
6406
6407
6408
6409
6410
6411
6412
6413
6414
6415
6416
6417
6418
6419
6420
6421
6422
6423
6424
6425
6426
6427
6428
6429
6430
6431
6432
6433
6434
6435
6436
6437
6438
6439
6440
6441
6442
6443
6444
6445
6446
6447
6448
6449
6450
6451
6452
6453
6454
6455
6456
6457
6458
6459
6460
6461
6462
6463
6464
6465
6466
6467
6468
6469
6470
6471
6472
6473
6474
6475
6476
6477
6478
6479
6480
6481
6482
6483
6484
6485
6486
6487
6488
6489
6490
6491
6492
6493
6494
6495
6496
6497
6498
6499
6500
6501
6502
6503
6504
6505
6506
6507
6508
6509
6510
6511
6512
6513
6514
6515
6516
6517
6518
6519
6520
6521
6522
6523
6524
6525
6526
6527
6528
6529
6530
6531
6532
6533
6534
6535
6536
6537
6538
6539
6540
6541
6542
6543
6544
6545
6546
6547
6548
6549
6550
6551
6552
6553
6554
6555
6556
6557
6558
6559
6560
6561
6562
6563
6564
6565
6566
6567
6568
6569
6570
6571
6572
6573
6574
6575
6576
6577
6578
6579
6580
6581
6582
6583
6584
6585
6586
6587
6588
6589
6590
6591
6592
6593
6594
6595
6596
6597
6598
6599
6600
6601
6602
6603
6604
6605
6606
6607
6608
6609
6610
6611
6612
6613
6614
6615
6616
6617
6618
6619
6620
6621
6622
6623
6624
6625
6626
6627
6628
6629
6630
6631
6632
6633
6634
6635
6636
6637
6638
6639
6640
6641
6642
6643
6644
6645
6646
6647
6648
6649
6650
6651
6652
6653
6654
6655
6656
6657
6658
6659
6660
6661
6662
6663
6664
6665
6666
6667
6668
6669
6670
6671
6672
6673
6674
6675
6676
6677
6678
6679
6680
6681
6682
6683
6684
6685
6686
6687
6688
6689
6690
6691
6692
6693
6694
6695
6696
6697
6698
6699
6700
6701
6702
6703
6704
6705
6706
6707
6708
6709
6710
6711
6712
6713
6714
6715
6716
6717
6718
6719
6720
6721
6722
6723
6724
6725
6726
6727
6728
6729
6730
6731
6732
6733
6734
6735
6736
6737
6738
6739
6740
6741
6742
6743
6744
6745
6746
6747
6748
6749
6750
6751
6752
6753
6754
6755
6756
6757
6758
6759
6760
6761
6762
6763
6764
6765
6766
6767
6768
6769
6770
6771
6772
6773
6774
6775
6776
6777
6778
6779
6780
6781
6782
6783
6784
6785
6786
6787
6788
6789
6790
6791
6792
6793
6794
6795
6796
6797
6798
6799
6800
6801
6802
6803
6804
6805
6806
6807
6808
6809
6810
6811
6812
6813
6814
6815
6816
6817
6818
6819
6820
6821
6822
6823
6824
6825
6826
6827
6828
6829
6830
6831
6832
6833
6834
6835
6836
6837
6838
6839
6840
6841
6842
6843
6844
6845
6846
6847
6848
6849
6850
6851
6852
6853
6854
6855
6856
6857
6858
6859
6860
6861
6862
6863
6864
6865
6866
6867
6868
6869
6870
6871
6872
6873
6874
6875
6876
6877
6878
6879
6880
6881
6882
6883
6884
6885
6886
6887
6888
6889
6890
6891
6892
6893
6894
6895
6896
6897
6898
6899
6900
6901
6902
6903
6904
6905
6906
6907
6908
6909
6910
6911
6912
6913
6914
6915
6916
6917
6918
6919
6920
6921
6922
6923
6924
6925
6926
6927
6928
6929
6930
6931
6932
6933
6934
6935
6936
6937
6938
6939
6940
6941
6942
6943
6944
6945
6946
6947
6948
6949
6950
6951
6952
6953
6954
6955
6956
6957
6958
6959
6960
6961
6962
6963
6964
6965
6966
6967
6968
6969
6970
6971
6972
6973
6974
6975
6976
6977
6978
6979
6980
6981
6982
6983
6984
6985
6986
6987
6988
6989
6990
6991
6992
6993
6994
6995
6996
6997
6998
6999
7000
7001
7002
7003
7004
7005
7006
7007
7008
7009
7010
7011
7012
7013
7014
7015
7016
7017
7018
7019
7020
7021
7022
7023
7024
7025
7026
7027
7028
7029
7030
7031
7032
7033
7034
7035
7036
7037
7038
7039
7040
7041
7042
7043
7044
7045
7046
7047
7048
7049
7050
7051
7052
7053
7054
7055
7056
7057
7058
7059
7060
7061
7062
7063
7064
7065
7066
7067
7068
7069
7070
7071
7072
7073
7074
7075
7076
7077
7078
7079
7080
7081
7082
7083
7084
7085
7086
7087
7088
7089
7090
7091
7092
7093
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>The Discover Hardware Detection System</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"></HEAD
><BODY
CLASS="book"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="BOOK"
><A
NAME="AEN1"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
><A
NAME="AEN2"
>The <SPAN
CLASS="application"
>Discover</SPAN
> Hardware Detection System</A
></H1
><H3
CLASS="author"
><A
NAME="AEN5"
></A
>G. Branden Robinson</H3
><H3
CLASS="author"
><A
NAME="AEN9"
></A
>John R. Daily</H3
><P
CLASS="copyright"
>Copyright &copy; 2002 Progeny Linux Systems, Inc.</P
><P
CLASS="copyright"
>Copyright &copy; 2002 Hewlett-Packard Company</P
><DIV
CLASS="legalnotice"
><P
></P
><A
NAME="AEN22"
></A
><P
>Permission is hereby granted, free of charge, to any
    person obtaining a copy of this software and associated
    documentation files (the "Software"), to deal in
    the Software without restriction, including without
    limitation the rights to use, copy, modify, merge, publish,
    distribute, sublicense, and/or sell copies of the Software,
    and to permit persons to whom the Software is furnished to
    do so, subject to the following conditions:</P
><P
>The above copyright notice and this permission notice
    shall be included in all copies or substantial portions of
    the Software.</P
><P
>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT
    WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
    LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
    PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
    THE COPYRIGHT HOLDER(S) BE LIABLE FOR ANY CLAIM, DAMAGES OR
    OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
    OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
    SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
    SOFTWARE.</P
><P
></P
></DIV
><DIV
CLASS="legalnotice"
><P
></P
><A
NAME="AEN26"
></A
><P
>Linux is a registered trademark of Linus Torvalds.</P
><P
></P
></DIV
><SPAN
CLASS="releaseinfo"
>$Progeny$<BR></SPAN
><HR></DIV
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
><A
HREF="#pr-what_is_discover"
>What Is <SPAN
CLASS="application"
>Discover</SPAN
>?</A
></DT
><DT
>I. <A
HREF="#pt-data_structure"
>Data Structure</A
></DT
><DD
><DL
><DT
>1. <A
HREF="#ch-overview_discover_data_format"
>Overview of
      the <SPAN
CLASS="application"
>Discover</SPAN
> Data Format</A
></DT
><DT
>2. <A
HREF="#ch-master_list"
>Master List</A
></DT
><DT
>3. <A
HREF="#ch-busclass_lists"
>Busclass Lists</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="#sc-busclass_list_element"
>The
        <CODE
CLASS="sgmltag"
>busclass_list</CODE
> element</A
></DT
><DD
><DL
><DT
>3.1.1. <A
HREF="#sc-busclass_list_element_bus_attribute"
>The
          <CODE
CLASS="sgmltag"
>bus</CODE
> attribute</A
></DT
></DL
></DD
><DT
>3.2. <A
HREF="#sc-busclass_element"
>The
        <CODE
CLASS="sgmltag"
>busclass</CODE
> element</A
></DT
><DD
><DL
><DT
>3.2.1. <A
HREF="#sc-busclass_element_id_attribute"
>The
          <CODE
CLASS="sgmltag"
>id</CODE
> attribute</A
></DT
><DT
>3.2.2. <A
HREF="#sc-busclass_element_name_attribute"
>The
          <CODE
CLASS="sgmltag"
>name</CODE
> attribute</A
></DT
></DL
></DD
></DL
></DD
><DT
>4. <A
HREF="#ch-vendor_lists"
>Vendor Lists</A
></DT
><DD
><DL
><DT
>4.1. <A
HREF="#sc-vendor_list_element"
>The
        <CODE
CLASS="sgmltag"
>vendor_list</CODE
> element</A
></DT
><DD
><DL
><DT
>4.1.1. <A
HREF="#sc-vendor_list_element_bus_attribute"
>The
          <CODE
CLASS="sgmltag"
>bus</CODE
> attribute</A
></DT
></DL
></DD
><DT
>4.2. <A
HREF="#sc-vendor_element"
>The <CODE
CLASS="sgmltag"
>vendor</CODE
> element</A
></DT
><DD
><DL
><DT
>4.2.1. <A
HREF="#sc-vendor_element_id_attribute"
>The <CODE
CLASS="sgmltag"
>id</CODE
> attribute</A
></DT
><DT
>4.2.2. <A
HREF="#sc-vendor_element_name_attribute"
>The <CODE
CLASS="sgmltag"
>name</CODE
> attribute</A
></DT
></DL
></DD
></DL
></DD
><DT
>5. <A
HREF="#ch-device_lists"
>Device Lists</A
></DT
><DD
><DL
><DT
>5.1. <A
HREF="#sc-device_list_element"
>The
        <CODE
CLASS="sgmltag"
>device_list</CODE
> element</A
></DT
><DD
><DL
><DT
>5.1.1. <A
HREF="#sc-device_list_element_bus_attribute"
>The
          <CODE
CLASS="sgmltag"
>bus</CODE
> attribute</A
></DT
></DL
></DD
><DT
>5.2. <A
HREF="#sc-device_element"
>The <CODE
CLASS="sgmltag"
>device</CODE
> element</A
></DT
><DT
>5.3. <A
HREF="#sc-data_element"
>The <CODE
CLASS="sgmltag"
>data</CODE
> element</A
></DT
><DD
><DL
><DT
>5.3.1. <A
HREF="#sc-data_element_class_attribute"
>The <CODE
CLASS="sgmltag"
>class</CODE
> attribute</A
></DT
><DT
>5.3.2. <A
HREF="#sc-data_element_version_attribute"
>The <CODE
CLASS="sgmltag"
>version</CODE
> attribute</A
></DT
></DL
></DD
><DT
>5.4. <A
HREF="#sc-accessing_device_data"
>Accessing the Device
        Data</A
></DT
></DL
></DD
></DL
></DD
><DT
>II. <A
HREF="#pt-data_content"
>Recommended Data Content Conventions</A
></DT
><DD
><DL
><DT
>6. <A
HREF="#ch-data_hierarchy"
>Data Hierarchy</A
></DT
><DD
><DL
><DT
>6.1. <A
HREF="#sc-linux_kernel_modules"
>Linux Kernel Modules</A
></DT
><DT
>6.2. <A
HREF="#sc-xfree86_x_servers"
>XFree86 X Servers</A
></DT
><DT
>6.3. <A
HREF="#sc-locally-defined_interfaces"
>Locally-Defined Interfaces</A
></DT
></DL
></DD
><DT
>7. <A
HREF="#ch-order-matters"
>Why Order Matters</A
></DT
><DT
>8. <A
HREF="#ch-using_data_versioning"
>Using Data Versioning</A
></DT
><DD
><DL
><DT
>8.1. <A
HREF="#sc-specifying_range"
>Specifying a Range</A
></DT
><DT
>8.2. <A
HREF="#sc-how_discover_library_matches_range"
>How the <SPAN
CLASS="application"
>Discover</SPAN
> Library Matches a Range</A
></DT
></DL
></DD
></DL
></DD
><DT
>III. <A
HREF="#pt-command-line_tools"
>Command-Line Tools</A
></DT
><DD
><DL
><DT
>9. <A
HREF="#ch-discover_manpage"
><B
CLASS="command"
>discover</B
> Manual Page</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN798"
>discover</A
>&nbsp;--&nbsp;hardware detection utility</DT
></DL
></DD
><DT
>10. <A
HREF="#ch-discover-conf_manpage"
><TT
CLASS="filename"
>discover.conf</TT
> Manual Page</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN1223"
>discover.conf</A
>&nbsp;--&nbsp;configuration file format for discover(1)</DT
></DL
></DD
><DT
>11. <A
HREF="#ch-discover-modprobe_manpage"
><B
CLASS="command"
>discover-modprobe</B
>
      Manual Page</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN1270"
>discover-modprobe</A
>&nbsp;--&nbsp;kernel module loading using discover(1)</DT
></DL
></DD
><DT
>12. <A
HREF="#ch-discover-modprobe-conf_manpage"
><TT
CLASS="filename"
>discover-modprobe.conf</TT
>
      Manual Page</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN1333"
>discover-modprobe.conf</A
>&nbsp;--&nbsp;configuration file for discover-modprobe(5)</DT
></DL
></DD
></DL
></DD
><DT
>IV. <A
HREF="#pt-library"
>Library</A
></DT
><DD
><DL
><DT
>13. <A
HREF="#ch-discover_library"
>The <SPAN
CLASS="application"
>Discover</SPAN
> Library</A
></DT
><DD
><DL
><DT
>13.1. <A
HREF="#sc-library_design_principles"
>Library Design
        Principles</A
></DT
><DT
>13.2. <A
HREF="#sc-discover_data_sources"
><SPAN
CLASS="application"
>Discover</SPAN
> Data
        Sources</A
></DT
><DT
>13.3. <A
HREF="#sc-bus_map"
>The Bus Map</A
></DT
><DT
>13.4. <A
HREF="#sc-scanning_system"
>Scanning the System</A
></DT
><DT
>13.5. <A
HREF="#sc-using_discover_device_t_structures"
>Using
        <SPAN
CLASS="type"
>discover_device_t</SPAN
> Structures</A
></DT
></DL
></DD
><DT
>14. <A
HREF="#ch-sysdeps"
>System Dependencies</A
></DT
><DD
><DL
><DT
>14.1. <A
HREF="#sc-sysdeps_api"
><ACRONYM
CLASS="acronym"
>API</ACRONYM
></A
></DT
></DL
></DD
></DL
></DD
><DT
>A. <A
HREF="#ap-discover_api_reference"
><SPAN
CLASS="application"
>Discover</SPAN
> <ACRONYM
CLASS="acronym"
>API</ACRONYM
> Reference</A
></DT
><DT
>B. <A
HREF="#ap-discover_dtd"
><SPAN
CLASS="application"
>Discover</SPAN
> <ACRONYM
CLASS="acronym"
>DTD</ACRONYM
></A
></DT
><DT
>C. <A
HREF="#ap-discover_conf_dtd"
><SPAN
CLASS="application"
>Discover</SPAN
> Configuration File <ACRONYM
CLASS="acronym"
>DTD</ACRONYM
></A
></DT
><DT
>D. <A
HREF="#ap-licensing_issue_linux_sysdeps"
>Licensing Issue on the Linux Sysdeps</A
></DT
></DL
></DIV
><DIV
CLASS="LOT"
><DL
CLASS="LOT"
><DT
><B
>List of Figures</B
></DT
><DT
>6-1. <A
HREF="#fg-linux_interface"
>Linux interface</A
></DT
><DT
>6-2. <A
HREF="#fg-xfree86_interface"
>XFree86 interface</A
></DT
></DL
></DIV
><DIV
CLASS="LOT"
><DL
CLASS="LOT"
><DT
><B
>List of Examples</B
></DT
><DT
>3-1. <A
HREF="#ex-busclass_list"
>The
        <CODE
CLASS="sgmltag"
>busclass_list</CODE
> element</A
></DT
><DT
>4-1. <A
HREF="#ex-vendor_list"
>The <CODE
CLASS="sgmltag"
>vendor_list</CODE
>
        element</A
></DT
><DT
>5-1. <A
HREF="#ex-sample_device_data"
>Sample device data</A
></DT
><DT
>6-1. <A
HREF="#ex-defining_an_interface"
>Defining an interface</A
></DT
><DT
>6-2. <A
HREF="#ex-using_linux_interface"
>Using the <CODE
CLASS="sgmltag"
>linux</CODE
> interface</A
></DT
><DT
>6-3. <A
HREF="#ex-using_xfree86_interface"
>Using the <CODE
CLASS="sgmltag"
>xfree86</CODE
> interface</A
></DT
><DT
>7-1. <A
HREF="#AEN737"
>Matching <CODE
CLASS="sgmltag"
>device</CODE
> elements</A
></DT
><DT
>8-1. <A
HREF="#ex-using_version_attribute_of_data_element"
>Using the
          <CODE
CLASS="sgmltag"
>version</CODE
> attribute of the
          <CODE
CLASS="sgmltag"
>data</CODE
> element</A
></DT
><DT
>9-1. <A
HREF="#d1-ex-scan-buses"
>Scan the local buses</A
></DT
><DT
>9-2. <A
HREF="#d1-ex-view-video-cards"
>View PCI video cards</A
></DT
><DT
>9-3. <A
HREF="#d1-ex-query-xfree86"
>Query for the driver module for
      XFree86 server version 4.2.0</A
></DT
><DT
>9-4. <A
HREF="#d1-ex-type-summary"
>Get model and vendor
      information by type</A
></DT
><DT
>10-1. <A
HREF="#AEN1252"
>Establishing default buses to scan</A
></DT
><DT
>10-2. <A
HREF="#AEN1255"
>A more complex example</A
></DT
><DT
>14-1. <A
HREF="#AEN1558"
>Linux <ACRONYM
CLASS="acronym"
>PCI</ACRONYM
> sysdep code</A
></DT
></DL
></DIV
><DIV
CLASS="preface"
><HR><H1
><A
NAME="pr-what_is_discover"
></A
>What Is <SPAN
CLASS="application"
>Discover</SPAN
>?</H1
><P
><SPAN
CLASS="application"
>Discover</SPAN
> is a tool that reports information about a
    system's hardware.  It uses operating system-dependent modules
    (selected at build time) to detect what hardware is actually on the
    system and provides system-independent interfaces for querying <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> data
    sources about this hardware.  These data sources contain specific
    information required to enable support for various devices via defined
    software interfaces.  The tool can be accessed by linking to the
    <SPAN
CLASS="application"
>Discover</SPAN
> library or by calling <A
HREF="#ch-discover_manpage"
><B
CLASS="command"
>discover</B
></A
> (which
    itself links to the <SPAN
CLASS="application"
>Discover</SPAN
> library) and parsing its output.  In the
    future, other interfaces (for example, modules for interpreted
    languages such as Perl and Python) may be included.</P
><P
>Why use <SPAN
CLASS="application"
>Discover</SPAN
>?  There are at least a few reasons:</P
><P
></P
><UL
><LI
><P
><EM
>Flexibility.</EM
> <SPAN
CLASS="application"
>Discover</SPAN
> is designed
        from the ground up to be flexible.  It is portable to a variety
        of operating environments, and its modular design supports the
        addition
        of arbitrary methods for querying the host operating system (OS)
        about installed devices.  <SPAN
CLASS="application"
>Discover</SPAN
> is also designed to be
        flexible in terms of the types of data that can be retrieved.
        <SPAN
CLASS="application"
>Discover</SPAN
> does not tie the user to retrieving only one type of
        information, such as the name of the Linux kernel module that
        should be loaded to support a given device.  Instead, <SPAN
CLASS="application"
>Discover</SPAN
>
        supports the association of arbitrary data with hardware devices,
        typically through specification of an interface to the hardware in
        question, such as a Linux kernel module or an XFree86 server driver
        module.</P
></LI
><LI
><P
><EM
>Updatability.</EM
> Many
        hardware-autodetection programs suffer from an inherent
        limitation in that they are restricted to reading hardware
        lists or databases that are stored on the local filesystem.
        This is not an efficient approach in the fast-moving world of
        consumer computer hardware, with new devices constantly being
        introduced.  A couple of months after the latest version of
        your OS of choice is released, it may fail to recognize that
        the latest revision of, for instance, a video chipset is
        compatible with an older one, and can use the same software
        interfaces.  <SPAN
CLASS="application"
>Discover</SPAN
> overcomes this problem by supporting the
        retrieval of hardware information via <ACRONYM
CLASS="acronym"
>HTTP</ACRONYM
><A
NAME="AEN53"
HREF="#FTN.AEN53"
><SPAN
CLASS="footnote"
>[1]</SPAN
></A
> (<SPAN
CLASS="QUOTE"
>"over the web"</SPAN
>).  When
        <ACRONYM
CLASS="acronym"
>HTTP</ACRONYM
> access is impossible, <SPAN
CLASS="application"
>Discover</SPAN
> falls back to
        locally stored hardware lists.</P
></LI
><LI
><P
><EM
>Portability.</EM
> On top of its
        flexibility in terms of system interfaces to hardware, <SPAN
CLASS="application"
>Discover</SPAN
>
        has been written to be broadly portable to all of
        today's popular POSIX-compliant systems.  <SPAN
CLASS="application"
>Discover</SPAN
> is not a
        Linux-only solution.  <SPAN
CLASS="application"
>Discover</SPAN
> is intended to provide operating
        system vendors, computer manufacturers, and third-party vendors of
        software and peripherals with a powerful tool for describing the
        hardware they support to the interfaces they care about.  Because
        <SPAN
CLASS="application"
>Discover</SPAN
>'s data sources can be anywhere on the Internet, the OS
        vendor need not be the sole provider of hardware catalogs.</P
></LI
><LI
><P
><EM
>Usability.</EM
> <SPAN
CLASS="application"
>Discover</SPAN
> is not an in-house
        tool designed to solve a narrow class of problems.  <SPAN
CLASS="application"
>Discover</SPAN
> is
        designed to be easy to use from the perspectives of the individual
        system administrator, the applications programmer, and the hardware
        manufacturer or support staff.  <SPAN
CLASS="application"
>Discover</SPAN
>'s <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> database
        structure, its command-line tools, and its library <ACRONYM
CLASS="acronym"
>API</ACRONYM
> are
        well documented and support extensions to meet diverse
        demands.</P
></LI
><LI
><P
><EM
>Freely licensed.</EM
> <SPAN
CLASS="application"
>Discover</SPAN
> has a
        copyright license that is highly adaptable to the needs of the
        varied audiences to which <SPAN
CLASS="application"
>Discover</SPAN
> is targeted.  Under the
        so-called
        <SPAN
CLASS="QUOTE"
>"UCB/BSD"</SPAN
> or <SPAN
CLASS="QUOTE"
>"MIT/X Consortium"</SPAN
> terms,
        after the names of American universities and some very well known
        software projects that used these terms, anyone is free to copy,
        modify, and distribute the software, and to extend (or not) these
        same freedoms to those who receive the software.  Progeny
        would like to see <SPAN
CLASS="application"
>Discover</SPAN
> adopted by a wide variety of existing
        software products, such the various GNU/Linux distributions; the
        FreeBSD, NetBSD, and OpenBSD projects; the GNU Project of the Free
        Software Foundation; the XFree86 Project; system integrators; and
        the designers and manufacturers of computer hardware.
        We believe that <SPAN
CLASS="application"
>Discover</SPAN
>'s design empowers those with the
        greatest knowledge of hardware and the software interfaces to that
        hardware to express
        that knowledge and make it available to the world, thereby
        ameliorating an entire class of computer configuration problems.
        Progeny does not want <SPAN
CLASS="application"
>Discover</SPAN
>'s licensing to stand in the way of
        realizing that dream, which is why we have chosen these license
        terms.</P
></LI
></UL
><P
>We must take a moment to explain what <SPAN
CLASS="application"
>Discover</SPAN
> is
    <EM
>not</EM
>: <SPAN
CLASS="application"
>Discover</SPAN
> is not a replacement for the
    service &#8212; usually provided by the underlying operating system
    kernel or a user-space program that interfaces with it &#8212; of
    simply translating bus-specific vendor and model identifiers to
    human-readable names.  <SPAN
CLASS="application"
>Discover</SPAN
> performs its own translations of
    this data as a convenience for generating human-readable reports, but
    it does not attempt to enumerate all hardware devices that exist for a
    particular bus architecture.  Rather, <SPAN
CLASS="application"
>Discover</SPAN
> is intended only to
    catalog data for which there is some useful information to impart
    regarding software interfaces.  Facilities already exist in modern
    operating systems for answering the questions <SPAN
CLASS="QUOTE"
>"What is the name
    of this device?"</SPAN
> and <SPAN
CLASS="QUOTE"
>"Who manufactured it?"</SPAN
>
    <SPAN
CLASS="application"
>Discover</SPAN
>'s role is to answer questions like <SPAN
CLASS="QUOTE"
>"What Linux kernel
    module do I need to load for this device to work?"</SPAN
>  More
    importantly, <SPAN
CLASS="application"
>Discover</SPAN
> will enable you to provide answers in the
    future to questions you don't even expect to ask today.</P
><P
><SPAN
CLASS="application"
>Discover</SPAN
> is not intended to be a comprehensive
    hardware-management tool.  It is an
    <EM
>enabling technology</EM
>,
    designed to provide data that a tool layered above it can use.  Two
    applications are provided with <SPAN
CLASS="application"
>Discover</SPAN
> to demonstrate how the
    library can be leveraged: the command-line utility <B
CLASS="command"
>discover</B
>,
    and a Linux kernel module loading script,
    <B
CLASS="command"
>discover-modprobe</B
>, designed to be invoked at system
    boot time.</P
><P
>This manual is divided into four parts.  First, we examine the
    <SPAN
CLASS="application"
>Discover</SPAN
> <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> data file format, exploring the elements and
    attributes used to describe hardware and various interfaces to it. This
    part will enable you to read and understand a <SPAN
CLASS="application"
>Discover</SPAN
> <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> file.  
    Next, we offer some recommendations for writing your own <SPAN
CLASS="application"
>Discover</SPAN
>
    <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> data. Knowing the syntax is valuable, but knowing how best to
    take advantage of it is even more useful.  We then present the
    reference pages describing Progeny's <SPAN
CLASS="application"
>Discover</SPAN
>-based command-line
    tools and the configuration files used to control their behavior. You
    may want to use these references as a guide when implementing your own
    <SPAN
CLASS="application"
>Discover</SPAN
>-based applications.  The final part describes the <SPAN
CLASS="application"
>Discover</SPAN
>
    library <ACRONYM
CLASS="acronym"
>API</ACRONYM
> so that you can develop your own solutions based on
    <SPAN
CLASS="application"
>Discover</SPAN
>.  Appendices offer references to the formal descriptions of
    the <SPAN
CLASS="application"
>Discover</SPAN
> <ACRONYM
CLASS="acronym"
>API</ACRONYM
> and <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> <ACRONYM
CLASS="acronym"
>DTD</ACRONYM
>s.</P
></DIV
><DIV
CLASS="PART"
><A
NAME="pt-data_structure"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
>I. Data Structure</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>1. <A
HREF="#ch-overview_discover_data_format"
>Overview of
      the <SPAN
CLASS="application"
>Discover</SPAN
> Data Format</A
></DT
><DT
>2. <A
HREF="#ch-master_list"
>Master List</A
></DT
><DT
>3. <A
HREF="#ch-busclass_lists"
>Busclass Lists</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="#sc-busclass_list_element"
>The
        <CODE
CLASS="sgmltag"
>busclass_list</CODE
> element</A
></DT
><DD
><DL
><DT
>3.1.1. <A
HREF="#sc-busclass_list_element_bus_attribute"
>The
          <CODE
CLASS="sgmltag"
>bus</CODE
> attribute</A
></DT
></DL
></DD
><DT
>3.2. <A
HREF="#sc-busclass_element"
>The
        <CODE
CLASS="sgmltag"
>busclass</CODE
> element</A
></DT
><DD
><DL
><DT
>3.2.1. <A
HREF="#sc-busclass_element_id_attribute"
>The
          <CODE
CLASS="sgmltag"
>id</CODE
> attribute</A
></DT
><DT
>3.2.2. <A
HREF="#sc-busclass_element_name_attribute"
>The
          <CODE
CLASS="sgmltag"
>name</CODE
> attribute</A
></DT
></DL
></DD
></DL
></DD
><DT
>4. <A
HREF="#ch-vendor_lists"
>Vendor Lists</A
></DT
><DD
><DL
><DT
>4.1. <A
HREF="#sc-vendor_list_element"
>The
        <CODE
CLASS="sgmltag"
>vendor_list</CODE
> element</A
></DT
><DD
><DL
><DT
>4.1.1. <A
HREF="#sc-vendor_list_element_bus_attribute"
>The
          <CODE
CLASS="sgmltag"
>bus</CODE
> attribute</A
></DT
></DL
></DD
><DT
>4.2. <A
HREF="#sc-vendor_element"
>The <CODE
CLASS="sgmltag"
>vendor</CODE
> element</A
></DT
><DD
><DL
><DT
>4.2.1. <A
HREF="#sc-vendor_element_id_attribute"
>The <CODE
CLASS="sgmltag"
>id</CODE
> attribute</A
></DT
><DT
>4.2.2. <A
HREF="#sc-vendor_element_name_attribute"
>The <CODE
CLASS="sgmltag"
>name</CODE
> attribute</A
></DT
></DL
></DD
></DL
></DD
><DT
>5. <A
HREF="#ch-device_lists"
>Device Lists</A
></DT
><DD
><DL
><DT
>5.1. <A
HREF="#sc-device_list_element"
>The
        <CODE
CLASS="sgmltag"
>device_list</CODE
> element</A
></DT
><DD
><DL
><DT
>5.1.1. <A
HREF="#sc-device_list_element_bus_attribute"
>The
          <CODE
CLASS="sgmltag"
>bus</CODE
> attribute</A
></DT
></DL
></DD
><DT
>5.2. <A
HREF="#sc-device_element"
>The <CODE
CLASS="sgmltag"
>device</CODE
> element</A
></DT
><DT
>5.3. <A
HREF="#sc-data_element"
>The <CODE
CLASS="sgmltag"
>data</CODE
> element</A
></DT
><DD
><DL
><DT
>5.3.1. <A
HREF="#sc-data_element_class_attribute"
>The <CODE
CLASS="sgmltag"
>class</CODE
> attribute</A
></DT
><DT
>5.3.2. <A
HREF="#sc-data_element_version_attribute"
>The <CODE
CLASS="sgmltag"
>version</CODE
> attribute</A
></DT
></DL
></DD
><DT
>5.4. <A
HREF="#sc-accessing_device_data"
>Accessing the Device
        Data</A
></DT
></DL
></DD
></DL
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-overview_discover_data_format"
></A
>Chapter 1. Overview of
      the <SPAN
CLASS="application"
>Discover</SPAN
> Data Format</H1
><P
>Most modern computer peripherals contain self-identifying
      information in a format standardized for the hardware interface
      (bus).  This enables the OS on the host system
      to query or scan a bus and catalog the devices.  In general, the OS
      stores this information in the same basic format in which it is
      returned, without translating it more times than necessary for
      device drivers to communicate with the peripheral.  However, this
      information varies by bus type and is often insufficiently clear for
      human consumption. Furthermore, many operating systems do not contain
      a comprehensive database that maps each peripheral to every subsystem
      running on the OS that may want to communicate with that peripheral.
      <SPAN
CLASS="application"
>Discover</SPAN
> addresses these issues by providing flexible databases
      stored in <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> format.</P
><P
>Extensible Markup Language (<ACRONYM
CLASS="acronym"
>XML</ACRONYM
>) is a highly flexible
      hypertext format. <SPAN
CLASS="application"
>Discover</SPAN
> uses <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> exclusively to store hardware
      information externally.  Some familiarity with <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> syntax is
      therefore assumed. For more information,
      see <A
HREF="http://www.w3.org/XML/"
TARGET="_top"
>the
      W3C's <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> website</A
>.</P
><P
>For a formal description of <SPAN
CLASS="application"
>Discover</SPAN
>'s <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> data format, see
      the <SPAN
CLASS="application"
>Discover</SPAN
> <A
HREF="#ap-discover_dtd"
>Document Type
      Definition (<ACRONYM
CLASS="acronym"
>DTD</ACRONYM
>)</A
> document.  The purpose of this document is
      to present the information in a form digestible by the novice.</P
><P
>Because each hardware bus type, such as <ACRONYM
CLASS="acronym"
>PCI</ACRONYM
> or <ACRONYM
CLASS="acronym"
>USB</ACRONYM
>,
      communicates different details about the connected devices
      (essentially, each one solves the same problem in a different way),
      <SPAN
CLASS="application"
>Discover</SPAN
> has a different set of lists for each bus type.  For each
      bus, up to three lists are stored: a bus class list
      maps the bus specification's notion of a device type (hereinafter
      referred to as a <SPAN
CLASS="QUOTE"
>"device class"</SPAN
> to reduce confusion) to
      <SPAN
CLASS="application"
>Discover</SPAN
>'s device types, which are used for running selective
      queries; a vendor list associates bus-specific vendor identification
      data with natural-language names for hardware vendors; and a device
      list contains information specific to individual devices.</P
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-master_list"
></A
>Chapter 2. Master List</H1
><P
>When <SPAN
CLASS="application"
>Discover</SPAN
> is provided with a <ACRONYM
CLASS="acronym"
>URL</ACRONYM
> for the retrieval of
      hardware information, the data retrieved is expected to be in
      <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> format and to contain further <ACRONYM
CLASS="acronym"
>URL</ACRONYM
>s for retrieval.</P
><P
>The root element must be <CODE
CLASS="sgmltag"
>discover-data</CODE
>, which has no attributes,
        and can only contain <CODE
CLASS="sgmltag"
>location</CODE
>
        elements.</P
><P
>The <CODE
CLASS="sgmltag"
>location</CODE
> element is
      always empty, and has three required attributes: <CODE
CLASS="sgmltag"
>bus</CODE
>, <CODE
CLASS="sgmltag"
>type</CODE
>, and <CODE
CLASS="sgmltag"
>url</CODE
>.</P
><P
></P
><DIV
CLASS="variablelist"
><P
><B
><CODE
CLASS="sgmltag"
>location</CODE
>
        Attributes</B
></P
><DL
><DT
><CODE
CLASS="sgmltag"
>type</CODE
></DT
><DD
><P
>This attribute can have one of these values: <CODE
CLASS="sgmltag"
>busclass</CODE
>, <CODE
CLASS="sgmltag"
>device</CODE
>, or <CODE
CLASS="sgmltag"
>vendor</CODE
>. See <A
HREF="#ch-busclass_lists"
>Chapter 3</A
>, <A
HREF="#ch-vendor_lists"
>Chapter 4</A
>, and <A
HREF="#ch-device_lists"
>Chapter 5</A
>.</P
></DD
><DT
><CODE
CLASS="sgmltag"
>url</CODE
></DT
><DD
><P
>This must be a valid <ACRONYM
CLASS="acronym"
>URL</ACRONYM
> containing one of the three
              types of data lists.</P
></DD
><DT
><CODE
CLASS="sgmltag"
>bus</CODE
></DT
><DD
><P
>This is the bus to which the <ACRONYM
CLASS="acronym"
>URL</ACRONYM
> applies.  See <A
HREF="#sc-busclass_element_name_attribute"
>Section 3.2.2</A
> for a list of
            valid bus names.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-busclass_lists"
></A
>Chapter 3. Busclass Lists</H1
><P
>As noted in the previous chapter, a busclass list provides a
      mapping between device classes recognized by the hardware bus and the
      device type names used by <SPAN
CLASS="application"
>Discover</SPAN
>.  Because every bus is
      different, sometimes there is no perfect, one-to-one correspondence
      between <SPAN
CLASS="application"
>Discover</SPAN
> device types and the device classes recognized by
      a particular bus.  This is one reason that the busclass lists, like
      other types of <SPAN
CLASS="application"
>Discover</SPAN
> data lists, are updatable.
      Revisions in a bus specification may demand updates to the
      mapping.</P
><P
>The device classes recognized by a bus are typically determined
      by the specification for the bus as determined by a standards
      committee or other technical body, and do not change frequently (if
      at all).</P
><DIV
CLASS="example"
><A
NAME="ex-busclass_list"
></A
><P
><B
>Example 3-1. The
        <CODE
CLASS="sgmltag"
>busclass_list</CODE
> element</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#60;?xml version="1.0"?&#62;

&#60;busclass_list bus="usb"&#62;
  &#60;busclass id="0202" name="modem"/&#62;
  &#60;busclass id="1030" name="broadband"/&#62;
  &#60;busclass id="0101" name="printer"/&#62;
  &#60;busclass id="ffff" name="imaging"/&#62;
  &#60;busclass id="0206" name="network"/&#62;
  &#60;busclass id="0300" name="humaninput"/&#62;
  &#60;busclass id="ff00" name="video"/&#62;
  &#60;busclass id="0000" name="unknown"/&#62;
  &#60;busclass id="0804" name="removabledisk"/&#62;
&#60;/busclass_list&#62;</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><P
>In the foregoing example, we can see one possible mapping of
      the <ACRONYM
CLASS="acronym"
>USB</ACRONYM
> bus's numeric device class IDs to <SPAN
CLASS="application"
>Discover</SPAN
>'s device type
      names (see <A
HREF="#sc-busclass_element_name_attribute"
>Section 3.2.2</A
>).
      The file begins by declaring the version of the <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> standard to
      which it conforms, and then presents data.  The format should be
      fairly familiar to those accustomed to <ACRONYM
CLASS="acronym"
>HTML</ACRONYM
>-style structured markup
      languages.</P
><P
>Not all of <SPAN
CLASS="application"
>Discover</SPAN
>'s supported device types are listed in
      the example; for example, <TT
CLASS="literal"
>display</TT
> is missing.
      This is not a problem, since not all buses are used for all hardware
      applications.  <ACRONYM
CLASS="acronym"
>USB</ACRONYM
> 1.1 would be a poor choice of bus for
      <ACRONYM
CLASS="acronym"
>VGA</ACRONYM
>-compatible display controllers, for instance, because the
      available bandwidth on the <ACRONYM
CLASS="acronym"
>USB</ACRONYM
> 1.1 bus is insufficient to handle
      typical data loads for such devices.</P
><P
>Another infelicity in the above example is the association of
      the <TT
CLASS="literal"
>ffff</TT
> device class ID with the <SPAN
CLASS="application"
>Discover</SPAN
> 
      device type <TT
CLASS="literal"
>imaging</TT
>.  In actuality, a device type 
      class of <TT
CLASS="literal"
>ffff</TT
> in the <ACRONYM
CLASS="acronym"
>USB</ACRONYM
> specification indicates 
      a device of an unknown classification.  In practice, most
      consumer-level devices with this device class are scanners, one of 
      the first applications of <ACRONYM
CLASS="acronym"
>USB</ACRONYM
> technology in the consumer 
      marketplace.  It is
      possible that in certain deployments, the association of <ACRONYM
CLASS="acronym"
>USB</ACRONYM
>'s
      unknown device class ID with <SPAN
CLASS="application"
>Discover</SPAN
>'s <TT
CLASS="literal"
>imaging</TT
>
      device type is suboptimal &#8212; another reason the busclass lists
      are not hard-coded into the library.</P
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-busclass_list_element"
>3.1. The
        <CODE
CLASS="sgmltag"
>busclass_list</CODE
> element</A
></H2
><P
>A <CODE
CLASS="sgmltag"
>busclass_list</CODE
> element possesses a
        <CODE
CLASS="sgmltag"
>bus</CODE
> attribute and contains one or more
        <CODE
CLASS="sgmltag"
>busclass</CODE
> elements.</P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="sc-busclass_list_element_bus_attribute"
>3.1.1. The
          <CODE
CLASS="sgmltag"
>bus</CODE
> attribute</A
></H3
><P
>The <CODE
CLASS="sgmltag"
>bus</CODE
> attribute of the
          <CODE
CLASS="sgmltag"
>busclass_list</CODE
> element is set to the name of
          the bus being described by the busclass list.</P
><P
>The <CODE
CLASS="sgmltag"
>bus</CODE
> attribute
          presently supports the following values:</P
><P
></P
><UL
><LI
><P
><TT
CLASS="literal"
>ata</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>pci</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>pcmcia</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>scsi</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>usb</TT
></P
></LI
></UL
><P
>We expect to support more buses in the future;
          <TT
CLASS="literal"
>ieee1394</TT
> and <TT
CLASS="literal"
>sbus</TT
> are
          possible candidates.</P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-busclass_element"
>3.2. The
        <CODE
CLASS="sgmltag"
>busclass</CODE
> element</A
></H2
><P
>A <CODE
CLASS="sgmltag"
>busclass</CODE
> element possesses two
        attributes, <CODE
CLASS="sgmltag"
>id</CODE
> and <CODE
CLASS="sgmltag"
>name</CODE
>, and
        contains no elements.</P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="sc-busclass_element_id_attribute"
>3.2.1. The
          <CODE
CLASS="sgmltag"
>id</CODE
> attribute</A
></H3
><P
>The <CODE
CLASS="sgmltag"
>id</CODE
> attribute is set to a bus-specific
          device class identifier.</P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="sc-busclass_element_name_attribute"
>3.2.2. The
          <CODE
CLASS="sgmltag"
>name</CODE
> attribute</A
></H3
><P
>The <CODE
CLASS="sgmltag"
>name</CODE
> attribute is set to a
          <SPAN
CLASS="application"
>Discover</SPAN
> device type.  <SPAN
CLASS="application"
>Discover</SPAN
>'s device types are an effort
          to balance a few criteria:</P
><P
></P
><UL
><LI
><P
>Device types (<SPAN
CLASS="QUOTE"
>"bus classes"</SPAN
> in <SPAN
CLASS="application"
>Discover</SPAN
>
              terminology) defined by the <ACRONYM
CLASS="acronym"
>PCI</ACRONYM
> specification</P
></LI
><LI
><P
>Bus classes defined by the <ACRONYM
CLASS="acronym"
>USB</ACRONYM
> specification</P
></LI
><LI
><P
>Bus classes defined by the <ACRONYM
CLASS="acronym"
>SCSI</ACRONYM
> specification</P
></LI
><LI
><P
>Device types commonly conceived of by the personal
              computer user</P
></LI
></UL
><P
><SPAN
CLASS="application"
>Discover</SPAN
>'s definitions of device types will not meet with
          universal agreement; as happens in most categorization problems,
          some decisions had to be made arbitrarily.  <SPAN
CLASS="application"
>Discover</SPAN
> does not
          attempt to solve the general problem of grouping various
          peripherals into categories; rather, <SPAN
CLASS="application"
>Discover</SPAN
> solves the
          problem for itself and uses bus-specific mappings to translate a
          device's own notion of its type to <SPAN
CLASS="application"
>Discover</SPAN
>'s device
          type.</P
><P
></P
><UL
><LI
><P
><TT
CLASS="literal"
>audio</TT
></P
><P
>A device capable of producing an analog or digital
    sound signal is an <I
CLASS="firstterm"
>audio</I
> device.
    Typically, any device commonly referred to as a
    <SPAN
CLASS="QUOTE"
>"sound card"</SPAN
> is classified by <SPAN
CLASS="application"
>Discover</SPAN
> as
    an audio device.</P
></LI
><LI
><P
><TT
CLASS="literal"
>bridge</TT
></P
><P
>A device that provides access to devices of a
    different type, commonly on a different bus, is a
    <I
CLASS="firstterm"
>bridge</I
> device.  For instance, consumer
    <ACRONYM
CLASS="acronym"
>PCI</ACRONYM
> chipsets often feature a bridge to <ACRONYM
CLASS="acronym"
>ATA</ACRONYM
> (also
    known as IDE) devices.</P
></LI
><LI
><P
><TT
CLASS="literal"
>broadband</TT
></P
><P
>An interface device to a computer communications
    network implemented on top of a technology not explicitly
    designed for that purpose is a <I
CLASS="firstterm"
>broadband</I
>
    device.  Examples include ISDN terminal adapters as well
    as DSL and cable <SPAN
CLASS="QUOTE"
>"modems"</SPAN
>; analog
    phone-line modems are not included in this classification
    (see <SPAN
CLASS="QUOTE"
>"modem"</SPAN
> below).</P
></LI
><LI
><P
><TT
CLASS="literal"
>display</TT
></P
><P
>A device controlled by the host machine's CPU and
    capable of producing an analog or digital video signal
    for output purposes is a <I
CLASS="firstterm"
>display</I
> device.
    Typically, any device commonly referred to as a
    <SPAN
CLASS="QUOTE"
>"video card"</SPAN
> is classified by <SPAN
CLASS="application"
>Discover</SPAN
> as
    a display device.</P
></LI
><LI
><P
><TT
CLASS="literal"
>fixeddisk</TT
></P
><P
>A high-speed, fixed magnetic storage device such as
    a hard disk drive is a <I
CLASS="firstterm"
>fixeddisk</I
> device.
    Removable media devices such as floppy disk drives,
    CD-ROM drives, magneto-optical devices, tape drives, and
    Compact Flash card readers are not included in this
    classification.</P
></LI
><LI
><P
><TT
CLASS="literal"
>humaninput</TT
></P
><P
>A device that receives tactile input from a person
    for the purpose of directing a computer's activity is a
    <I
CLASS="firstterm"
>humaninput</I
> device.  Examples include
    keyboards, mice, trackballs, joysticks, gamepads, digital
    tablets manipulated with a stylus or finger, and so
    forth.  Input devices that rely upon non-tactile means of
    determining a person's intent, such as speech-recognition
    devices or cameras, are not included in this
    classification.</P
></LI
><LI
><P
><TT
CLASS="literal"
>imaging</TT
></P
><P
>A device that captures still images for input
    purposes is an <I
CLASS="firstterm"
>imaging</I
> device.  Scanners
    and digital cameras are examples of imaging
    devices.  Motion-capture devices such as television tuner
    cards, webcams, and digital video cameras are not
    included in this classification.</P
></LI
><LI
><P
><TT
CLASS="literal"
>miscellaneous</TT
></P
><P
>Any device that cannot logically be classified as
    another device type is a <I
CLASS="firstterm"
>miscellaneous</I
>
    device.</P
></LI
><LI
><P
><TT
CLASS="literal"
>modem</TT
></P
><P
>An analog phone-line modulator/demodulator
    (modem) is classified by <SPAN
CLASS="application"
>Discover</SPAN
> as a
    <I
CLASS="firstterm"
>modem</I
> device.  No other kind of device is
    so classified.</P
></LI
><LI
><P
><TT
CLASS="literal"
>network</TT
></P
><P
>An interface device to a conventional computer
    data communications network that does not require the use of a terminal
    adapter is a <I
CLASS="firstterm"
>network</I
> device.  For example,
    Ethernet and Token Ring network interface cards are network
    devices.  Analog phone-line modems; terminal adapters
    for technologies such as ISDN and DSL; and <SPAN
CLASS="QUOTE"
>"cable modems"</SPAN
>
    are not <SPAN
CLASS="QUOTE"
>"network"</SPAN
> devices.</P
></LI
><LI
><P
><TT
CLASS="literal"
>optical</TT
></P
><P
>An optical-technology storage device, often using
    read-only media, is an <I
CLASS="firstterm"
>optical</I
> device.  By
    far the most common examples of these devices are CD-ROM
    and DVD-ROM drives, including versions of these drives
    that can <SPAN
CLASS="QUOTE"
>"burn"</SPAN
> (write to) optical
    discs.</P
></LI
><LI
><P
><TT
CLASS="literal"
>printer</TT
></P
><P
>A device that renders visual output in a permanent
    or semi-permanent manner to a physical medium is a
    <I
CLASS="firstterm"
>printer</I
>.  Typically, any device
    colloquially referred to as a <SPAN
CLASS="QUOTE"
>"printer"</SPAN
> is
    also classified by <SPAN
CLASS="application"
>Discover</SPAN
> as a
    printer.</P
></LI
><LI
><P
><TT
CLASS="literal"
>removabledisk</TT
></P
><P
>Storage devices that feature removable media using
    just about any technology except that of magnetic tape,
    CD-ROM, and DVD-ROM drives are
    <I
CLASS="firstterm"
>removabledisk</I
> devices.  Examples include
    floppy disk drives, magneto-optical drives, and Compact
    Flash card readers.</P
></LI
><LI
><P
><TT
CLASS="literal"
>tape</TT
></P
><P
>A sequential-access mass storage device using
    magnetic tape is a <I
CLASS="firstterm"
>tape</I
> device.  Commonly
    used for archival and backup purposes, DAT drives are
    examples of tape devices.</P
></LI
><LI
><P
><TT
CLASS="literal"
>video</TT
></P
><P
>A device that produces a real-time digital video
    signal for input purposes is a <I
CLASS="firstterm"
>video</I
>
    device.  Webcams, digital video cameras, and television
    tuners are examples of video
    devices.  Note that still digital cameras with
    <SPAN
CLASS="QUOTE"
>"movie"</SPAN
> capability are
    <EM
>not</EM
> considered video
    devices unless they can transmit the live video signal to
    the host in real time.</P
></LI
></UL
></DIV
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-vendor_lists"
></A
>Chapter 4. Vendor Lists</H1
><P
>Many buses have vendor identification numbers
      that are registered with that bus's standardization body and
      programmed into the devices when they are manufactured.  These
      numbers generally are assigned arbitrarily, and typically have little
      meaning to the end user; therefore, most hardware detection tools
      provide a way to translate these numeric vendor IDs to human-readable
      strings.  Thus, instead of knowing that your <ACRONYM
CLASS="acronym"
>PCI</ACRONYM
> or <ACRONYM
CLASS="acronym"
>AGP</ACRONYM
> video card
      was manufactured by <SPAN
CLASS="QUOTE"
>"1002,"</SPAN
> you can determine that it
      was manufactured by <SPAN
CLASS="QUOTE"
>"ATI Technologies, Inc."</SPAN
></P
><DIV
CLASS="example"
><A
NAME="ex-vendor_list"
></A
><P
><B
>Example 4-1. The <CODE
CLASS="sgmltag"
>vendor_list</CODE
>
        element</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#60;?xml version="1.0"?&#62;

&#60;vendor_list bus="pci"&#62;
  &#60;vendor id="0675" name="Dynalink"/&#62;
  &#60;vendor id="0e11" name="Compaq Computer Corporation"/&#62;
  &#60;vendor id="1004" name="VLSI Technology Inc"/&#62;
  &#60;vendor id="1025" name="Acer Incorporated [ALI]"/&#62;
  &#60;vendor id="102b" name="Matrox Graphics, Inc."/&#62;
  &#60;vendor id="109e" name="Brooktree Corporation"/&#62;
&#60;/vendor_list&#62;</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><P
>The foregoing example is similar in structure to the <A
HREF="#ex-busclass_list"
>busclass list example</A
>; a numeric
      vendor ID maps to a vendor name, which can be used by <SPAN
CLASS="application"
>Discover</SPAN
> for
      queries or reports generated for the user's benefit.</P
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-vendor_list_element"
>4.1. The
        <CODE
CLASS="sgmltag"
>vendor_list</CODE
> element</A
></H2
><P
>A <CODE
CLASS="sgmltag"
>vendor_list</CODE
> element possesses a
        <CODE
CLASS="sgmltag"
>bus</CODE
> attribute and contains one or more
        <CODE
CLASS="sgmltag"
>vendor</CODE
> elements.</P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="sc-vendor_list_element_bus_attribute"
>4.1.1. The
          <CODE
CLASS="sgmltag"
>bus</CODE
> attribute</A
></H3
><P
>The <CODE
CLASS="sgmltag"
>bus</CODE
> attribute of the
          <CODE
CLASS="sgmltag"
>vendor_list</CODE
> element is set to the name of
          the bus being described by the vendor list.</P
><P
>The following bus attributes are supported:</P
><P
></P
><UL
><LI
><P
><TT
CLASS="literal"
>ata</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>pci</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>pcmcia</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>scsi</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>usb</TT
></P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-vendor_element"
>4.2. The <CODE
CLASS="sgmltag"
>vendor</CODE
> element</A
></H2
><P
>A <CODE
CLASS="sgmltag"
>vendor</CODE
> element possesses two
        attributes, <CODE
CLASS="sgmltag"
>id</CODE
> and <CODE
CLASS="sgmltag"
>name</CODE
>, and
        contains no elements.</P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="sc-vendor_element_id_attribute"
>4.2.1. The <CODE
CLASS="sgmltag"
>id</CODE
> attribute</A
></H3
><P
>The <CODE
CLASS="sgmltag"
>id</CODE
> attribute is set to a bus-specific
          vendor identifier.</P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="sc-vendor_element_name_attribute"
>4.2.2. The <CODE
CLASS="sgmltag"
>name</CODE
> attribute</A
></H3
><P
>The <CODE
CLASS="sgmltag"
>name</CODE
> attribute is set to a
          human-readable vendor identifier, typically the official name of
          the corporation or other business entity that designed or
          manufactured that peripheral.</P
></DIV
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-device_lists"
></A
>Chapter 5. Device Lists</H1
><P
>The device lists are the heart of <SPAN
CLASS="application"
>Discover</SPAN
>'s functionality.
      They are the most frequently updated lists and contain the
      information of greatest value.</P
><P
><SPAN
CLASS="application"
>Discover</SPAN
>'s device lists not only provide a way to identify
      individual peripherals by name, but also permit the specification of
      an arbitrary quantity of organized data for each device, supporting
      an arbitrary number of software interfaces.</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="http://www.progeny.com/images/utility/note.png"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The following is a fictitious example.  The information
        within it is for illustrative purposes only.  See <A
HREF="#pt-data_content"
>Part II in <I
>The <SPAN
CLASS="application"
>Discover</SPAN
> Hardware Detection System</I
></A
> for a discussion of the
        <SPAN
CLASS="QUOTE"
>"real"</SPAN
> hardware data as provided by Progeny, and for
        some suggested conventions on organizing the data namespace.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="example"
><A
NAME="ex-sample_device_data"
></A
><P
><B
>Example 5-1. Sample device data</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#60;?xml version="1.0"?&#62;

&#60;device_list bus="pci"&#62;
  &#60;device busclass="1984" model="0101" model_name="Cerebral Reprogrammer" vendor="B16B"&#62;
    &#60;data class="linux"&#62;
      &#60;data class="module"&#62;
        &#60;data class="name"&#62;winston&#60;/data&#62;
        &#60;data class="options"&#62;base_address=0x300 manual_override=0&#60;/data&#62;
      &#60;/data&#62;
    &#60;/data&#62;
    &#60;data class="win2k"&#62;
      &#60;data class="hal_driver"&#62;
        &#60;data class="StrUglyHungarianNotatedDriverName"&#62;settlement&#60;/data&#62;
        &#60;data class="flags"&#62;NSA_KEY=96b5f3e3283a62c85f6cb6f4017135c2&#60;/data&#62;
      &#60;/data&#62;
    &#60;/data&#62;
  &#60;/device&#62;
&#60;/device_list&#62;</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><P
>The example above includes a <CODE
CLASS="sgmltag"
>device_list</CODE
>
      element containing <CODE
CLASS="sgmltag"
>device</CODE
> elements, and a
      <CODE
CLASS="sgmltag"
>device</CODE
> element that defines the device itself,
      but reserves any software- or interface-specific details to the
      <CODE
CLASS="sgmltag"
>data</CODE
> elements it contains.</P
><P
>The actual data provided in the example is accessed by means of
      data paths; see <A
HREF="#sc-accessing_device_data"
>Section 5.4</A
> for 
      further information.</P
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-device_list_element"
>5.1. The
        <CODE
CLASS="sgmltag"
>device_list</CODE
> element</A
></H2
><P
>A <CODE
CLASS="sgmltag"
>device_list</CODE
> element possesses a
        <CODE
CLASS="sgmltag"
>bus</CODE
> attribute and contains one or more
        <CODE
CLASS="sgmltag"
>device</CODE
> elements.</P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="sc-device_list_element_bus_attribute"
>5.1.1. The
          <CODE
CLASS="sgmltag"
>bus</CODE
> attribute</A
></H3
><P
>The <CODE
CLASS="sgmltag"
>bus</CODE
> attribute of the
          <CODE
CLASS="sgmltag"
>device_list</CODE
> element is set to the name of
          the bus described by the device list.</P
><P
>The following bus attributes are supported:</P
><P
></P
><UL
><LI
><P
><TT
CLASS="literal"
>ata</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>pci</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>pcmcia</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>scsi</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>usb</TT
></P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-device_element"
>5.2. The <CODE
CLASS="sgmltag"
>device</CODE
> element</A
></H2
><P
>A <CODE
CLASS="sgmltag"
>device</CODE
> element possesses four attributes:</P
><P
></P
><UL
><LI
><P
><CODE
CLASS="sgmltag"
>busclass</CODE
></P
></LI
><LI
><P
><CODE
CLASS="sgmltag"
>vendor</CODE
></P
></LI
><LI
><P
><CODE
CLASS="sgmltag"
>model</CODE
></P
></LI
><LI
><P
><CODE
CLASS="sgmltag"
>model_name</CODE
></P
></LI
></UL
><P
>All of these attributes must be specified for each
        <CODE
CLASS="sgmltag"
>device</CODE
> element.  The <CODE
CLASS="sgmltag"
>busclass</CODE
>
        attribute is set to a <A
HREF="#sc-busclass_element_id_attribute"
>busclass
        identifier</A
>, <CODE
CLASS="sgmltag"
>vendor</CODE
> to a <A
HREF="#sc-vendor_element_id_attribute"
>vendor
        identifier</A
>, <CODE
CLASS="sgmltag"
>model</CODE
> to a bus-specific
        model identifier, and <CODE
CLASS="sgmltag"
>model_name</CODE
> to a
        human-readable vendor identifier, typically the name of the product
        under which the device reporting the <CODE
CLASS="sgmltag"
>model</CODE
>
        identifier is sold or otherwise distributed.</P
><P
>A <CODE
CLASS="sgmltag"
>device</CODE
> element contains zero or more
        <CODE
CLASS="sgmltag"
>data</CODE
> elements.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-data_element"
>5.3. The <CODE
CLASS="sgmltag"
>data</CODE
> element</A
></H2
><P
>A <CODE
CLASS="sgmltag"
>data</CODE
> element possesses a mandatory
        <CODE
CLASS="sgmltag"
>class</CODE
> attribute, an optional
        <CODE
CLASS="sgmltag"
>version</CODE
> attribute, and zero or more
        <CODE
CLASS="sgmltag"
>data</CODE
> elements.</P
><P
>The ability to nest <CODE
CLASS="sgmltag"
>data</CODE
> elements inside
        other <CODE
CLASS="sgmltag"
>data</CODE
> elements affords interface designers
        and device driver authors the ability to specify a hierarchy of
        data, instead of being compelled to encapsulate only one piece of
        data per device for their interface.</P
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="sc-data_element_class_attribute"
>5.3.1. The <CODE
CLASS="sgmltag"
>class</CODE
> attribute</A
></H3
><P
>A <CODE
CLASS="sgmltag"
>class</CODE
> attribute is set to an arbitrary
          value determined by an interface designer.  For
          <CODE
CLASS="sgmltag"
>data</CODE
> elements whose parent element is a
          <CODE
CLASS="sgmltag"
>device</CODE
> element, this should be the name of
          the interface being described, such as
          <TT
CLASS="literal"
>freebsd</TT
>, <TT
CLASS="literal"
>linux</TT
>, or
          <TT
CLASS="literal"
>xfree86</TT
>.</P
><P
>A <CODE
CLASS="sgmltag"
>data</CODE
> element whose parent element is a
          <CODE
CLASS="sgmltag"
>data</CODE
> element should set this attribute to a
          term reflecting the interface designer's intended data hierarchy.
          <SPAN
CLASS="application"
>Discover</SPAN
> does not mandate any particular hierarchy for
          interface designers.</P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="sc-data_element_version_attribute"
>5.3.2. The <CODE
CLASS="sgmltag"
>version</CODE
> attribute</A
></H3
><P
>Data elements have an optional attribute named <CODE
CLASS="sgmltag"
>version</CODE
>.  This indicates a version
          <EM
>range</EM
> applicable to the data contained
          within the element.  The purpose of this attribute is to permit
          the specification of data that is valid only for a range of
          versions of the given interface.  For example, the Linux kernel
          changed some of the names of its modules between the 2.2 and 2.4
          series.</P
><P
><SPAN
CLASS="application"
>Discover</SPAN
>'s range syntax, common in mathematical writings,
          is expressed as an interval; that is, it consists of a pair of
          endpoints with a comma between them, and brackets or parentheses
          as qualifiers for inclusion or exclusion of the endpoints' exact
          values.  For example, the version specification <TT
CLASS="literal"
>[1.0,
          2.0)</TT
> matches any version less than 2.0 and greater
          than or equal to 1.0.  It is the responsibility of the calling
          environment to specify the version of the interface actually in
          use.  In other words, the <SPAN
CLASS="application"
>Discover</SPAN
> library does not take it
          upon itself to determine the currently running version of the
          Linux kernel, XFree86 X server, CUPS printing daemon, and so
          forth.</P
><P
>Due to the lack of consistent standards for version numbers
          (in fact, some version numbers aren't numbers at all),
          <SPAN
CLASS="application"
>Discover</SPAN
> requires simplifications for the <CODE
CLASS="sgmltag"
>version</CODE
> attribute.  The versions that
          express the range must be in dotted-decimal form, such as
          <TT
CLASS="literal"
>7.1.0</TT
>.  The version that is supplied to the
          <SPAN
CLASS="application"
>Discover</SPAN
> library as part of a query (for example, via the
          <CODE
CLASS="option"
>--data-version</CODE
> argument to <B
CLASS="command"
>discover</B
>)
          may or may not comply with this requirement, but should
          be expressed such that it compares in a desirable way against
          version strings that do.</P
><P
>In place of the upper end of the range,
          <TT
CLASS="literal"
>inf</TT
> (infinity) can be used if the information
          is still relevant and should be for forseeable versions.</P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-accessing_device_data"
>5.4. Accessing the Device
        Data</A
></H2
><P
><SPAN
CLASS="application"
>Discover</SPAN
> data is grouped into hierarchical <CODE
CLASS="sgmltag"
>data</CODE
> elements.  This data can be accessed
        via its data path.  The data path is the concatenation of the class
        attribute values of a <CODE
CLASS="sgmltag"
>data</CODE
>
        element and all its parents, separated by slash
        (<TT
CLASS="literal"
>/</TT
>) characters.  In the following example,
        <TT
CLASS="literal"
>quux</TT
> is accessed via the data path
        <SPAN
CLASS="QUOTE"
>"foo/bar"</SPAN
>:</P
><DIV
CLASS="informalexample"
><P
></P
><A
NAME="AEN580"
></A
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#60;data class="foo"&#62;
  &#60;data class="bar"&#62;quux&#60;/data&#62;
&#60;/data&#62;</PRE
></FONT
></TD
></TR
></TABLE
><P
></P
></DIV
><P
>In <A
HREF="#ex-sample_device_data"
>Example 5-1</A
> above, we would
        determine the name of the Linux kernel module
        (<SPAN
CLASS="QUOTE"
>"winston"</SPAN
>) for the <SPAN
CLASS="QUOTE"
>"Cerebral
        Reprogrammer"</SPAN
> device by referencing the data path
        <TT
CLASS="literal"
>linux/module/name</TT
>; similarly, the data path
        <TT
CLASS="literal"
>win2k/hal_driver/flags</TT
> returns
        <TT
CLASS="literal"
>NSA_KEY=96b5f3e3283a62c85f6cb6f4017135c2</TT
>.</P
></DIV
></DIV
></DIV
><DIV
CLASS="PART"
><A
NAME="pt-data_content"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
>II. Recommended Data Content Conventions</H1
><DIV
CLASS="PARTINTRO"
><A
NAME="AEN591"
></A
><P
>As discussed in the <A
HREF="#pr-what_is_discover"
>preface</A
>, <SPAN
CLASS="application"
>Discover</SPAN
> is not
      intended to be a replacement for system utilities such as
      <B
CLASS="command"
>lspci</B
> on Linux.  A
      <CODE
CLASS="sgmltag"
>device</CODE
> element should exist
      for a piece of hardware only if there is some interface information
      to communicate about the hardware; that is, some 
      <CODE
CLASS="sgmltag"
>data</CODE
> elements to house within the
      <CODE
CLASS="sgmltag"
>device</CODE
> element. This part of the
      manual contains Progeny's recommendations on how to organize that
      information for maximum utility.</P
></DIV
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>6. <A
HREF="#ch-data_hierarchy"
>Data Hierarchy</A
></DT
><DD
><DL
><DT
>6.1. <A
HREF="#sc-linux_kernel_modules"
>Linux Kernel Modules</A
></DT
><DT
>6.2. <A
HREF="#sc-xfree86_x_servers"
>XFree86 X Servers</A
></DT
><DT
>6.3. <A
HREF="#sc-locally-defined_interfaces"
>Locally-Defined Interfaces</A
></DT
></DL
></DD
><DT
>7. <A
HREF="#ch-order-matters"
>Why Order Matters</A
></DT
><DT
>8. <A
HREF="#ch-using_data_versioning"
>Using Data Versioning</A
></DT
><DD
><DL
><DT
>8.1. <A
HREF="#sc-specifying_range"
>Specifying a Range</A
></DT
><DT
>8.2. <A
HREF="#sc-how_discover_library_matches_range"
>How the <SPAN
CLASS="application"
>Discover</SPAN
> Library Matches a Range</A
></DT
></DL
></DD
></DL
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-data_hierarchy"
></A
>Chapter 6. Data Hierarchy</H1
><P
>As discussed in <A
HREF="#sc-accessing_device_data"
>Section 5.4</A
>, the
      <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> structure around the data allows for a hierarchical
      view.</P
><P
>While <SPAN
CLASS="application"
>Discover</SPAN
> does not mandate any particular hierarchy or
      namespace organization for <CODE
CLASS="sgmltag"
>data</CODE
>
      elements, the <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> files provided by Progeny express &#8212; and
      some applications based on <SPAN
CLASS="application"
>Discover</SPAN
> (such as
      <B
CLASS="command"
>discover-modprobe</B
>) expect &#8212; a certain
      structure for Linux kernel module and XFree86 configuration
      information.</P
><P
>At Progeny, we have often found it convenient to refer to a
      top-level <CODE
CLASS="sgmltag"
>data</CODE
> element's <CODE
CLASS="sgmltag"
>class</CODE
> attribute value as an
      <SPAN
CLASS="QUOTE"
>"interface"</SPAN
> (see the following example).</P
><DIV
CLASS="example"
><A
NAME="ex-defining_an_interface"
></A
><P
><B
>Example 6-1. Defining an interface</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#60;device busclass="0300" vendor="de8d" model="90a9" model_name="Stingray"&#62;
  &#60;data class="xfree86"&#62;
    &#60;data class="server" version="[3, 4)"&#62;
      &#60;data class="name"&#62;XF86_SVGA&#60;/data&#62;
    &#60;/data&#62;
  &#60;/data&#62;
  &#60;data class="openbsd"&#62;
    &#60;data class="security_level"&#62;untrusted&#60;/data&#62;
  &#60;/data&#62;
&#60;/device&#62;</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><P
>In <A
HREF="#ex-defining_an_interface"
>Example 6-1</A
>, two interfaces
      have been defined for the <SPAN
CLASS="QUOTE"
>"Stingray"</SPAN
> device:
      <TT
CLASS="literal"
>xfree86</TT
> and <TT
CLASS="literal"
>openbsd</TT
>.</P
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-linux_kernel_modules"
>6.1. Linux Kernel Modules</A
></H2
><P
>A hardware device that requires a particular Linux kernel
        module should have nested <CODE
CLASS="sgmltag"
>data</CODE
>
        elements to describe that module.  The top-level <CODE
CLASS="sgmltag"
>data</CODE
> element should have a <CODE
CLASS="sgmltag"
>class</CODE
> attribute with a value of
        <CODE
CLASS="sgmltag"
>linux</CODE
>.  Underneath that should
        be a <CODE
CLASS="sgmltag"
>data</CODE
> element with a
        <CODE
CLASS="sgmltag"
>class</CODE
> of <CODE
CLASS="sgmltag"
>module</CODE
>.</P
><P
>Within that <CODE
CLASS="sgmltag"
>data</CODE
> element,
        there should be one or two more, one with a <CODE
CLASS="sgmltag"
>class</CODE
> of <CODE
CLASS="sgmltag"
>name</CODE
>, and an optional one with a
        <CODE
CLASS="sgmltag"
>class</CODE
> of <CODE
CLASS="sgmltag"
>options</CODE
>.  The former has as content the
        name of the module; the latter, options to be passed to
        <B
CLASS="command"
>modprobe</B
>.</P
><DIV
CLASS="figure"
><A
NAME="fg-linux_interface"
></A
><P
><B
>Figure 6-1. Linux interface</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>/linux
    |
    |-/module
          |
          |-/name
          |
          |-/options</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><P
>In <A
HREF="#fg-linux_interface"
>Figure 6-1</A
>, each component of
        the tree represents a <CODE
CLASS="sgmltag"
>data</CODE
>
        element; the label is the value of its <CODE
CLASS="sgmltag"
>class</CODE
> attribute.</P
><P
>If the kernel version affects the choice of module name or
        options, the top-level <CODE
CLASS="sgmltag"
>linux</CODE
>
        <CODE
CLASS="sgmltag"
>data</CODE
> element should have a
        version range attribute; see <A
HREF="#sc-data_element_version_attribute"
>Section 5.3.2</A
>.</P
><DIV
CLASS="example"
><A
NAME="ex-using_linux_interface"
></A
><P
><B
>Example 6-2. Using the <CODE
CLASS="sgmltag"
>linux</CODE
> interface</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#60;device busclass="0204" model="1702" model_name="IS64PH ISDN Adapter" vendor="0675"&#62;
  &#60;data class="linux"&#62;
    &#60;data class="module"&#62;
       &#60;data class="name"&#62;hisax&#60;/data&#62;
       &#60;data class="options"&#62;io=0x300 irq=11&#60;/data&#62;
    &#60;/data&#62;
  &#60;/data&#62;
&#60;/device&#62;</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><P
>See <A
HREF="#ex-using_version_attribute_of_data_element"
>Example 8-1</A
> for guidance
        on how to specify different Linux kernel modules for the same
        device, depending on the version of the Linux kernel in use.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-xfree86_x_servers"
>6.2. XFree86 X Servers</A
></H2
><P
>The data hierarchy of a video card device (<SPAN
CLASS="application"
>Discover</SPAN
>'s
        <TT
CLASS="literal"
>display</TT
> type) should include a top-level
        <CODE
CLASS="sgmltag"
>data</CODE
> element with a <CODE
CLASS="sgmltag"
>class</CODE
> attribute of <CODE
CLASS="sgmltag"
>xfree86</CODE
> (the interface)
        and likely with a <CODE
CLASS="sgmltag"
>version</CODE
>
        attribute as well; nested within that element will be a <CODE
CLASS="sgmltag"
>server</CODE
> <CODE
CLASS="sgmltag"
>data</CODE
> element containing a <CODE
CLASS="sgmltag"
>name</CODE
> <CODE
CLASS="sgmltag"
>data</CODE
> element identifying the name of the
        server executable.  For XFree86 version 4.0 or greater, the
        <CODE
CLASS="sgmltag"
>name</CODE
> will always be <CODE
CLASS="sgmltag"
>XFree86</CODE
>, and the <CODE
CLASS="sgmltag"
>server</CODE
> <CODE
CLASS="sgmltag"
>data</CODE
> element will also contain a <CODE
CLASS="sgmltag"
>device</CODE
> <CODE
CLASS="sgmltag"
>data</CODE
> element, which contains one or more
        <CODE
CLASS="sgmltag"
>data</CODE
> elements communicating
        information to be stored in the <TT
CLASS="filename"
>XF86Config</TT
>
        file.  The children of the <CODE
CLASS="sgmltag"
>device</CODE
> <CODE
CLASS="sgmltag"
>data</CODE
> element are named in correspondence
        with the syntax of the <TT
CLASS="filename"
>XF86Config</TT
> file's
        <TT
CLASS="literal"
>Device</TT
> section; see the <A
HREF="http://www.xfree86.org/current/XF86Config.5.html"
TARGET="_top"
>XF86Config
        manual page</A
> for further information.  In particular, note
        that in many cases only a
        <CODE
CLASS="sgmltag"
>driver</CODE
> <CODE
CLASS="sgmltag"
>data</CODE
> element is necessary.</P
><DIV
CLASS="figure"
><A
NAME="fg-xfree86_interface"
></A
><P
><B
>Figure 6-2. XFree86 interface</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>/xfree86
    |
    |-/server
          |
          |-/name
          |
          |-/device
                |
                |-/driver
                |
                |-/chipid
                |
                |-/chipset
                |
                |-/ramdac
                |
                |-/dacspeed
                |
                |-/videoram
                |
                |-/options
                |
                |-...</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><P
><A
HREF="#fg-xfree86_interface"
>Figure 6-2</A
> illustrates the
        <CODE
CLASS="sgmltag"
>xfree86</CODE
>
        interface.  <A
HREF="#ex-using_xfree86_interface"
>Example 6-3</A
> shows
        how you might write <CODE
CLASS="sgmltag"
>xfree86</CODE
>
        interface information for a <SPAN
CLASS="application"
>Discover</SPAN
> <CODE
CLASS="sgmltag"
>display</CODE
> device.</P
><DIV
CLASS="example"
><A
NAME="ex-using_xfree86_interface"
></A
><P
><B
>Example 6-3. Using the <CODE
CLASS="sgmltag"
>xfree86</CODE
> interface</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#60;device busclass="0300" vendor="1002" model="4654" model_name="Mach64 VT [264VT FT]"&#62;
  &#60;data class="xfree86"&#62;
    &#60;data class="server" version="[4, inf)"&#62;
      &#60;data class="name"&#62;XFree86&#60;/data&#62;
      &#60;data class="device"&#62;
        &#60;data class="driver"&#62;ati&#60;/data&#62;
      &#60;/data&#62;
    &#60;/data&#62;
    &#60;data class="server" version="(0, 4)"&#62;
      &#60;data class="name"&#62;XF86_Mach64&#60;/data&#62;
    &#60;/data&#62;
  &#60;/data&#62;
&#60;/device&#62;</PRE
></FONT
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-locally-defined_interfaces"
>6.3. Locally-Defined Interfaces</A
></H2
><P
>Progeny recommends that publicly distributed <SPAN
CLASS="application"
>Discover</SPAN
>
          <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> files avoid using the interface name
          <TT
CLASS="literal"
>local</TT
>; that is, a
          <CODE
CLASS="sgmltag"
>class</CODE
> attribute value of
          <TT
CLASS="literal"
>local</TT
> in a top-level
          <CODE
CLASS="sgmltag"
>data</CODE
> element.  This
          means that data paths such as <TT
CLASS="literal"
>local/foo/bar</TT
>
          should not be defined in a public <SPAN
CLASS="application"
>Discover</SPAN
> <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> file, but
          both <TT
CLASS="literal"
>foo/bar/local</TT
> and
          <TT
CLASS="literal"
>foo/local/bar</TT
> are okay.</P
><P
>The intention is to reserve this part of the namespace
          for users' experiments with defining their own &#8212;
          and possibly future, widely adopted &#8212; interface definitions
          for <SPAN
CLASS="application"
>Discover</SPAN
> data.  An interface definition could thus be
          <SPAN
CLASS="QUOTE"
>"beta tested"</SPAN
> by a person or organization to ensure
          that it is efficiently structured before it is unleashed upon the
          world elsewhere in the namespace, where people may write tools
          that expect to be able to resolve the interface definition's data
          paths.</P
><P
>Likewise, Progeny recommends that authors of applications
          that use <SPAN
CLASS="application"
>Discover</SPAN
> avoid traversing into a top-level
          <TT
CLASS="literal"
>local</TT
> <CODE
CLASS="sgmltag"
>data</CODE
>
          element, which may impose an undesirable support burden on
          the designers of the interface while they are still working out
          their design.  (The application also may not find the data it
          desires, or may not get back what it expects.)</P
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-order-matters"
></A
>Chapter 7. Why Order Matters</H1
><P
>When searching device elements, the first exact match will be
      selected.  Subsequent matches are ignored.
      </P
><P
>Specifically, three comparisons are made:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>The hardware must provide identification that matches
          attributes of the <CODE
CLASS="sgmltag"
>device</CODE
> element.  As an
          example, a <ACRONYM
CLASS="acronym"
>PCI</ACRONYM
> device supplies numeric vendor and model
          identifiers, which are used to match the
          <CODE
CLASS="sgmltag"
>model</CODE
> and <CODE
CLASS="sgmltag"
>vendor</CODE
>
          attributes.</P
></LI
><LI
><P
>The <CODE
CLASS="sgmltag"
>class</CODE
> attributes of child
          <CODE
CLASS="sgmltag"
>data</CODE
> elements must match the data path as
          given to the library for searching.</P
></LI
><LI
><P
>The first version range, if any, associated with the nested
          <CODE
CLASS="sgmltag"
>data</CODE
> elements must encompass any
          version provided by the client.</P
></LI
></OL
><DIV
CLASS="example"
><A
NAME="AEN737"
></A
><P
><B
>Example 7-1. Matching <CODE
CLASS="sgmltag"
>device</CODE
> elements</B
></P
><P
>Assume that the path <TT
CLASS="literal"
>linux/module/name</TT
> is
        provided, along with a version of 2.4.2.  The following is sample
        data; the <CODE
CLASS="sgmltag"
>device</CODE
> elements may be from the same
        or different data files.</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;&#60;device busclass="0000" vendor="102f" model="5555" model_name="100VG ethernet"&#62;
  &#60;data class="linux" version="[2.4, inf)"&#62;<A
NAME="bad_name"
><IMG
SRC="http://www.progeny.com/images/utility/callouts/1.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(1)"></A
>
    &#60;data class="modules"&#62;
        &#60;data class="name"&#62;vg100&#60;/data&#62;
    &#60;/data&#62;
  &#60;/data&#62;
  &#60;data class="linux" version="[2.0, 2.2)"&#62;<A
NAME="range_20to22"
><IMG
SRC="http://www.progeny.com/images/utility/callouts/2.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(2)"></A
>
    &#60;data class="module"&#62;
        &#60;data class="name"&#62;vg100&#60;/data&#62;
        &#60;data class="options"&#62;io=0x300&#60;/data&#62;
    &#60;/data&#62;
  &#60;/data&#62;
&#60;/device&#62;

&#60;device busclass="0000" vendor="102f" model="5555" model_name="100VG ethernet"&#62;
  &#60;data class="linux"&#62;<A
NAME="blank_range"
><IMG
SRC="http://www.progeny.com/images/utility/callouts/3.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(3)"></A
>
    &#60;data class="module"&#62;
        &#60;data class="name"&#62;vg100new&#60;/data&#62;
    &#60;/data&#62;
  &#60;/data&#62;
  &#60;data class="linux" version="[2.4, inf)"&#62;<A
NAME="range_24toinf"
><IMG
SRC="http://www.progeny.com/images/utility/callouts/4.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(4)"></A
>
    &#60;data class="module"&#62;
        &#60;data class="name"&#62;vg100old&#60;/data&#62;
    &#60;/data&#62;
  &#60;/data&#62;
&#60;/device&#62;

</PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="calloutlist"
><DL
COMPACT="COMPACT"
><DT
><A
HREF="#bad_name"
><IMG
SRC="http://www.progeny.com/images/utility/callouts/1.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(1)"></A
></DT
><DD
>This item is the first one scanned, and would match,
            except that the requested data path includes
            <SPAN
CLASS="QUOTE"
>"module"</SPAN
> as a component, not
            <SPAN
CLASS="QUOTE"
>"modules"</SPAN
> as specified here.</DD
><DT
><A
HREF="#range_20to22"
><IMG
SRC="http://www.progeny.com/images/utility/callouts/2.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(2)"></A
></DT
><DD
>This item doesn't match because the provided range is
            outside the limits defined by the element. (2.4.2 is not
            greater than or equal to 2.0 and less than 2.2.)</DD
><DT
><A
HREF="#blank_range"
><IMG
SRC="http://www.progeny.com/images/utility/callouts/3.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(3)"></A
></DT
><DD
>This item matches because no range is given, so
            <SPAN
CLASS="QUOTE"
>"vg100new"</SPAN
> is the value returned.</DD
><DT
><A
HREF="#range_24toinf"
><IMG
SRC="http://www.progeny.com/images/utility/callouts/4.gif"
HSPACE="0"
VSPACE="0"
BORDER="0"
ALT="(4)"></A
></DT
><DD
>This is the nearest match, but the <SPAN
CLASS="application"
>Discover</SPAN
> library
            will never select it because its previous sibling has no
            version range, and thus will catch any version provided.</DD
></DL
></DIV
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-using_data_versioning"
></A
>Chapter 8. Using Data Versioning</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="sc-specifying_range"
>8.1. Specifying a Range</A
></H2
><P
>Because multiple versions of a software interface often are
        in simultaneous deployment, Progeny recommendeds that the upper
        bound of a <CODE
CLASS="sgmltag"
>data</CODE
> element's
        <CODE
CLASS="sgmltag"
>version</CODE
> attribute be defined
        as the first version that is inconsistent with the information
        provided within it, and that the upper end of the interval be open
        (terminated with a parenthesis).  As an example, suppose we know
        that the name of the Linux kernel module to drive the RealTek
        RTL-8139 Ethernet device was <TT
CLASS="literal"
>rtl8139</TT
> in the 2.2
        kernel series and <TT
CLASS="literal"
>8139too</TT
> in the 2.4 series.  To
        express this, we would say the following:</P
><DIV
CLASS="example"
><A
NAME="ex-using_version_attribute_of_data_element"
></A
><P
><B
>Example 8-1. Using the
          <CODE
CLASS="sgmltag"
>version</CODE
> attribute of the
          <CODE
CLASS="sgmltag"
>data</CODE
> element</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#60;device_list bus="pci"&#62;
&#60;device busclass="0200" model="8139" model_name="RTL-8139" vendor="10ec"&#62;
  &#60;data class="linux" version="[2.4,inf)"&#62;
    &#60;data class="module"&#62;
       &#60;data class="name"&#62;8139too&#60;/data&#62;
    &#60;/data&#62;
  &#60;/data&#62;
  &#60;data class="linux" version="[2.2,2.4)"&#62;
    &#60;data class="module"&#62;
       &#60;data class="name"&#62;rtl8139&#60;/data&#62;
    &#60;/data&#62;
  &#60;/data&#62;
&#60;/device&#62;
&#60;/device_list&#62;</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><P
>In the first data element, for instance, we would not use a
        version attribute of <TT
CLASS="literal"
>[2.2.0,2.2.19]</TT
> because it is needlessly specific.  What happens if the Linux kernel
        developers release Linux kernel 2.2.20?  By saying
        <TT
CLASS="literal"
>[2.2,2.4)</TT
>, we <SPAN
CLASS="QUOTE"
>"catch"</SPAN
> everything in
        the kernel 2.2 series<A
NAME="AEN779"
HREF="#FTN.AEN779"
><SPAN
CLASS="footnote"
>[2]</SPAN
></A
> &#8212; past,
        present, and future.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-how_discover_library_matches_range"
>8.2. How the <SPAN
CLASS="application"
>Discover</SPAN
> Library Matches a Range</A
></H2
><P
>The data files will be searched in order; the first data path
        that matches the version range or doesn't have a version range will
        be returned.</P
><P
>Recalling the discussion in <A
HREF="#sc-data_element_version_attribute"
>Section 5.3.2</A
>, if you want the
        first data element matching the requested data path to also be the
        <SPAN
CLASS="QUOTE"
>"fallback"</SPAN
> element if no version range applies, you
        can duplicate that data element and place it at the end.  However,
        a better practice is to make certain that all reasonable versions
        will match one of the ranges, and that the first range listed has
        an open-ended high end, such as <TT
CLASS="literal"
>[2.4, inf)</TT
> for
        Linux kernel modules in
        <A
HREF="#ex-using_version_attribute_of_data_element"
>Example 8-1</A
>.  This
        will have the effect of <SPAN
CLASS="QUOTE"
>"assuming"</SPAN
> that
        all unversioned requests for <TT
CLASS="literal"
>linux</TT
> data will be
        for Linux kernel 2.4 or later.</P
></DIV
></DIV
></DIV
><DIV
CLASS="PART"
><A
NAME="pt-command-line_tools"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
>III. Command-Line Tools</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>9. <A
HREF="#ch-discover_manpage"
><B
CLASS="command"
>discover</B
> Manual Page</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN798"
>discover</A
>&nbsp;--&nbsp;hardware detection utility</DT
></DL
></DD
><DT
>10. <A
HREF="#ch-discover-conf_manpage"
><TT
CLASS="filename"
>discover.conf</TT
> Manual Page</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN1223"
>discover.conf</A
>&nbsp;--&nbsp;configuration file format for discover(1)</DT
></DL
></DD
><DT
>11. <A
HREF="#ch-discover-modprobe_manpage"
><B
CLASS="command"
>discover-modprobe</B
>
      Manual Page</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN1270"
>discover-modprobe</A
>&nbsp;--&nbsp;kernel module loading using discover(1)</DT
></DL
></DD
><DT
>12. <A
HREF="#ch-discover-modprobe-conf_manpage"
><TT
CLASS="filename"
>discover-modprobe.conf</TT
>
      Manual Page</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN1333"
>discover-modprobe.conf</A
>&nbsp;--&nbsp;configuration file for discover-modprobe(5)</DT
></DL
></DD
></DL
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-discover_manpage"
></A
>Chapter 9. <B
CLASS="command"
>discover</B
> Manual Page</H1
><H1
><A
NAME="AEN798"
></A
>discover</H1
><DIV
CLASS="refnamediv"
><A
NAME="AEN812"
></A
><H2
>Name</H2
>discover&nbsp;--&nbsp;hardware detection utility</DIV
><DIV
CLASS="refsynopsisdiv"
><A
NAME="AEN815"
></A
><H2
>Synopsis</H2
><P
><B
CLASS="command"
>discover</B
>  [DATA_OPTIONS] [DISPLAY_OPTIONS] [--bus-summary] [bus...]</P
><P
><B
CLASS="command"
>discover</B
>  [DATA_OPTIONS] [DISPLAY_OPTIONS]  --type-summary  [type...]</P
><P
><B
CLASS="command"
>discover</B
>  [DATA_OPTIONS]  --data-path=<TT
CLASS="replaceable"
><I
>path/to/data</I
></TT
>...  [--data-version=<TT
CLASS="replaceable"
><I
>version</I
></TT
>] [--normalize-whitespace] [--format=<TT
CLASS="replaceable"
><I
>format string</I
></TT
>] [type | id...]</P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>DATA_OPTIONS</DT
><DD
><P
></P
><UL
><LI
><P
><CODE
CLASS="option"
>-d | --disable-bus=<TT
CLASS="replaceable"
><I
>bus</I
></TT
></CODE
></P
></LI
><LI
><P
><CODE
CLASS="option"
>-e | --enable-bus=<TT
CLASS="replaceable"
><I
>bus</I
></TT
></CODE
></P
></LI
><LI
><P
><CODE
CLASS="option"
>--insert-url=<TT
CLASS="replaceable"
><I
>url</I
></TT
></CODE
></P
></LI
><LI
><P
><CODE
CLASS="option"
>--append-url=<TT
CLASS="replaceable"
><I
>url</I
></TT
></CODE
></P
></LI
><LI
><P
><CODE
CLASS="option"
>-v | --verbose</CODE
></P
></LI
></UL
></DD
><DT
>DISPLAY_OPTIONS</DT
><DD
><P
></P
><UL
><LI
><P
><CODE
CLASS="option"
>--model | --no-model</CODE
></P
></LI
><LI
><P
><CODE
CLASS="option"
>--model-id | --no-model-id</CODE
></P
></LI
><LI
><P
><CODE
CLASS="option"
>--vendor | --no-vendor</CODE
></P
></LI
><LI
><P
><CODE
CLASS="option"
>--vendor-id | --no-vendor-id</CODE
></P
></LI
></UL
></DD
></DL
></DIV
></DIV
><DIV
CLASS="refsect1"
><A
NAME="d1-rs-description"
></A
><H2
>Description</H2
><P
><B
CLASS="command"
>discover</B
> provides an extensible hardware
    detection and reporting interface. Hardware information is stored in an
    <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> data format and can be retrieved across the network.</P
><P
>Fundamental modes of operation:</P
><P
></P
><UL
><LI
><P
>Display a list of hardware devices based on type of device or
          system bus on which the devices reside, via
          <CODE
CLASS="option"
>--type-summary</CODE
> or
          <CODE
CLASS="option"
>--bus-summary</CODE
> (the latter of which is the
          default behavior).
          
        </P
></LI
><LI
><P
>Query specified data for attached hardware, via
          <CODE
CLASS="option"
>--data-path</CODE
>.</P
></LI
></UL
></DIV
><DIV
CLASS="refsect1"
><A
NAME="d1-rs-options"
></A
><H2
>Options</H2
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
><CODE
CLASS="option"
>-h | --help</CODE
></DT
><DD
><P
>Display a simple help message.</P
></DD
><DT
><CODE
CLASS="option"
>-v | --verbose</CODE
></DT
><DD
><P
>Instruct the tool to provide feedback as it operates. This
          will affect the output as <B
CLASS="command"
>discover</B
> parses certain
          arguments, so this should appear early in the command line.</P
></DD
><DT
><CODE
CLASS="option"
>-V | --version</CODE
></DT
><DD
><P
>Display the tool name and version.</P
></DD
><DT
><CODE
CLASS="option"
>-b | --bus-summary</CODE
></DT
><DD
><P
>This is the default behavior: Display basic information
          regarding all devices on the appropriate buses. See
          <A
HREF="#d1-rs-bus-selection"
><I
>Selecting Buses</I
></A
>.</P
></DD
><DT
><CODE
CLASS="option"
>-t | --type-summary</CODE
></DT
><DD
><P
>Summarize devices by class of hardware. Examples of valid
          device types include <TT
CLASS="literal"
>broadband</TT
>,
          <TT
CLASS="literal"
>fixeddisk</TT
>,
          <TT
CLASS="literal"
>display</TT
>, and
          <TT
CLASS="literal"
>network</TT
>.  See <A
HREF="#d1-rs-device-types"
><I
>Device Types</I
></A
>.</P
></DD
><DT
><CODE
CLASS="option"
>--data-path=<TT
CLASS="replaceable"
><I
>path/to/data</I
></TT
></CODE
></DT
><DD
><P
>Query matching devices for detailed information.
          Device-specific data is stored in a hierarchical
          fashion, and the query argument comprises strings
          naming each level in that hierarchy.</P
><P
>Typically, the top-level component of the data
          path will be the <SPAN
CLASS="QUOTE"
>"platform"</SPAN
> that will need
          the information, such as <TT
CLASS="literal"
>linux</TT
> or
          <TT
CLASS="literal"
>xfree86</TT
>. For example, to retrieve
          the Linux kernel module name for a piece of hardware,
          the <CODE
CLASS="option"
>--data-path</CODE
> argument would be
          <TT
CLASS="literal"
>linux/module/name</TT
>.</P
><P
>If multiple <CODE
CLASS="option"
>--data-path</CODE
>
          arguments are given and no format string (see
          <CODE
CLASS="option"
>--format</CODE
>) is provided, only the last
          path is used.</P
><P
>See also the <CODE
CLASS="option"
>--data-version</CODE
>
          argument.</P
></DD
><DT
><CODE
CLASS="option"
>--data-version=<TT
CLASS="replaceable"
><I
>version</I
></TT
></CODE
></DT
><DD
><P
>Specify a version string for the platform that
          will use the information specified by the argument to
          <CODE
CLASS="option"
>--data-path</CODE
>.</P
><P
>This string must be in dotted-decimal notation in
          order to be matched against a range of values, and thus
          may be shorter than the real version.</P
></DD
><DT
><CODE
CLASS="option"
>--format=<TT
CLASS="replaceable"
><I
>format string</I
></TT
></CODE
></DT
><DD
><P
>Dictate the output of the results of the queries
          specified by <CODE
CLASS="option"
>--data-path</CODE
> arguments.
          This format string should follow
          <CODE
CLASS="function"
>printf(3)</CODE
> specifications, although
          only <TT
CLASS="literal"
>%s</TT
> and appropriate flags,
          precision, and width values are supported (or
          make sense); literal text and <TT
CLASS="literal"
>%%</TT
>
          can also be used.  The behavior when the string is
          poorly formatted is undefined.  See also
          <CODE
CLASS="option"
>--normalize-whitespace</CODE
>.</P
></DD
><DT
><CODE
CLASS="option"
>-d | --disable-bus=<TT
CLASS="replaceable"
><I
>bus</I
></TT
></CODE
></DT
><DD
><P
>Use this option to override the list of
          buses to scan by default as defined in
          <TT
CLASS="filename"
>discover.conf</TT
>. Use
          <TT
CLASS="replaceable"
><I
>all</I
></TT
> as an argument to
          disable all buses; this is useful only if
          followed by
          <CODE
CLASS="option"
>--enable-bus</CODE
> (or <CODE
CLASS="option"
>-e</CODE
>)
          arguments.</P
></DD
><DT
><CODE
CLASS="option"
>-e | --enable-bus=<TT
CLASS="replaceable"
><I
>bus</I
></TT
></CODE
></DT
><DD
><P
>Specify a bus to be scanned.</P
></DD
><DT
><CODE
CLASS="option"
>--insert-url=<TT
CLASS="replaceable"
><I
>url</I
></TT
></CODE
></DT
><DD
><P
>Insert a <ACRONYM
CLASS="acronym"
>URL</ACRONYM
> at the head of
          the list of network resources to include in the search
          for hardware information.  Earlier data overrides
          later data; to override the local data
          sources, insert URLs into the list.  See also
          <CODE
CLASS="option"
>--append-url</CODE
>.</P
></DD
><DT
><CODE
CLASS="option"
>--append-url=<TT
CLASS="replaceable"
><I
>url</I
></TT
></CODE
></DT
><DD
><P
>Append a <ACRONYM
CLASS="acronym"
>URL</ACRONYM
> to the end of the
          list of network resources to search for
          hardware information. See also
          <CODE
CLASS="option"
>--insert-url</CODE
>.</P
></DD
><DT
><CODE
CLASS="option"
>--model</CODE
></DT
><DD
><P
>Include the model description in summary
          information. This is enabled by default.</P
></DD
><DT
><CODE
CLASS="option"
>--model-id</CODE
></DT
><DD
><P
>Include the numeric model identifier in summary
          information.</P
></DD
><DT
><CODE
CLASS="option"
>--no-model</CODE
></DT
><DD
><P
>Do not include the model description in summary
          information.</P
></DD
><DT
><CODE
CLASS="option"
>--no-model-id</CODE
></DT
><DD
><P
>Do not include the numeric model identifier in summary
          information. This is the default.</P
></DD
><DT
><CODE
CLASS="option"
>--vendor</CODE
></DT
><DD
><P
>Include the vendor description in summary
          information. This is enabled by default.</P
></DD
><DT
><CODE
CLASS="option"
>--vendor-id</CODE
></DT
><DD
><P
>Include the numeric vendor identifier in summary
          information.</P
></DD
><DT
><CODE
CLASS="option"
>--no-vendor</CODE
></DT
><DD
><P
>Do not include the vendor description in summary
          information.</P
></DD
><DT
><CODE
CLASS="option"
>--no-vendor-id</CODE
></DT
><DD
><P
>Do not include the numeric vendor identifier in summary
          information. This is the default.</P
></DD
><DT
><CODE
CLASS="option"
>--normalize-whitespace</CODE
></DT
><DD
><P
>Consolidate whitespace in the results of a
          <CODE
CLASS="option"
>--data-path</CODE
> query.  The default is not to do so,
          which faithfully reproduces all text in the raw <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> data.</P
><P
>With this option enabled, leading and trailing whitespace
          is removed, and any consecutive internal whitespaces are
          compressed to a single space character.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="refsect1"
><A
NAME="d1-rs-bus-selection"
></A
><H2
>Selecting Buses</H2
><P
><TT
CLASS="filename"
>discover.conf</TT
> defines two lists of system
    buses: one to scan by default (used by the <B
CLASS="command"
>discover</B
>
    command), and one never to scan (used by the <SPAN
CLASS="application"
>Discover</SPAN
> library).</P
><P
>You can override and/or extend the list of default buses with
    <CODE
CLASS="option"
>--disable-bus</CODE
> and <CODE
CLASS="option"
>--enable-bus</CODE
>.
    The list of buses <EM
>not</EM
> to scan cannot be overridden
    without changing <TT
CLASS="filename"
>discover.conf</TT
>, so that list
    should be used only for buses that may be dangerous to probe.</P
><P
>Both arguments take the string <SPAN
CLASS="QUOTE"
>"all"</SPAN
> as a
    value.</P
><P
>If a bus summary is being performed, which is indicated
    either by the presence of <CODE
CLASS="option"
>--bus-summary</CODE
> or
    the absence of <CODE
CLASS="option"
>--type-summary</CODE
> and
    <CODE
CLASS="option"
>--data-path</CODE
>, any unattached arguments on the
    command line will be interpreted as the only buses to scan.
    This is equivalent to using <CODE
CLASS="option"
>--disable-bus
    all</CODE
> before invoking <CODE
CLASS="option"
>--enable-bus</CODE
>
    for the buses of interest.</P
><P
>The following buses are currently supported by <SPAN
CLASS="application"
>Discover</SPAN
>:
    



<P
></P
><UL
><LI
><P
><TT
CLASS="literal"
>ata</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>pci</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>pcmcia</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>scsi</TT
></P
></LI
><LI
><P
><TT
CLASS="literal"
>usb</TT
></P
></LI
></UL
>

    </P
></DIV
><DIV
CLASS="refsect1"
><A
NAME="d1-rs-device-types"
></A
><H2
>Device Types</H2
><P
><SPAN
CLASS="application"
>Discover</SPAN
> defines its own device types, to which the
    device types used by each bus are mapped.  <SPAN
CLASS="application"
>Discover</SPAN
>
    currently recognizes the following device types:
    



<P
></P
><UL
><LI
><P
><TT
CLASS="literal"
>audio</TT
></P
><P
>A device capable of producing an analog or digital
    sound signal is an <I
CLASS="firstterm"
>audio</I
> device.
    Typically, any device commonly referred to as a
    <SPAN
CLASS="QUOTE"
>"sound card"</SPAN
> is classified by <SPAN
CLASS="application"
>Discover</SPAN
> as
    an audio device.</P
></LI
><LI
><P
><TT
CLASS="literal"
>bridge</TT
></P
><P
>A device that provides access to devices of a
    different type, commonly on a different bus, is a
    <I
CLASS="firstterm"
>bridge</I
> device.  For instance, consumer
    <ACRONYM
CLASS="acronym"
>PCI</ACRONYM
> chipsets often feature a bridge to <ACRONYM
CLASS="acronym"
>ATA</ACRONYM
> (also
    known as IDE) devices.</P
></LI
><LI
><P
><TT
CLASS="literal"
>broadband</TT
></P
><P
>An interface device to a computer communications
    network implemented on top of a technology not explicitly
    designed for that purpose is a <I
CLASS="firstterm"
>broadband</I
>
    device.  Examples include ISDN terminal adapters as well
    as DSL and cable <SPAN
CLASS="QUOTE"
>"modems"</SPAN
>; analog
    phone-line modems are not included in this classification
    (see <SPAN
CLASS="QUOTE"
>"modem"</SPAN
> below).</P
></LI
><LI
><P
><TT
CLASS="literal"
>display</TT
></P
><P
>A device controlled by the host machine's CPU and
    capable of producing an analog or digital video signal
    for output purposes is a <I
CLASS="firstterm"
>display</I
> device.
    Typically, any device commonly referred to as a
    <SPAN
CLASS="QUOTE"
>"video card"</SPAN
> is classified by <SPAN
CLASS="application"
>Discover</SPAN
> as
    a display device.</P
></LI
><LI
><P
><TT
CLASS="literal"
>fixeddisk</TT
></P
><P
>A high-speed, fixed magnetic storage device such as
    a hard disk drive is a <I
CLASS="firstterm"
>fixeddisk</I
> device.
    Removable media devices such as floppy disk drives,
    CD-ROM drives, magneto-optical devices, tape drives, and
    Compact Flash card readers are not included in this
    classification.</P
></LI
><LI
><P
><TT
CLASS="literal"
>humaninput</TT
></P
><P
>A device that receives tactile input from a person
    for the purpose of directing a computer's activity is a
    <I
CLASS="firstterm"
>humaninput</I
> device.  Examples include
    keyboards, mice, trackballs, joysticks, gamepads, digital
    tablets manipulated with a stylus or finger, and so
    forth.  Input devices that rely upon non-tactile means of
    determining a person's intent, such as speech-recognition
    devices or cameras, are not included in this
    classification.</P
></LI
><LI
><P
><TT
CLASS="literal"
>imaging</TT
></P
><P
>A device that captures still images for input
    purposes is an <I
CLASS="firstterm"
>imaging</I
> device.  Scanners
    and digital cameras are examples of imaging
    devices.  Motion-capture devices such as television tuner
    cards, webcams, and digital video cameras are not
    included in this classification.</P
></LI
><LI
><P
><TT
CLASS="literal"
>miscellaneous</TT
></P
><P
>Any device that cannot logically be classified as
    another device type is a <I
CLASS="firstterm"
>miscellaneous</I
>
    device.</P
></LI
><LI
><P
><TT
CLASS="literal"
>modem</TT
></P
><P
>An analog phone-line modulator/demodulator
    (modem) is classified by <SPAN
CLASS="application"
>Discover</SPAN
> as a
    <I
CLASS="firstterm"
>modem</I
> device.  No other kind of device is
    so classified.</P
></LI
><LI
><P
><TT
CLASS="literal"
>network</TT
></P
><P
>An interface device to a conventional computer
    data communications network that does not require the use of a terminal
    adapter is a <I
CLASS="firstterm"
>network</I
> device.  For example,
    Ethernet and Token Ring network interface cards are network
    devices.  Analog phone-line modems; terminal adapters
    for technologies such as ISDN and DSL; and <SPAN
CLASS="QUOTE"
>"cable modems"</SPAN
>
    are not <SPAN
CLASS="QUOTE"
>"network"</SPAN
> devices.</P
></LI
><LI
><P
><TT
CLASS="literal"
>optical</TT
></P
><P
>An optical-technology storage device, often using
    read-only media, is an <I
CLASS="firstterm"
>optical</I
> device.  By
    far the most common examples of these devices are CD-ROM
    and DVD-ROM drives, including versions of these drives
    that can <SPAN
CLASS="QUOTE"
>"burn"</SPAN
> (write to) optical
    discs.</P
></LI
><LI
><P
><TT
CLASS="literal"
>printer</TT
></P
><P
>A device that renders visual output in a permanent
    or semi-permanent manner to a physical medium is a
    <I
CLASS="firstterm"
>printer</I
>.  Typically, any device
    colloquially referred to as a <SPAN
CLASS="QUOTE"
>"printer"</SPAN
> is
    also classified by <SPAN
CLASS="application"
>Discover</SPAN
> as a
    printer.</P
></LI
><LI
><P
><TT
CLASS="literal"
>removabledisk</TT
></P
><P
>Storage devices that feature removable media using
    just about any technology except that of magnetic tape,
    CD-ROM, and DVD-ROM drives are
    <I
CLASS="firstterm"
>removabledisk</I
> devices.  Examples include
    floppy disk drives, magneto-optical drives, and Compact
    Flash card readers.</P
></LI
><LI
><P
><TT
CLASS="literal"
>tape</TT
></P
><P
>A sequential-access mass storage device using
    magnetic tape is a <I
CLASS="firstterm"
>tape</I
> device.  Commonly
    used for archival and backup purposes, DAT drives are
    examples of tape devices.</P
></LI
><LI
><P
><TT
CLASS="literal"
>video</TT
></P
><P
>A device that produces a real-time digital video
    signal for input purposes is a <I
CLASS="firstterm"
>video</I
>
    device.  Webcams, digital video cameras, and television
    tuners are examples of video
    devices.  Note that still digital cameras with
    <SPAN
CLASS="QUOTE"
>"movie"</SPAN
> capability are
    <EM
>not</EM
> considered video
    devices unless they can transmit the live video signal to
    the host in real time.</P
></LI
></UL
>

    </P
></DIV
><DIV
CLASS="refsect1"
><A
NAME="d1-rs-examples"
></A
><H2
>Examples</H2
><DIV
CLASS="example"
><A
NAME="d1-ex-scan-buses"
></A
><P
><B
>Example 9-1. Scan the local buses</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
># discover
Intel Corporation 82815 Chipset Host Bridge and Memory Controller Hub
unknown unknown
unknown unknown
unknown unknown
Intel Corporation 82815 Chipset IDE controller
Intel Corporation 82815 Chipset USB (A)
Intel Corporation 82815 System Management bus controller
ATI Technologies, Inc. Rage 128 Pro GL [PF]
3Com Corporation 3c905C-TX [Fast Etherlink]
Ensoniq ES1371 [AudioPCI-97]
unknown unknown</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="example"
><A
NAME="d1-ex-view-video-cards"
></A
><P
><B
>Example 9-2. View PCI video cards</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
># discover -v --type-summary --disable-bus all --enable-bus pci display
Disabled pci
Disabled pcmcia
Disabled scsi
Disabled usb
Enabled pci
Loading XML data... pci Done
Scanning buses... pci Done
ATI Technologies, Inc. Rage 128 Pro GL [PF]</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="example"
><A
NAME="d1-ex-query-xfree86"
></A
><P
><B
>Example 9-3. Query for the driver module for
      XFree86 server version 4.2.0</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
># discover --data-path=xfree86/server/device/driver --data-version=4.2.0 display
ati</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="example"
><A
NAME="d1-ex-type-summary"
></A
><P
><B
>Example 9-4. Get model and vendor
      information by type</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>$ discover -t --no-model
Intel Corporation
NVIDIA Corporation
3Com Corporation
$ discover -t --no-vendor
82815 System Management bus controller
Vanta [NV6]
3c905C-TX [Fast Etherlink]</PRE
></FONT
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="refsect1"
><A
NAME="d1-rs-files"
></A
><H2
>Files</H2
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
><TT
CLASS="filename"
>/etc/discover.conf.d</TT
></DT
><DD
><P
>The directory containing configuration files that control 
          the default behavior for both the <B
CLASS="command"
>discover</B
> tool and 
          the <SPAN
CLASS="application"
>Discover</SPAN
> library.
          </P
></DD
><DT
><TT
CLASS="filename"
>file:///lib/discover/list.xml</TT
></DT
><DD
><P
>An <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> file containing <ACRONYM
CLASS="acronym"
>URL</ACRONYM
>s with
            hardware information. This list can be extended with
            <CODE
CLASS="option"
>--append-url</CODE
> and
            <CODE
CLASS="option"
>--extend-url</CODE
>.
          </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="refsect1"
><A
NAME="d1-rs-authors"
></A
><H2
>Authors</H2
><P
>Josh Bressers, John R. Daily, and
    G. Branden Robinson developed the current implementation of
    <SPAN
CLASS="application"
>Discover</SPAN
> for Progeny Linux Systems.</P
><P
>The Linux implementation of the system-dependent interfaces is
    derived from <B
CLASS="command"
>detect</B
>, by MandrakeSoft SA.</P
></DIV
><DIV
CLASS="refsect1"
><A
NAME="d1-rs-see-also"
></A
><H2
>See Also</H2
><P
>discover.conf(5), discover-modprobe(8)</P
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-discover-conf_manpage"
></A
>Chapter 10. <TT
CLASS="filename"
>discover.conf</TT
> Manual Page</H1
><H1
><A
NAME="AEN1223"
></A
>discover.conf</H1
><DIV
CLASS="refnamediv"
><A
NAME="AEN1237"
></A
><H2
>Name</H2
>discover.conf&nbsp;--&nbsp;configuration file format for discover(1)</DIV
><DIV
CLASS="refsect1"
><A
NAME="dc5-rs-description"
></A
><H2
>Description</H2
><P
><SPAN
CLASS="application"
>Discover</SPAN
> looks for configuration files in a configuration
    directory, containing a number of files.  These define the 
    system buses that should be scanned by default, those that should 
    never be scanned, and the <ACRONYM
CLASS="acronym"
>URL</ACRONYM
>s for hardware data 
    files beyond the local copy provided with the software.</P
><P
>The file format is <ACRONYM
CLASS="acronym"
>XML</ACRONYM
>; the <A
HREF="#ap-discover_conf_dtd"
><ACRONYM
CLASS="acronym"
>DTD</ACRONYM
></A
>
    is provided with the <SPAN
CLASS="application"
>Discover</SPAN
> software, and can be used for
    informational or validation purposes.</P
></DIV
><DIV
CLASS="refsect1"
><A
NAME="dc5-rs-examples"
></A
><H2
>Examples</H2
><DIV
CLASS="example"
><A
NAME="AEN1252"
></A
><P
><B
>Example 10-1. Establishing default buses to scan</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;&#60;?xml version="1.0"?&#62;

&#60;!DOCTYPE conffile SYSTEM "conffile.dtd"&#62;

&#60;conffile&#62;
  &#60;busscan scan="default"&#62;
    &#60;bus name="ata"/&#62;
    &#60;bus name="pci"/&#62;
    &#60;bus name="pcmcia"/&#62;
    &#60;bus name="scsi"/&#62;
    &#60;bus name="usb"/&#62;
  &#60;/busscan&#62;
&#60;/conffile&#62;

</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="example"
><A
NAME="AEN1255"
></A
><P
><B
>Example 10-2. A more complex example</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;&#60;?xml version="1.0"?&#62;

&#60;!DOCTYPE conffile SYSTEM "conffile.dtd"&#62;

&#60;conffile&#62;
  &#60;busscan scan="default"&#62;
    &#60;bus name="ata"/&#62;
    &#60;bus name="pci"/&#62;
    &#60;bus name="pcmcia"/&#62;
    &#60;bus name="usb"/&#62;
  &#60;/busscan&#62;
  &#60;!-- My ancient SCSI card locks up when probed --&#62;
  &#60;busscan scan="never"&#62;
    &#60;bus name="scsi"/&#62;
  &#60;/busscan&#62;
  &#60;data-sources&#62;
    &#60;data-source url="http://www.example.com/discover/xfree86.xml"
                 label="Updated XFree86 hardware information"&#62;
  &#60;/data-sources&#62;
&#60;/conffile&#62;

</PRE
></FONT
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="refsect1"
><A
NAME="AEN1258"
></A
><H2
>Authors</H2
><P
>Josh Bressers, John R. Daily, and
    G. Branden Robinson developed the current implementation of
    <SPAN
CLASS="application"
>Discover</SPAN
> for Progeny Linux Systems.</P
><P
>The Linux implementation of the system-dependent interfaces is
    derived from <B
CLASS="command"
>detect</B
>, by MandrakeSoft SA.</P
></DIV
><DIV
CLASS="refsect1"
><A
NAME="dc5-rs-see-also"
></A
><H2
>See Also</H2
><P
>discover(1)</P
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-discover-modprobe_manpage"
></A
>Chapter 11. <B
CLASS="command"
>discover-modprobe</B
>
      Manual Page</H1
><H1
><A
NAME="AEN1270"
></A
>discover-modprobe</H1
><DIV
CLASS="refnamediv"
><A
NAME="AEN1284"
></A
><H2
>Name</H2
>discover-modprobe&nbsp;--&nbsp;kernel module loading using discover(1)</DIV
><DIV
CLASS="refsynopsisdiv"
><A
NAME="AEN1287"
></A
><H2
>Synopsis</H2
><P
><B
CLASS="command"
>discover-modprobe</B
>  [-n] [-v]</P
></DIV
><DIV
CLASS="refsect1"
><A
NAME="dm8-rs-description"
></A
><H2
>Description</H2
><P
><B
CLASS="command"
>discover-modprobe</B
> loads kernel modules
    identified by <B
CLASS="command"
>discover</B
>. It will typically be invoked
    automatically at boot time.</P
></DIV
><DIV
CLASS="refsect1"
><A
NAME="dm8-rs-options"
></A
><H2
>Options</H2
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
><CODE
CLASS="option"
>-n</CODE
></DT
><DD
><P
>Echo the <B
CLASS="command"
>modprobe</B
> invocations instead of
          running them.</P
></DD
><DT
><CODE
CLASS="option"
>-v</CODE
></DT
><DD
><P
>Be verbose.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="refsect1"
><A
NAME="dm8-rs-files"
></A
><H2
>Files</H2
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
><TT
CLASS="filename"
>/etc/discover-modprobe.conf</TT
></DT
><DD
><P
>This configuration file defines the types of modules
          to load by default, and specific modules
          <EM
>not</EM
> to load.</P
></DD
><DT
><TT
CLASS="filename"
>/var/lib/discover/crash</TT
></DT
><DD
><P
>A crash file written and erased each time
    <B
CLASS="command"
>discover-modprobe</B
> attempts to load a
    module. If the file lingers, the computer is assumed to have
    crashed while loading that module, and the module name is added
      to <TT
CLASS="filename"
>discover-modprobe.conf</TT
> as a module to
    skip in the future.
    </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="refsect1"
><A
NAME="dm8-rs-see-also"
></A
><H2
>See Also</H2
><P
>discover-modprobe.conf(5), modprobe(8), discover(1)</P
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-discover-modprobe-conf_manpage"
></A
>Chapter 12. <TT
CLASS="filename"
>discover-modprobe.conf</TT
>
      Manual Page</H1
><H1
><A
NAME="AEN1333"
></A
>discover-modprobe.conf</H1
><DIV
CLASS="refnamediv"
><A
NAME="AEN1347"
></A
><H2
>Name</H2
>discover-modprobe.conf&nbsp;--&nbsp;configuration file for discover-modprobe(5)</DIV
><DIV
CLASS="refsect1"
><A
NAME="dmc5-rs-description"
></A
><H2
>Description</H2
><P
><TT
CLASS="filename"
>discover-modprobe.conf</TT
> is the configuration
      file for <B
CLASS="command"
>discover-modprobe</B
>, which is responsible
      for retrieving and loading kernel modules.</P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="http://www.progeny.com/images/utility/warning.png"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>This file is a shell script, and
      as such is subject to a string variable assignment syntax. No space
      is allowed between the variable name, the equal (=) sign, and the
      value(s) assigned. If multiple values are to be assigned, the list
      must be space-delimited with surrounding quotes.</P
></TD
></TR
></TABLE
></DIV
><P
>Two directives can be used in this file:
      <TT
CLASS="literal"
>types</TT
> and <TT
CLASS="literal"
>skip</TT
>. Both can be
      defined multiple times.</P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
><TT
CLASS="literal"
>types</TT
></DT
><DD
><P
>This describes the classes of hardware that should be
            scanned and queried.</P
></DD
><DT
><TT
CLASS="literal"
>skip</TT
></DT
><DD
><P
>These modules should never be loaded. See the
            <SPAN
CLASS="QUOTE"
>"Files"</SPAN
> section for details on the mechanism for
            generating these entries automatically.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="refsect1"
><A
NAME="dmc5-rs-files"
></A
><H2
>Files</H2
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
><TT
CLASS="filename"
>/var/lib/discover/crash</TT
></DT
><DD
><P
>A crash file written and erased each time
    <B
CLASS="command"
>discover-modprobe</B
> attempts to load a
    module. If the file lingers, the computer is assumed to have
    crashed while loading that module, and the module name is added
      to <TT
CLASS="filename"
>discover-modprobe.conf</TT
> as a module to
    skip in the future.
    </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="refsect1"
><A
NAME="dmc5-rs-see-also"
></A
><H2
>See Also</H2
><P
>discover-modprobe(8), modprobe(8), discover(1)</P
></DIV
></DIV
></DIV
><DIV
CLASS="PART"
><A
NAME="pt-library"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
>IV. Library</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>13. <A
HREF="#ch-discover_library"
>The <SPAN
CLASS="application"
>Discover</SPAN
> Library</A
></DT
><DD
><DL
><DT
>13.1. <A
HREF="#sc-library_design_principles"
>Library Design
        Principles</A
></DT
><DT
>13.2. <A
HREF="#sc-discover_data_sources"
><SPAN
CLASS="application"
>Discover</SPAN
> Data
        Sources</A
></DT
><DT
>13.3. <A
HREF="#sc-bus_map"
>The Bus Map</A
></DT
><DT
>13.4. <A
HREF="#sc-scanning_system"
>Scanning the System</A
></DT
><DT
>13.5. <A
HREF="#sc-using_discover_device_t_structures"
>Using
        <SPAN
CLASS="type"
>discover_device_t</SPAN
> Structures</A
></DT
></DL
></DD
><DT
>14. <A
HREF="#ch-sysdeps"
>System Dependencies</A
></DT
><DD
><DL
><DT
>14.1. <A
HREF="#sc-sysdeps_api"
><ACRONYM
CLASS="acronym"
>API</ACRONYM
></A
></DT
></DL
></DD
></DL
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-discover_library"
></A
>Chapter 13. The <SPAN
CLASS="application"
>Discover</SPAN
> Library</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="sc-library_design_principles"
>13.1. Library Design
        Principles</A
></H2
><P
>Lazy allocation is used throughout <SPAN
CLASS="application"
>Discover</SPAN
>.  This means
        that there are no <SPAN
CLASS="QUOTE"
>"init"</SPAN
> functions, and no functions
        to scan the bus.  Instead, retrieval functions scan or initialize
        as necessary. Each of these retrieval functions has an equivalent
        function for freeing the allocated memory.  This is valuable to
        long-lived processes to aid in memory management, but even
        short-lived processes may want to use them to force reloading of
        the information.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-discover_data_sources"
>13.2. <SPAN
CLASS="application"
>Discover</SPAN
> Data
        Sources</A
></H2
><P
><SPAN
CLASS="application"
>Discover</SPAN
> knows about one data source by default: the local
        data from the <TT
CLASS="literal"
>discover-data</TT
> package.  Additional
        sources can be added with the
        <CODE
CLASS="function"
>discover_conf_append_url</CODE
> and
        <CODE
CLASS="function"
>discover_conf_insert_url</CODE
> functions.  As their
        names suggest, they append or insert <ACRONYM
CLASS="acronym"
>URL</ACRONYM
>s on the data source
        list.  Earlier data overrides later data; to override
        the local data sources, insert <ACRONYM
CLASS="acronym"
>URL</ACRONYM
>s.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-bus_map"
>13.3. The Bus Map</A
></H2
><P
>Most high-level operations begin at the bus map.  Bus maps
        (<A
HREF="api-reference/group__types.html#a2"
TARGET="_top"
><SPAN
CLASS="type"
>discover_bus_map_t</SPAN
></A
>)
        are retrieved with calls to
        <CODE
CLASS="function"
>discover_conf_get_bus_map</CODE
> or
        <CODE
CLASS="function"
>discover_conf_get_bus_map_by_name</CODE
>.
        <CODE
CLASS="function"
>discover_conf_get_bus_map</CODE
> returns an array of
        maps, one for each supported bus, with the last element being all
        0s. <CODE
CLASS="function"
>discover_conf_get_bus_map_by_name</CODE
> returns
        the map for the named bus.  The map contains pointers to all the
        functions that operate on the bus, as well as the
        <CODE
CLASS="varname"
>scan_default</CODE
> variable, which determines whether
        the bus is scanned by default.  There is also a
        <CODE
CLASS="varname"
>scan_never</CODE
> variable, but it is for internal use
        only.  The name of the bus is stored in the
        <CODE
CLASS="varname"
>name</CODE
> variable.</P
><P
>The following functions are available in the bus map.  The
        <SPAN
CLASS="QUOTE"
>"get"</SPAN
> functions take a single <A
HREF="api-reference/group__types.html#a1"
TARGET="_top"
><SPAN
CLASS="type"
>discover_error_t</SPAN
></A
>
        argument and return a list of <A
HREF="api-reference/group__types.html#a3"
TARGET="_top"
><SPAN
CLASS="type"
>discover_device_t</SPAN
></A
>
        structures, while the <SPAN
CLASS="QUOTE"
>"free"</SPAN
> functions take no
        arguments and return no value.</P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
><CODE
CLASS="function"
>get_devices</CODE
></DT
><DD
><P
>Retrieve the list of devices found on this bus.
              Returns NULL if the bus is not present on the
              system, or if no devices are attached to it.</P
></DD
><DT
><CODE
CLASS="function"
>xml_get_busclasses</CODE
></DT
><DD
><P
>Retrieve the list of busclasses for this bus (from
              the <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> data sources).</P
></DD
><DT
><CODE
CLASS="function"
>xml_get_devices</CODE
></DT
><DD
><P
>Retrieve the list of devices for this bus (from
              the <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> data sources).  Note that this is the list of
              devices that <SPAN
CLASS="application"
>Discover</SPAN
> knows about, not the list of devices
              present on the system.</P
></DD
><DT
><CODE
CLASS="function"
>xml_get_vendors</CODE
></DT
><DD
><P
>Retrieve the list of vendors for this bus (from
              the <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> data sources).</P
></DD
><DT
><CODE
CLASS="function"
>xml_get_busclass_urls</CODE
></DT
><DD
><P
>Retrieve the list of <ACRONYM
CLASS="acronym"
>URL</ACRONYM
>s from which busclass data
              is retrieved.  This function is probably not useful to
              most clients.</P
></DD
><DT
><CODE
CLASS="function"
>xml_get_device_urls</CODE
></DT
><DD
><P
>Retrieve the list of <ACRONYM
CLASS="acronym"
>URL</ACRONYM
>s from which device data
              is retrieved.  This function is probably not useful to
              most clients.</P
></DD
><DT
><CODE
CLASS="function"
>xml_get_vendor_urls</CODE
></DT
><DD
><P
>Retrieve the list of <ACRONYM
CLASS="acronym"
>URL</ACRONYM
>s from which vendor data
              is retrieved.  This function is probably not useful to
              most clients.</P
></DD
><DT
><CODE
CLASS="function"
>free_devices</CODE
></DT
><DD
><P
>Free the list of devices.</P
></DD
><DT
><CODE
CLASS="function"
>xml_free_busclasses</CODE
></DT
><DD
><P
>Free the list of busclasses.</P
></DD
><DT
><CODE
CLASS="function"
>xml_free_devices</CODE
></DT
><DD
><P
>Free the list of devices (the <ACRONYM
CLASS="acronym"
>XML</ACRONYM
> data, not the
              list of devices found on the system).</P
></DD
><DT
><CODE
CLASS="function"
>xml_free_vendors</CODE
></DT
><DD
><P
>Free the list of vendors.</P
></DD
><DT
><CODE
CLASS="function"
>xml_free_busclass_urls</CODE
></DT
><DD
><P
>Free the list of busclass <ACRONYM
CLASS="acronym"
>URL</ACRONYM
>s.</P
></DD
><DT
><CODE
CLASS="function"
>xml_free_device_urls</CODE
></DT
><DD
><P
>Free the list of device <ACRONYM
CLASS="acronym"
>URL</ACRONYM
>s.</P
></DD
><DT
><CODE
CLASS="function"
>xml_free_vendor_urls</CODE
></DT
><DD
><P
>Free the list of vendor <ACRONYM
CLASS="acronym"
>URL</ACRONYM
>s.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-scanning_system"
>13.4. Scanning the System</A
></H2
><P
><SPAN
CLASS="application"
>Discover</SPAN
> provides a few ways to scan the system for
        information.</P
><P
>You can walk the bus map:</P
><DIV
CLASS="informalexample"
><P
></P
><A
NAME="AEN1511"
></A
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>for (i = 0; busmap[i].name; i++) {
    if (busmap[i].scan == DISCOVER_SCAN_DEFAULT) {
        devices = busmap[i].get_devices(&#38;status);
        check_status(status);
        do_something_cool(devices);
    }
}</PRE
></FONT
></TD
></TR
></TABLE
><P
></P
></DIV
><P
>You can scan a specific bus:</P
><DIV
CLASS="informalexample"
><P
></P
><A
NAME="AEN1514"
></A
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>devices = discover_get_pci_devices(&#38;status);
check_status(status);
do_something_cool(devices);</PRE
></FONT
></TD
></TR
></TABLE
><P
></P
></DIV
><P
>Perhaps most usefully, you can scan for devices
        of a specific type:</P
><DIV
CLASS="informalexample"
><P
></P
><A
NAME="AEN1517"
></A
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>devices = discover_device_find("video", &#38;status);
check_status(status);
do_something_video(devices);</PRE
></FONT
></TD
></TR
></TABLE
><P
></P
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="sc-using_discover_device_t_structures"
>13.5. Using
        <SPAN
CLASS="type"
>discover_device_t</SPAN
> Structures</A
></H2
><P
>Now that you have some device structures, what can you
        do with them?  The most interesting operation is retrieving
        data with <CODE
CLASS="function"
>discover_device_get_data</CODE
>.  Also
        available are
        <CODE
CLASS="function"
>discover_device_get_vendor_name</CODE
>,
        <CODE
CLASS="function"
>discover_device_get_model_name</CODE
>,
        <CODE
CLASS="function"
>discover_device_get_model_id</CODE
>, and
        <CODE
CLASS="function"
>discover_device_get_vendor_id</CODE
>.</P
><P
><CODE
CLASS="function"
>discover_device_get_data</CODE
> takes a
        <A
HREF="#sc-accessing_device_data"
>data path</A
> and a
        <A
HREF="#sc-data_element_version_attribute"
>version
        number</A
> and searches for the first data structure that
        matches.</P
><P
><CODE
CLASS="function"
>discover_device_get_vendor_name</CODE
>
        returns the human-readable name for the device's
        vendor.</P
><P
><CODE
CLASS="function"
>discover_device_get_model_name</CODE
>
        returns the human-readable name for the device's model.</P
><P
><CODE
CLASS="function"
>discover_device_get_model_id</CODE
>
        returns the bus-specific ID for the device model.</P
><P
><CODE
CLASS="function"
>discover_device_get_vendor_id</CODE
>
        returns the bus-specific ID for the device vendor.</P
></DIV
></DIV
><DIV
CLASS="chapter"
><HR><H1
><A
NAME="ch-sysdeps"
></A
>Chapter 14. System Dependencies</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="sc-sysdeps_api"
>14.1. <ACRONYM
CLASS="acronym"
>API</ACRONYM
></A
></H2
><P
>The system-dependent code (<I
CLASS="firstterm"
>sysdeps</I
>)
        that must be custom-written for each operating system conforms to a
        very simple <ACRONYM
CLASS="acronym"
>API</ACRONYM
>.  <SPAN
CLASS="application"
>Discover</SPAN
> invokes
        <CODE
CLASS="function"
>_discover_get_<TT
CLASS="replaceable"
><I
>busname</I
></TT
>_raw()</CODE
>
        with no arguments, and expects a linked list of
        <A
HREF="api-reference/sysdep_8h.html#a0"
TARGET="_top"
><SPAN
CLASS="type"
>discover_sysdep_data_t</SPAN
></A
> structures in return.</P
><P
>The <A
HREF="api-reference/sysdep_8h.html#a0"
TARGET="_top"
><SPAN
CLASS="type"
>discover_sysdep_data_t</SPAN
></A
> structures should
        contain as much descriptive information as they can regarding the
        devices discovered.  Specifically, the three pieces of information
        desired are the <A
HREF="#ch-busclass_lists"
>busclass</A
> (device
        type), <A
HREF="#ch-vendor_lists"
>vendor
        identifier</A
>, and model identifier, which is a unique
        identification string that the vendor has provided for the given
        piece of hardware.</P
><DIV
CLASS="example"
><A
NAME="AEN1558"
></A
><P
><B
>Example 14-1. Linux <ACRONYM
CLASS="acronym"
>PCI</ACRONYM
> sysdep code</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>#include &#60;config.h&#62;

#include &#60;stdio.h&#62;
#include &#60;stdlib.h&#62;

#include &#60;sysdep.h&#62;

discover_sysdep_data_t *
_discover_get_pci_raw(void)
{
    FILE *f;
    char *line = NULL;
    size_t len = 0;
    discover_sysdep_data_t *head = NULL, *node, *last = NULL;
    unsigned int id;

    if ((f = fopen(PATH_PROC_PCI, "r"))) {
        while (getline(&#38;line, &#38;len, f) &#62;= 0) {
            if (line[0] == '\n' || line[0] == '#') {
                continue;
            }

            node = _discover_sysdep_data_new();
            sscanf(line, "%*04x\t%08x", &#38;id);
            node-&#62;vendor = (id &#62;&#62; 16);
            node-&#62;model = id &#38; 0xffff;

            if (head == NULL) {
                head = node;
                last = head;
            } else {
                last-&#62;next = node;
                last = node;
            }
        }
        free(line);
        fclose(f);
    }
    return head;
}
</PRE
></FONT
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="appendix"
><HR><H1
><A
NAME="ap-discover_api_reference"
></A
>Appendix A. <SPAN
CLASS="application"
>Discover</SPAN
> <ACRONYM
CLASS="acronym"
>API</ACRONYM
> Reference</H1
><P
>The <ACRONYM
CLASS="acronym"
>API</ACRONYM
> reference is <A
HREF="api-reference/index.html"
TARGET="_top"
>here</A
>.</P
></DIV
><DIV
CLASS="appendix"
><HR><H1
><A
NAME="ap-discover_dtd"
></A
>Appendix B. <SPAN
CLASS="application"
>Discover</SPAN
> <ACRONYM
CLASS="acronym"
>DTD</ACRONYM
></H1
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;&#60;!-- $Progeny$ --&#62;

&#60;!ELEMENT discover-data (location)*&#62;

&#60;!ELEMENT location EMPTY&#62;
&#60;!ATTLIST location bus          NMTOKEN #REQUIRED
                   type         NMTOKEN #REQUIRED
                   url          CDATA   #REQUIRED&#62;

&#60;!ELEMENT busclass_list (busclass)*&#62;
&#60;!ATTLIST busclass_list bus NMTOKEN #REQUIRED&#62;

&#60;!ELEMENT busclass EMPTY&#62;
&#60;!ATTLIST busclass id           NMTOKEN #REQUIRED
                   name         NMTOKEN #REQUIRED&#62;

&#60;!ELEMENT vendor_list (vendor)*&#62;
&#60;!ATTLIST vendor_list bus NMTOKEN #REQUIRED&#62;

&#60;!ELEMENT vendor EMPTY&#62;
&#60;!ATTLIST vendor id             CDATA #REQUIRED
                 name           CDATA #REQUIRED&#62;

&#60;!ELEMENT device_list (device)*&#62;
&#60;!ATTLIST device_list bus NMTOKEN #REQUIRED&#62;

&#60;!ELEMENT device (data)*&#62;
&#60;!ATTLIST device busclass       NMTOKEN #REQUIRED
                 model          CDATA #DEFAULT default
                 model_name     CDATA   #REQUIRED
                 vendor         CDATA #REQUIRED&#62;

&#60;!ELEMENT data (#PCDATA|data)*&#62;
&#60;!ATTLIST data class		NMTOKEN	#REQUIRED
               version		CDATA	#IMPLIED&#62;

&#60;!-- vim:set ai et sts=8 sw=8 tw=0: --&#62;

    </PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="appendix"
><HR><H1
><A
NAME="ap-discover_conf_dtd"
></A
>Appendix C. <SPAN
CLASS="application"
>Discover</SPAN
> Configuration File <ACRONYM
CLASS="acronym"
>DTD</ACRONYM
></H1
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;&#60;!-- $Progeny$ --&#62;

&#60;!ELEMENT conffile (busscan*,data-sources?)&#62;

&#60;!ELEMENT data-sources (data-source)*&#62;
&#60;!ELEMENT data-source EMPTY&#62;
&#60;!ATTLIST data-source url          CDATA #REQUIRED
                      label        CDATA #IMPLIED
                      place        NMTOKEN #IMPLIED&#62;

&#60;!ELEMENT busscan (bus)*&#62;

&#60;!-- The attributes will likely be handled by different parts of        --&#62;
&#60;!-- Discover. If there is a list of buses never to scan, the library   --&#62;
&#60;!-- should be aware of it. If there is a list of buses to scan by      --&#62;
&#60;!-- default, that will be of interest to the client tool.              --&#62;
&#60;!ATTLIST busscan scan (default|never) #REQUIRED&#62;

&#60;!ELEMENT bus EMPTY&#62;
&#60;!ATTLIST bus name              NMTOKEN #REQUIRED&#62;

    </PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="appendix"
><HR><H1
><A
NAME="ap-licensing_issue_linux_sysdeps"
></A
>Appendix D. Licensing Issue on the Linux Sysdeps</H1
><P
>It should be noted that the Linux-specific files in the
    <TT
CLASS="filename"
>sysdeps/linux</TT
> directory of the source distribution
    are derived from code written for the <SPAN
CLASS="application"
>Detect</SPAN
>
    library by MandrakeSoft SA, and are licensed under the
    <ACRONYM
CLASS="acronym"
>GNU</ACRONYM
> Project's <A
HREF="http://www.gnu.org/copyleft/gpl.html"
TARGET="_top"
>General Public
    License</A
> (<ACRONYM
CLASS="acronym"
>GPL</ACRONYM
>).</P
><P
>Note that section 2 of the <ACRONYM
CLASS="acronym"
>GPL</ACRONYM
> places
    requirements on derived works that prevent licensees from exercising
    some of the permissions granted under the license on the rest of
    <SPAN
CLASS="application"
>Discover</SPAN
>.  However, not everyone who modifies or distributes
    <SPAN
CLASS="application"
>Discover</SPAN
> will necessarily be subject to the terms of the
    <ACRONYM
CLASS="acronym"
>GPL</ACRONYM
>.  If you do not compile, use, or distribute the
    Linux sysdeps (for instance, if you are building <SPAN
CLASS="application"
>Discover</SPAN
> for
    FreeBSD), then the license terms on them do not attach.</P
><P
>We realize, however, that it is desirable that all of <SPAN
CLASS="application"
>Discover</SPAN
>
    be under the the same license terms.  There are a few possible
    solutions to this problem:</P
><P
></P
><UL
><LI
><P
>If you do not need the Linux sysdeps, you can delete them
        from your copy of <SPAN
CLASS="application"
>Discover</SPAN
>.</P
></LI
><LI
><P
>You can rewrite the Linux sysdeps.  The resulting code will
        be your work, so the only limitations on you will be those imposed
        by <SPAN
CLASS="application"
>Discover</SPAN
>'s license.  If you do so, we encourage you to license
        your rewrite under the same terms as the rest of <SPAN
CLASS="application"
>Discover</SPAN
> &#8212;
        in that event, Progeny will be happy to incorporate your code into
        a future release of <SPAN
CLASS="application"
>Discover</SPAN
>.</P
></LI
><LI
><P
>You can contact MandrakeSoft SA and negotiate a different
        license to their code that is used in the Linux sysdeps.</P
></LI
><LI
><P
>You can contact MandrakeSoft SA and attempt to persuade them
        to relicense their code that is used in the Linux sydeps
        under the terms used by the rest of <SPAN
CLASS="application"
>Discover</SPAN
>. (MandrakeSoft SA
        would not have to abandon or assign their copyright.)  If you
        succeed in this effort, please let Progeny know and we will update
        the license terms on our copy of the MandrakeSoft SA code.</P
></LI
><LI
><P
>You can wait; eventually Progeny employees, or some
        volunteer, will rewrite the Linux sysdeps and license them under
        the terms that the rest of <SPAN
CLASS="application"
>Discover</SPAN
> uses.</P
></LI
></UL
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="http://www.progeny.com/images/utility/note.png"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The foregoing discussing is not legal advice and makes no claim
      to be such.  It is a layperson's understanding of the licensing
      issues from a software developer's perspective.  Progeny makes no
      warranties or guarantees as to the accuracy of the above
      analysis in a legal context.  If you require a professional legal
      opinion, consult attorneys specializing in copyright and licensed to
      practice in the jurisdictions of interest to you or to your
      organization.</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><H3
CLASS="FOOTNOTES"
>Notes</H3
><TABLE
BORDER="0"
CLASS="FOOTNOTES"
WIDTH="100%"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN53"
HREF="#AEN53"
><SPAN
CLASS="footnote"
>[1]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>Other
        protocols such as <ACRONYM
CLASS="acronym"
>FTP</ACRONYM
> are available but deprecated; <SPAN
CLASS="application"
>Discover</SPAN
>
        uses integrity verification mechanisms such as
        <ACRONYM
CLASS="acronym"
>MD5</ACRONYM
> checksums in the <ACRONYM
CLASS="acronym"
>HTTP</ACRONYM
>
        protocol.</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN779"
HREF="#AEN779"
><SPAN
CLASS="footnote"
>[2]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>We would say
        <TT
CLASS="literal"
>[2.2,2.3)</TT
> instead, but, like many Free Software
        projects, the Linux kernel uses odd minor version numbers to
        denote unstable, development series of the software, and even minor
        version numbers to denote stable, production series of the
        software. In the example, then, we arbitrarily treat all 2.3 series
        kernels the same as 2.2 kernels.</P
></TD
></TR
></TABLE
></BODY
></HTML
>