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 7094 7095 7096 7097 7098 7099 7100 7101 7102 7103 7104 7105 7106 7107 7108 7109 7110 7111 7112 7113 7114 7115 7116 7117 7118 7119 7120 7121 7122 7123 7124 7125 7126 7127 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168 7169 7170 7171 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7271 7272 7273 7274 7275 7276 7277 7278 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7326 7327 7328 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7339 7340 7341 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7513 7514 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7553 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7600 7601 7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8027 8028 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8092 8093 8094 8095 8096 8097 8098 8099 8100 8101 8102 8103 8104 8105 8106 8107 8108 8109 8110 8111 8112 8113 8114 8115 8116 8117 8118 8119 8120 8121 8122
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> Linux Gazette Table of Contents LG #76</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#0000AF"
ALINK="#FF0000" >
<center>
<!-- A HREF="http://www.linuxgazette.com/">
<H1><IMG SRC="../gx/newlogo.jpg" ALT="LINUX GAZETTE" border="0"></H1></A> -->
<A HREF="http://www.linuxgazette.com/">
<H1><IMG ALT="LINUX GAZETTE" SRC="../gx/lglogo.png"
WIDTH="600" HEIGHT="124" border="0"></H1></A>
<H2>March 2002, Issue 76
Published by <I>Linux Journal</I></H2>
<A HREF=../index.html>Front Page</A> |
<A HREF=../index.html>Back Issues</A> |
<A HREF=../lg_faq.html>FAQ</A> |
<A HREF=../mirrors.html>Mirrors</A> <!-- | --><BR>
<A HREF="../tag-kb.html">The Answer Gang knowledge base</A> (your Linux questions here!) <!-- | --><BR>
<A HREF="http://www.linuxgazette.com/search.html">Search (www.linuxgazette.com)</A>
<!-- *** BEGIN mirror site search link *** -->
<!-- <A HREF="http://www.linuxgazette.com/search.html">(SITE.COM
mirror)</A> -->
<!-- *** END mirror site search link *** -->
</CENTER>
<HR NOSHADE>
<!--=================================================================-->
<!-- H1><font color="#BB0000">Table of Contents:</font></H1 -->
<!-- *** BEGIN toc *** -->
<UL>
<LI> <a HREF="lg_mail.html">The MailBag</A>
<LI> <a HREF="lg_tips.html">More 2-Cent Tips</A>
<LI> <a HREF="lg_answer.html">The Answer Gang</A>
<LI> <a HREF="lg_bytes.html">News Bytes</A>
<LI> <a HREF="alcidi.html">Linux User Caricatures</A> , <EM>by Franck Alcidi</EM>
<LI> <a HREF="fillil.html">Fil & Lil</A> , <EM>by ESC Technologies</EM>
<LI> <a HREF="marinov.html">Taming The Linux Keyboard (My Programming Adventures in Writing a Console Application for Linux)</A> , <EM>by Petar Marinov</EM>
<LI> <a HREF="orr.html">The Foolish Things We Do With Our Computers</A> , <EM>by Mike "Iron" Orr</EM>
<LI> <a HREF="qubism.html">Qubism and HelpDex</A> , <EM>by Jon "Sir Flakey" Harsem and Shane Collinge</EM>
<LI> <a HREF="rogers.html">The Standard C Library for Linux, part 7: String Handling</A> , <EM>by James M Rogers</EM>
<LI> <a HREF="spiel.html">Writing Documentation, Part IV: Texinfo</A> , <EM>by Christoph Spiel</EM>
<LI> <a HREF="vermeer.html">Poetry Requiem</A> , <EM>by Martin Vermeer</EM>
<LI> <a HREF="whitmarsh.html">Implementing a Bridging Firewall</A> , <EM>by David Whitmarsh</EM>
<LI> <a HREF="lg_backpage.html">The Back Page</A>
</UL>
<!-- *** END toc *** -->
<HR NOSHADE>
<!--=================================================================-->
<H3 ALIGN="center"><EM>Linux Gazette</EM> Staff and The Answer Gang</H3>
<BLOCKQUOTE>
<STRONG>Editor:</STRONG> Michael Orr<BR>
<STRONG>Technical Editor:</STRONG> Heather Stern<BR>
<STRONG>Senior Contributing Editor:</STRONG> Jim Dennis<BR>
<STRONG>Contributing Editors:</STRONG>
Ben Okopnik, Dan Wilder, Don Marti
</BLOCKQUOTE>
<HR NOSHADE>
<!--=================================================================-->
<A HREF="issue76.txt.gz">TWDT 1 (gzipped text file)</A><BR>
<A HREF="issue76.html">TWDT 2 (HTML file)</A><BR>
are files containing the entire issue: one in text format, one in HTML.
They are provided
strictly as a way to save the contents as one file for later printing in
the format of your choice;
there is no guarantee of working links in the HTML version.
<HR NOSHADE>
<!--=================================================================-->
<center>
<I>Linux Gazette</I><img alt="[tm]" src="../gx/tm.gif">,
<A HREF="http://www.linuxgazette.com/">http://www.linuxgazette.com/</A><BR>
This page maintained by the Editor of <I>Linux Gazette</I>,
<A HREF="mailto: gazette@ssc.com"> gazette@ssc.com</A>
<P>
<H5>Copyright © 1996-2002 Specialized Systems Consultants, Inc.</H5>
</center>
<HR NOSHADE>
<!--=================================================================-->
<center>
<H1><A NAME="wanted"><IMG ALIGN=MIDDLE ALT="" SRC="../gx/mailbox.gif">
The Mailbag</A></H1> <BR>
<!-- BEGIN wanted -->
</center>
<P> <hr> <P>
<!-- =================================================================== -->
<center><H3><font color="maroon">HELP WANTED : Article Ideas</font></H3></center>
<P>
<P> Send tech-support questions, Tips, answers and article ideas to The Answer Gang
<<A HREF="mailto:linux-questions-only@ssc.com"
>linux-questions-only@ssc.com</A>>. Other mail (including
questions or comments about the <EM>Gazette</EM> itself) should go to
<<A HREF="mailto:gazette@ssc.com">gazette@ssc.com</A>>. All material
sent to either of these addresses will be considered for publication in the
next issue. <EM>Please send answers to the original querent too, so that s/he
can get the answer without waiting for the next issue.</EM>
<P> Unanswered questions might appear here. Questions with
answers--or answers only--appear in The Answer Gang, 2-Cent Tips, or here,
depending on their content. There is no guarantee that questions will
<em>ever</em> be answered, especially if not related to Linux.
<P> <STRONG>Before asking a question, please check the
<A HREF="../lg_faq.html"><I>Linux Gazette</I> FAQ</A> (for questions about the
Gazette) or <A HREF="../tag-kb.html">The Answer Gang Knowledge Base</A> (for
questions about Linux) to see if it has been
answered there.</STRONG>
<P> <HR> <P>
<!--====================================================================-->
<!-- BEGIN HELP WANTED : Article Ideas -->
<UL>
<!-- index_text begins -->
<li><A HREF="#wanted/1"
><strong>LG 73, 2c Tips #12, USB Modems.</strong></a>
<li><A HREF="#wanted/2"
><strong>xt (xtraceroute)</strong></a>
<li><A HREF="#wanted/3"
><strong>Euro symbol available?</strong></a>
<li><A HREF="#wanted/4"
><strong>DHCP & MAC Addresses question</strong></a>
<li><A HREF="#wanted/5"
><strong>Convex</strong></a>
<li><A HREF="#wanted/6"
><strong>Boot problem on software raid</strong></a>
<li><A HREF="#wanted/7"
><strong>System crash on RH 7.2 - could be related to N.P.Strickland's problem</strong></a>
<!-- index_text ends -->
</UL>
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="wanted/1"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">LG 73, 2c Tips #12, USB Modems.</FONT></H3>
Sun, 20 Jan 2002 11:36:35 -0600
<BR>tomkrieger (<a href="mailto:linux-questions-only@ssc.com?cc=tomkrieger@yahoo.com&subject=%20Re%3A%20%5BLG%2076%5D%20help%20wanted%20%231%20USB%20Modems">tomkrieger from yahoo.com</a>)
<P>
I am writing reguarding the Alcatel Speed Touch USB modem, under Linux,
particularly Mandrake Linux 8.1.
</P>
<P>
I have been trying to get this modem to work for about a month now. It
seems I almost have it, at least compared to where I was a couple of
weeks ago. I have been following the HowTo's, I've found on the
internet. They seem to differ slightly from web page to web page, but I
believe I finally got the kernel and the drivers set up to work, but I
think I might have some setting messed up somewhere, or maybe a module
not loaded or something. I was hoping you might be able to help me find
where I'm having a problem. The message I get when I try to connect
with br2684ctl -b -c 0 -a 0.0.35 is something like
</P>
<blockquote><pre>RFC1483/2684 bridge : Created nas0 interface
</pre></blockquote>
<P>
(something like that)
</P>
<blockquote><pre>RFC1483/2684 bridge : Connecting to ATM 0.0.35 Encapsulation LLC
</pre></blockquote>
<P>
(again it says something like this)
</P>
<blockquote><pre>RFC1483/2684 bridge : fatal : failed to connect on socket
</pre></blockquote>
<P>
(here's the error message I get exactly as given to me)
</P>
<P>
Is there anything you might be able to tell me from the informatoin
given, what I should be looking at to correct my problem? If you need
anymore info please let me know what it is and I will get it right to
you.
</P>
<P>
Thanks
<br>Tom
</P>
<!-- end 1 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="wanted/2"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">xt (xtraceroute)</FONT></H3>
Sun, 20 Jan 2002 11:01:32 -0800
<BR>Mike Orr (<a href="mailto:linux-questions-only@ssc.com?cc=rory@ssc.com&subject=%20Re%3A%20%5BLG%2076%5D%20help%20wanted%20%232%20xtraceroute"><i>LG</i> Editor</a>)
<P>
There's a program in <A HREF="http://www.debian.org/">Debian</A> unstable called xt (xtraceroute).
It's supposed to plot the traceroute path on a picture of the
earth. However, it doesn't seem to have enough location
coordinates in its database to do anything. Has anybody used
this program? Did you have to enter your own coordinates for
all the hosts you traceroute from and to?
</P>
<!-- end 2 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="wanted/3"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">Euro symbol available?</FONT></H3>
Sat, 2 Feb 2002 17:05:10 -0000
<BR>Donal Rogers (<a href="mailto:linux-questions-only@ssc.com?cc=rogers@clubi.ie&subject=%20Re%3A%20%5BLG%2076%5D%20help%20wanted%20%233%20Euro">rogers from clubi.ie</a>)
<P>
Hi guys,
I don't know how much this will matter to the non-Europeans in the audience,
but how am I going to get the Euro symbol to appear in my favourite
applications? I have just installed <A HREF="http://www.redhat.com/">Red Hat</A> 7.2 on my laptop, and would like
to indicate my preferred currency symbol in a spreadsheet or word processor
document. The only mention I can find in previous issues of LG (wonderful
publication - keep up the great work!), apart from a <A HREF="http://www.debian.org/">Debian</A> Euro-HOWTO, is
the usual "just my .02 Euro". Does anyone have any ideas?
</P>
<P>
Regards,
<br>Donal.
</P>
<!-- end 3 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="wanted/4"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">DHCP & MAC Addresses question</FONT></H3>
Thu, 7 Feb 2002 13:54:04 -0800
<BR>Dave Wulkan (<a href="mailto:linux-questions-only@ssc.com?cc=dwulkan@earthlink.net&subject=%20Re%3A%20%5BLG%2076%5D%20help%20wanted%20%234%20DHCP">dwulkan from earthlink.net</a>)
<P>
Hi,
</P>
<P>
I've read where DHCP can return a fixed IP for specified MAC hardware
addresses. My question is can DHCP be limited to return either fixed or
dynamic IP to only a list of MAC hardware addresses? This would be a
security enhancement as only specified machines could get access to the
server?
</P>
<P>
Dave Wulkan
</P>
<!-- end 4 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="wanted/5"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">Convex</FONT></H3>
Wed, 6 Feb 2002 02:44:22 +0100
<BR>Robos (<a href="mailto:linux-questions-only@ssc.com?cc=robos@geekmail.de&subject=%20Re%3A%20%5BLG%2076%5D%20help%20wanted%20%235%20Convex">robos from geekmail.de</a>)
<P>
Hi Gang!
Some time ago a friend of mine took me to a guy that - via some
strange ways - had gotten hold of some convex computers (2
refrigerator-sized boxes). They were struggeling to get them to boot
again (I think they called the OS spp-ux os something similar) and
maybe in the end getting them to boot linux (hey, not totally OT). So,
short question: does somebody of you know these beasts? If yes, I can
figure out more about'em, otherwise forget them (saw something like a
VAXbar some time ago, maybe that'll be their new purpose real soon
<IMG SRC="../gx/dennis/smily.gif" ALT=";-)"
height="24" width="20" align="middle">.
</P>
<P>
TIA
<br>Robos
</P>
<!-- end 5 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="wanted/6"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">Boot problem on software raid</FONT></H3>
Thu, 14 Feb 2002 09:17:28 -0500
<BR>Joe St.Clair (<a href="mailto:linux-questions-only@ssc.com?cc=ksimach@ksimachine.com&subject=%20Re%3A%20%5BLG%2076%5D%20help%20wanted%20%236%20software%20raid">ksimach from ksimachine.com</a>)
<P>
I am running RedHat 7.2 and using ext3 file system with software raid,
using 2 20gig drives. The raid drive(s) are my boot drive. The 2
drives are identical and are used something like this <TT>/dev/hda1</TT> = ext3,
<TT>/dev/hdb1</TT> = ext3. I made everything between the 2 drives the same. The
mirrored drive is <TT>/dev/hda1</TT> and <TT>/dev/hda2</TT> = <TT>/dev/md0.</TT> The system has
been running very well.
</P>
<P>
I recently did a kernel upgrade. The upgrade went ok and will boot and
run from a floppy drive with no problems. But if I attempt to boot from
the hard drive(s) drive it will only boot the old kernel. I have
updated the grub.conf and have even attempted to enter the commands for
booting from the command line. The grub menu never shows the commands
entered into the grub.conf file and I receive a error "Can't find files"
if I attempt to enter the command line.
</P>
<P>
I have attempted to find what I need to change/fix but have not found
the information needed to update grub while booting from a raid/ext3
file system.
</P>
<P>
Anyone have any ideas?
</P>
<P>
Thanks,
<br>Joseph St.Clair
</P>
<!-- end 6 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="wanted/7"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">System crash on RH 7.2 - could be related to N.P.Strickland's problem</FONT></H3>
Tue, 29 Jan 2002 14:10:15 +1100
<BR>icalla (<a href="mailto:linux-questions-only@ssc.com?cc=icalla@bigpond.net.au&subject=%20Re%3A%20%5BLG%2076%5D%20help%20wanted%20%237%20lockups%20after%20upgrade">icalla from bigpond.net.au</a>)
<P>
Hi Gang,
</P>
<P>
I recently upgraded from RedHat 6.2 to 7.2. Since then I have
experienced a number of incidents where the system simply froze up
solid. It would not respond to keyboard input or mouse clicks. Screen
was not being updated at all. The only way out was the Reset button.
This sounds similar to the problems reported by N.P.Strickland
(<A HREF="../issue74/tag/9.html"
>http://www.linuxgazette.com/issue74/tag/9.html</A>), but I can relate my
incidents to some things which infer that the solutions suggested to
that post will not resolve my situation.
</P>
<P>
Firstly, this has only started happening since I upgraded. I never
experienced anything similar on RH 6.2 (or 5.2 fot that matter). The
hardware is unchanged, so I believe it must be caused by software, not
hardware.
</P>
<P>
Secondly, I am pretty confident that it is related somehow to sound. I
can bring on a freeze by running a number of multimedia programs (e.g.
XMMS, gtv). They appear to work fine for, say, 30 seconds, then Zap! the
system freezes up solid.
</P>
<P>
Can anyone shed any more light?
</P>
<P>
Thanks
<br>Ian Callahan
</P>
<!-- end 7 -->
<a name="mailbag"></a>
<P> <hr> <P>
<!-- =================================================================== -->
<center><H3><font color="maroon">GENERAL MAIL</font></H3></center>
<P> <HR> <P>
<!--====================================================================-->
<!-- BEGIN GENERAL MAIL -->
<UL>
<!-- index_text begins -->
<li><A HREF="#mailbag/1"
><strong>Windows Telnet Client for Linux</strong></a>
<li><A HREF="#mailbag/2"
><strong>installing software from source</strong></a>
<!-- index_text ends -->
</UL>
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="mailbag/1"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">Windows Telnet Client for Linux</FONT></H3>
Wed, 23 Jan 2002 14:49:23 -0800
<BR>Mike Orr (<a href="mailto:gazette@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%20mailbag%20%231%20cybercoffee%20shop"><i>LG</i> Editor</a>)
<br>replying to Jay Ashworth (The Answer Gang)
<P><STRONG><FONT COLOR="#000066"><EM>
Not if you're at the only cybercafe in town and they don't let you
install software there,
</EM></FONT></STRONG></P>
<P><STRONG>
Educate, advocate.
</STRONG></P>
<P>
The only reason I'd be in a cybercafe is if I'm in a strange town and there
are no other Internet options. So I don't have much opportunity to find the
most receptive staff members and spring a World Domination campaign on them.
</P>
<P><STRONG>
There <EM>has</EM> to be at least one geek there...
</STRONG></P>
<P>
You must have forgotten the smiley.
<IMG SRC="../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle"> That must be a joke, because in most
of the cybercafes I've been in, the staff know a lot about espresso and chai,
but very little about their own computers. The only two exceptions were the
Speakeasy in Seattle and CoffeeNet in San Francisco, neither of which
exist any more.
</P>
<!-- end 1 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="mailbag/2"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">installing software from source</FONT></H3>
Tue, 29 Jan 2002 22:01:01 -0500
<BR>Adam York (<a href="mailto:gazette@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%20mailbag%20%232%20make%20install">Anonymous</a>)
<P>
Ben,
</P>
<P>
Since I'm a relative linux newbie and software installation has been
learning process, I appreciatee your article on installing from source.
One question though. After downloading and uncompressing the source,
installation seems to be pretty much a three step process.
</P>
<Pre>
./configure
make
make install
</Pre>
<P>
My question is this: should I become root in this process and if so at
what stage? I'm thinking that I should become root after "make." and
not before.
</P>
<P>
Anyway I appreciated the article especially the part about analyzing a
failed install. It would have taken me a while to figure that out on my
own.
</P>
<P>
Thanks,
<br>Adam York
</P>
<!-- end 2 -->
<a name="gaz"></a>
<P> <hr> <P>
<!-- =================================================================== -->
<center><H3><font color="maroon">GAZETTE MATTERS</font></H3></center>
<P> <HR> <P>
<!--====================================================================-->
<!-- BEGIN GAZETTE MATTERS -->
<UL>
<!-- index_text begins -->
<li><A HREF="#gaz/1"
><strong>TAG members</strong></a>
<li><A HREF="#gaz/2"
><strong>Confidential disclaimers</strong></a>
<li><A HREF="#gaz/3"
><strong>HOWTO subscribe to <i>Linux Gazette</i></strong></a>
<li><A HREF="#gaz/4"
><strong>All your wonderful tips...</strong></a>
<li><A HREF="#gaz/5"
></a>feedback --or--
<br><A HREF="#gaz/5"
><strong>Why we stay plain when we could look Really Cool</strong></a>
<!-- index_text ends -->
</UL>
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="gaz/1"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">TAG members</FONT></H3>
Wed, 20 Feb 2002 14:26:40 -0800
<BR>Mike Orr (<a href="mailto:gazette@ssc.com?subject=%20Re%3A%20%5BLG%2075%5D%20gazette%20matters%20%231%20welcome%20gang"><i>LG</i> Editor</a>)
<BR>linux-questions-only (linux-questions-only@ssc.com)
<P>
By the way, TAG now has thirty members, an increase of about eight from a couple
months ago. Welcome, new Gang members, and thanks for your contributions.
</P>
<P>
If you haven't sent in your TAG bio yet or you need to revise it, send it to
<A HREF="mailto:gazette@ssc.com"
>gazette@ssc.com</A>. See
</P>
<P><a href="tag/bios.html">"Meet The Answer Gang"</a>
to read about your peers and see some example bios.
</P>
<BLOCKQUOTE><EM>
[28-Feb: Somehow it doubled in eight days. There are now
sixty TAG members. -Iron.]
</EM></BLOCKQUOTE>
<!-- end 1 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="gaz/2"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">Confidential disclaimers</FONT></H3>
Fri, 25 Jan 2002 10:56:08 -0800
<BR>Mike Orr (<a href="mailto:gazette@ssc.com?subject=%20Re%3A%20%5BLG%2075%5D%20gazette%20matters%20%232"><i>LG</i> Editor</a>)
<P><STRONG>
In the section on confidentiality disclaimers in the TAG faq, can
we provide some examples of what we need the querent to say?
</STRONG></P>
<P>
Provided, in
<a href="tag/ask-the-gang.html#privacy">"Ask The Gang"</a> -- Heather
</P>
<!-- end 2 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="gaz/3"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">HOWTO subscribe to <em>Linux Gazette</em></FONT></H3>
Sun, 20 Jan 2002 09:20:05 -0800
<BR>multiple readers (<a href="mailto:gazette@ssc.com?subject=%20Re%3A%20%5BLG%2075%5D%20gazette%20matters%20%233%20subscribe">shown below</a>)
<P>
We've had a number of questions on this topic lately...
</P>
<!-- sig -->
<p><em>D Johnson</em></p>
<P><STRONG>
I always enjoy reading the Gazette offline (maybe even at the beach on my
notebook). Have you ever considered providing it in pdf format. Would save
me the trouble of converting it myself. Imagine lotsa others do too.
Keep up the good work.
</STRONG></P>
<blockquote><font color="#001F3F">Thanks for the support.
-- Mike</font></blockquote>
<HR width="10%" align="center">
<!-- sig -->
<p><em>P Reddy</em></p>
<P><STRONG>
i am a student from india , i want to know wether there is a mailing news
letter available, if yes how to subscribe.
please reply at...
</STRONG></P>
<HR width="10%" align="center">
<!-- sig -->
<p><em>Martin Willem</em></p>
<P><STRONG>
I'm making the jump into the linux world. Do you offer the GAZETTE in hard
copy form?
</STRONG></P>
<HR width="10%" align="center">
<blockquote><font color="#000066">To all these people and everyone else out there wondering: ...
</font></blockquote>
<P><DL><DT>
There is no subscription. Read it online:
<DD><A HREF=".."
>http://www.linuxgazette.com</A>
</DL></P>
<P>
Paper?
</P>
<blockquote>
It's under an open license. Anybody has the right to publish
it that way. <EM>We</EM> can't afford to do all that for free though.
</blockquote>
<blockquote>
If anybody chooses to convert it to paper form <EM>regularly</EM> ...
and maintain that as a longterm service ... could you please
let us know? We could add you to the Mirrors page
<IMG SRC="../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
</blockquote>
<P>
Other electronic formats?
See <A HREF="../faq.html#formats_no"
>http://www.linuxgazette.com/faq.html#formats_no</A>
</P>
<blockquote>
You can be <EM>notified</EM> that the new one has been posted each month, by
subscribing to the announce list (it does <EM>not</EM> contain the articles):
<A HREF="http://www.ssc.com/mailman/listinfo/lg-announce"
>http://www.ssc.com/mailman/listinfo/lg-announce</A>
</blockquote>
<blockquote>
You might be able to use services (elsewhere!) which let you know websites
have changed (by emailing you the changed page) to give you the table of
contents ONLY, by telling them to keep an eye on:
<A HREF="../current/"
>http://www.linuxgazette.com/current/</A>
</blockquote>
<blockquote>
One example of such an external service is Sitescooper - PDA users can get
the document this way, as can others who install the Sitescooper scripts:
<A HREF="http://scoops.sitescooper.org"
>http://scoops.sitescooper.org</A>
</blockquote>
<p>So much work to get it so I was hoping...</p>
<blockquote>
Our webzine is quite large so it's well worth your time to find an <EM>LG</EM>
mirror site that's closer to your home in cyberspace:
<A HREF="../mirrors.html"
>http://www.linuxgazette.com/mirrors.html</A>
</blockquote>
<blockquote>
You can also download the FTP files, or find it in the <A HREF="http://www.debian.org/">Debian</A> distribution.
Read more about all this at the Linux Gazette FAQ:
<A HREF="../faq.html"
>http://www.linuxgazette.com/faq.html</A>
</blockquote>
<HR width="10%" align="center">
<blockquote><font color="#000066">However Martin had more to ask so we
answered that too
<IMG SRC="../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
-- Heather</font></blockquote>
<P><STRONG>
Do you offer recommendations on the most successful ways to jump
from microsoft to LINUX? Any help that can save me pain would be greatly
appreciated i.e. hardware, linux flavor, good books for the beginner to read
before/during the move to lynux!
</STRONG></P>
<P>
That's a very general question, so I can offer only a general answer.
Look in The Answer Gang Knowledge Base:
<A HREF="../lg-kb.html"
>http://www.linuxgazette.com/lg-kb.html</A>
especially under the sections "Linux Distributions", "Before you install Linux",
"Installing Linux", etc. Also see the section "Linux tech support questions"
question "How can I get help on Linux?", which has a list of books and a link
to the <A HREF="http://www.linuxdoc.org/">Linux Documentation Project</A> (LDP) (Linux Documentation Project), which should be your first stop.
</P>
<P>
-- Mike
</P>
<!-- end 3 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="gaz/4"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">All your wonderful tips...</FONT></H3>
Sun, 23 Dec 2001 00:57:55 -0500
<BR>Robos (<a href="mailto:gazette@ssc.com?subject=%20Re%3A%20%5BLG%2075%5D%20gazette%20matters%20%234">robos from muon.de</a>)
<!-- sig -->
<P><STRONG>
Hi Gang!
Just had some time and took a look into the howto section at
linuxdoc.org and found the Tips-HOWTO.
</STRONG></P>
<P><STRONG>
Nice thingies in there, although the last editing seems to be ages
ago.
</STRONG></P>
<P><STRONG>
Soooo, since LG is already present in there and you have such
wonderful ideas, scripts and perl-thingies (Ben?), after you have
discussed them here in the list and optimized them one could post it
to the maintainer of the Tips-HOWTO for inclusion.
</STRONG></P>
<P><STRONG>
What do you think? Thats a place a newbie finds rather easier than
this mailing-list, don't you think?
Just a suggestion.
</STRONG></P>
<P><STRONG>
CU Robos
</STRONG></P>
<P>
<grin> Good idea, Robos. Instead of the Tips-HOWTO, however, the areas
you're asking about are a subset of the LG Knowledge Base that
Chris Gianakopoulos and I have been working on for the past month plus;
see <<A HREF="../kb-faq.html>"
>http://www.linuxgazette.com/kb-faq.html></A>;. Better yet, wait
a week or
so and see the new version - Chris has been doing a sterling job of adding
the stuff from the previous issues of LG while I'm banging away on
modifying the overall KB-FAQ, TAG-FAQ, etc. The difference between the last
month and the one that's coming up is going to be a large one - there are
many, many more articles/issues incorporated into it than there were the
last time - and it's really turning into a great resource. -- Ben
</P>
<!-- end 4 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="gaz/5"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/envelope.gif">
<FONT COLOR="navy">Why we stay plain when we could look Really Cool</FONT></H3>
Fri, 18 Jan 2002 15:21:53 +1100
<BR>Leon Czechowicz (<a href="mailto:gazette@ssc.com?subject=%20Re%3A%20%5BLG%2075%5D%20gazette%20matters%20%235">Leon.Czechowicz from anu.edu.au</a>)
<!-- sig -->
<!-- ::
Why we stay plain when we could look Really Cool
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:: -->
<P>
Hey!
</P>
<P>
Nice to see your online mag - content seems good!
</P>
<P>
...pity I was about as excited about the presentation of your "mag" as I
am about brussel sprouts!
</P>
<P>
Check out <A HREF="http://www.onlamp.com"
>http://www.onlamp.com</A> for an example of what to make it look
like - I know in essence its the same, but I'd love to see some Linux
heads make something that actually looks good! (ie stop acting like
text crazed command line geeks and get with us poxy graphical idiots,
who have been web building with Macromedia products and the like)
</P>
<P>
Yes that means you will actually have to stop using Lynx and start using
Mozilla to check the visual integrity of your code!
</P>
<P>
I'm not really bagging, just sick of not being excited when I hit a
linux site.
</P>
<P>
cheers,
L
</P>
<blockquote><font color="#000066">Oh my. This resulted in a lively discussion defending
<a href="#brussel">Brussel sprouts</a>,
our decision process in making the webzine
<a href="#style">rather more plain than all-dancing-and-glitzy</a>,
some comments about
<a href="#check">the browsers we actually use</a>,
thoughts on
<a href="#flash">Macromedia Flash</a>,
a certain amount of
<a href="#grump">curmudgeonly eyebrow raising</a>,
cheerful
<a href="#thanks">thanks</a>
for the kudos that were present, and
<a href="#goforit">encouragement</a>
to take on the glitzy task himself. Pleasantly he took it
<a href="#goodsport">all in good stride</a>
and will probably join the Answer Gang
<IMG SRC="../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
-- Heather</font></blockquote>
<HR width="10%" align="center">
<h4><a name="thanks">KUDOS</a>
</h4>
<P><STRONG>
Nice to see your online mag - content seems good!
</STRONG></P>
<blockquote><font color="#000066">Thanks, always happy to hear it.
-- Heather</font></blockquote>
<blockquote><font color="#001F3F">Thanks for writing in. If you like the content, well, that's our goal.
-- Mike</font></blockquote>
<HR width="10%" align="center">
<h4>
<a name="brussel"
>BRUSSEL SPROUTS</a>
</h4>
<P><STRONG>
...pity I was about as excited about the presentation of your "mag" as I
am about brussel sprouts!
</STRONG></P>
<blockquote><font color="#000066">I <EM>like</EM> brussel sprouts, when prepared properly and covered with butter
<IMG SRC="../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
Oh, you mean the boiled-grey kind, perhaps ...
-- Heather</font></blockquote>
<blockquote><font color="#001F3F">I can force myself to eat brussel sprouts and broccoli. But I
draw the line at cauliflower.
-- Mike</font></blockquote>
<blockquote><font color="#1F1F1F">I'll trade you: you can have my brussel sprouts, and I'll have the
cauliflower. It's good to have friends.
<IMG SRC="../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
-- Ben</font></blockquote>
<HR width="10%" align="center">
<h4>
<a name="grump"
>CURMUDGEONS, THAT'S US</a>
</h4>
<P><STRONG>
...pity I was about as excited about the presentation of your "mag" as I
am about brussel sprouts!
</STRONG></P>
<font color="#003F00">
<blockquote>
The Answer Guy, enjoying yet another
Python book (in this case New Riders' "Python Web Programming" -- slow since
it aims at non-programmers, but quite good nontheless) at a local coffee shop,
was heard to mutter:
</blockquote>
<blockquote><blockquote>"Bon Apetit mon ami, enjoy your sprouts"
</blockquote></blockquote>
<blockquote>before taking another sip of his latte. -- Jim</blockquote>
</font>
<blockquote><font color="#1F1F1F">Hey, nice layout on your e-mail!
</font></blockquote>
<blockquote><font color="#1F1F1F">...too bad the content had me yawning.
</font></blockquote>
<blockquote><font color="#1F1F1F">So you've got your MacroWhozits, ShockWhatsits, and RealWhatchamacallits
running. Booo-ring. I can get more and better flash and glitter at the
99-cent store. Incidentally, I find the layout of the site that you've
mentioned just as garbaged up as that of Slashdot - it requires a 21"
screen just to see properly, and the "noisiness" of unrelated multi-column
layout, with 2-3 words per column (hey, you've got to make room for all
those ads - right?) is something that I find really unpleasant to read.
</font></blockquote>
<blockquote><font color="#1F1F1F">Look. Our strength is that we are accessible to _everyone._ Not everybody
in the world has a cable modem, or even a fast phone connection; a number
of our readers are still using 33.6 modems attached to their 486s, and a
fair number of them are still paying for content "by the byte". I'm using a
CDPD modem (I live on a sailboat) to connect, myself. Should we all be
denied access, or should it be made more difficult or expensive because our
layout doesn't reflect somebody's idea of the Latest And Greatest fashion
in web pages? Please, let's not even go there.
-- Ben</font></blockquote>
<P><STRONG>
I'm not really bagging, just sick of not being excited when I hit a
linux site.
</STRONG></P>
<blockquote><font color="#1F1F1F"><snort> I'll make you a deal: we'll tell you how to dress and how to
present yourself in general (anybody here have some orange lipstick and a
flourescent pink purse?), and you'll be welcome to present us with your
idea of an "up-to-date" site that excites you. That sound good to you?
</font></blockquote>
<blockquote><font color="#1F1F1F">Thought so.
-- Ben</font></blockquote>
<HR width="10%" align="center">
<h4>
<a name="style"
>ALL GLITZ, WE'RE NOT</a>
</h4>
<P><STRONG>
Check out <A HREF="http://www.onlamp.com"
>http://www.onlamp.com</A> for an example of what to make it look
like -
</STRONG></P>
<blockquote><font color="#001F3F">It looks nice.
-- Mike</font></blockquote>
<blockquote><font color="#000066">(For the readers: ONlamp is an O'Reilly Network site.)
</font></blockquote>
<blockquote><font color="#000066">Are you <EM>with</EM> O'Reilly? They are a big publishing house and hire people
to maintain their websites. We are a batch of volunteers scattered all
over the world. But we're flattered that you chose to compare us with them.
</font></blockquote>
<blockquote><font color="#000066">(it turns out, no, he's not; he just feels their site looks cool.)
</font></blockquote>
<blockquote><font color="#000066">To be fair, though, I tried to visit that site with Netscape. I only got
an ad -- no content! Ouchie!
</font></blockquote>
<blockquote><font color="#000066">Luckily we only put these itty bitty graphics at the side and logos on top.
Since we don't do animated banners you can't get hit with the won't-finish
bug in some browsers either
<IMG SRC="../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
-- Heather</font></blockquote>
<P><STRONG>
I know in essence its the same, but I'd love to see some Linux
heads make something that actually looks good!
</STRONG></P>
<blockquote><font color="#001F3F">Go to
<a href="http://www.linux.com/">linux.com</a>. Or better yet,
put up your own demonstration site. Then
send us a link to it and an announcement about what it contains, and we'll
put an item for it in News Bytes. Maybe all that will encourage other Linux
sites to get more pizzazz.
-- Mike</font></blockquote>
<P><STRONG>
(ie stop acting like text crazed command line geeks and get with us poxy
graphical idiots, who have been web building with Macromedia products and the
like)
</STRONG></P>
<blockquote><font color="#001F3F">Linux Gazette is slow to adopt new visual technology, kind of like the Amish.
We prefer to wait a few years and see which technologies would actually be a
long-term benefit to all our users. It's an unusual kind of zine; I don't know
of any others like it. Most people read it from mirrors in 47 countries,
through the Linux Documentation Project, download the FTP files, read it on a
CD-ROM, download the articles to their palm pilot, etc.
So anything dynamic is out because it would cut off a significant portion of
the readership. We also don't want to impose any special software requirements
on the mirrors. Two concessions to dynamism: the search engine and talkbacks
on the main site.
</font></blockquote>
<blockquote><font color="#001F3F">We're also mindful of bandwidth restraints: many readers and mirrors live in
countries where they pay by the minute for Internet access, so I try to keep
each issue down to less than a megabyte or two (compressed).
</font></blockquote>
<blockquote><font color="#001F3F">We also have to piece together the whole thing into an all-in-one version (the
entire issue on one page), because that's how LG started and many readers prefer
to print it that way. This rules out differing stylesheets per article, or
anything special the article needs in the HTML header.
</font></blockquote>
<blockquote><font color="#001F3F">Most of the editors subscribe to the "good website design" philosophy, meaning
content is king. If you can't say it in text, it isn't worth saying. Obviously
we don't go all the way on that, because we have been publishing several cartoon
series. But still, all decorations are evaluated in terms of how essential they
are to the content. If readers like the text, they'll be back. if they won't
read it unless it has bells and whistles all around it, well, we don't want them
anyway. There are plenty of sites that are highly graphical (and can't be
navigated unless you have Flash and Javascript enabled), and LG doesn't wish to
compete in that department.
</font></blockquote>
<blockquote><font color="#001F3F">By the way, Your Editor has a strong adversion to "left column" and
"right column" sidebars (tables), and will resist them as long as he can.
Let the article text flow freely across the entire width of the browser,
outside a table, and in the default font. Persumably, the reader has
adjusted his default font to his preference.
-- Mike</font></blockquote>
<blockquote><font color="#1F1F1F">A-men to that! And a-women, too. I don't long for uniformity on the Web,
but if more people paid attention to those basics, more information would
be more easily accessible. Sing that song!
-- Ben</font></blockquote>
<blockquote><font color="#000066">Not to rag too hard back, but:
<ol>
<li> Tell O'Reilly to get that wart zapped. The last time I saw this
was LWN having some problems with an ad provider whose "pull
through" would bomb out that way about 1 time in 10. I'm not
sure if they fired the ad provider, or just made 'em fix it,
but I know it's tricky to chase down problems that are hard to
reproduce.
<li> We can't shoot at bugs without a target symbol over the varmint.
In other words "it's ugly" isn't enough of a problem description.
Try again.
</ol>
</font></blockquote>
<blockquote><font color="#000066">Since we live in a world of choice, try a few of the following on for size:
Dillo, Chimera, Amaya, Opera, Arachne, links (not the same as lynx), w3m,
Browsex, ViewML, mnemonic, Zen, konqueror. If you find a copy of Grail
let me know as its homesite died ages ago and I haven't found packages since.
Maybe it was under a non-free license??
-- Heather</font></blockquote>
<blockquote><font color="#001F3F">Grail (a Python web browser) is now at
<A HREF="http://grail.sourceforge.net"
>http://grail.sourceforge.net</A> . The
last version was April 1999. It died because its sponsoring organization
(CNRI?) stopped putting developer resources into it. They did that because
they realized its features and speed were never going to compete with recent
versions of Netscape and Internet Explorer.
</font></blockquote>
<blockquote><font color="#001F3F">With Grail died the ability to run Python applets in a browser, but that's OK
because there never were any Python applets except a few demos. But now there's
Jython, which is an implementation of Python in Java, so you can do almost the
same thing.
</font></blockquote>
<blockquote><font color="#001F3F">However, there was a good thing from the Grail legacy. The parts to build a
browser, parse URLs, parse HTML files, etc, and everything else a browser needs
to do, got put in the standard Python distribution as modules, so you can use
them in other programs.
-- Mike</font></blockquote>
<blockquote><font color="#000066">Visit some students at your local
blind school, ask them if their speech readers do our site alright... and
have your local PDA pick up the current Linux Gazette packet from Sitescooper.
I'm <EM>not</EM> going to suggest that you telnet to port 80 and handle your own
client side of the HTTP connection, but you can do that if it makes you
feel like a completist :D
</font></blockquote>
<blockquote><font color="#000066">We try not to change the templates too often
<IMG SRC="../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
</font></blockquote>
<blockquote><font color="#000066">Variety may be the spice of life but aiming generic rather than in any one
direction means less work to have readable results without heavy testing.
(We <EM>do</EM> try to test for broken hotlinks, and sorta glance around for typos,
but those sometimes escape us too.) As we're all unpaid volunteers, and not
very many of us, making the best use of our time is important too.
</font></blockquote>
<blockquote><font color="#000066">We're modeled more after the community green sheet (e.g. Campbell Reporter
gets a picture here and there, but mostly it's plain ink on rag paper)
than a large city newspaper (with its Home and Garden section, coupons in
the food section, comics section bigger than some articles, classified ads
fatter than all other sections but the sports, etc) or a 90 page glossy
magazine on clay-laden paper with dye sublimation ink. On the flip side
we don't charge $7.95 on newsstands and have a two to three month lead time
for articles, either.
</font></blockquote>
<blockquote><font color="#000066">There's a great little article at "This website optimized for --- arguing
with customers" (<A HREF="http://www.htmlhelp.com/feature/art2.htm"
>http://www.htmlhelp.com/feature/art2.htm</A>). Like it says,
we're not going to tell people to get rid of whatever they already have just
to read anything here.
-- Heather</font></blockquote>
<blockquote><font color="#001F3F">OnRamp gets brownie points
for using the default font in the center column, but loses points for having
the left sidebar. At least the center column isn't too narrow. And at
least--thankfully--they don't split the articles into pages, unlike, say,
Salon (<A HREF="http://salon.com"
>http://salon.com</A>), where you have to wait for a download cycle
between each page.
-- Mike</font></blockquote>
<HR width="10%" align="center">
<h4>
<a name="check"
>JUST CHECKING...</a>
</h4>
<P><STRONG>
Yes that means you will actually have to stop using Lynx and start using
Mozilla to check the visual integrity of your code!
</STRONG></P>
<blockquote><font color="#001F3F">Actually, I do most of my work in Netscape 4. I occasionally use
Konqueror 2.2.1 for comparision, but I get sick of the 3-5 seconds of
extra overhead on every
click. At home I use Galeon. For local documentation or when I'm going to a
known-text page, I use links, or lynx if it requires https:. I don't know what
the other editors use.
-- Mike</font></blockquote>
<blockquote><font color="#000066">Funny you should mention that, I was able to read your site with lynx
when Netscape failed abysmally -- since noting yourself as a GUI fan, I
figured to hit it with a graphical browser first...
</font></blockquote>
<blockquote><font color="#000066">My <EM>portion</EM> of the Gazette is always checked with both lynx (2.8.3dev9 with
SSL patches, yeah I know it's ancient, but I'm happy with my color settings)
and netscape (4.77 normally). They each correct for different varieties of
HTML misbehavior, and that allows me to fix glitches generated by my
preprocessing script, which tortures about 400 slices of mail into something
resembling pieces of a webzine. I <EM>sometimes</EM> test with konqueror, NS6,
or Browsex. We've been advised that Opera's rendering of the Front Page
only (ironically, the only one where we tried to get fancy with layout)
is a mite strange... of course, that's commercial software, and the effect
doesn't really stop reading, but we dunno any way to convince it to do
the table-heuristic we wanted. Oh well.
-- Heather</font></blockquote>
<blockquote><font color="#001F3F">That vertical black line is gone. It was a 1-pixel black .gif inside a table
cell, which was supposed to expand into a vertical black bar. However, it
used WIDTH="2%", which made it stretch wide on some browsers. So I changed it
to a fixed width. However, Opera continued to expand it while the other
browsers stopped. Now it's gone. Good riddance.
-- Mike</font></blockquote>
<blockquote><font color="#000066">What version of Mozilla are you using, what bug/wart did you encounter,
and does it also afflict Netscape 6, Galeon, or other mozilla derivatives?
-- Heather</font></blockquote>
<blockquote><font color="#1F1F1F">Argh. Leon, could you send your stuff in plain text, and wrap
it at less than 80 (preferably, around 72) columns? That's
considered good e-mail manners.
-- Ben</font></blockquote>
<P><STRONG>
Argh indeed - I am forced by the hand of Bill Gates - my headers will
inform you my work machine is a W2K with Outlook - I couldn't be polite
with my text if I tried. As far as it's concerned I AM sending plain
text!!!!!!!! I am moving jobs soon, but staying on the same campus - I
will then rebel and use Linux for my desktop....AND BILL WILL
WEEP!!!!!!!!!!!! (HeeHeeHeeee...)
</STRONG></P>
<P>
Seems like there's a way to tell even Outlook to be civil, at least
in this respect.
</P>
<P>
Unfortunately this way eludes me ... could somebody here more versed
than I in the Dark Arts speak up?
-- Dan
</P>
<blockquote><font color="#1F1F1F"><laugh> Cool. Mike Orr, our editor here, has mentioned that we have the
procedure for smacking Outlook down to decent behavior written down
somewhere;
-- Ben</font></blockquote>
<P>
Chris G here, from the Dark Arts group of people. I supplied detailed
instructions on how to set up Outlook Express to send in plain text mode
when sending email. In it was included the fact that the MUA should not
reply in the same format as the original message. That was in issue 65,
"Setup of Microsoft Outlook Express 5 for Sending of Clear Text":
<A HREF="../issue65/tag/8.html"
>http://www.linuxgazette.com/issue65/tag/8.html</A>
</P>
<P>
Hopefully, that will work for Leon.
-- Chris G
</P>
<blockquote><font color="#1F1F1F">
A friend of
mine sent me the following step-by-step guide (he works in a mixed
environment, and needs to twiddle his settings back and forth):
</font></blockquote>
<TABLE WIDTH="95%" BORDER="1" BGCOLOR="#FFFFCC"><TR><TD>
<p align="center">...............</p>
<P>
How to send plain text email using Outlook in 3 clicks or less
By Samuel Kopel
</P>
<P>
This will work in Outlook(not sure about express)
</P>
<P>
Start a new message
</P>
<P>
On the menu bar select 'Format/Plain Text'
</P>
<P>
Click [YES] to the message "Warning: Changing the formatting of this
message from HTML to plain text requires removing all the current
formatting, including any pictures you may have included. Are you sure you
want to do this?"
</P>
<P>
If you want to change your default to text (recommended if the majority of
your email does not go to other Outlook users) you need to change the
options settings.
</P>
<P>
From the menu:
'Tools/Options'
Select the [Mail Format] tab and change to "plain text"
</P><p align="center">...............</p>
</TD></TR></TABLE>
<HR width="10%" align="center">
<h4>
<a name="flash"
>MACROMEDIA FLASH</a>
</h4>
<P>
Macromedia Flash, Javascript and fancy graphics would be possible since
they are self-contained (i.e., don't require particular software on the
web server). However, they would have problems on non-major browsers,
and LG readers have a wide variety of browsers, and are more likely
than the general public to run experimental browsers on principle.
Also, some readers have older computers, and buying a new computer would
cost several months' salary. Last year I got a letter from a reader in
Africa asking if there is an e-mail version of LG (there isn't),
because his school cannot afford to read it on the web.
--Mike
</P>
<blockquote><font color="#000066">Macromedia Shockwave isn't readable on Linux (unless something new has
happened that I don't know about). Flash is ok but broken in some
contexts, unusable entirely in others, and we don't want the site unusable
to anyone. There are so many versions of Javascript nee' ECMAscript I
stopped counting -- and Java is getting there. People read us worldwide
including on PDAs and in libaries and coffee shops. (ok, the coffee shops
probably can handle the cool stuff. We've gotten lots of questions about
coffee shops running Linux.) Also on "that slow old thing" and a cheap
dialup link while preparing the spiffy new box to run Linux. (Even though
they <EM>can</EM> render the graphics, maybe it's so bad they even turn off image
loading in the GUI.) Etc.
-- Heather</font></blockquote>
<blockquote><font color="#001F3F">I forgot to mention. If you have a small Flash movie on a Linux theme, we
may be able to put it in as an article. Or if you'd like to write an article
about building Flash movies on Linux or something like that, we could also
publish it.
-- Mike</font></blockquote>
<HR width="10%" align="center">
<h4>
<a name="goforit"
>YOU CAN DO IT</a>
</h4>
<P><STRONG>
I'm not really bagging, just sick of not being excited when I hit a
linux site.
</STRONG></P>
<blockquote><font color="#001F3F">Linux is a do-it-yourself thing. Go forth and build the ultimate
Linux web site.
-- Mike</font></blockquote>
<blockquote><font color="#000066">Feel free to actually do a cool new layout
and have that be the format
for your new mirror of us. We'd happily list you in our mirrors database,
and publish the script you use to tweak it if you like, so other mirrors
can do things your way too. Sharing resources is good.
</font></blockquote>
<blockquote><font color="#000066">That's the beauty of stuff under free
licenses ... you can tweak your
copy and you aren't breaking any laws whatsoever.
</font></blockquote>
<blockquote><font color="#000066">If you have good tricks for having your
GUI cake
and eating text too, it'd make an excellent article for the Gazette (a linux
focus in it would put it on topic), and Mike Orr
(<A HREF="mailto:gazette@ssc.com"
>gazette@ssc.com</A>) would be
glad to accept your submission. If <EM>that</EM> excites you about us, read our
author guidelines in the Linux Gazette FAQ, and we look forward to seeing it!
-- Heather</font></blockquote>
<P><STRONG>
cheers,
L
</STRONG></P>
<blockquote><font color="#000066">Have a good weekend, hope your Linux is being more fun than our layout for ya.
-- Heather</font></blockquote>
<HR width="10%" align="center">
<h4>
<a name="goodsport"
>ALL IN GOOD STRIDE</a>
</h4>
<P><STRONG>
Ben,
</STRONG></P>
<P><STRONG>
Don't take it so personal - the Editor explained everything very nicely,
I'm sorry if I offended - I am a graphical ponse, it's not my fault I
was born that way!!!!!!!
</STRONG></P>
<P><STRONG>
L
</STRONG></P>
<blockquote><font color="#1F1F1F"><grin> No worries, Leon - you didn't offend me. I got a little grumpy at
you telling us how we've got to do something without knowing our
requirements, but that's all; no offense involved.
</font></blockquote>
<blockquote><font color="#1F1F1F">For myself, I like graphical stuff when done in appropriate amounts
relevant to the material at hand. Today, there are <EM>way</EM> too many web pages
that use graphics gratuitously, without any sense behind them - and I must
say that the page you pointed to does not fit that category, although it
has other problems (at least from my perspective.)
</font></blockquote>
<blockquote><font color="#1F1F1F">So, here's an idea for you; an opportunity to possibly convert a few folks
into "graphical ponses", if you will. Go with what Mike suggested: write an
article about Web page design; include some links to demonstrate each of
your points. Who knows?... it might become a graphical ponse revolution.
<IMG SRC="../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
-- Ben</font></blockquote>
<HR width="10%" align="center"><P><STRONG>
Heather,
</STRONG></P>
<P><STRONG>
You write too much - I can't even type that fast and you want me to read
all that!????
</STRONG></P>
<P><STRONG>
As I said I like the content - I'm sold an that - I also said I'm new to
Linux, thus may only be bagging what I don't understand....yet!
</STRONG></P>
<P><STRONG>
All points on bandwidth, mirroring etc etc are taken - OK!!!!!
</STRONG></P>
<P><STRONG>
I still hate Brussel sprouts with butter - I'd rather eat the tub of
butter.
</STRONG></P>
<P><STRONG>
Geez, I know not now to stir whith what ain't broken....
</STRONG></P>
<P><STRONG>
Oh and to clarify - I Certainly Don't Work For O'Reilly!! (And I'm not
such a fan of Flash myself - but don't tell my boss!)
</STRONG></P>
<P><STRONG>
I am glad to have stimulated some conversation though
</STRONG></P>
<HR width="10%" align="center"><P><STRONG>
Mike,
</STRONG></P>
<P><STRONG>
Thanks for an in depth reply : This shows me your commitment to uphold
all that is good and right in the computing world, and your reasons for
doing it. Good on ya! - I can take much of what you have said about the
web and put it into practice - thanks - all points noted.
</STRONG></P>
<P><STRONG>
I am pleased that you did in fact reply - you would be surprised how
many people would take a comment like my and ignore it - so thanks
again.
</STRONG></P>
<P><STRONG>
I am what your world would call a Linux Newbie so your feedback and
explanations are essential to my development, and I suspect yours. I am
looking forward to building new sites, I do have some commercial
Intranets on the build, and in use, none of which I can advertise -
interestingly enough, I am using mySQL, PHP on guess what: <A HREF="http://www.redhat.com/">Red Hat</A> Linux
7.2. They work a dream, and are - FULL of lovely graphics, but tied to
100Mbps LANs, so I can afford the bandwidth! Call me a cheat!
</STRONG></P>
<P><STRONG>
Oh and thanks for the cauliflower laugh.
</STRONG></P>
<blockquote><font color="#001F3F">You want some more cauliflower?
<IMG SRC="../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
-- Mike</font></blockquote>
<P><STRONG>
Keep up the good work, I will be a regular visitor for the CONTENT!
</STRONG></P>
<P><STRONG>
cheers,
L
</STRONG></P>
<blockquote><font color="#001F3F">Leon, given your responsiveness (most important), verbosity and funny
comebacks, have you ever considered a career in The Answer Gang? Would you
feel comfortable answering questions about Linux?
</font></blockquote>
<blockquote><font color="#001F3F">If so, see The Answer Gang FAQ, <A HREF="../tag-faq.html"
>http://www.linuxgazette.com/tag-faq.html</A>
-- Mike</font></blockquote>
<P><STRONG>
I gave it some thought Mike - I dont know if I can match up to the class
of company - I have little Linux experience (love the 'Iron Orr' bit)
When I move jobs next week, (and desktop machines! yay to the end of
W2K) I'll have to set up some Linux servers, with RAID and big network
transfer speeds for up to 20 Mac OSX clients running video editing
software - Utilising the network drives as a data bank, so clients can
log onto any machine to edit and be presented with up to 10GB of storage
space for the hungry video stuff.
</STRONG></P>
<P>
Only 10GB? What are they editing; news packages?
<IMG SRC="../gx/dennis/smily.gif" ALT=":-)"
height="24" width="20" align="middle">
-- jra
</P>
<P><STRONG>
After that I'll be in a position to answer some questions on Linux!
</STRONG></P>
<P><STRONG>
(If anyone has some pointers on the above problem please jump in - or
even if it is possible! specially Mac OSX Vs Linux issues.)
</STRONG></P>
<P><STRONG>
'till then Ciao!
</STRONG></P>
<P><STRONG>
Leon Czechowicz
</STRONG></P>
<P>
The problem is <EM>sustained throughput</EM>. TTBOMK, <EM>nothing</EM> is fast
enough at the network filer level at the moment to do anything much
faster than DV (3.5MB/s). To beat that, you need, I think, to go to
NAS, or something similar: shared <EM>drives</EM>, rather than shared
filesystems.
</P>
<P>
Perhaps things have speeded up a bit... but be prepared to go to either
100Mbs Ether with dedicated adapters, or Gigabit shared... and
something more towards token than ether is not out of line.
</P>
<P>
Either that, or nasty buffering on the mount client.
</P>
<P>
Investigate Cinelerra, too.
</P>
<P>
Cheers,
-- jra
</P>
<!-- end 5 -->
<P> <hr> </p>
<!-- *** BEGIN copyright *** -->
<H5 align="center">This page edited and maintained by the Editors
of <I>Linux Gazette</I>
<a href="http://www.linuxgazette.com/copying.html"
>Copyright ©</a> 2002
<BR>Published in issue 76 of <I>Linux Gazette</I> March 2002</H5>
<H6 ALIGN="center">HTML script maintained by
<A HREF="mailto:star@starshine.org">Heather Stern</a> of
Starshine Technical Services,
<A HREF="http://www.starshine.org/">http://www.starshine.org/</A>
</H6>
<!-- *** END copyright *** -->
<center>
<H1><A NAME="tips"><IMG ALIGN=MIDDLE ALT="" SRC="../gx/twocent.jpg">
More 2¢ Tips!</A></H1> <BR>
<!-- BEGIN tips -->
Send Linux Tips and Tricks to <A HREF="mailto:linux-questions-only@ssc.com">linux-questions-only@ssc.com</A></center>
</center>
<UL>
<!-- index_text begins -->
<li><A HREF="#tips/1"
><strong>ques</strong></a>
<li><A HREF="#tips/2"
><strong>File cache...</strong></a>
<li><A HREF="#tips/3"
><strong>Answer for "getting volume label from CD".</strong></a>
<li><A HREF="#tips/4"
><strong>Compiling from source</strong></a>
<li><A HREF="#tips/5"
><strong>Automate dialing?</strong></a>
<li><A HREF="#tips/6"
><strong>Redhat 7.2 Linux firewall-Howto</strong></a>
<li><A HREF="#tips/7"
><strong>File System problem</strong></a>
<li><A HREF="#tips/8"
><strong>Quick C function lookup</strong></a>
<li><A HREF="#tips/9"
><strong>GNU</strong></a>
<li><A HREF="#tips/10"
><strong>Is there a way to check if a dial up ppp connection is REALLY up?</strong></a>
<li><A HREF="#tips/11"
><strong>large file support detection</strong></a>
<li><A HREF="#tips/12"
><strong>Linux with win2000</strong></a>
<li><A HREF="#tips/13"
><strong>Basic Newbie Question</strong></a>
<li><A HREF="#tips/14"
><strong>O'Reilly posters</strong></a>
<li><A HREF="#tips/15"
><strong>printing</strong></a>
<li><A HREF="#tips/16"
><strong>Linux rocks!</strong></a>
<li><A HREF="#tips/17"
><strong>Setting up telnet in a Linux server.</strong></a>
<li><i>Linux Journal</i>'s Weekly News Notes <a href="#tips/lj">Tech Tips</a>
<ul>
<li><A HREF="#lj/1"
><strong>ssh -n</strong></a>
<li><A HREF="#lj/2"
><strong>The simplest way to process a web form</strong></a>
<li><A HREF="#lj/3"
><strong>How to switch between several network profiles on your laptop</strong></a>
<li><A HREF="#lj/4"
><strong>Speeding up commands like "route" and "netstat"</strong></a>
<li><A HREF="#lj/5"
><strong>Very important topic: keeping your "fortune" file indexed</strong></a>
<li><A HREF="#lj/6"
><strong>Limiting the files "locate" shows</strong></a>
<li>
<A HREF="http://noframes.linuxjournal.com/subscribe/lja-sub.html"
>subscribe to <I>Linux Journal's</I> Weekly News Notes</A>
</ul>
<!-- index_text ends -->
</UL>
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/1"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">ques</FONT></H3>
<p>Fri, 1 Feb 2002 11:32:44 -0800
<BR>Dan Wilder (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%231%20big%20disks">The Answer Gang</a>)
<BR>asked by piyush moghe
</p>
<P><STRONG>
respected sir
<br>i have a problem with linux instalation on 20Gb or
more capacity disks,i had installed on p3,20gb hd,64
mb ram.i make 2 1Gb partition as linux native & one
200 mb as swap the instalation goes on smoothly but at
the end it gives error that first partition not lies
in 1024 cylinders what i can do to solve this problem
</STRONG></P>
<P>
Actually we're several guys, and one or more gals. If you
respect us, that's nice, but not essential.
</P>
<P>
Upgrade to current LILO. Most new distributions should
contain a LILO able to overcome the 1024 cylinder limit,
and so a newer distribution might be the easiest way
to do it.
</P>
<P>
Or, re-partition the disk so that its first partition, about 16Mb,
is mounted at <TT>/boot</TT>, second partition is swap, and the third partition
containing the remainder of the disk is mounted as <TT>/</TT>, the root
partition. The installation scripts on the distribution will
probably give you an opportunity to specify how you want
the hard drive partitioned, and that's where you do this.
</P>
<P>
Make sure your kernel boot image (usuall vmlinuz) is located
in <TT>/boot</TT>, and is referenced from <TT>/etc/lilo.conf</TT> as such.
You may have to move things around and rerun lilo after
the installation stuff completes.
</P>
<P>
Let us know how you are doing.
</P>
<!-- end 1 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/2"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">File cache...</FONT></H3>
<p>Thu, 14 Feb 2002 22:25:24 -0800
<BR>Dan Wilder (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%232%202.4%20file%20cache">dan from ssc.com</a>)
<BR>asked by Matthew Koundakjian
</P>
<P><STRONG>
Is there a way to control in a 2.4.x kernel how large the file cache can grow?
</STRONG></P>
<P><STRONG>
File cache always seems to take as much as it can and we <EM>really</EM> would
prefer to keep it low.
</STRONG></P>
<P><STRONG>
The main user is routinely running tasks upwards of 1.5GB at time and there
are times when the system thrashes and thrashes.
</STRONG></P>
<Pre><STRONG>
3:55pm up 2 days, 23:36, 19 users, load average: 0.60, 0.72, 0.75
162 processes: 160 sleeping, 2 running, 0 zombie, 0 stopped
CPU0 states: 76.0% user, 0.0% system, 0.0% nice, 23.0% idle
CPU1 states: 31.0% user, 13.0% system, 0.0% nice, 55.0% idle
Mem: 2059412K av, 2053732K used, 5680K free, 0K shrd, 41576K buff
Swap: 3072112K av, 703596K used, 2368516K free 1236900K cached
</STRONG></Pre>
<blockquote>
<P>
Big file cache is not necessarily A Bad Thing. As long as it
unloads fast when demand grows.
</P>
<P>
I'd look to other problems first.
</P>
<ol>
<li> Are you running 2.4.17 or something older and buggier? If not
2.4.17, upgrade now.
<li>
Are you running an AMD Duron or Athlon + AGP video? If so,
you'll need a kernel boot parameter to cut cache page size,
there's an interference between the way the kernel handles
DMA and the way AMD handles AGP, leading to sporadic random
cache corruption.
<li>
You're 700M into swap. That's never a Good Idea. Unless what's
swapped out is more or less permanently swapped out. If so
why are you running it? If possible, get another gig of
memory. The slowest memory is much faster than the fastest
hard drive.
</ol>
</blockquote>
<P><STRONG>
Hello Dan...
</STRONG></P>
<P><STRONG>
Thanks so much. Yes, we're running an older kernel ... mostly, 2.4.6 ...
I'll fix that.
</STRONG></P>
<P><STRONG>
As far as the swap, originally, we had no swap, but because the file cache
is so "hungry", I threw in swap as a brute force means because processes
were dying from lack of memory...
</STRONG></P>
<P><STRONG>
As it is, we run a computational fluid dynamics code that periodically dies
with no more than "broken pipe" as the error diagnostic, which, if I had to
make a W.A.G., I would assume a process died. Before, it was a LOT
worse... It was ugly when something like portmap would croak. So, lacking
any coherent solution and having unhappy users, I threw some swap in and it
seemed to help with stability tremendously.
</STRONG></P>
<P><STRONG>
But most recently, with one user process running, allocating about 1.7G,
the system was apparently thrashing horribly... very unresponsive and with
a system load on the order of 10.
</STRONG></P>
<P><STRONG>
As far as the swap versus file cache, it would seem to be silly to have a
file cache that's so large that swap starts coming into play.
</STRONG></P>
<P><STRONG>
Bye,
<br>Matt
</STRONG></P>
<!-- end 2 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/3"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Answer for "getting volume label from CD".</FONT></H3>
<p>Thu, 24 Jan 2002 16:09:19 -0700
<BR>Sean Reifschneider (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%233%20cd%20label">jafo from tummy.com</a>)
<P>
The URL:
</P>
<P><BLOCKQuote>
<A HREF="../issue72/tag/2.html"
>http://www.linuxgazette.com/issue72/tag/2.html</A>
</BLOCKQuote></P>
<P>
asks the question "How do I get the volume label from a data CD", and then
the three guys go on to not provide a very good answer...
</P>
<P>
If you would like to add the following, it may be useful to other readers.
</P>
<P>
There are two problems in identifying CDs -- one is identifying a data CD,
the other is identifying an audio CD. Mr. Bray is asking specifically
about data, but it's also possible to determine a fairly unique ID for
audio CDs as well.
</P>
<P>
Data CDs are easy -- a 32-byte string is written in the ISO at offset
32808. Some systems have a program called "volname" (part of the eject
package), which can pull this data out. Otherwise, "dd" can be used:
</P>
<P><CODE>
dd if=/dev/cdrom bs=1 skip=32808 count=32
</CODE></P>
<P>
This is the volume label specified via the "-V" argument to "mkisofs" when
creating the CD image.
</P>
<P>
For audio CDs, it's (unfortunately) not as easy. The CD Digital Audio
standard does not include a location for storing CD or track identification
information. The answer for this that I've heard is that they felt it was
too hard a problem to solve initially.
</P>
<P>
While it may seem easy to add a few strings on the CD, it becomes harder
when you have to deal with an international market -- how do you make it so
that Japanese tracks can be identified, for example. Remember, this was
back in the <gasp> '80s, when Unicode wasn't common.
</P>
<P>
So, the way people go about identifying audio CDs is by generating a
signature. This signature consists of information about the length of
tracks, number of tracks, and various other information. You can then
condense this information down into a single value.
</P>
<P>
This value can then be used to submit and request more specific data about
a disc or track.
</P>
<P>
Thanks to the LinuxDoc CDROM-HOWTO for the dd command to pull this data off
the CD.
</P>
<P>
Sean
</P>
<!-- end 3 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/4"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Compiling from source</FONT></H3>
<p>Fri, 1 Feb 2002 09:03:21 -0800
<BR>John Davies (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%234%20install%20from%20source">johnny5_tc from yahoo.co.uk</a>)
</p>
<P><STRONG>
Hi,
I've just read your informative article on installing
from source in this months Linux Gazette.
</STRONG></P>
<P><STRONG>
You mention that it would be good if make files has
and uninstall target and that most don't. Well, if you
have a look at Checkinstall
(<A HREF="http://asic-linux.com.mx/~izto/checkinstall-en.html"
>http://asic-linux.com.mx/~izto/checkinstall-en.html</A>)
it allows you to uninstall programs built from source.
</STRONG></P>
<P><STRONG>
What it does is to replace the "make install" command
with checkinstall. It makes a note of which files were
installed and allows you to uninstall the program
using the package management tools on your machine (in
my case dpkg). It also creates a .deb (or .rpm) so you
can install it on another machine.
</STRONG></P>
<P><STRONG>
I've played with it for a few days now and it is
extremely useful.
</STRONG></P>
<P><STRONG>
Regards
John
</STRONG></P>
<P>
John,
</P>
<P>
Thanks for that tip. I'm a moderately long-time member of
The Answer Gang, and had not heard of checkinstall before.
I often build from source, and had until now resorted to
clumsy and time-consuming expedients to manage uninstalls.
</P>
<P>
"checkinstall" is just what we need here at SSC, host of
The Answer Gang's mailing list server and The Linux Gazette's
web site.
</P>
<blockquote><font color="#1F1F1F">This is pretty much the reason that I forwarded this to TAG. I've had seven
or eight e-mails telling me me about "buildpkg", "rpm", etc.; under Debian,
I'm familiar with "alien" - but none of these deal with the real issue of
"remembering" what the "make" did. They just convert the tarball (which
often cannot be done due to layout, etc.) into RPMs or DEBs, etc. This tool
- although I have not yet had the time to check it out - sounds like a very
nice possibility, and I'm going to be looking into it.
-- Ben</font></blockquote>
<P>
Well thanks, Ben, for forwarding it.
</P>
<P>
It sounds like this tool does something like what I've been doing by hand.
After building a package, I often
</P>
<blockquote><pre> su root
script
make install
^D
</pre></blockquote>
<P>
(that's "CTRL-D", an EOT character, to log out of script)
then edit the resulting "typescript" file to build a roster of what
was installed, which I then save in an "ssc" subdirectory of the build
directory, against a day when I wish to know what was installed.
</P>
<P>
You're absolutely right about alien et al. They work from a tarball,
.deb, .rpm, etc.
</P>
<P>
However, most stock GNU packages don't even build an install tarball.
They just install directly, leaving a cryptic trail of what they
installed in the output from the "make install". Without analyzing
that output you don't even get a tarball to "alien".
</P>
<P>
There are exceptions. <A HREF="http://www.debian.org/">Debian</A>-modified source trees build the
.deb packages directly, which can then be installed. <A HREF="http://www.slackware.org/">Slackware</A>-modified
source trees build a tarball directly. No doubt <A HREF="http://www.redhat.com/">Red Hat</A> et al has
something similar ... brainfade prevents me from saying at the moment ...
</P>
<P>
All too often I find I must go directly to the original release of
some package, rather than using the distribution's source, either
because the package is not available under the appropriate distribution,
or because the distribution's package doesn't do it for us. Wrong
or broken version, etc etc etc.
</P>
<P>
If this checkinstall does what it looks like it might do, it solves
that problem of "what do you do if you've only the original source code".
-- Dan
</P>
<!-- end 4 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/5"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Automate dialing?</FONT></H3>
<p>Wed, 20 Feb 2002 18:26:42 -0500
<BR>Ben Okopnik (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%235%20autodial%20ISP">The Answer Gang</a>)
<BR>asked by gagandgupta
<P><STRONG>
I want to write a program that on getting some sort of
trigger will automatically connect to the internet by
dialling the ISP's telephone number. After it has
established connection it should store the IP address
assigned to it by the ISP in a file.
</STRONG></P>
<P>
Two major hints that, together, should give you the solution:
</P>
<ol>
<li> Search the Net for "linux" and "dial-on-demand". The standard answer to
this used to be "Diald", but nowadays it's built into pppd, so reading the
man page may be an even better solution.
<li> Read "<TT>/etc/ppp/ip-up</TT>", paying special attention to "PPP_REMOTE".
</ol>
<P>
That's it. There's no deep science to it.
</P>
<!-- end 5 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/6"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Redhat 7.2 Linux firewall-Howto</FONT></H3>
<p>Tue, 5 Feb 2002 22:01:56 -0800
<BR>Dan Wilder (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%236%20firewall">The Answer Gang</a>)
<br>asked by Franco Fernandes
</p>
<P><STRONG>
Hi!
</STRONG></P>
<P><STRONG>
Can anyone tell me from where can i get the Redhat 7.2 Linux firewall-Howto
download
</STRONG></P>
<P><STRONG>
Thanks & Regards
<br>Franco.F
</STRONG></P>
<P>
I don't know about a Redhat 7.2 firewall howto ... if there is
such, I'd expect to find it by searching www.redhat.com.
</P>
<P>
A generic Linux howto, now ...
</P>
<P>
<A HREF="http://www.linuxdoc.org/HOWTO/Firewall-HOWTO.html"
>http://www.linuxdoc.org/HOWTO/Firewall-HOWTO.html</A>
</P>
<P>
There's a lot of other great stuff in that same directory.
-- Dan
</P>
<BLOCKQUOTE>
Not the question you were asking - but if you want to get a basic
iptables firewall in place you could want to look at firestarter or
something similar
-- Mike E
</BLOCKQUOTE>
<!-- end 6 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/7"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">File System problem</FONT></H3>
Fri, 8 Feb 2002 11:53:32 +0000 (GMT)
<BR>Thomas Adam (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%237">The <i>LG</i> Weekend Mechanic</a>)
<BR>asked by Ben Wood
</p>
</P>
<P><STRONG><BLOCKQuote>
i require help fixing my linux hard drive, it is a
ext2 file system and
during startup it fails to pass the file system
check, it says
"Directory inode 38381, block 0, offset 0: directorty corrupted"
how do i fix it, can it be fixed?
</BLOCKQuote></STRONG></P>
<P>
You can do the following.....
</P>
<ul>
<li> Assuming that you are using Lilo as your linux
loader, then at the prompt type:
<blockquote><pre>linux init=/bin/bash root=/dev/hdxx ro
</pre></blockquote>
where "<TT>/dev/hdaxx</TT>" is the device file which points to
the root of your Linux partition (i.e. mounted "<TT>/</TT>")
(or change "linux" to the name of the stanza within
"<TT>/etc/lilo.conf</TT>" that will load Linux).
<br>
This will then put you into a single user mode, with
all the partitions mounted as read-only.
<br>
Then at the prompt, type:
<blockquote><pre>fsck -f /
</pre></blockquote>
and this should fix any errors on the drive.
<br>
Usually, any inode data is stored within the
"<TT>/Lost+Found</TT>" directory.
</ul>
<p>
If you need any help, let me (us) know.
<br>Kind Regards,
<br>Thomas Adam
</P>
<!-- end 7 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/8"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Quick C function lookup</FONT></H3>
<p>Thu, 24 Jan 2002 22:24:21 -0500
<BR>Ben Okopnik (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%238">The Answer Gang</a>)
</p>
<P>
In your ".bashrc" file, add the following line:
</P>
<blockquote><pre>alias chlp="info --file libc.info.gz --node \"Function Index\" --index-search $1"
</pre></blockquote>
<P>
The next time you log in (or even open another xterm or console), you'll
have this as an alias. Call it this way:
</P>
<blockquote><pre>chlp setuid
</pre></blockquote>
<P>
to have it drill down to where the "setuid" function is defined in the
documentation. For those of you that use "vi", you can also redefine your
"man page lookup" key:
</P>
<blockquote><pre>set kp=chlp
</pre></blockquote>
<P>
Put your cursor on a function name and press 'K'; Magic Will Happen.
<IMG SRC="../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
</P>
<!-- end 8 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/9"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">GNU</FONT></H3>
<p>Thu, 21 Feb 2002 18:25:10 -0500
<BR>Jay R. Ashworth, Chris Gianakopoulos (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%239%20GNU">The Answer Gang</a>)
<br>asked by
Rafel Burrial
</P>
<P><STRONG>
What in the hell does GNU mean?
</STRONG></P>
<P>
It's this uncommon African animal, also called a white bearded
wildebeest.
-- Jay
</P>
<BLOCKQUOTE>
In hell, it's the ...
-- Ben
</BLOCKQUOTE>
<BLOCKQUOTE><em>
I </EM>really<EM> think Ben needs to stop talking about dark things like that...
Poor Chris, who specializes in our cross-MSwin questions, got bit by a
nasty mailerdevil for that one. Just in case, I didn't print it
<img src="../gx/dennis/smily.gif" height="24" width="20" alt=":D">
-- Heather
</em></BLOCKQUOTE>
<BLOCKQUOTE>
I think if you go to (D'oh!) <A HREF="http://www.gnu.org">www.gnu.org</A>, and look at the <EM>first</EM> page
-- and I might point out that this is the <EM>first</EM> hit on Google for
'gnu' <EM>and the answer is in the frigging page title</EM> -- you'll probably
find the answer to your question.
-- Jay
</BLOCKQUOTE>
<BLOCKQUOTE>
GNU's not Unix like Unix is not Multics!!!!! !!
Ho! Ho! Ho! <laugh from down there in h*ll>
</BLOCKQUOTE>
<BLOCKQUOTE>
A day late, because I've had no mail for the last 24 hours!!
-- Chris
</BLOCKQUOTE>
<!-- end 9 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/10"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Is there a way to check if a dial up ppp connection is REALLY up?</FONT></H3>
<p>Tue, 29 Jan 2002 08:54:08 -0500
<BR>Chuck & Crystal Shepherd (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%2310%20ISP%20up">cc_shep from yahoo.com</a>)
<BR>with points from Ben and John K. of The Answer Gang
</p>
<P><STRONG>
I have a linux box (RH 7.1) set up to serve as mail and internet server for
my two other home computers.
</STRONG></P>
<P><STRONG>
It is set up to dial on demand. Therefore ifconfig shows ppp0 up and
running all the time (when it is working properly)
</STRONG></P>
<P><STRONG>
I would like to be able to check the status of the modem without lifting
the telephone from it's cradle.
</STRONG></P>
<P><STRONG>
I have checked into using the lock file which can be written by pppd but
this is not very reliable when if pppd goes down unexpectantly it does not
always clean up after itself.
</STRONG></P>
<P>
I haven't done anything with "diald" in a couple of years, but doesn't it
use SLIP to do its dirty work (i.e., the PPP link you request is actually
to a local VT; "diald" feeds your PPP daemon lots of baloney and sweet talk
while it actually makes the connection behind its back)? If so, then you
could always check if the 'sl0' interface is up without tripping off the
dial-up.
-- Ben
</P>
<BLOCKQUOTE>
The querent doesn't specifically mention 'diald', which does use the slip
interface as part of its mechanism. The newer versions of pppd also
support dial on demand, and uses a different type of mechanism.
Unfortunately, I can't be too specific, as I've never set it up. I would
guess that you could simply check to see if ppp0 (assuming only one
dial-up connection active at a time) is up, much the same way as was
suggested for diald. Actually IIRC, in the case of diald, (which AFAIK,
is no longer actively supported) the slip interface goes away when the ppp
link gets established; so simply checking for a ppp interface would work
for diald as well.
-- John Karns
</BLOCKQUOTE>
<P><STRONG>
I am a big LG fan. Thanks for all the tips and advise.
</STRONG></P>
<P>
<smile> We do what we can. Good luck - let us know how it goes!
-- Ben
</P>
<P><STRONG>
Thanks for your response.
</STRONG></P>
<P><STRONG>
I think I have got my solution by using lsof <TT>/dev/ttyS1</TT>
</STRONG></P>
<P><STRONG>
(ttyS1 is my serial port)
</STRONG></P>
<P><STRONG>
It does not seem to initiate a connection and does not seem to interrupt an existing connection.
</STRONG></P>
<P><STRONG>
Thanks for your help!
</STRONG></P>
<P><STRONG>
Chuck
</STRONG></P>
<!-- end 10 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/11"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">large file support detection</FONT></H3>
<p>Mon, 21 Jan 2002 22:37:22 -0500
<BR>Robos (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%2311%20large%20files">robos from geekmail.de</a>)
<BR>and Ben from The Answer Gang
</p>
<!-- sig -->
<!-- sig -->
<P>
On Tue, Jan 22, 2002 at 01:35:56AM +0100, Robos wrote:
</P>
<P><STRONG>
Hi Gang!
Maybe I already told you about my little program to copy dvd's to
harddisk, called vobcopy (look on freshmeat). In the next release I
want to incorporate large file support (lfs - no, not linux from
scratch
<IMG SRC="../gx/dennis/smily.gif" ALT=";-)"
height="24" width="20" align="middle">. I found Jim Dennis' answer in the 67 issue and read
around various places (info libc, the suse-page, the large file summit
papers) but I am still unable to <EM>detect</EM> if the usersystem has support
for large files. We (another person joined me and did most of the lfs
stuff) found out about the -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE (the last one being redundant if not even close
to being wrong in my opinion) and off_t. But we are not sure if this
works correctly on both systems (supporting/not supporting). I would
think its better to know if the users system has support or not and compile
accordingly.
My approach would be somthing along the lines of look whats defined in
<linux/*file.h> and what the file system is the file gets written
to. But kinda ugly and probably wrong. Does one of you happen to know
how to figure it out?
</STRONG></P>
<P>
Check for the presence of "ftello64" (declared in <stdio.h>
<IMG SRC="../gx/dennis/smily.gif" ALT=";)"
height="24" width="20" align="middle">. From "info
libc -> I/O on streams -> File Positioning":
</P>
<TABLE WIDTH="95%" BORDER="1" BGCOLOR="#FFFFCC"><TR><TD>
<p align="center">...............</p>
<P>
- Function: off64_t ftello64 (FILE *STREAM)
</P>
<P>
This function is similar to `ftello' with the only difference that
the return value is of type `off64_t'. This also requires that the
stream STREAM was opened using either `fopen64', `freopen64', or
`tmpfile64' since otherwise the underlying file operations to
position the file pointer beyond the 2^31 bytes limit might fail.
</P>
<P>
If the sources are compiled with `_FILE_OFFSET_BITS == 64' on a 32
bits machine this function is available under the name `ftello'
and so transparently replaces the old interface.
</P><p align="center">...............</p>
</TD></TR></TABLE>
<P>
"ftello" is the 'fixed' version of "ftell", but can be found on systems
with or without LFS. From the above, it looks like "ftello64" would only
exist on systems with LFS, where "ftello" would be an alias for it. I've
got to hand it to the GNU folks: cute trick.
</P>
<!-- end 11 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/12"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Re: [LG 75] 2c Tips #5 Linux with win2000</FONT></H3>
<p>Fri, 22 Feb 2002 15:26:13 +0530
<BR>sanjay sharma (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%2312%20w2k%20after%20linux">sanjayjisuno from hotmail.com</a>)
</p>
<P>
this related with redhat linux
</P>
<ol>
<li> if you have free space in your harddisk for windows 2000 partition
then
<ul>
<li>first install win2000 on your system after installation
<li>
boot your pc with redhat linux7.2 cdrom and type on prompt "linux rescue"
enter
<li>
check on which partition no. windows 2000 install you can check this by
typing
<blockquote><pre>fdisk /dev/hda
</pre></blockquote>
press enter
<br>
then type "p " press enter
<br>
now you know your windows partition no.
<li>
mount the partition by typing
<blockquote><pre>mount -t vfat /dev/hda(windows partition no.) /hdd
</pre></blockquote>
press enter
<br>
it will mount your windows partition at <TT>/hdd</TT> directory
<li>
as you installed linux first so your linux partition must be hda1 or
check your linux partition
<br>
run command
<blockquote><pre>dd if=/dev/hda(linux partition no.) of=/hdd/bootlin bs=512 count=1
</pre></blockquote>
press enter
<br>this command show you the message
<blockquote><pre>1 record in
1 record out
</pre></blockquote>
<li>
now type "exit" press enter
<li>
now edit the boot.ini in windows partition
<br>
add one line under the heading Oprating system
</P>
<blockquote><pre>c:\bootlin=3D"Redhat Linux "
</pre></blockquote>
save it and you are done
<li>
reboot the system
</ul>
<li>
if there is no free space
<br>
use partition magic to make some free space for windows 2000 and use the
same steps
</ol>
<!-- end 12 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/13"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Basic Newbie Question</FONT></H3>
<p>Thu, 21 Feb 2002 22:11:03 -0500
<BR>Faber Fedor (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%2313%20user%20not%20all%20powerful">The Answer Gang</a>)
<br>asked by Steven Bruce
</p>
<P><STRONG>
I've just installed RH 7.2 on a sony vaio, and was quite surprised by the
ease with which it went on (Far cry from RH5.5). Anyway, I created the
suggested user so that I wouldn't be logging in as Root all the time,
however, the user I created can not create, delete, copy, etc, files in
ROOT, or USR, or even HOME.
</STRONG></P>
<P>
Of course you can't! This isn't That Other Operating System.
<IMG SRC="../gx/dennis/smily.gif" ALT=":-)"
height="24" width="20" align="middle">
</P>
<P><STRONG>
I am assuming I have to login as ROOT and join
the user to the administrators group, or some such group which will allow
the user the appropriate permissions, but I am not sure. Is thre something I
am missing or something I should be doing different?
</STRONG></P>
<P>
You're missing something.
<IMG SRC="../gx/dennis/smily.gif" ALT=":-)"
height="24" width="20" align="middle"> In Linux (and unix in general) users
<em>don't</em> have the right to willy-nilly create files and run any old
program. Would you like it if user jane had the rights to delete files
in you home directory? Of course not!
</P>
<P>
Linux has rather strict rules about what you, a normal user can do. The
root user, OTOH, can do <EM>anything</EM>. This is a very dangerous thing if
you're not careful. Let's say you wanted to delete all the files in
your home directory (you're allowed to do that, they're <EM>your</EM> files).
That would be done with the command
</P>
<P><CODE>
rm -rf /home/steve
</CODE></P>
<P>
If you accidentally typed it as
</P>
<P><CODE>
rm -rf / home/steve
</CODE></P>
<P>
You would get some error about not having permissions, etc. And
depending where you were in the directory, ypou might or might not wipe
out your home directory.
</P>
<P>
However, if you were logged in as root and type the accidental line, you
would, literally, wipe out every file on the hard drive.
</P>
<P>
You might want to add the normal user to various groups, but you should
proabbly read up on Linux and permissions and all that. Start by reading
the Dos/Windows User to Linux User HOWTO
( <A HREF="http://www.linuxdoc.org/HOWTO/DOS-Win-to-Linux-HOWTO-4.html"
>http://www.linuxdoc.org/HOWTO/DOS-Win-to-Linux-HOWTO-4.html</A> ) to get
an idea on what's going on.
</P>
<P>
Reading the HOWTOs in general is a good idea (maybe not all at once,
mind you). You can find all of them and more at www.linuxdoc.org
</P>
<P><STRONG>
Any help would be greatly appreciated!
</STRONG></P>
<P>
A little appreciation is just fine, thank you.
<IMG SRC="../gx/dennis/smily.gif" ALT=":-)"
height="24" width="20" align="middle">
</P>
<HR width="10%" align="center"><P>
Regards,
<br>Faber
</P>
<!-- end 13 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/14"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Re: [LG 75] 2c Tips #15 posters</FONT></H3>
<p>Thu, 31 Jan 2002 15:22:52 -0500
<BR>Boyer, Charles (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%2314%20posters">Charles.Boyer from tycoelectronics.com</a>)
</p>
<P>
Probably old news...but just in case:
</P>
<P><BLOCKQuote>
<A HREF="http://linux.oreilly.com/news/linuxanatomy_0101.html"
>http://linux.oreilly.com/news/linuxanatomy_0101.html</A>
</BLOCKQuote></P>
<P>
backPosters are available free with a $50 purchase at the following O'Reilly
conferences and tradeshows:
</P>
<P>
O'Reilly Conferences:
</p>
<ul>
<li> <A HREF="http://conferences.oreilly.com/p2p/"
>http://conferences.oreilly.com/p2p/</A> The O'Reilly P2P Conference,
San Francisco
<li> <A HREF="http://conferences.oreilly.com/oscon2001/"
>http://conferences.oreilly.com/oscon2001/</A> O'Reilly Open Source
Software Convention, San Diego
</ul>
<P>
Tradeshows:
</P>
<ul>
<li><A HREF="http://events.oreilly.com/#lwny"
>http://events.oreilly.com/#lwny</A> LinuxWorld, New York
</P>
<P>
<li><A HREF="http://events.oreilly.com/#usenix"
>http://events.oreilly.com/#usenix</A> Usenix, Boston
<li>
<A HREF="http://events.oreilly.com/#lwsf"
>http://events.oreilly.com/#lwsf</A> LinuxWorld, San Francisco
<li><A HREF="http://events.oreilly.com/#alxt"
>http://events.oreilly.com/#alx</A> Annual Linux Showcase, Oakland
</ul>
<P>
Cheers.
</P>
<!-- end 14 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/15"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">printing</FONT></H3>
<p>Thu, 31 Jan 2002 22:11:58 -0600
<BR>Jack Berger (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%2315%20printing">jhb from mapp.org</a>)
</p>
<P>
You mention that you are having problems w/your epson printer.
</P>
<P>
I'm not too familiar w/printer defs in things like ghostscript or gimp, but my
printing w/an hp 970 improved by orders of magnitude for all applications when I
installed turbo print. Colors come out good, speed is improved. Just works nice.
</P>
<P>
-jhb-
</P>
<!-- end 15 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/16"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Linux rocks!</FONT></H3>
Thu, 21 Feb 2002 23:21:00 -0500
<BR>Ben Okopnik (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%2316%20USB%20sync">The Answer Gang</a>)
<P>
Today, the curiosity bug bit me again, so I poked my nose into the Linux
Visor USB mailing list, and - lo and behold - there it was. Seems that the
new version of "coldsync", at least the beta, now handles the m125! I
downloaded it, configured it, compiled it, made a config file - and...
ta-daa! Palm USB synchronization, under Linux.
</P>
<P>
Life is good.
<IMG SRC="../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
</P>
<!-- end 16 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/17"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Setting up telnet in a Linux server.</FONT></H3>
<p>Thu, 24 Jan 2002 18:43:04 -0800
<BR>Dan Wilder (<a href="mailto:linux-questions-only@ssc.com?subject=%20Re%3A%20%5BLG%2076%5D%202c%20Tips%20%2317%20telnet%20no%20use%20ssh">The Answer Gang</a>)
<br>asked by Subroto Sengupta
</P>
<P><STRONG>
Hello Sir,
</STRONG></P>
<P><STRONG>
I would like to know how to set up a Linux 7.1 server and configure it
properly to be able to telnet into it from a Windows client machine.
</STRONG></P>
<P><STRONG>
A reply would be greatly appreciated.
</STRONG></P>
<P><STRONG>
Sincerely,
<br>Subroto.
</STRONG></P>
<P>
Well, that's a whole lot of questions.
</P>
<P>
There's no "Linux 7.1". The Linux kernel's current versions
are 2.5.2 (pretty wild), 2.4.17 (conditionally stable), and
2.2.20 (quite stable). (labels mine).
</P>
<P>
Linux is distributed by several vendors, who label their own
distribution with a version number. You may be thinking about
<A HREF="http://www.redhat.com/">Red Hat</A> Linux 7.1. Don't. Get Red Hat Linux 7.2 or 6.2.
Other vendors (<A HREF="http://www.debian.org/">Debian</A>, Mandrake, <A HREF="http://www.slackware.org/">Slackware</A>, <A HREF="http://www.suse.com/">SuSE</A>, <A HREF="http://www.caldera.com/">Caldera</A>,
to name just a few) each use their own numbering schemes,
which have not much to do with those of the others.
</P>
<P>
How to set up a server? Best advice I can give is "follow
the vendor's directions, and ask questions here when you
get lost".
</P>
<P>
Telnet? Only on a protected network, I hope! Telnet exchanges
a password in the clear, OK if just your immediate family is
watching the 'net, not so good if the password traverses six ISPs
and a few chunks of the backbone.
</P>
<P>
That said, during install, select the telnet package. Sometimes
that's part of some other package, sometimes not. Consult the
vendor documentation and help.
</P>
<P>
On exposed networks, use the ssh (secure shell) package on Linux,
and get "putty" secure shell client for Windows. It's much
better than windows telnet, and it'll even telnet, if you must.
</P>
<P>
<A HREF="http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html"
>http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html</A>
</P>
<P>
or search google.com for "putty.exe".
</P>
<P>
--
Dan Wilder
</P>
<!-- sig -->
<!-- end 17 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="tips/lj"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy"><i>Linux Journal</i>'s Weekly News Notes Tech Tips</FONT></H3>
</P>
<!-- begin ljwnn -->
<P> <A NAME="lj/1"><HR WIDTH="75%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">ssh -n</FONT></H3>
<P>
Use ssh -n to run an X program from one computer on another.
For example,
</P>
<blockquote><pre>ssh -n frodo gimp &
</pre></blockquote>
<P>
will run the GIMP on the host frodo, but display locally.
</P>
<P>
Using ssh for this is much easier and more secure than setting it up
in X manually.
</P>
<P>
The -n option means prevent reading of stdin. Many times you don't need
this, but if your application hangs waiting for input or does something
else strange, try it.
</P>
<!-- end 1 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="lj/2"><HR WIDTH="40%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">The simplest way to process a web form</FONT></H3>
<P>
You can put a simple form on your web site even if you don't have CGI
privileges. Just use <form method=GET action="result.html"> where
result.html is a "thank you for filling out the form" page.
</P>
<P>
You can then get the values people filled in from the web server
access log.
</P>
<!-- end 2 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="lj/3"><HR WIDTH="40%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">How to switch between several network profiles on your laptop</FONT></H3>
<P>
Use the scheme option to cardctl to manage multiple network schemes on
one laptop. The scheme is passed in as the first part of the device
address in the PCMCIA wireless.opts script. Make two entries in
wireless.opts:
</P>
<blockquote><pre>ssc,*,*,*)
INFO="SSC WiFi Net"
ESSID="wifi.ssc.com"
;;
dana,*,*,*)
INFO="live.com network at Dana St. Roasting Co."
ESSID="LIVE.COM"
;;
</pre></blockquote>
<P>
To switch between them, do
</P>
<blockquote><pre>sudo cardctl scheme ssc
</pre></blockquote>
<P>
or
</P>
<blockquote><pre>sudo cardctl scheme dana
</pre></blockquote>
<P>
For more info, see the PCMCIA HOWTO. You can change all the settings,
including WEP key, mode and other options. For more information on
free wireless access and coffee in Mountain View, California, see Dana
Street:
<A HREF="http://www.live.com/danastreet"
>http://www.live.com/danastreet</A>, a <TT>LIVE.COM</TT> Neighborhood Network.
</P>
<P>
Rob Flickenger explains how to set up shell scripts to switch schemes
with less typing in his new book, Building Wireless Community Networks
(O'Reilly, 2002).
</P>
<!-- end 3 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="lj/4"><HR WIDTH="40%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Speeding up commands like "route" and "netstat"</FONT></H3>
<P>
If "route" takes a long time to run because you have no route to your
nameserver, do "route -n" to skip the DNS lookup and use IP addresses
only.
</P>
<P>
This works with "netstat", "ping" and "traceroute" too.
</P>
<!-- end 4 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="lj/5"><HR WIDTH="40%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Very important topic: keeping your "fortune" file indexed</FONT></H3>
<P>
You can keep your fortune file indexed and up-to-date on multiple
servers with make. Here's an example Makefile to handle common
fortune-related tasks:
</P>
<blockquote><pre># List all the fortune files you maintain here. (I just have them
# all in one big file)
FORTUNES = dmarti
# For every fortune file, the datfile is the same name but with .dat
# on the end
DATFILES = $(FORTUNES:=.dat)
# Make a copy of the fortunes file to the zork.net collection
# (http://zork.net/fortunes/) Since it's the first target, this
# target and its dependencies will run if you just type "make"
tozork : $(DATFILES)
scp $(FORTUNES) $(DATFILES) zork.net:/usr/local/etc/fortunes
touch tozork
# This target makes each .dat file from the appropriate fortune
# file, if it has changed.
%.dat : %
strfile $<
# Get rid of all the .dat files (not really needed, but it's traditional
# to have "make clean" do _something_)
clean :
rm -f $(DATFILES)
# There is no file named "clean", but always build this target.
.PHONY : clean
</pre></blockquote>
<P>
For more information, see "man strfile" and "info make". Now that you know
how to manage fortunes by editing only one file and typing make, why
not put your favorite sayings on your web site as a fortune file
others can also use? (The old fortunes that come with most
distributions have come up way too often for us.)
</P>
<!-- end 5 -->
<!-- .~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~.~~. -->
<P> <A NAME="lj/6"><HR WIDTH="40%" ALIGN="center"></A> <P>
<H3><IMG ALIGN=BOTTOM ALT="" SRC="../gx/lil2cent.gif">
<FONT COLOR="navy">Limiting the files "locate" shows</FONT></H3>
<P>
"locate" is a wonderful command for quickly finding files on your system.
Unfortunately, sometimes it produces so many hits that it takes too long
to find the forest among the trees.
Distributions and programs often have lots of files, making locate
seem useless. To refine your search, type:
</P>
<blockquote><pre>loc () {
locate "$1" | egrep -v 'bmp|html|whatever'
}
</pre></blockquote>
<P>
or put it in your .bashrc, and you won't receive any entries that contain
</P>
<!-- end 6 -->
<!-- end ljwnn -->
<P> <hr> </p>
<!-- *** BEGIN copyright *** -->
<H5 align="center">This page edited and maintained by the Editors
of <I>Linux Gazette</I>
<a href="http://www.linuxgazette.com/copying.html"
>Copyright ©</a> 2002
<BR>Published in issue 76 of <I>Linux Gazette</I> March 2002</H5>
<H6 ALIGN="center">HTML script maintained by
<A HREF="mailto:star@starshine.org">Heather Stern</a> of
Starshine Technical Services,
<A HREF="http://www.starshine.org/">http://www.starshine.org/</A>
</H6>
<!-- *** END copyright *** -->
<H4 ALIGN="center">
"Linux Gazette...<I>making Linux just a little more fun!</I>"
</H4>
<P> <HR> <P>
<!--===================================================================-->
<center>
<H1><font color="maroon">The Answer Gang</font></H1>
<H4>By <a href="mailto:tag@ssc.com"></a></H4>
</center>
<P> <HR> <P>
<!-- END header -->
<P> The Answer Gang column isn't ready yet. Check back tomorrow.
<!-- *** BEGIN bio *** -->
<!-- *** END bio *** -->
<!-- *** BEGIN copyright *** -->
<P> <hr> <!-- P -->
<H5 ALIGN=center>
Copyright © 2002, .<BR>
Copying license <A HREF="../copying.html">http://www.linuxgazette.com/copying.html</A><BR>
Published in Issue 76 of <i>Linux Gazette</i>, March 2002</H5>
<!-- *** END copyright *** -->
<H4 ALIGN="center">"Linux Gazette...<I>making Linux just a little more fun!</I>"</H4>
<HR>
<center>
<table cellpadding=7><tr><td>
<IMG SRC="../gx/bytes.gif" border=1 ALT="News Bytes">
</td><td>
<H3>Contents:</H3>
<ul>
<li><a HREF="#leg">Legislation and More Legislation</a>
<li><a HREF="#links">Linux Links</a>
<li><a HREF="#conferences">Conferences and Events</a>
<li><a HREF="#general">News in General</a>
<li><a HREF="#distro">Distro News</A>
<li><a HREF="#commercial">Software and Product News</a>
</ul>
</td></tr></table>
<STRONG>Selected and formatted by <A HREF="mailto:michael.conry@softhome.net">Michael Conry</A></STRONG>
</center>
<P> Submitters, send your News Bytes items in
<FONT SIZE="+2"><STRONG>PLAIN TEXT</STRONG></FONT>
format. Other formats may be rejected without reading. You have been
warned! A one- or two-paragraph summary plus URL gets you a better
announcement than an entire press release.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<font color="green">
March 2002 <I>Linux Journal</I>
</font>
</H3>
<IMG ALT="[issue 95 cover image]" SRC="misc/bytes/lj-cover95.png" WIDTH=200 HEIGHT=268
ALIGN="left" HSPACE="20">
The March issue of <A HREF="http://www.linuxjournal.com/"><I>Linux
Journal</I></A> is on newsstands now.
This issue focuses on web scripting. Click
<A HREF="http://www.linuxjournal.com/modules.php?op=modload&name=NS-lj-issues/issue95&file=index">here</A>
to view the table of contents, or
<A HREF="http://www.linuxjournal.com/subscribe/">here</A>
to subscribe.
<P>
<FONT COLOR="green">All articles through December 2001 are available for
public reading at
<A HREF="http://www.linuxjournal.com/magazine.php">http://www.linuxjournal.com/magazine.php</A></FONT>.
Recent articles are available on-line for subscribers only at
<A HREF="http://interactive.linuxjournal.com">http://interactive.linuxjournal.com/</A>.
<BR CLEAR="all">
<!-- =================================================================== -->
<a name="leg"></a>
<p><hr><p>
<!-- =================================================================== -->
<center><H3><font color="green">Legislation and More Legislation</font></H3></center>
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">DMCA
</FONT>
</H3>
At risk of sounding like a broke record, there are a couple of links we
would like to bring to your attention regarding the DMCA (Digital
Millennium Copyright Act), the law used to imprison Dmitry Sklyarov.
<a href="http://www.eff.org/">
The Electronic Frontier Foundation</a>
has produced an extensive
<a href="http://www.eff.org/IP/DMCA/US_v_Sklyarov/us_v_sklyarov_faq.html">
FAQ</a>
about the Dmitry Sklyarov & ElcomSoft Prosecution. The information is
of course relevant to a wider range of circumstances than this particular
case, and details the DMCA, fair use, eBooks and the EFF's role in the
case. This is a good resource for anyone who wants to get the whole crazy
story straight (if that is even possible!).
<P>
A recent story on
<a href="http://slashdot.org/">
Slashdot</a>
highlighted how bad this law really is. Apparently it turns out that
<a href="http://slashdot.org/article.pl?sid=02/02/14/1745238&mode=nested">
serial cables might be illegal</a>.
The story submitter, Colin McMillen, related how US Customs rejected entry
of a PC-Sega Dreamcast serial cable into the US, even though the cable had
a legitimate academic use.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">Copyright
</FONT>
</H3>
The New York Times has
<a href="http://www.nytimes.com/2002/02/19/national/19CND-RIGHTS.html">
reported</a> [registration required] on a
<a href="http://eon.law.harvard.edu/openlaw/eldredvreno/">
legal challenge</a>
to the Copyright Term Extensions Act 1998, which extended copyrights
another 20 years. The US Supreme Court has agreed to hear the challenge,
which is being brought by a coalition of interested parties (publishers,
etc.,) who depend on using material in the public domain. It will be
interesting to see how this challenge progresses, as the original law was
the result of extensive lobbying by powerful players in the media industry,
notably Disney who would lose control of Mickey Mouse in 2003 under the
original law which gave 75 year protection. The challenge is being backed
by at least one lawyer most readers will be familiar with: Lawrence Lessig.
Various
<a href="http://eon.law.harvard.edu/openlaw/eldredvreno/">
news and information resources</a> are available on the
<a href="http://eon.law.harvard.edu/openlaw/">
Openlaw</a>
website.
<p>
<hr noshade width="20%">
<p>
In related news, Slashdot
<a href="http://slashdot.org/article.pl?sid=02/02/19/1916245&mode=nested">
reported</a>
that Canada is to hold
<a href="http://strategis.ic.gc.ca/SSG/rp01100e.html">
public hearings</a>
on digital copyright. There are
<a href="http://strategis.ic.gc.ca/SSG/rp00833e.html">
various locations and dates</a>,
and it would be great if people from Canada with an interest in the Free
Software movement were able to make their points of view heard at these
meetings.
<a name="links"></a>
<p><hr><p>
<!-- =================================================================== -->
<center><H3><font color="green">Linux Links</font></H3></center>
<p><hr><p>
<p>
<IMG ALT="Linux Focus" SRC="../gx/linuxfocus.jpg" WIDTH="143" HEIGHT="45">
<BR CLEAR="all">
The following articles are in the March issue of the E-zine
<A HREF="http://www.linuxfocus.org/">LinuxFocus</A>:
<ul>
<li>
<a href="http://linuxfocus.org/English/March2002/article177.shtml">
Samba configuration</a>
</li>
<li>
<a href="http://linuxfocus.org/English/March2002/article229.shtml">
GCC - the root of all</a>
</li>
<li>
<a href="http://linuxfocus.org/English/March2002/article230.shtml">
IOS, another REBOLution</a>
</li>
<li>
<a href="http://linuxfocus.org/English/March2002/article231.shtml">
Programming the AVR Microcontroller with GCC</a>
</li>
<li>
<a href="http://linuxfocus.org/English/March2002/article232.shtml">
Bookreview: The qmail Handbook</a>
</li>
<li>
<a href="http://linuxfocus.org/English/March2002/article233.shtml">
Introduction to Ncurses</a>
</li>
<li>
<a href="http://linuxfocus.org/English/March2002/article235.shtml">
Setting up a Squid-Proxy Server</a>
</li>
<li>
<a href="http://linuxfocus.org/English/March2002/article237.shtml">
Game Review - Barrel Patrol 3D</a>
</li>
<li>
<a href="http://linuxfocus.org/English/March2002/article238.shtml">
Playing around with Dingbats and The Gimp</a>
</li>
</ul>
<p>
<a href="http://www.theregister.co.uk/">
The Register</a>
have featured the following stories which might interest you:
<ul>
<li>
First of all, we must mention that those living on the western side of
the Atlantic
<a href="http://www.theregister.co.uk/content/31/24195.html">
now have</a>
their very own version of The Register,
<a href="http://www.theregus.com/">
http://www.theregus.com/</a>, which is co-published with
<a href="http://www.tomshardware.com/">
Tom's Hardware Guide</a>.
The new site has mostly the same content as the original
Register, minus esoteric UK stories, plus esoteric North America
stories.
</li>
<li>
Sun is to
<a href="http://www.theregister.co.uk/content/4/24192.html">
charge</a>
for StarOffice on Linux and Windows, but not on Solaris. [The Register]
LWN <A HREF="http://lwn.net/2002/0228/">speculates</A> why, but notes that
all hope is not lost: StarOffice is "
based on <a href="http://www.openoffice.org/">OpenOffice</a>,
which, thanks to Sun, <i>is</i> free software.
</li>
<li>
Barlow lambasts DMCA,
<a href="http://www.theregister.co.uk/content/4/24186.html">
citing example</a>
of Grateful Dead.
</li>
<li>
Walmart to sell
<a href="http://www.theregister.co.uk/content/54/24165.html">
OS-free PCs</a>.
</li>
<li>
BSD
<a href="http://www.theregister.co.uk/content/4/24060.html">
`3 times as popular as desktop Linux'</a>
thanks to Mac OS X of course.
</li>
</ul>
<p>
The
<a href="http://www.oreillynet.com/">O'Reilly</a>
stable of websites have published various articles which might be useful or
interesting to you:
<ul>
<li>
<a href="http://www.onlamp.com/pub/a/bsd/2002/02/21/FreeBSD_Basics.html">
Finding things</a>
in the UNIX environment, and more.
</li>
<li>
<a href="http://www.onlamp.com/pub/a/onlamp/2002/02/21/sysperf.html">
Performance analysis</a> and system tuning.
</li>
<li>
<a href="http://onlamp.com/pub/a/bsd/2002/02/14/Big_Scary_Daemons.html">
Understanding NFS</a>
</li>
<li>
<a href="http://linux.oreillynet.com/pub/a/linux/2002/01/31/make_intro.html">
Introduction to make</a> and a guide to
<a href="http://linux.oreillynet.com/pub/a/linux/2002/02/14/makefiles.html">
advanced Makefiles</a>, by Jennifer Vesperman
</li>
<li>
Also by Jennifer Vesperman, an
<a href="http://linux.oreillynet.com/pub/a/linux/2002/01/03/cvs_intro.html">
introduction to CVS</a> and a guide to
<a href="http://linux.oreillynet.com/pub/a/linux/2002/01/17/cvsadmin.html">
CVS administration</a>.
</li>
<li>
<a href="http://linux.oreillynet.com/pub/a/linux/2001/12/14/rootkit.html">
Understanding rootkits</a> and
<a href="http://linux.oreillynet.com/pub/a/linux/2002/02/07/rootkits.html">
Scanning for rootkits</a>.
</li>
</ul>
<p>The
<a href="http://dillo.sourceforge.net/">
Dillo</a> web browser. Still pretty basic, no frames or style sheets, but
it is VERY FAST! This is worth supporting.
<P>
Mike Orr's Linux Journal
<a href="http://www.linuxjournal.com/article.php?sid=5854">
report</a>
from the Tenth International Python Conference.
<P>
Slashdot
<a href="http://slashdot.org/articles/02/02/27/1627214.shtml?tid=106">
story</a>
on CodeWeavers CrossOver plugin 1.1 which plays Windows Media 6.4 under
Linux.
<P>
The
<a href="http://www.linuxbios.org/">
LinuxBIOS project</a>.
<p>
<a href="http://www.unixreview.com/">
UnixReview.com</a>
have taken
<a href="http://www.unixreview.com/documents/s=2424/uni1014152480113/0202i.htm">
a look at three Linux firewall products</a>:
SuSE Firewall on CD, Mandrake Single Network Firewall and Coyote Linux.
<p>
LinuxSecurity.com has a guide to
<a href="http://www.linuxsecurity.com/feature_stories/feature_story-91.html">
configuring Postfix</a>.
<p>
Newsforge
<a href="http://www.newsforge.com/article.pl?sid=02/02/06/0220236&mode=nocomment">
reports on</a>
Fluxbox, an evolved version of the Blackbox window manager.
<p>
IBM
<a href="http://www-105.ibm.com/developerworks/education.nsf/linux-onlinecourse-bytitle/F86D74C7B3B4E65486256B2900073A2E?open&l=3">
article</a>
on clustering with MOSIX.
<p>
Linuxtoday with a
<a href="http://linuxtoday.com/news_story.php3?ltsn=2002-02-01-013-26-PR-DV">
Boston Consulting Group report</a>
on the mind of the average Open Source community member.
<p>
<a href="http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=/netahtml/srchnum.htm&r=1&f=G&l=50&s1='6,341,372'.WKU.&OS=PN/6,341,372&RS=PN/6,341,372">
US-Patent on perfect machine translation</a>.
Quoting a little from a post by Hartmut Pilch to the European Patent Office
mailing list:
<blockquote>
"The description is very voluminous and explains a whole new cosmology,
comprising insights about Buddhism illumination, androids, perpetuum
mobiles, subject-object dichotomy and much more. Based on this
cosmology, a solution to the above-claimed problem seems to become
possible. At least it should be difficult for an examiner to refute
that it does. He could ask the inventor to provide a working
reference implementation, but that is not adequate, because only a
key idea of a huge complex system is claimed."
</blockquote>
<p>
Some more patents links
<ul>
<li>
The Register reports that
<a href="http://www.theregister.co.uk/content/4/24157.html">
EU thumbs nose at US</a>
with software patent proposals.
</li>
<li>
New Scientist reports that British Telecom has
<a href="http://www.newscientist.com/news/news.jsp?id=ns99991905">
taken to the courts</a> to enforce its patent on hyperlinking.
</li>
<li>
The French Socialist Party (PSF)
<a href="http://www.parti-socialiste.fr/tic/ps-tic_2002.php">
opposes software patents</a> [french]. Urges resistance to US pressure.
</li>
<li>
<a href="http://www.law.nyu.edu/benklery/IP&Organization.pdf">
Intellectual Property and the Organization of Information
Production</a> [pdf]
by Yochai Benkler.
</li>
<li>
</li>
Touché to LWN:
<A HREF="http://lwn.net/2002/0228/commerce.php3">EU lets Microsoft write its Patent Directive.</A>
</ul>
<P> <A HREF="http://www.wotsit.org/">Wotsit.org</A> ("What's it?")
is a reference site for information on various file formats.
<a name="conferences"></a>
<p><hr><p>
<!-- =================================================================== -->
<center><H3><font color="green">Upcoming conferences and events</font></H3></center>
<p><hr><p>
<P> Listings courtesy <EM>Linux Journal</EM>. See <EM>LJ</EM>'s
<A HREF="http://www.linuxjournal.com/events.php">Events</A> page for the
latest goings-on.
<!-- *** BEGIN events table [this line needed by Linux Gazette events.py *** -->
<table cellpadding=5 border=0 width=100%>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>COMDEX (Key3Media)</b><BR>
<td valign=top>March 5-7, 2002<BR>Chicago, IL<BR>
<a href="http://www.key3media.com/comdex/chicago2002/" target="_blank">
http://www.key3media.com/comdex/chicago2002/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>BioIT World Conference & Expo (IDG)</b><BR>
<td valign=top>March 12-14, 2002<BR>Boston, MA<BR>
<a href="http://www.bioitworld.com/" target="_blank">
http://www.bioitworld.com/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>Embedded Systems Conference (CMP)</b><BR>
<td valign=top>March 12-16, 2002<BR>San Francisco, CA<BR>
<a href="http://www.esconline.com/sf/" target="_blank">
http://www.esconline.com/sf/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>CeBIT (Hannover Fairs)</b><BR>
<td valign=top>March 14-22, 2002<BR>Hannover, Germany<BR>
<a href="http://www.cebit.de/" target="_blank">
http://www.cebit.de/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>COMDEX (Key3Media)</b><BR>
<td valign=top>March 19-21, 2002<BR>Vancouver, BC<BR>
<a href="http://www.key3media.com/comdex/vancouver2002/" target="_blank">
http://www.key3media.com/comdex/vancouver2002/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>FOSE</b><BR>
<td valign=top>March 19-21, 2002<BR>Washington, DC<BR>
<a href="http://www.fose.com/" target="_blank">
http://www.fose.com/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>Game Developers Conference (CMP)</b><BR>
<td valign=top>March 19-23, 2002<BR>San Jose, CA<BR>
<a href="http://www.gdconf.com/" target="_blank">
http://www.gdconf.com/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>LinuxWorld Conference & Expo Singapore (IDG)</b><BR>
<td valign=top>March 20-22, 2002<BR>Singapore<BR>
<a href="http://www.idgexpoasia.com/" target="_blank">
http://www.idgexpoasia.com/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>Software Solutions / eBusiness World</b><BR>
<td valign=top>March 26-27, 2002<BR>Toronto, Canada<BR>
<a href="http://www.softmatch.com/soln20.htm#ssebw" target="_blank">
http://www.softmatch.com/soln20.htm#ssebw</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>SANS 2002 (SANS Institute)</b><BR>
<td valign=top>April 7-9, 2002<BR>Orlando, FL<BR>
<a href="http://www.sans.org/newlook/home.htm" target="_blank">
http://www.sans.org/newlook/home.htm</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>LinuxWorld Conference & Expo Malaysia (IDG)</b><BR>
<td valign=top>April 9-11, 2002<BR>Malaysia<BR>
<A HREF="http://www.idgexpoasia.com/" TARGET="_blank">
http://www.idgexpoasia.com/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>LinuxWorld Conference & Expo Dublin (IDG)</b><BR>
<td valign=top>April 9-11, 2002<BR>Dublin, Ireland<BR>
<BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>Internet World Spring (Penton)</b><BR>
<td valign=top>April 22-24, 2002<BR>Los Angeles, CA<BR>
<a href="http://www.internetworld.com/events/spring2002/" target="_blank">
http://www.internetworld.com/events/spring2002/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>O'Reilly Emerging Technology Conference (O'Reilly)</b><BR>
<td valign=top>April 22-25, 2002<BR>Santa Clara, CA<BR>
<a href="http://conferences.oreillynet.com/etcon2002/" target="_blank">
http://conferences.oreillynet.com/etcon2002/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>Software Development Conference & Expo, West (CMP)</b><BR>
<td valign=top>April 22-26, 2002<BR>San Jose, CA<BR>
<a href="http://www.sdexpo.com/" target="_blank">
http://www.sdexpo.com/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>Networld + Interop (Key3Media)</b><BR>
<td valign=top>May 7-9, 2002<BR>Las Vegas, NV<BR>
<a href="http://www.key3media.com/" target="_blank">
http://www.key3media.com/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>Strictly e-Business Solutions Expo (Cygnus Expositions)</b><BR>
<td valign=top>May 8-9, 2002<BR>Minneapolis, MN<BR>
<a href="http://www.strictlyebusiness.net/strictlyebusiness/index.po?" target="_blank">
http://www.strictlyebusiness.net/strictlyebusiness/index.po?</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>Embedded Systems Conference (CMP)</b><BR>
<td valign=top>June 3-6, 2002<BR>Chicago, IL<BR>
<a href="http://www.esconline.com/chicago/" target=_"blank">
http://www.esconline.com/chicago/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>USENIX Annual (USENIX)</b><BR>
<td valign=top>June 9-14, 2002<BR>Monterey, CA<BR>
<a href="http://www.usenix.org/events/usenix02/" target="_blank">
http://www.usenix.org/events/usenix02/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>PC Expo (CMP)</b><BR>
<td valign=top>June 25-27, 2002<BR>New York, NY<BR>
<a href="http://www.techxny.com/" target="_blank">
http://www.techxny.com/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>O'Reilly Open Source Convention (O'Reilly)</b><BR>
<td valign=top>July 22-26, 2002<BR>San Diego, CA<BR>
<a href="http://conferences.oreilly.com/" target="_blank">
http://conferences.oreilly.com/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>USENIX Securty Symposium (USENIX)</b><BR>
<td valign=top>August 5-9, 2002<BR>San Francisco, CA<BR>
<a href="http://www.usenix.org/events/sec02/" target="_blank">
http://www.usenix.org/events/sec02/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>LinuxWorld Conference & Expo (IDG)</b><BR>
<td valign=top>August 12-15, 2002<BR>San Francisco, CA<BR>
<a href="http://www.linuxworldexpo.com" target="_blank">
http://www.linuxworldexpo.com</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>LinuxWorld Conference & Expo Australia (IDG)</b><BR>
<td valign=top>August 14 - 16, 2002<BR>Australia<BR>
<a href="http://www.idgexpoasia.com/" target="_blank">
http://www.idgexpoasia.com/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>Communications Design Conference (CMP)</b><BR>
<td valign=top>September 23-26, 2002<BR>San Jose, California<BR>
<a href="http://www.commdesignconference.com/" target="_blank">
http://www.commdesignconference.com/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
<tr><td valign=top>
<b>Software Development Conference & Expo, East (CMP)</b><BR>
<td valign=top>November 18-22, 2002<BR>Boston, MA<BR>
<a href="http://www.sdexpo.com/" target="_blank">
http://www.sdexpo.com/</A><BR>
<tr><td colspan=2><HR size=5 width=100% noshade align=center></td></tr>
</table>
<!-- *** END events table [this line needed by Linux Gazette events.py *** -->
<a name="general"></a>
<p><hr><p>
<!-- =================================================================== -->
<center><H3><font color="green">News in General</font></H3></center>
<p><hr><p>
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">Linux, Microsoft and the Bundestag
</FONT>
</H3>
A group of German citizens concerned that Germany should both exploit
the advantages of free software, and avoid some of the perils of
proprietary software have been lobbying for the introduction of free
software into the German parliament, the Bundestag.
The
<a href="http://www.bundestux.de/english.html">
www.bundestux.de</a> (English and Deutsch) calmly makes the case for free
software in the Bundestag (and indeed in all government), and provides the
opportunity to submit your contact details in support of the sentiments.
<p>
The Register
<a href="http://www.theregister.co.uk/content/4/23964.html">
reported</a>
that this civil activity was received with hostility by Microsoft Germany,
who felt they were unjustly being labelled as:
"undemocratic and a hindrance to democracy".
The consultants report released later on basically
<a href="http://www.theregister.co.uk/content/4/24048.html">
divided the spoils</a> [The Register] between Microsoft (recommended for
desktops) and free software (recommended in server/groupware roles).
Microsoft's poor email client security was noted, but was not sufficient to
tip the balance.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">W3C Climbdown
</FONT>
</H3>
<a href="http://lwn.net/">
Linux Weekly News</a>
has
<a href="http://lwn.net/2002/0131/">
reported</a>
that the W3C appears to have backed down on the issue of incorporating
royalty governed technology into its standards. This is a significant
victory for people speaking out on issues that upset them. LWN also notes
that there is
<a href="http://lists.w3.org/Archives/Public/www-patentpolicy-comment/2002Jan/0151.html">
another comment period</a>
leading up to the final review, for those who still have something to say
or contribute.
<p>
<hr noshade width="20%">
<p>
Also on the topic of open standards,
The Register
<a href="http://www.theregister.co.uk/content/4/23908.html">
reported</a>
on the
<a href="http://www.freestandards.org/">
Free Standards Group</a>,
which has currently completed two standards, the
<a href="http://www.linuxbase.org/">
Linux Standard Base</a> (broadly covering system layout)
and the
<a href="http://www.li18nux.org/">
Li18nux</a> standard (covering internationalization). Happily, this
initiative seems to have widespread support, and should be a significant
boon to the whole Free Software movement.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">Linux Weekly News
</FONT>
</H3>
<P>
<a href="http://www.lwn.net/">
Linux Weekly News</a> (LWN) is becoming independent again. Tucows, which had
acquired it, has spun it off. "As of the beginning of February, LWN
will operate, once again, as an independent publication of Eklektix,
Inc., which will be owned by the current LWN staff. All of our financial
issues remain, and they have only gotten more pressing over time, but we
will have more freedom in how we try to address those issues." LG has long
been a supporter of LWN (after all, we get some of our best links from them!),
and we were
<A HREF="../issue72/lg_bytes72.html#general">saddened in November</A> to hear
of their difficulties. We wish the LWN staff the very best of luck.
<a name="distro"></a>
<p><hr><p>
<!-- =================================================================== -->
<center><H3><font color="green">Distro News</font></H3></center>
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">General
</FONT>
</H3>
<P>
Distro News is based on the information sent to us by the
publishers/authors of Linux distributions. This does not necessarily give
a broad view of the Linux scene. One excellent resource for anyone
interested in choosing a distribution or just in the state of the business
is
<a href="http://www.distrowatch.com/">
DistroWatch.com</a>
which has profiles and comparisons of almost every distribution under the
sun. Another resource is the distribution section of
<a href="http://www.lwn.net/">
Linux Weekly News</a>
(for example,
<a href="http://lwn.net/2002/0221/dists.php3">
here</a>)
which covers news regarding new distribution releases, changes/updates to
existing distros, and distribution releases.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">Bluecat
</FONT>
</H3>
<P>
<a href="http://www.lynuxworks.com">
LynuxWorks</a>
have announced BlueCat 4.0 Linux and VisualLynux Integrated Development
Environment (IDE) support
for the for the new ARM920T processor. Developers will now be able to
develop embedded Linux software applications for the ARM920T
processor, which features high-performance and low-power characteristics
for handheld devices, network computers, smart phones and other
processor-intensive applications.
LynuxWorks' BlueCat 4.0 Linux distribution is based
on the 2.4 Linux kernel. With VisualLynux, developers have access to an
integrated and tested cross development environment to facilitate
development. VisualLynux is an extension of
Microsoft Visual Studio, developed for Windows-hosted development, with
the added benefit of all the commands and standard GNU tools needed to
streamline the design and creation of applications targeted to run on
BlueCat Linux.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">Debian
</FONT>
</H3>
<a href="http://www.debian.org/News/weekly">
Debian Weekly News</a>
<a href="http://www.debian.org/News/weekly/2002/8/">
reported</a> that a new revision (r6) of Potato is
<a href="http://master.debian.org/~joey/2.2r6/">
in preparation</a>, and is expected to arrive early March. Looking to the
next release, it seems Woody is beginning to
<a href="http://lists.debian.org/debian-devel-announce-0202/msg00012.html">
take shape</a>
for its ultimate release. Unofficial Woody CD's have been available for a
while, but recently Ho-seok Lee has released a
<a href="http://www.debian.or.kr/~alee/cdimages/">
mini CD image</a> suitable for 3.5" mini CD's.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">SuSE
</FONT>
</H3>
<a href="http://www.suse.de/en/">
SuSE</a>
has announced the implementation of mySAP.com on "SuSE Linux Enterprise
Server". Since the beginning of this year, SuSE Linux has been utilising
SAP's enterprise resource planning tool on Compaq hardware for the
company's business operations. SuSE has also announced the availability of
"SuSE Linux Enterprise Server 7 for iSeries and pSeries"
<a name="commercial"></a>
<p><hr><p>
<!-- =================================================================== -->
<center><H3><font color="green">Software and Product News</font></H3></center>
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">Graphics Muse Tools CD V1.0.0 for GIMP 1.2
</FONT>
</H3>
<P> In response to the growing demand for off the shelf products for desktop
Linux systems, the Graphics Muse is now offering
<a href="http://www.graphics-muse.org/gfxmuse/gfxmuse.html">
The Graphics Muse Tools CD</a>,
an easy to install package of plug-ins, scripts, and data for use with the
latest version of GIMP. The Graphics Muse Tools CD V1.0.0, a suite of
Plug-Ins, scripts and data designed specifically for use with GIMP 1.2 and
Red Hat 7.x was released on Feb 7, 2002.
This release includes 4 original plug-ins and 84 plug-ins and Perl
scripts from the GIMP Registry, all compiled for use on Red Hat 7.x.
This includes 16 programs that had not previously been ported to GIMP 1.2.
Additionally, the CD includes over 125 new brushes and 125 new patterns.
<P> The Graphics Muse Tools CD is available for Red Hat Linux 7.x systems and
can be purchased for $12, plus shipping and any applicable sales tax, from
the Graphics Muse Tools
<a href="http://www.graphics-muse.org/gfxmuse/gfxmuse.html">
CD web site</a>. (Should also work on SuSE 7.2 and Mandrake 8.1)
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">CryptoHeaven
</FONT>
</H3>
<p>
<a href="http://www.cryptoheaven.com/">
CryptoHeaven</a> offer a set of tools and services aimed at bringing
encryption technologies to a wider audience. The tools deal with such
tasks as encrypting/signing emails, secure instant messaging and chatting,
online encrypted file storage, key management, etc., with the emphasis on
ease of use. Available for Windows, Linux, Mac OS X. Free download, with
charges for some services, consult website for details.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">OmniCluster SlotServer
</FONT>
</H3>
<a href="http://www.omnicluster.com">
OmniCluster Technologies</a>
is an IBM spin-off that has created a plug-n-play server blade products
that fit within the PCI expansion slots of existing hardware.
Since SlotServers are built on an industry standard PCI architecture
and are compatible with virtually all operating environments -- including
Windows 2000, Windows NT, RedHat Linux and FreeBSD.
Users can run applications tuned for an operating system, regardless of the
host server's operating system. For example, users can run a Linux-based
firewall within a Windows-based host, on an isolated server.
SlotServers range in cost from $499 - $1,199.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">Zend Studio 2.0
</FONT>
</H3>
<P>
<a href="http://www.zend.com">
Zend Technologies</a> have released
<a href="http://www.zend.com/store/products/zend-studio.php">
Zend Studio 2.0</a>:
an environment for developing, debugging, and deploying PHP applications in
one integrated package. Zend Studio 2.0 is intended to allow people with
intermediate computer skills to develop, de-bug and deploy PHP-based
applications ranging from e-commerce to Web hosting.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">New Release of Motif
</FONT>
</H3>
<P>
In cooperation with The Open Group,
<a href="http://www.ics.com">
ICS</a>
have just released an update to the
Motif GUI toolkit.
Open Motif 2.2 includes 10 new user interface controls and universal tooltip
support. A roadmap has also been defined that defines availability
for additional functionality including anti-aliased fonts, improved imaging
support (png, jpg, etc.) and canvases.
<P>More details are available at
<a href="http://www.motifzone.net">
www.motifzone.net</a>.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">Fake
</FONT>
</H3>
<P>
<a href="http://www.vergenet.net/linux/fake/">
Fake</a>
is a utility, released by
<a href="http://www.vergenet.net/">
Verge Systems</a>,
that enables an IP address to be taken over by bringing up a second
interface on the host machine and using arp spoofing. This can be used to
switch in backup servers on a LAN during periods of both unscheduled and
scheduled down time.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">QuickHelp and QuickUML Linux
</FONT>
</H3>
<P>
<a href="http://www.excelsoftware.com">
Excel Software</a>
have announced the availability of two new packages for Linux.
<a href="http://www.excelsoftware.com/quickhelplinux.html">
QuickHelp</a>
is a development tool for quickly creating and distributing online help for
Linux applications with support for the Linux KDE and GNOME desktops.
QuickHelp consists of a QuickHelp Builder for creating help systems and a
QuickHelp Viewer for deploying them to end-users. The help information
resides in a single XML file distributed with the QuickHelp Viewer.
<p>
<a href="http://www.excelsoftware.com/quickumllinuxnews100.html">
QuickUML for Linux</a>
is an object-oriented design tool that provides extensive integration and
ease-of-use for a core set of UML models. An entire project is accessible
through a tabbed window with smooth integration between use cases, class
models, object models, dictionary and code. The project is saved as an XML
file that is compatible with QuickUML Windows so design work can be shared
between platforms.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">Team ASA Releases Dual Gigabit Ethernet NPWR Linux
Engine with 733 MHz XScale CPU
</FONT>
</H3>
<P>
<a href="http://www.TeamASA.com">
Team ASA</a>
have today announced the latest
release in the NPWR single board networking computer series.
NPWR, a first single board networking computer (SBNC) designed for
manufacturers and OEMs in the Network Attached Storage (NAS), RAID,
and Personal Server marketplaces, is now available with dual Gigabit
Ethernet ports.
The NPWR is powered by the Intel XScale processor and the standard
configuration includes a 160 Mbytes per second (LVD) SCSI port, 8
Mbytes of FLASH ROM, 128 Mbytes of SDRAM and Dual Gigabit Ethernet
ports.
<P> <hr> <P>
<!-- =================================================================== -->
<H3><IMG ALT=" " SRC="../gx/bolt.gif">
<FONT COLOR="green">VariCAD
</FONT>
</H3>
<P>
<a href="http://www.varicad.com">
VariCAD</a>
have announced the recent release of its MCAD - VariCAD 8.1. This
CAD package features many tools for 3D modelling and 2D drafting:
libraries of mechanical parts, surface development (unbending),
calculations of standard mechanical components, tools for working with
non-graphical information (BOM), and more. VariCAD 8.1 can also import and
export common CAD file types such as DWG, DXF, and IGES.
<!-- *** BEGIN copyright *** -->
<P> <hr> <P>
<H5 ALIGN=center>
Copyright © 2002, Michael Conry and
the Editors of <A HREF="mailto:gazette@ssc.com"><I>Linux Gazette</I></A>.<BR>
Copying license <A HREF="../copying.html">http://www.linuxgazette.com/copying.html</A><BR>
Published in Issue 76 of <i>Linux Gazette</i>, March 2002</H5>
<!-- *** END copyright *** -->
<H4 ALIGN="center">
"Linux Gazette...<I>making Linux just a little more fun!</I>"
</H4>
<P> <HR> <P>
<!--===================================================================-->
<center>
<H1><font color="maroon">Linux User Caricatures</font></H1>
<H4>By <a href="mailto:francka1@dingoblue.net.au">Franck Alcidi</a></H4>
</center>
<P> <HR> <P>
<!-- END header -->
<IMG ALT="[cartoon]" SRC="misc/alcidi/color_mickey_and_tux.jpg"
WIDTH="500" HEIGHT="386">
<P> My previous LG cartoons:
<A HREF="../issue72/alcidi.html">issue72</A>
<A HREF="../issue73/alcidi.html">issue73</A>
<P> You can view my other artwork and sketches on my
<A HREF="http://www.ozemail.com.au/~geisha/projects.html">projects page</A>.
<!-- *** BEGIN bio *** -->
<SPACER TYPE="vertical" SIZE="30">
<P>
<H4><IMG ALIGN=BOTTOM ALT="" SRC="../gx/note.gif">Franck Alcidi</H4>
<EM>Franck is an artist in Australia. His home page ("Ausmosis") is
<A HREF="http://www.ozemail.com.au/~geisha/projects.html">http://www.ozemail.com.au/~geisha/projects.html</A>.
</EM>
<!-- *** END bio *** -->
<!-- *** BEGIN copyright *** -->
<P> <hr> <!-- P -->
<H5 ALIGN=center>
Copyright © 2002, Franck Alcidi.<BR>
Copying license <A HREF="../copying.html">http://www.linuxgazette.com/copying.html</A><BR>
Published in Issue 76 of <i>Linux Gazette</i>, March 2002</H5>
<!-- *** END copyright *** -->
<H4 ALIGN="center">
"Linux Gazette...<I>making Linux just a little more fun!</I>"
</H4>
<P> <HR> <P>
<!--===================================================================-->
<center>
<H1><font color="maroon">Fil & Lil</font></H1>
<H4>By <a href="mailto:webmaster@whatisnew.com">ESC Technologies</a></H4>
</center>
<P> <HR> <P>
<!-- END header -->
<IMG ALT="[cartoon]" SRC="misc/fillil/fillil2002january4.png"
WIDTH="610" HEIGHT="250">
<BR CLEAR="all">
<IMG ALT="[cartoon]" SRC="misc/fillil/fillil2002january7.png"
WIDTH="610" HEIGHT="250">
<BR CLEAR="all">
<IMG ALT="[cartoon]" SRC="misc/fillil/fillil2002january10.png"
WIDTH="625" HEIGHT="250">
<BR CLEAR="all">
<IMG ALT="[cartoon]" SRC="misc/fillil/fillil2002january12.png"
WIDTH="625" HEIGHT="250">
<BR CLEAR="all">
<IMG ALT="[cartoon]" SRC="misc/fillil/fillil2002january13.png"
WIDTH="625" HEIGHT="250">
<BR CLEAR="all">
<IMG ALT="[cartoon]" SRC="misc/fillil/fillil2002january14.png"
WIDTH="625" HEIGHT="250">
<BR CLEAR="all">
<IMG ALT="[cartoon]" SRC="misc/fillil/fillil2002january15.png"
WIDTH="625" HEIGHT="250">
<BR CLEAR="all">
<IMG ALT="[cartoon]" SRC="misc/fillil/fillil2002january18.png"
WIDTH="625" HEIGHT="250">
<BR CLEAR="all">
<IMG ALT="[cartoon]" SRC="misc/fillil/fillil2002january22.png"
WIDTH="625" HEIGHT="250">
<BR CLEAR="all">
<P> Fil and Lil's Linux Gazette debut was in
<A HREF="../issue74/fillil.html">January</A>.
All their cartoons are on the
<A HREF="http://www.whatisnew.com/">What Is New</A> page.
<!-- *** BEGIN bio *** -->
<!-- *** END bio *** -->
<!-- *** BEGIN copyright *** -->
<P> <hr> <!-- P -->
<H5 ALIGN=center>
Copyright © 2002, ESC Technologies.<BR>
Copying license <A HREF="../copying.html">http://www.linuxgazette.com/copying.html</A><BR>
Published in Issue 76 of <i>Linux Gazette</i>, March 2002</H5>
<!-- *** END copyright *** -->
<H4 ALIGN="center">
"Linux Gazette...<I>making Linux just a little more fun!</I>"
</H4>
<P> <HR> <P>
<!--===================================================================-->
<center>
<H1><font color="maroon">Taming The Linux Keyboard (My Programming Adventures in Writing a Console Application for Linux)</font></H1>
<H4>By <a href="mailto:mar22@usa.net">Petar Marinov</a></H4>
</center>
<P> <HR> <P>
<!-- END header -->
It was about a year ago when I ventured into the idea of porting my
Windows-based console editor to Linux. Naturally, I targeted the text
console. The editor was designed in a way to facilitate the porting to
any other text console environment. I have isolated all the
keyboard input and text output functions in two files, which I planned to
rewrite whenever a new platform comes to my way. I've supplied two
different versions of these files for Windows console and plain DOS
which, I presumed then, validated my initial idea that porting should
be a simple task.
<p>
My only knowledge about Linux then comprised the GNU compiler package
obtained by spending a year with its DJGPP port to DOS. While I knew
how to write, compile, and debug programs in Linux, my knowledge for
the console was limited to functions like printf() and getch(). As I
knew how prominent is the role of the text console in Unix, I supposed
that programming console applications should be really advanced and on
a par or even better to this in DOS and Windows.
<p>
I pulled the anchor and once underway, I started to gather necessary
information. Getting the advantage of having the sources of everything,
I tried to find the good tides by downloading two applications that had
console oriented text interfaces.
<p>
First it was the ubiquitous MC (Midnight Commander). This program was
the straw, which everyone that comes from Windows or DOS into the UNIX
land grabs gasping for a breath in the ocean of the unknown.
<p>
Second it was the TurboVision port to Linux. TurboVision is a popular
windowing framework for DOS designed in Borland. The company was
amicable enough to release the sources in public domain and shortly
after having them in 32-bit DJGPP I found out that there is a Linux
version as well. This pretty much showed me that there is a resolution
to my problems. To further milk the ship metaphor, this blew good winds
in my sails.
<p>
Something has spoiled the nice experience of using MC. There is
something rotten in Denmark, as one of the Great used to say. Why ESC
... is not ESC? In MC when you press ESC it does nothing until you
press it again and then the two-ESC combination does the action
supposed for the single ESC. Helloooo, why is that? Read on, to learn
what dictates the rules here.
<p>
In DOS we had ANSI.SYS. You use printf() with a sequence (starting with
ESC and hitherto called an ESC-sequence) of funky characters to move
the cursor, change the color etc, following the needs of the full-text
screen applications. It was considered primitive and unproductive to
use ANSI.SYS, and besides fancy ASCII art, nothing serious engaged in
using this methodology. Advanced libraries offered direct access to the
video memory which greatly improved the user experience in working with
console applications. I remember looking in dismay the sources of
tpcrt.pas of the TurboPower package, where tight assembler code tried
to squeeze whatever the graphic (maybe we should say "text") card had
to offer.
<p>
It turned out that what was considered a very primitive way to do full
screen applications in DOS, is the road to go in UNIX! I needed
sometime to collect myself after learning one of those basic facts of
life. Back on my feet
I tried to devise a scheme for taming the beast; I thought that as I
learn the ESC-sequences and write the functions it would be a dream
come true.
After some further research I discovered that there is no single
standard for these ESC sequences! There are different terminals that
support different set of operations and that one needs to have a whole
database to properly operate all possible terminals. Why does everything
grow so complex? I still tremble remembering the waves of the
aftershock by all the discoveries I made in a single day.
<p>
"Curses" is the king. Long live the king! It turns out that somebody
has already developed this database and all the functions I need in a
library originally called "curses". In Linux it is "ncurses". Everyone
uses it.
<p>
Screen access functions are almost intuitive enough for everyone to
start immediately utilizing them. "Ncurses" takes care to update only
the portions of the screen that actually changed, which is a nice
performance improvement when you use your program in a telnet session
or any other remote mode to minimize the amount of the transferred data.
<p>
One simple problem I faced was the fact that DOS and Windows color
attributes do not directly map to "ncurses" color attributes. The
problem is aggravated by the fact that in "ncurses" I have only 64
pairs of color and background available. How will I map my 127 possible
color/background attributes to just 64?! Well, a short analysis
revealed that my program uses only about 25 distinctive attributes,
which allows me to fit them nicely in the 64 attributes map that
"ncurses" uses. It works like that, I have an array of attributes -- my
pallete. I first go and count how many unique attributes I have. Then
for each unique attribute, that I dissolve to color and background, I
create correspondent entry in the "ncurses" color palette. The index of
this entry (consider it as an ID) is stored in a secondary array of
256 bytes (the whole range of Windows and DOS). When I then pass to my
display function an attribute from my palette it is used as an index in
this secondary array to extract the correspondent attribute ID that is
generated by "ncurses". So as long as I do not go beyond 64 unique
attributes, my program will be happy and will use the good old 256
attribute values. This allows me to have a single color palette for all
the platforms that I currently support, where for DOS and Windows it is
used natively, it is dynamically remapped in Linux.
<p>
The TurboVision port used a direct screen access when running in a text
mode linux terminal. Temporarily I considered this option, it is still
possible to add this to my modules, but later I thought that the small
performance gain simply doesn't worth the effort.
<p>
I had a bad hunch about the keyboard. First just by looking in the key
definitions in ncurses headers, I noticed that this library basically
lacks the infrastructure to define rich key combinations. The terminal
ships all the "extended" keys via ESC sequences which, I don't know
why, prevents you from getting single ESC as an ESC and you are always
required to press ESC twice for your program to receive it once. Plus
you have only a certain number of key codes, which I presume are
derived from an ancient crippled terminal, and nothing creative
happened to the definitions since then. Compare this to Windows, and
even in DOS, where you can have an ASCII translation of a key, then you
can have the keys as position codes and you can always have the shift
state of the keyboard. In Windows you are delivered, via a standard
API, different events as key pressed and key released. It sounds
natural, isn't it? Well, because it is so natural, UNIX faithful to its
orthodox approach to these matters defines everything in an extremely
crippled model. Working this way is maybe good for improving your
mental stamina, but believe me, is totally unproductive if you would
like to achieve something fast.
<p>
Then I was unable to make ncurses operate with a 0 timeout when reading
a key. Add to this the double ESC syndrome, the total lack of any roads
to extend this, and in a while you look as an abandoned donkey in a
desert with a water for just couple of hours. I always have a bottle of
Evian within reach, I needed no more evidences that while "ncurses"
support for the display is adequate, its keyboard support beyond some
very basic functionality is totally irrelevant to my needs. I started
to think how to maintain the whole keyboard business with my own code.
<p>
The keyboard is a file -- stdin. I never thought I will use stdin in a
full screen program but, as you can suspect, this is the way to go in
Unix. The stdin file transports everything in ASCII codes and keys like
the arrows form a sequence that starts with ESC. At first the
impression is that if ESC is a start of sequence then the key ESC
itself should be ESC-caped as well. That is the way "ncurses" go.
That's why in MC we need to press ESC twice.
<p>
Beside delivering all the ASCII codes and the ESC sequences, the
keyboard module needs to supply a kbhit() function. In the
documentation "ncurses" promises that its getch() function can work
with a 0 timeout, thus never blocking when there is no key in the
buffer. Maybe a plan like mine starts to form in your mind, I will use
getch() with 0 timeout, then I will have a small sleep(xxx) and this
loop will exit whenever a key is pressed. This sounds good in theory,
but "ncurses" is short on delivering on this specific feature. Its
maybe something that I didn't do right, or I used old version, or maybe
it is something else, I may eventually even look at the sources of the
"ncurses". I didn't want to go that deep, the whole keyboard model
looked totally outdated, fixing a small flaw in "ncurses" wouldn't have
helped me, I thought.
<p>
I need basically this: 1. kbhit(). I need to check for a key and exit.
2. I need to be able to read something like Ctrl+Shift+Left_Arrow. 3. I
need to exit with a timeout if for sometime a key is not pressed.
<p>
For anything of this to happen one needs to put the keyboard stdin file
in a row mode. By default you enter lines of text, which are send to
your program only after the user presses Enter. So to be able to read a
single character you need to switch to a row mode. The stdin file may
not only serve a keyboard but may get characters via a serial cable,
yes, only 3 wires should be enough to manipulate a whole machine. For a
serial connection to operate properly you need to maintain flow
control. This could be done by adding 2 additional wires for each of
the talking sides to request "stop sending me characters" and when the
buffer is empty to ask "now start dumping again". But adding 2 wires
may prove expensive and even complex, and this shuttle in the space,
who knows, something may happen if we introduce this extra level of
hardware complexity. What one can not do with the hardware makes up
with the software, a host of characters (in fact 31) is wasted to not
only maintain the flow control but to switch modes of echoing, the
canonicality (whew, this is a word, a?!) etc. As you may already know
these 31 characters are the control characters that populate the lower
district of the ASCII table. While this sounded as a good idea 20 years
ago now pressing Ctrl+S to suspend the output on the screen looks
arcane to me, and I need to use Ctrl+S to save the current file. It
smells like the keyboard needs some extra massaging to fit into the
shape I need. So the setup function easily grows beyond the lines of a
single screen, after some hours of reading documentation and
experimentation I managed to come up with something that actually
works. I felt proud, and in this era of people doing space tourism I
felt that I have my small shred of achievements to show.
<p>
Kbhit() proved to be relatively easy. To wait for a characters
on a file (or socket), use select(). If you apply this to stdin then
select() will unblock when someone presses a key. If the timeouts are
tuned to 0, then it will exit immediately with a failure or success
code indicating that a key is ready to be read.
<p>
The ReadKey() function has a 2-tier structure (complex isn't it, sounds
like something that is multi-tire). At the first level I use select() to
block for incoming characters. When select() unblocks I issue a single
read() function and try to extract as much as possible. Whatever I
manage to suck from stdin I store in a fifo queue. On the second level
the characters are extracted one by one and a string sequence is
compiled that is matched against an exhaustive list of ESC sequences.
We have a definite success if we find a matching string. We have a
definite success if we have a single ESC followed by a time-out. Then
it is just an ESC, simple! Some code takes place to close the extra
cases where nothing matches and it is not an ESC etc. All this is
supplied by a function that extracts the Shift state of the keyboard.
You may guess that this is a hack that only works in Linux text
terminals. I learned this from the source code of MC. The downside is
that this doesn't work outside bare-bones text Linux terminals. Try to
work in a X terminal and you are dead, no shift key status and no means
to ever extract it.
<p>
Linux keyboard gives one more advantage in front of any other Unix
keyboard (that I know of), you may define your own ESC sequences. So,
if you need for example Ctrl+Shift+F3 you can define this with a new
ESC sequence and by using the "loadkey" utility to download it into the
kernel. The changes are immediate and non-permanent. If you reboot you
need to reexecute the same command with the same definition. I liked
this, so I added all the key combinations that I used, and were
undefined in Linux and defined in Windows.
<p>Actually by having the
function to extract the shift-state, the possible key-combinations one
needs to explicitly define is greatly decreased. As for example if we
have Shift+F3 defined, we can get the Control key state and then we have
Ctrl+Shift+F3. Which without the shift-state function should be defined
as a new key sequence with "loadkey". A problem surfaces here, which
although subtle, should be well noted. If the extraction of the key
from the keybuffer does not coincide with the time we extract the shift
state we create a big mess. With a great probability (the computers
nowadays a fast enough) we can expect for this not to happen, but hey,
as this is just a probability so mathematicions say the odds are that
sometimes it may actually happen. Example follow. If in my editor F3 is "close
all files and discard changes" and Ctrl+Shift+F3 is assigned to be
"next file", I beg for trouble here. Imagine that F3 is in the buffer
and you can not get the shift state at the same time you will get just
F3 and not "Ctrl+Shift+F3".
<p>
Having stdin as keyboard input has one great advantage, I should admit.
The editor is subject to a total automation by just supplying an input
file, provided that you put there the ESC sequences to activate various
extended keys if necessary.
<p>To scold the enthusiasm in your eyes I should note that ... ostensibly,
full automation is possible, but to a certain extent ... maybe you have
already figured this out, right ... you can not supply the shift states in a
text file. Well, that's life, you can not have your cake and eat it too!
<p>
In Windows a console application works equally well in text mode and in
a graphical console window. While my module works perfectly well in a
text linux console ($TERM="linux"), its keyboard support is totaly
inadequate when started from within X window terminal. All this is
corollary of the fact that the most common denominator of the UNIX
keyboards is "unsigned char" and the extended keys use predefined ESC
sequences that didn't evolve for the last 20 (or more) years. So I'll
keep working in making my modules X aware. Whenever the program senses
that it is started from within X terminal it will open a new window
where all the text output will be emulated with a fixed width font and the
keyboard will be processed to the best possible extent that X server
offers.
<p>Eventually what I initially planed proved
to be doable. It was quite an effort and that is why the victory was
so sweet.
<p>
<a href="/misc/marinov/demo.tar.gz">demo.tar.gz</a> contains the whole story expresed in C language.
<p>
You may find this article at the "zepp" discussion group,
<a href="http://groups.yahoo.com/group/zepp/message/347">here</a>. I will be glad
to respond to questions or any opinions regarding this article posted in the
discussion group. Generally, the discussions are usually about software
development, comments on hardware, programming languages. Anything
related to 42 will find benign soil. You are welcome to join.
<!-- *** BEGIN bio *** -->
<SPACER TYPE="vertical" SIZE="30">
<P>
<H4><IMG ALIGN=BOTTOM ALT="" SRC="../gx/note.gif">Petar Marinov</H4>
<EM>I come originally from Rousse, Bulgaria. Now I live in San Francisco
and work in Foster City (California). I program mainly embedded systems. I
started using Linux in 1998. My work is mainly done on Windows because of
Visual C, but it is deployed on Linux platform.</EM>
<!-- *** END bio *** -->
<!-- *** BEGIN copyright *** -->
<P> <hr> <!-- P -->
<H5 ALIGN=center>
Copyright © 2002, Petar Marinov.<BR>
Copying license <A HREF="../copying.html">http://www.linuxgazette.com/copying.html</A><BR>
Published in Issue 76 of <i>Linux Gazette</i>, March 2002</H5>
<!-- *** END copyright *** -->
<H4 ALIGN="center">
"Linux Gazette...<I>making Linux just a little more fun!</I>"
</H4>
<P> <HR> <P>
<!--===================================================================-->
<center>
<H1><font color="maroon">The Foolish Things We Do With Our Computers</font></H1>
<H4>By <a href="mailto:gazette@ssc.com">Mike "Iron" Orr</a></H4>
</center>
<P> <HR> <P>
<!-- END header -->
<H2>Horror Story</H2>
By <A HREF="mailto:CraigR@servex.com.au">Craig Reeson</A>
<P> Here's a quick horror story for you.
I was recently admin-ing one of my Linux servers. This server is the
company print server.
What had happened was a user was connected to a legacy system via a
terminal program. Somewhere along the line there was a screwup and his
system starting dumping lots of extraneous data to the nearest printer. The
user tried to power-cycle the printer to no avail. Thankfully, they came to
me next to try and resolve the problem.
<P> Anyway, I ssh'd into the Linux box, changed to the 'spool/' directory and
did an 'ls' of the appropriate folder. After noting that there were a few
hundred print jobs waiting in the print queue I decided it was best if I
just deleted them all...
<P> Here is where the proverbial hit the spinning thing!
<P> ...I decided to 'rm -rf *' all the files. The problem is I did it from the
'spool/' directory rather than the proper printer directory. This had the
effect of deleting everything in my system spool directory!
<P> After realising my error I tried to fix it. First thing was trying "unrm".
This did not work as I could not read from the filesystem without errors.
Next I tried using a boot floppy and trying 'unrm' again. But no that would
not work because I could not get the RAID array to be recognised!!! Tried a
few other options until I gave up and decided it was time for an "upgrade".
<P> Problem solved after 3 hours :)
<H2></H2>
By <A HREF="mailto:craigshelley@yahoo.com">Craig Shelley</A>
<P> After buying an all-on-board style PC and installing linux, I wanted to
try out a dual-headed configuration. This was mainly because I found
myself with a spare graphics card and monitor. I plugged in the new
graphics card, and realised that the super complex modular BIOS system
was automatically disabling interrupts from the on-board graphics
system. According to the manual, it was impossible to turn off this
'feature'. Then I had an idea!
<P> The idea was that if the new graphics card could be disabled while
booting, the BIOS may ignore it. Then, I could re-enable the card for
normal use.
<P> After studying the PCI bus pinout and specs, I decided to disconnect the
reset line from the graphics card using a sharp screwdriver to destroy
the track. I then re-connected the reset line through a switch, and then
down to the ground connection. (Reset is Active Low)
<P> Using the switch I could disable the card, but it then became
impossible to re-enable it because the PC could not reset it when it
wanted to. I then decided to connect a resistor across the broken track
so that the card could also be reset by the PC, and my switch would not
affect anything else.
<P> The switch was neatly mounted on the metal back plate of the card, and
can be switched when required.
<P> Using the switch, I put the card into reset mode, booted the PC, then
turned the card back on, and found myself with two working monitors ;-) ;-)
<P> Also, have you ever wondered how to get out of the situation where X
does not return VGA text mode? Adding one of these switches to your card
solves this problem.
<HR NOSHADE WIDTH="80%%"> <!--*********************** -->
<BLOCKQUOTE><EM>
[If you have a story about something foolish or ingenious you
did to your computer, send it to
<A HREF="mailto:gazette@ssc.com">gazette@ssc.com</A>-Iron.]
</EM></BLOCKQUOTE>
<!-- *** BEGIN bio *** -->
<SPACER TYPE="vertical" SIZE="30">
<P>
<H4><IMG ALIGN=BOTTOM ALT="" SRC="../gx/note.gif">Mike Orr</H4>
<EM>Mike ("Iron") is the Editor of <I>Linux Gazette</I>. You can read what he has
to say in the Back Page column in this issue. He has been a Linux enthusiast
since 1991 and a Debian user since 1995. He is SSC's web technical
coordinator, which means he gets to write a lot of Python scripts.
Non-computer interests include Ska/Oi! music and the international language
Esperanto. The nickname Iron was given to him in college--short for Iron Orr,
hahaha.</EM>
<!-- *** END bio *** -->
<!-- *** BEGIN copyright *** -->
<P> <hr> <!-- P -->
<H5 ALIGN=center>
Copyright © 2002, Mike "Iron" Orr.<BR>
Copying license <A HREF="../copying.html">http://www.linuxgazette.com/copying.html</A><BR>
Published in Issue 76 of <i>Linux Gazette</i>, March 2002</H5>
<!-- *** END copyright *** -->
<H4 ALIGN="center">
"Linux Gazette...<I>making Linux just a little more fun!</I>"
</H4>
<P> <HR> <P>
<!--===================================================================-->
<center>
<H1><font color="maroon">Qubism and HelpDex</font></H1>
<H4>By <a href="mailto:sirflakey@core.org.au">Jon "Sir Flakey" Harsem</a>
and
<a href="mailto:shane_collinge@yahoo.com">Shane Collinge</a></H4>
</center>
<P> <HR> <P>
<!-- END header -->
<BLOCKQUOTE><EM>
[I'm putting these two cartoons on the same page because the
cartoonists are borrowing ideas from each other, and because
there are few HelpDex cartoons available at the current time. -Iron.]
</EM></BLOCKQUOTE>
<P>
<IMG ALT="[cartoon]" SRC="misc/qubism/qb-luxojr-s.jpg"
WIDTH="600" HEIGHT="240">
<BR CLEAR="all">
<IMG ALT="[cartoon]" SRC="misc/qubism/qb-rocketjump-s.jpg"
WIDTH="600" HEIGHT="240">
<BR CLEAR="all">
<IMG ALT="[cartoon]" SRC="misc/qubism/hdrivein.jpg"
WIDTH="600" HEIGHT="240">
<BR CLEAR="all">
<IMG ALT="[cartoon]" SRC="misc/qubism/qb-viisback.jpg"
WIDTH="600" HEIGHT="240">
<BR CLEAR="all">
<P> Previous cartoons about Vi-agra, the evil vi paperclip, are in
issues
<A HREF="../issue54/collinge.html">54</A>,
<A HREF="../issue55/collinge.html">55</A>,
<A HREF="../issue66/collinge.html">66</A>, and
<A HREF="../issue67/collinge.html">67</A>.
<P> All Qubism cartoons are
<A HREF="http://www.core.org.au/modules.php?name=Cartoons">here</A>
at the CORE web site.
<!-- *** BEGIN bio *** -->
<SPACER TYPE="vertical" SIZE="30">
<P>
<H4><IMG ALIGN=BOTTOM ALT="" SRC="../gx/note.gif">Jon "SirFlakey" Harsem</H4>
<EM>Jon is the and creator of the Qubism cartoon strip and current
Editor-in-Chief of the
<A HREF="http://www.core.org.au/">CORE</A> News Site.
Somewhere along the early stages of
his life he picked up a pencil and started drawing on the wallpaper. Now
his cartoons appear 5 days a week on-line, go figure. He confesses to
owning a Mac but swears it is for "personal use".</EM>
<P>
<H4><IMG ALIGN=BOTTOM ALT="" SRC="../gx/note.gif">Shane Collinge</H4>
<EM>Part computer programmer, part cartoonist, part Mars Bar. At night, he runs
around in a pair of colorful tights fighting criminals. During the day... well,
he just runs around. He eats when he's hungry and sleeps when he's sleepy.</EM>
<!-- *** END bio *** -->
<!-- *** BEGIN copyright *** -->
<P> <hr> <!-- P -->
<H5 ALIGN=center>
Qubism copyright © 2002, Jon "Sir Flakey" Harsem.<BR>
HelpDex copyright © 2002, Shane Collinge<BR>
HelpDex cartoons may be be published
electronically, but
may not be used in a public print publication without permission from the
author.<BR>
Copying license <A HREF="../copying.html">http://www.linuxgazette.com/copying.html</A><BR>
Published in Issue 76 of <i>Linux Gazette</i>, March 2002</H5>
<!-- *** END copyright *** -->
<H4 ALIGN="center">
"Linux Gazette...<I>making Linux just a little more fun!</I>"
</H4>
<P> <HR> <P>
<!--===================================================================-->
<center>
<H1><font color="maroon">The Standard C Library for Linux, part 7: String Handling</font></H1>
<H4>By <a href="mailto:buckrogers@users.sourceforge.net">James M Rogers</a></H4>
</center>
<P> <HR> <P>
<!-- END header -->
<EM>I finally have time (after a few years) to give back a little more to
the Linux community with the next in my series of articles on the Standard
C Library. I hope that you enjoy.</EM> </p>
<p>The <A HREF="../issue41/rogers.html">last article</A> was on <assert.h>
diagnostics for programmers.
This article is on <string.h> string handling. C is not
much better at handling strings than machine code, so machine language programmers
will feel quite at home in this section. There are many limitations
and problems with string.h that will be addressed in the appropriate function
descriptions. </p>
<p>I am assuming a knowledge of C programming on the part of the reader.
There is no guarantee of accuracy in any of this information nor suitability
for any purpose. </p>
<p>The example is <a href="misc/rogers/rogers_example07.c">
rogers_example07.c</a> . This is a basic example that will demonstrate
each of the string functions. If you compile it and run it you will
be able to see the output. Compare the output to the code and enjoy.
</p>
<p>As always, if you see an error in my documentation please tell me and I
will correct myself in a later document. See corrections at end of
the document to review corrections to the previous articles. </p>
<p><b>WARNING:</b> Copying strings in C is the most dangerous part of
programming in C. C itself doesn't perform bounds checking, so it is
very easy to overwrite the end of a string and actually overwrite other variables
or even to crash the program. Crackers use this weakness in C and inexpert
coding practices to perform controlled overflows to force programs into giving
them a shell to the account that the program is running under. This
is usually root for most servers. </p>
<p>C doesn't really have strings. I know that is a strange thing to
say in a document talking about string handling in C, but it is true.
What C does have is an array of characters. To make space for a string
you can ask the compiler to reserve room for that string. The most
common way is with a simple character array: </p>
<p><tt>char string[17];</tt> </p>
<p>This reserves room for 16 characters and an end-of-string marker. </p>
<p><tt>strcpy ( string, "This is a string" );</tt> </p>
<p>Will work to copy the static string "This is a string" into the space that
we allocated. The static string is composed of 16 characters followed
by the ASCII nil character. So there is plenty of room in the variable
called string to hold the static string. Nil is typically represented
with the number zero or with the character '\0' or with the character '\000'.
</p>
<p>Surprisingly the following will sometimes work as well, even though there
are more then 17 characters copied into the char array: </p>
<p><tt>strcpy ( string, "This is a long string" );</tt> </p>
<p>There is never any bounds checking when you are copying strings.
So even though you went past the end of string and wrote to memory in an
unexpected way, most of the time you can get away with it. Of course
your program can also unexpectedly crash at anytime as well, sometimes in
a place far away from the place where you made your error. Crackers
can get a shell from the computer by overwriting the end of a buffer in such
a way that the program executes a shell. This is one of the reasons
that you should really not use strcpy. Use strncpy instead: </p>
<p><tt>#define MAX_STRING_LENGTH 17</tt> <br>
<tt>char string[MAX_STRING_LENGTH];</tt> <br>
<tt>strncpy ( string, "This is a long string", MAX_STRING_LENGTH );</tt>
<br>
<tt>string[MAX_STRING_LENGTH-1] = '\000';</tt> </p>
<p>The reason that I used a macro for the string length is that I am using
this length in many places in my program, if I ever decide to change the
size of the variable string I would have to find everywhere where I used
the number 17 and fix each one. Sometimes you may use the same number
in different places to mean different things. So even if you only use
a literal number in a few places using a macro can make the meaning of that
number really stand out and it makes it trivial to change the size of the
string buffer in this case. </p>
<p>The reason that I put the last line there is that if the literal string
is longer than the string that we are copying into then the end-of-string
marker isn't put into place. If you don't set the final character
to null, most of the time you will be fine, but every once in a while your
program will crash and you will wonder why. </p>
<p>There is also a third way to define a string and that is with malloc, realloc
and calloc. These functions work by requesting the memory that you
need at runtime. This is the most complicated but also the most flexible
and powerful. </p>
<p><tt>#define STATIC_STRING "This is a long string that will be copied into
a location during runtime"</tt> </p>
<p><tt>char *string;</tt> <br>
<tt>int string_length;</tt> </p>
<p><tt>string_length = strlen(STATIC_STRING);</tt> </p>
<p><tt>if (!(string = (char *) malloc ( string_length ))){</tt> <br>
<tt> /* no memory left, die */</tt> <br>
<tt> exit (1);</tt> <br>
<tt>}</tt> </p>
<p><tt>strncpy( string, STATIC_STRING, string_length);</tt> <br>
<tt>string[string_length] = '\000';</tt> </p>
<p><tt>/* do something with the string */</tt> </p>
<p><tt>free(string);</tt> </p>
<p> </p>
One of the dangers of this method is that you have to clean up after
yourself, using the free function. If you don't free everything when
you are done with then you will be leaking memory and eventually your program
will crash.<br>
<hr noshade>
<p>The <string.h> library has numerous problems. </p>
<p>The biggest problem is that the library was never designed to be complete
and consistent. <string.h> really is a collection of functions
written by various people, assembled into a library and given to the world.
And now we are stuck with it. </p>
<p>Most of the functions can return a NULL or a pointer to a string.
If a function <EM>can</EM> return a NULL, you should always check the return
value after calling it, and take appropriate action if it is NULL. If you
attempt to treat a NULL return value as a pointer to a string, you will quickly
crash your program. </p>
<p> </p>
<hr noshade>
<p>I have arbitrarily grouped the functions into sections according to task,
to show the slight differences between similar functions. One could also
group by string functions vs memory functions, but that seemed less useful.
</p>
<p> </p>
<hr noshade>
<p><b><font size="+1">Copying</font></b> </p>
<ul>
<tt>#include <string.h></tt>
<p><tt>void *memcpy(void *dest, const void *src, size_t n);</tt> <br>
<tt>void *memmove(void *dest, const void *src, size_t n);</tt> <br>
<tt>char *strncpy(char *dest, const char *src, size_t n);</tt> <br>
<tt>char *strcpy(char *dest, const char *src);</tt> <br>
</p>
</ul>
<tt>void *dest</tt> is a pointer to the array which will receive the
copy. <br>
<tt>char *dest</tt> is a pointer to the string which will receive the
copy. <br>
<tt>const void *src</tt> is a pointer to the array from which the
copy will be made. <br>
<tt>const char *src</tt> is a pointer to the string from which the copy
will be made. <br>
<tt>size_t n </tt>is the number of characters to be copied.
<p>These functions all return a pointer to dest. Which is strange, because
you already have a pointer to dest. </p>
<p><b>memcpy</b> copies n characters from the location pointed at by src to
the location pointed at by dest. Don't copy areas that overlap or your
program will crash. </p>
<p><b>memmove</b> also copies n characters from the location pointed at by
src to the location pointed at by dest. But it first copies the characters
to a temporary location then into the final location, so this is the function
to use if you are copying overlapping areas of memory. </p>
<p><b>strncpy</b> copies no more than n characters from the location pointed
at by src to the location pointed at by dest. This function will stop
at the first null character, which may be at any location less than or equal
to n. If n characters are copied and no null is found, no null is written.
This is a great way to leave the end of a string open. You should
always explictly write zero to the end of the string. </p>
<p><b>strcpy</b> copies the string pointed at by src to the location pointed
at by dest, including the ending null character. <b>Warning! Never
use this function for data that comes from the real world !!! </b>
The biggest danger of using this function is that if there is no
null character you will happily go copying through memory until you randomly
find a null or you access memory that doesn't belong to your process and
the process is killed with a SEGV (segfault) signal. Programs can capture this signal
and shutdown, but at this point you are so hosed that it is best just to
let the program core dump. </p>
<p>I have already given a few examples of how to use strcpy and strncpy.
memcpy and memmove are used exactly like strncpy, but they can copy arbitrary
blocks of bytes, not just strings. </p>
<p> </p>
<hr noshade>
<p><b><font size="+1">Concatenation</font></b> </p>
<ul>
<tt>#include <string.h></tt>
<p><tt>char *strcat(char *dest, const char *src);</tt> <br>
<tt>char *strncat(char *dest, const char *src, size_t n);</tt></p>
</ul>
<tt>char *dest </tt> is a pointer to the string which will receive
the copy. <br>
<tt>const char *src</tt> is a pointer to the string from which
the copy will be made. <br>
<tt>size_t n</tt> is the number of characters to be copied. <br>
<p><b>strcat</b> appends the source string, including the final '\0', onto
the end of the destination string. It overwrites the trailing '\0' on the
end of the destination string. </p>
<p><b>strncat</b> does the same, except it will only copy at most n characters
from destination and it will append a '\0'. </p>
<p>Both <b>strcat </b>and <b>strncat</b> return a pointer to the destination
string. Again, there is no bounds checking on the resulting string,
so make sure that the string you create isn't too long to fit in the memory
you have allocated for it. </p>
<p> </p>
<hr noshade>
<p><b><font size="+1">Comparison</font></b> </p>
<ul>
<tt>#include <string.h></tt>
<p><tt>int memcmp(const void *s1, const void *s2, size_t n);</tt> <br>
<tt>int strcmp(const char *s1, const char *s2);</tt> <br>
<tt>int strncmp(const char *s1, const char *s2, size_t n);</tt> <br>
<tt>int strcoll(const char *s1, const char *s2);</tt> <br>
<tt>size_t strxfrm(const char *s1, const char *s2, size_t n);</tt></p>
</ul>
<tt>const char *s1</tt> is a pointer to the first string. <br>
<tt>const void *s1</tt> is a pointer to the first memory array.
<br>
<tt>const char *s2</tt> is a pointer to the second string. <br>
<tt>const void *s2</tt> is a pointer to the second memory array.
<br>
<tt>size_t n</tt> is the number of characters to be copied.
<p><b>memcmp</b> compares the number of bytes given by n. If s1
is less than s2, return a value less than zero. If s1 is equal to s2,
return zero. If s1 is greater than s2, return a value greater than
zero. The comparison is based on the byte values of the ASCII characters
in the memory array. </p>
<p><b>strcmp</b> compares the two strings s1 and s2. A string is a
null terminated array of characters. If s1 is less than s2, return
a value less than zero. If s1 is equal to s2, return zero.
If s1 is greater than s2, return a value greater than zero. The comparison
is based on the byte values of the ASCII characters in the two strings.
</p>
<p><b>strncmp</b> is very similar to memcmp, except that it compares the two
strings, up to the length given by n. If a string is shorter than n,
than the memory locations following n are not compared. If s1
is less than s2, return a value less than zero. If s1 is equal to s2,
return zero. If s1 is greater than s2, return a value greater than
zero. </p>
<p><b>strcoll</b> compares the two strings s1 and s2. If
s1 is less than s2, return a value less than zero. If s1 is equal
to s2, return zero. If s1 is greater than s2, return a value greater
than zero. The comparison is based on the locale that is set with the
setlocale() function in the <locale.h> library. I will cover this
library in a later article. </p>
<p><b>strxfrm</b> transforms string s2 based on the locale category LC_COLLATE.
It then copies n bytes into string s1. Finally it returns the number
of characters actually placed into string s1. If y >= n then there
was an error. </p>
<p> </p>
<hr noshade>
<p><b><font size="+1">Search</font></b> </p>
<ul>
<tt>#include <string.h></tt>
<p><tt>void *memchr(const void *s, int c, size_t n);</tt> <br>
<tt>char *strchr(const char *s, int c);</tt> <br>
<tt>size_t *strcspn(const char *s, const char *reject);</tt> <br>
<tt>size_t *strspn(const char *s, const char *accept);</tt> <br>
<tt>char *strpbrk(const char *s, const char *accept);</tt> <br>
<tt>char *strchr(const char *s, int c);</tt> <br>
<tt>char *strrchr(const char *s, int c);</tt> <br>
<tt>char *strstr(const char *s, const char *substring);</tt> <br>
<tt>char *strtok(char *s, const char *delim);</tt></p>
</ul>
const void *s is the pointer to the array to be searched.<br>
int c is the character to search for.<br>
char *dest is a pointer to the array which will receive the copy.
<br>
const char *src is a pointer to the array from which the copy will
be made. <br>
size_t n is the number of characters to be copied.
<p><b>memchr</b> will search the memory array pointed to by s for character
c, up to n characters, returning a pointer to the first location, or NULL
if the character is not found in the memory array. </p>
<p><b>strcspn</b> returns the length of the beginning of the string s that
contains no characters in the reject string. </p>
<p><b>strspn</b> returns the length of the beginning of the string s that
contains only characters in the accept string. </p>
<p><b>strpbrk</b> returns a pointer to the location of the first character
in string s that matches any character in the accept string. Or a
NULL if c is not found in string s. </p>
<p><b>strchr</b> will search the string pointed to by s for character c, returning
a pointer to the first location, or NULL if the character is not found in
the string. </p>
<p><b>strrchr</b> returns a pointer to the location of the last character
in string s that matches the character represented by integer c. Or
a NULL of c is not found in s. </p>
<p><b>strstr</b> returns a pointer to the location of string substring in
string s, or a NULL if the substring is not found in s. </p>
<p>The <b>strtok</b> man page says that there are a lot of problems with this
function and says to never use the function. <b>strtok </b>takes a
string and divides it up into tokens. The first call to the function
has string s as its first argument and returns the first token. After
the first call the function is called with NULL as the first argument and
the function continues to return each token in turn until a NULL is returned
when there are no more tokens. The delimiter can be changed with each
call, or can be kept the same through all the calls. The limitations
of this function are many; the function modifies the original string
s, the value of the delimiter isn't retained between calls and the function
won't work with constant strings. </p>
<p> </p>
<hr noshade>
<p><b><font size="+1">Miscellaneous</font></b> </p>
<ul>
<tt>#include <string.h></tt>
<p><tt>void *memset(void *s, int c, size_t n);</tt> <br>
<tt>char *strerror(int errnum);</tt> <br>
<tt>size_t *strlen(const char *s);</tt> <br>
</p>
</ul>
void *s <br>
int c <br>
size_t n <br>
int errnum <br>
const char *s
<p><b>memset</b> fills memory array s of size n with the integer value in
c and returns a pointer to memory array s. </p>
<p><b>strerror</b> returns a pointer to the string that describes the errornum
passed as an argument, or an unknown error string if the errnum isn't known.
This works with various other error related functions in the <stdio.h>
and <error.h> libraries that a future article will have to cover in
great depth. </p>
<p><b>strlen</b> returns the number of characters in string s, not including
the '\0' string terminator. </p>
<p> </p>
<hr noshade>
<p><b><font size="+1">Non-Portable Functions</font></b> </p>
<p>The GNU string library has many that the Standard C Library doesn't.
The descriptions are taken out of the man pages cut and paste. If
you want your code to work on any Unix box then don't use these functions.
However, they are a good guide for implementing a function in your own code
that is portable. </p>
<p><tt>int strcasecmp(const char *s1, const char *s2);</tt> </p>
<p><b>strcasecmp</b> compares the two strings s1 and s2, ignoring
the case of the characters. It returns an integer less than,
equal to, or greater than zero if s1 is found, respectively,
to be less than, to match, or be greater than s2. </p>
<p><tt>int strncasecmp(const char *s1, const char *s2, size_t n);</tt> </p>
<p><b>strncasecmp</b> is similar, except it only compares the first n characters
of s1. </p>
<p><b>strcasecmp </b>and <b>strncasecmp</b> return an integer less than,
equal to, or greater than zero if s1 (or the first
n bytes thereof) is found, respectively, to be less than, to match, or be
greater than s2. </p>
<p><tt>char *strdup(const char *s);</tt> </p>
<p>I have implemented this function all on my own without knowing about this
function! I learn something new about Linux everyday. </p>
<p><b>strdup</b> returns a pointer to a new string which is a duplicate of
the string s. Memory for the new string is obtained
with malloc(3), and can be freed with free(3). </p>
<p><b>strdup</b> returns a pointer to the duplicated string, or NULL
if insufficient memory was available. </p>
<p><tt>char *strfry(char *string);</tt> </p>
<p><b>strfry</b> randomizes the contents of string by using rand(3) to randomly
swap characters in the string. The result is an anagram of
string. </p>
<p><b>strfry</b> returns a pointer to the randomized string. </p>
<p><tt>char *strsep(char **stringp, const char *delim);</tt> </p>
<p><b>strsep</b> returns the next token from the string
stringp which is delimited by delim. The token is terminated
with a `\0' character and stringp is updated to point past the token.
Similar to the strtok() function, but is non-portable. </p>
<p><b>strsep</b> returns a pointer to the token, or NULL if delim
is not found in stringp. </p>
<p><tt>char *index(const char *s, int c);</tt> </p>
<p><b>index</b> returns a pointer to the first occurrence of the character
c in the string s. We should probably just use the strchr() function,
it performs the same function in a portable manner. </p>
<p><tt>char *rindex(const char *s, int c);</tt> </p>
<p><b>rindex</b> returns a pointer to the last occurrence of the character
c in the string s. The terminating '\0' character is considered to
be a part of the strings. Please use the Standard C Library function
strrchr(), it performs the exact same function, in a portable manner. </p>
<p><b>index</b> and <b>rindex</b> return a pointer to the matched character
or NULL if the character is not found. </p>
<p> </p>
<hr noshade>
<h3> Corrections to previous articles:</h3>
That's right! I have <b>finally </b>gotten around to publishing
all the accumulated corrections to my previous articles. Just look
at all the mistakes that I have made! My thanks to those who
took the time to e-mail me after noticing a mistake in my articles. <br>
<p><b>Subject: The Standard C Library for Linux,
Part Three"</b> <br>
Date: Wed, 12 Aug 1998 11:27:08
+0200 <br>
From: Lars Hesdorf <hesdorf@ibm.net>
</p>
<p>Hej James M. Rogers </p>
<p>You wrote somewhere in
<A HREF="../issue32/rogers.html">The Standard C Library for Linux, Part Three</A> </p>
<p>"putchar writes a character to standard out. putchar(x) is the same
as <br>
fputc(x, STDIN)" </p>
<p>You probably meant "...fputc(x, STDOUT) </p>
<p>Lars Hesdorf <br>
HESDORF@IBM.NET </p>
<p>Reply: </p>
<p> Actually I think that I even got the capitalization wrong, I believe
that it should be "fputc(x, <b>stdout</b>)" The example program is
correct because I compiled and tested that for correctness. <br>
</p>
<p><b>Subject: The Standard
C Library for Linux, Part Two</b> <br>
Date:
Wed, 04 Aug 1999 21:00:59 +1000 <br>
From:
32000151 <32000151@snetmp.cpg.com.au> <br>
Organization: Student of Computer Power Institute <br>
</p>
<p>Dear Sir, </p>
<p>in <A HREF="../issue31/rogers1.html">The Standard C Library for Linux,
Part Two</A> you wrote </p>
<p>" char *fgets(char *s, int n, FILE *stream); </p>
<p>char *s the string that will hold the result. <br>
int n the maximum number of characters to read. <br>
FILE *stream is an already existing stream. <br>
. <br>
. <br>
. </p>
<p>fgets reads at most n characters from the stream into the string. </p>
<p> char s[1024]; <br>
FILE *stream; <br>
if((stream = fopen ("filename", "r")) != (FILE *)0)
{ <br>
while((fgets(s, 1023, stream)) !=
(char *)0 ) { <br>
<process each line>
<br>
} <br>
} else { <br>
<do fopen error handling>
<br>
} " </p>
<p>but fgets() actually reads up to n-1 characters, so it always has room
<br>
for the \0 (if n is set to the array size). </p>
<p>Tim McCormack <br>
32000151@bran.snetmp.cpg.com.au </p>
<p><b>Reply:</b> <br>
Thanks, I am going to have to make sure that I used this
function correctly in my example program. <br>
</p>
<p><b> Subject: snprintf in Article C Library for Linux?</b> <br>
Date: Tue, 01 Sep 1998 17:53:19 +0200 <br>
From: Renaud Hebert <hebert@bcv01y01.vz.cit.alcatel.fr>
</p>
<p>I didn't know snprintf, but I think that it is a clever thing to <br>
do to avoid overflowing the string buffer (much better than the evil
<br>
sprintf). </p>
<p>But that the first time I see it in a C library, so is-it a Linux only
<br>
function or is-it a "new" standard function which wasn't included in
<br>
HP-UX for example. </p>
<p>Maybe you could distinguish in your article, the standard library <br>
function and those Linux only. </p>
<p>Anyway this snprintf function is "A good Thing" TM. </p>
<p>Thanks for your articles, they are very well-written and very <br>
informative. <br>
-- <br>
__________________________________________________________________ <br>
Renaud HEBERT
CR2A-DI <br>
Software Developer </p>
<p><b>Reply:</b> <br>
I think that it is a GNU only thing. So you may want to
avoid using the snprintf function unless you only want your programs to
work in a GNU environment. I found a bunch of very useful GNU only
string functions and will taking your advice on pointing out those functions
that are only found in Linux. <br>
</p>
<p><b>Subject: Standard
C Programming Library Part 3</b> <br>
Date:
Sun, 20 Sep 1998 09:52:29 -0400 <br>
From:
Laurin Killian <lek@uconect.net> <br>
Organization:
Streamlined Development <br>
</p>
<p>Since you ask for corrections.... <br>
There are a couple of typos in your
<A HREF="../issue32/rogers.html">examples</A>: </p>
<p>------------you wrote: <br>
float x=99.1234; <br>
sprintf(string, "%d", x) <br>
------------should be... <br>
sprintf(string, "%f", x); <br>
^ <br>
------------you wrote: <br>
float x=99.1234; <br>
returnValue=sprintf(string, 4, "%d", x) <br>
------------should be... <br>
returnValue=snprintf(string, 5, "%f", x); <br>
^
^ ^ <br>
(to get the desired result of "99.1" - you need space for the null char)
</p>
<p>All the "scanf" type functions should have ampersands (&): <br>
scanf("%f%2d%d", &float1, &int1, &int2); </p>
<p>Hope this helps <br>
-Laurin </p>
<p><b>Reply:</b> <br>
Helps a lot, thank you! <br>
</p>
<p><b>Subject: character handling program</b>
<br>
Date: Mon, 15 Mar 1999 13:31:41
+0100 <br>
From: jorgen.tegner@sundsdefibrator.com
</p>
<p>Hi, </p>
<p>your code in Linux gazette is missing the setlocale() function call at
the <br>
beginning. That´s why you don´t get any <br>
useful results for characters above 127 as programs start out in the
C locale by <br>
default. Also, isalpha(), toupper() <br>
and tolower() are not restricted to the A-Za-z range. </p>
<p>Regards, <br>
Jörgen Tegnér </p>
<p><b>Reply:</b> <br>
Absolutely right, I am saving setlocale() for when I cover <locale.h>.
:) </p>
<p> </p>
<hr noshade>
<h4> Bibilography:</h4>
<i>The ANSI C Programming Language, Second Edition</i>, Brian W. Kernighan,
Dennis M. Ritchie, Printice Hall Software Series, 1988
<p><i>The Standard C Library</i>, P. J. Plauger, Printice Hall P T R, 1992
</p>
<p><i>The Standard C Library, Parts 1, 2, and 3</i>, Chuck Allison, <i>C/C++
Users Journal</i>, January, February, March 1995 </p>
<p>STRING(3), BSD MANPAGE, <i>Linux Programmer's Manual</i> <br>
</p>
<hr noshade>
<center> <i>
<h4>Previous "The Standard C Library for Linux" Articles</h4>
</i></center>
<i> <a href="../issue24/rogers.html">The Standard
C Library for Linux, stdio.h, January 1998</a><br>
<a href="../issue31/rogers1.html">The Standard
C Library for Linux, stdio.h, August 1998</a><br>
<a href="../issue32/rogers.html">The Standard
C Library for Linux, stdio.h, September 1998</a><br>
<a href="../issue38/rogers.html">The Standard
C Library for Linux, ctype.h, March 1999</a><br>
<a href="../issue39/rogers.html">The Standard
C Library for Linux, stdlib.h, April 1999</a><br>
<a href="../issue41/rogers.html">The Standard
C Library for Linux, assert.h, May 1999</a><br>
</i> <br>
<!-- *** BEGIN bio *** -->
<SPACER TYPE="vertical" SIZE="30">
<P>
<H4><IMG ALIGN=BOTTOM ALT="" SRC="../gx/note.gif">James Rogers</H4>
<EM>James Rogers is a systems programmer specializing in the area of Cloverleaf
HL7 routers. He is also currently working on an open source library of HL7
routines. He hopes to use this library to write an open source HL7
interface engine.</EM>
<!-- *** END bio *** -->
<!-- *** BEGIN copyright *** -->
<P> <hr> <!-- P -->
<H5 ALIGN=center>
Copyright © 2002, James M Rogers.<BR>
Copying license <A HREF="../copying.html">http://www.linuxgazette.com/copying.html</A><BR>
Published in Issue 76 of <i>Linux Gazette</i>, March 2002</H5>
<!-- *** END copyright *** -->
<H4 ALIGN="center">
"Linux Gazette...<I>making Linux just a little more fun!</I>"
</H4>
<P> <HR> <P>
<!--===================================================================-->
<center>
<H1><font color="maroon">Writing Documentation, Part IV: Texinfo</font></H1>
<H4>By <a href="mailto:cspiel@hammersmith-consulting.com">Christoph Spiel</a></H4>
</center>
<P> <HR> <P>
<!-- END header -->
<a name="texinfo"></a>
<p>Texinfo is the documentation system preferred by GNU projects.</p>
<p>The major design goal of the Texinfo format is to produce high quality
printed output as well as online browsable output from the same source
(<em>.texi</em>) file. Texinfo obtains the basis for a high quality hardcopy
with a trick: it builds on plain TeX and adapts it by reading the
file <em>texinfo.tex</em> (Your system might have more than one copy of
this file. Check that you are really using a recent version (2002-01-04.07 as
of this writing)). <em>texinfo.tex</em> does all the necessary formatting
setup. It extends TeX to recognize hyper-references and all the gizmos that is
needed for online documentation. Rendered for online viewing, Texinfo source
yields Info (<em>.info</em>) files.</p>
<h3><a name="info what's that">Info? What's that?</a></h3>
<p>Info is an ASCII file format suitable for browsing hyperlinked documents.
It is intended to be portable to all platforms which run GNU applications.
Info focuses on textual data; this is, all Info files are viewable from a text
console. High resolution graphics are available only in printed output. Thus,
Info is the GNU counterpart of HTML minus some graphical extras. However, <a
href="#item_texi2html"><code>texi2html(1)</code></a> transforms Texinfo
sources (<em>.texi</em>) directly into HTML; see the section on <a href=
"#browsers">Browsers</a>.</p>
<h3><a name="document structure">Document Structure</a></h3>
<p>Since Texinfo is based on TeX (see my second article in this series,
"<a href=
"../issue74/spiel.html">LaTeX with latex2html</a>"),
we expect to see again a header-body division. Also, the support for
hyperlinks calls for additional structuring that we will meet in the form of
so-called nodes.</p>
<h4><a name="overall structure">Overall Structure</a></h4>
<p>Every Texinfo document starts by reading <em>texinfo.tex</em> with the
plain TeX command <code>\input</code>. This is about the only place where
plain TeX leaks into Texinfo. The part of the file from the inclusion of
<em>texinfo.tex</em> up to the so called Top node -- more on nodes later -- is
the document's header. The Top node opens up the body of the document, which
extends to the closing command <code>@bye</code>.</p>
<p>All Texinfo commands are introduced with an ``<code>@</code>''-character.
The at-character is followed by one or more letters. Only a few commands require
curly braces to group together their arguments. We have already encountered
the end-of-document command <code>@bye</code>. The following example of a
minimal Texinfo file introduces the comment command, which is <code>@c</code>.
Texinfo comments extend to the end of the line in which they are given.</p>
<blockquote><code>\input texinfo<br>
<br>
<br>
@c === header ===<br>
...<br>
<br>
<br>
@c === body ===<br>
<br>
@c --- Top Node ---<br>
...<br>
<br>
@c --- Sub Nodes ---<br>
...<br>
<br>
<br>
@bye</code></blockquote>
<h4><a name="header">Header</a></h4>
<p>The header of a Texinfo file is optional, but it appears in all documents.
It at least contains the name of the online-reading output file, and the title
used in the printed output.</p>
<p>The output filename is set with the command <code>@setfilename</code>
<em>output-filename</em>. I recommend adding the extension <em>.info</em> to
<em>output-filename</em>, because files without an extension are harder to access
with common shell tools--just think of <code>ls *.info</code>! The argument of
<code>@setfilename</code> reaches right to the end of the line, thus you
cannot add a comment after setting the output filename. Bummer!</p>
<p>Set the document title with
<code>@settitle</code> <em>document-title</em>. Again, the argument
stretches until the end of the line. The title -- as defined by
<code>@settitle</code> -- is used for page headers or footers in the printed
output. It has nothing to do with the document title used on the title page
(if a title page exists at all).</p>
<p>Thus, a simple header looks like this:</p>
<pre>
@setfilename example.info
@settitle Texinfo Example
</pre>
<p>Other useful commands in the header are:</p>
<ul>
<li>@afourpaper and @afourwide
<p>By default Texinfo assumes a paper size of 8.5" by 11". Outside
Northern America, paper sizes are chosen according to DIN (DIN is the
abbreviation for ``Deutsche Industrie Norm'', ``German Industry Standard'' in
English). The commands <code>@afourpaper</code> and
<code>@afourwide</code> adjust the printable area for sheets of size
DIN A4, where <code>@afourwide</code> selects a somewhat larger printable
area; it does not switch to landscape.</p>
<p><em>Tip:</em> It is a good plan to inspect the paper size settings of any
foreign Texinfo document before you send it to the printer.</p>
</li>
<li>@setchapternewpage on | off | odd
<dl>
<dt><strong><a name="item_on">on</a></strong><br>
</dt>
<dd>Start a new page for each chapter. Format page headers and footers for
single-sided printing. This is the default setting.</dd>
<dt><strong><a name="item_off">off</a></strong><br>
</dt>
<dd>Do not start a new page for a new chapter; just insert some white space
before the new chapter. Format page headers and footers for single-sided
printing.</dd>
<dt><strong><a name="item_odd">odd</a></strong><br>
</dt>
<dd>Start new chapters on odd-numbered pages. Format page headers and footers
for double-sided (``recto verso'') printing.</dd>
</dl>
<p>Note that no <code>@setchapternewpage even</code> command is
defined.</p>
</li>
<li>@paragraphindent asis | <em>number</em>
<dl>
<dt><strong><a name="item_asis">asis</a></strong><br>
</dt>
<dd>Do not change indentation</dd>
<dt><strong><a name="item_number"><em>number</em></a></strong><br>
</dt>
<dd>Indent the first line of each paragraph by <em>number</em> spaces,
where <em>number</em> can be zero.</dd>
</dl>
</li>
</ul>
<p>Tip: All GNU development projects ship with documentation in Texinfo
format. If you want to print the documentation on your local output device, it
is a good plan to modify the header of the Texinfo files to match your paper
size (Letter, A4) and printing equipment (duplex unit, and so on).</p>
<h4><a name="body">Body</a></h4>
<p>The body of a Texinfo document is a mixture of sectioning commands for
printing (the TeX part: chapters, sections, sub-sections, and so on) and
grouping commands for online viewing (the Info part: nodes). In theory both
parts can impose different structures on the document, however this would
seriously confuse readers -- probably not what you want when writing technical
documentation.</p>
<p>I will present a simplified way of writing the body, where the structure of
the online version and of the printed version closely go together. This saves
the writer the headaches of manually setting up the structure for the online
version at the price of sacrificing some additional navigation possibilities.
The simplified way requires pairing the Info structure information with that
of the printed version.</p>
<p>The Info structure is defined with
<code>@node</code> <em>node-name</em> commands, whereas the printed
structure is given -- among others -- with the
commands <code>@chapter</code> <em>chapter-title</em>,
<code>@section</code> <em>section-title</em>, and
<code>@subsection</code> <em>subsection-title</em>. The
<code>@node</code> command always goes first. So we get, for example,</p>
<pre>
@node Introduction
@chapter Introduction
</pre>
<p>or</p>
<pre>
@node Iterative-Processes
@section Iterative Processes
</pre>
<p>or</p>
<pre>
@node Numerical Stability
@subsection Numerical Stability of Iterative Algorithms
</pre>
<p>The argument to <code>@node</code>, assigns the
name <em>node-name</em> to the node. The name consists of one or more
words. Spaces are perfectly valid in <em>node-name</em>, but
periods ``<code>.</code>'', commas ``<code>,</code>'',
colons ``<code>:</code>'', and apostrophes ``<code>'</code>'' are
not. It is also better to avoid commands (anything starting with
``<code>@</code>'') in a node name. Case of node-names is significant. Within
a Texinfo document each node must have a unique name. By convention, node
names are capitalized just as chapter or section titles are.</p>
<p>A node either contains only data (this is, text, tables, images, and
cross-references), or a node defines a navigation menu. I call the former a
Terminal Nodes and the latter a Menu Nodes.</p>
<dl>
<dt><strong><a name="item_Terminal_Node">Terminal Node</a></strong><br>
</dt>
<dd>The structure of a Terminal Node is
<blockquote><code>@node</code> <var>node-name</var><br>
<code>@section</code> <var>section-title</var><br>
<br>
<var>text-for-node-and-chapter</var></blockquote>
<p>where I use <code>@section</code> as an example for a sectioning
command.</p>
<p>Terminal Nodes are the ``meat'' of a document. They hold all the
visible information. <em>text-for-node-and-chapter</em> usually consists of
one or more paragraphs, tables, and so on.</p>
</dd>
<dt><strong><a name="item_Menu_Node">Menu Node</a></strong><br>
</dt>
<dd>Menu nodes provide decentralized tables of contents, this is meta
information, from which you can jump to any of the topics referred to in the
menu.
<p>The structure of a Menu Node is the same as for a Terminal Node,
with the exception that a Menu Node is ended by the definition of a
navigation menu. The navigation menu only goes into the Info version, never
into the printed one.</p>
<blockquote><code>@node</code> <var>node-name</var><br>
<code>@chapter</code> <var>chapter-title</var><br>
<br>
<var>optional-introductory-text-for-node-and-chapter</var><br>
<br>
<code>@menu</code><br>
<code>*</code> <var>Node name of first section</var><code>::</code>
<var>Synopsis of first section</var><br>
<code>*</code> <var>Node name of second section</var><code>::</code>
<var>Synopsis of second section</var><br>
...<br>
<code>*</code> <var>Node name of last section</var><code>::</code>
<var>Synopsis of last section</var><br>
<code>@end menu</code></blockquote>
<p>A navigation menu is bracketed by</p>
<blockquote><code>@menu</code><br>
<br>
<code>@end menu</code></blockquote>
<p>where every line in between makes up one menu entry. Each menu entry starts
with an asterisk ``<code>*</code>'' followed by the name of the node it
points to (the target node's name). It is ended by two colons
``<code>::</code>'' and an optional short description of the target:</p>
<p><code>*</code> <em>Target Node Name</em><code>::</code> <em>Optional
description of target node</em></p>
</dd>
<dt><strong><a name="item_Top_Node">Top Node</a></strong><br>
</dt>
<dd>One menu node in every Texinfo document plays a special role: the master
menu node from which the rest of the document is accessed. This root node is
called <code>Top</code> node; we define it with the pair
<blockquote><code>@node Top</code><br>
<code>@top</code> <var>name-of-top-node</var></blockquote>
<p>As the Top node will appear first whenever the online version is browsed
(unless you explicitly specify a node to start browsing with), you want to
have some introductory text to go with it. This introduction often is not
suited for the printed version. The printed version shows no menus at all,
remember? Thus, we want to exclude the introductory text from the printed
version, which is done with the <a href=
"#conditional_translation">conditional translation</a> command pair
<code>@ifinfo</code> and <code>@end ifinfo</code>. A simple Top node then
looks like this:</p>
<blockquote><code>@ifinfo</code><br>
<code>@node</code> Top<br>
<code>@top</code> Example<br>
This is an example Texinfo document.<br>
<br>
<code>@end ifinfo</code><br>
<br>
<code>@menu</code><br>
<code>*</code> Name of first chapter<code>::</code> Synopsis of first
chapter<br>
<code>*</code> Name of second chapter<code>::</code> Synopsis of second
chapter<br>
<code>*</code> Name of third chapter<code>::</code> Synopsis of third
chapter<br>
<code>@end menu</code></blockquote>
</dd>
</dl>
<p>Now we are ready to write a complete Texinfo document.</p>
<pre>
\input texinfo
</pre>
<pre>
@setfilename example.info
@settitle Texinfo Example
</pre>
<pre>
@ifinfo
@node Top
@top Example
</pre>
<pre>
This is an example Texinfo document.
@end ifinfo
</pre>
<pre>
@menu
* Introduction:: Definitions, Measures, Complexity
* Evaluation of Polynomials:: Study of a common operation
@end menu
</pre>
<pre>
@node Introduction
@chapter Introduction
</pre>
<pre>
In this chapter I define the concepts that will be used throughout the
rest of the document. Moreover, measures of efficiencies as well as
bounds of complexity will be introduced.
</pre>
<pre>
@menu
* Definitions:: Fundamental stuff
* Measures of Efficiency:: How to measure efficiency
* Bounds of Complexity:: Typical bounds of complexity
@end menu
</pre>
<pre>
@node Definitions
@section Definitions
</pre>
<pre>
...
</pre>
<pre>
@node Measures of Efficiency
@section Measures of Efficiency
</pre>
<pre>
...
</pre>
<pre>
@node Bounds of Complexity
@section Bounds of Complexity
</pre>
<pre>
...
</pre>
<pre>
@node Evaluation of Polynomials
@chapter Evaluation of Polynomials
</pre>
<pre>
...
</pre>
<pre>
@bye
</pre>
<h3><a name="syntax">Syntax</a></h3>
<p>As we have already seen, Texinfo commands start with an at-sign
``<code>@</code>''. The at-sign is either followed by a single non-letter
character or one or more characters. Some commands of the first group
include</p>
<dl>
<dt><strong><a name="item_%40%40"><code>@@</code></a></strong><br>
</dt>
<dd>Insert a literal at-sign (``<code>@</code>'').</dd>
<dt><strong><a name=
"item_%40%22character"><code>@"</code><em>character</em></a></strong><br>
</dt>
<dd>Typeset the umlaut equivalent of <em>character</em>, where
<em>character</em> is a single ASCII character like, for example, ``a''. The
same holds for accented (<code>@'</code><em>character</em>), circumflexed
(<code>@^</code><em>character</em>), or cedilla decorated
(<code>@,</code><em>character</em>) characters. See node
``Inserting Accents'' in the Texinfo documentation for details.</dd>
</dl>
<p>and some in the latter group are</p>
<dl>
<dt><strong><a name="item_%40contents">@contents</a></strong><br>
</dt>
<dd>Insert the table of contents where @contents occurs.</dd>
<dt><strong><a name="item_%40page">@page</a></strong><br>
</dt>
<dd>Start a new page.</dd>
<dt><strong><a name="item_%40findex_function%2Dname">@findex
<em>function-name</em></a></strong><br>
</dt>
<dd>Generate an index entry for <em>function-name</em> in the index of all
functions.</dd>
</dl>
<p>Depending on the command, no argument, one argument, or more than one
argument may be required. Some commands require their arguments to be enclosed
on curly braces, like cross references,
<code>@xref{</code><em>node-name</em><code>,</code>
<em>cross-reference-name</em><code>,</code>
<em>title-or-topic</em><code>}</code>. We have seen commands which take rest
of the line as their arguments (for example <code>@setfilename</code>).</p>
<h3><a name="sectioning">Sectioning</a></h3>
<p>As with TeX, we just type text, separating paragraphs with blank lines.
Paragraphs will be filled or even justified depending on the used translation
tools.</p>
<p>Section <a>Body</a> has introduced the main sectioning commands.
<code>@node</code> groups the input together in chunks for online reading. An
accompanying TeX-like sectioning command does the same for the printed output.
In particular Texinfo offers the following sectioning commands:
<code>chapter</code>, <code>section</code>, <code>subsection</code>, and
<code>subsubsection</code>.</p>
<p>Please remember that -- for a simplified node management -- each
<code>@node</code> must be followed by one of the sectioning commands for the
printed version.</p>
<h3><a name="title page">Title Page</a></h3>
<p>Making a decent title page is easy. The
<code>@titlepage</code> command with its sub-commands
<code>@title</code>, <code>@subtitle</code> (optional), and
<code>@author</code> completely takes care of the layout. If you want the
material after the title to go on an odd page add a page
break <a><code>@page</code></a> right before
<code>@end titlepage</code>.</p>
<p>Example:</p>
<pre>
@titlepage
@title A Texinfo Example Document
@subtitle Playing With the Texinfo Format
@author Joanne H. Acker
@page @c -- force odd page
@end titlepage
</pre>
<h3><a name="conditional_translation">Conditional Translation</a></h3>
<p>In the section on the <a href="#item_Top_Node">Top Node</a>, we encountered the
condition translation
command <code>@ifinfo</code>/<code>@end info</code>. Conditional
translation means directing parts of a document to one translator only, or, in
the negated form <code>@ifnotinfo</code>/<code>@end notinfo</code>, excluding
one translator (makeinfo in our example) from processing a chunk of the
document.</p>
<p>The opening (<code>@if</code><em>format</em>) and closing sequence
(<code>@end</code> <em>format</em>) should appear on lines by themselves.</p>
<p>Three conditionals are available in positive and negative form for
diverting data to or away from Info, TeX and HTML.</p>
<pre>
@iftex
...
@end tex
</pre>
<pre>
@ifinfo
...
@end info
</pre>
<pre>
@ifhtml
...
@end html
</pre>
<pre>
@ifnottex
...
@end nottex
</pre>
<pre>
@ifnotinfo
...
@end notinfo
</pre>
<pre>
@ifnothtml
...
@end nothtml
</pre>
<h3><a name="lists">Lists</a></h3>
<p>Texinfo features the fundamental types of lists, which any author expects:
itemized and enumerated lists. Description lists are written in terms of
tables.</p>
<p>All lists nest.</p>
<p>Command <code>@item</code> starts an entry in a list or table. The
entry can comprise several paragraphs or further lists. Did I tell you that
all lists nest? They do!</p>
<dl>
<dt><strong><a name="item_Itemized_Lists">Itemized Lists</a></strong><br>
</dt>
<dd>
<blockquote><code>@itemize</code> <var>glyph</var><br>
<code>@item</code> <var>Text for first item</var><br>
<code>@item</code> <var>Text for second item</var><br>
...<br>
<code>@item</code> <var>Text for last item</var><br>
<code>@end itemize</code></blockquote>
<p>Symbol <em>glyph</em> will be put in front of every item. Useful
values for <em>glyph</em> are <code>@bullet</code>, <code>@minus</code>, and
<code>*</code>.</p>
</dd>
<dt><strong><a name="item_Enumerated_Lists">Enumerated Lists</a></strong><br>
</dt>
<dd>
<blockquote><code>@enumerate</code> <var>counter-selector</var><br>
<code>@item</code> <var>Text for first item</var><br>
<code>@item</code> <var>Text for second item</var><br>
...<br>
<code>@item</code> <var>Text for last item</var><br>
<code>@end enumerate</code></blockquote>
<p><em>counter-selector</em> selects the type of counter (numeral or letter)
and the starting value. If <em>counter-selector</em> is omitted, the list will
be decorated with Arabic numerals starting at one.</p>
<p>A positive integer value for <em>counter-selector</em> starts the list at
the given value. This is useful when continuing a list. An uppercase or
lowercase letter for <em>counter-selector</em> selects letters for the
enumeration; again, the list starts with the given letter.</p>
<p>Texinfo cannot render enumerate lists with Roman numerals.</p>
</dd>
<dt><strong><a name="item_Description_Lists">Description
Lists</a></strong><br>
</dt>
<dd>I have mentioned that Texinfo does not offer native description lists, but
emulates typesetting them with two-column tables. So, we get the following
syntax for description lists:
<blockquote><code>@table</code> <var>format-selector</var><br>
<code>@item</code> <var>First term</var><br>
<var>Description for first item</var><br>
<code>@item</code> <var>Second term</var><br>
<var>Description for second item</var><br>
...<br>
<code>@item</code> <var>Last term</var><br>
<var>Description for last item</var><br>
<code>@end table</code></blockquote>
<p><em>format-selector</em> determines how the terms are typeset. For no added
markup, this is, plain description lists, use <code>@asis</code> as
<em>format-selector</em>. If you have code, sample input or output, variables,
or keystrokes as terms, use <code>@code</code>, <code>@samp</code>,
<code>@var</code>, or <code>@kbd</code> respectively. See
section <a>Inline Markup</a> for how to markup specific items.</p>
<p>Within a table, the argument to <code>@item</code> is all the text from
<code>@item</code> to the end of the line. Note that this is different from
itemized and enumerated lists! Thus, the term in a "description list" can only
be a single line. The text after the <code>@item</code>-line up to the next
<code>@item</code> or the end of the table becomes the term's description. The
description can be several paragraphs long and it can contain other lists, and
so on.</p>
<p>Sometimes we need additional terms on separate lines. Because
<code>@item</code> puts its argument on a single lines, another command is
required: <code>@itemx</code> places an additional term right below an
existing term. <code>@itemx</code> is only valid directly after an
<code>@item</code> command or <code>@itemx</code> command.</p>
</dd>
</dl>
<h3><a name="crossreferences">Cross-References</a></h3>
<p>Texinfo supports a variety of cross reference types: with or without
additional text, within the same file, across different Texinfo files, and to
the outside world.</p>
<p>Nodes are the primary targets of cross references.
<code>@anchor{</code><em>anchor-name</em><code>}</code> marks additional
targets. Command <code>@anchor</code> does not produce any output. The names
of anchors must not conflict with node names.</p>
<dl>
<dt><strong><a name="item_%40xref">@xref</a></strong><br>
</dt>
<dd>Insert a decorated cross reference. @xref formats the decoration for the
start of a sentence.
<p>Example usage:</p>
<pre>
... is the basis for several multi-point
methods. @xref{Multi-point Methods}. We
study the single point method ...
</pre>
</dd>
<dt><strong><a name="item_%40pxref">@pxref</a></strong><br>
</dt>
<dd>@pxref behaves like @xref, but it is meant to be used inside parenthesis.
<p>Example usage:</p>
<pre>
The algorithm fails at higher order
roots (@pxref{Higher Order Root}) and
ill-conditioned roots of order one.
</pre>
</dd>
<dt><strong><a name="item_%40ref">@ref</a></strong><br>
</dt>
<dd>Inserts an undecorated cross reference. Otherwise it behaves like
@xref.</dd>
</dl>
<p>Until now we have only used the one-argument form of the cross referencing
commands. However, they accept up to five parameters. Here is how the output
changes with the number of parameters. I demonstrate the flexible usage with
@xref.</p>
<dl>
<dt><strong><a name="item_One_Argument">One Argument</a></strong><br>
</dt>
<dd><code>@xref{</code><em>target-name</em><code>}</code>
<p>produces</p>
<p><code>*Note</code> <em>target-name</em><code>::</code></p>
<p>in the Info version and</p>
<p><code>See Section</code> <em>target-section</em>
<code>[</code><em>target-name</em><code>],</code> <code>page</code>
<em>target-page</em></p>
<p>in the printed version, where <em>target-section</em> and
<em>target-page</em> are the section number and the page number where the
target lives in the printed version.</p>
</dd>
<dt><strong><a name="item_Two_Arguments">Two Arguments</a></strong><br>
</dt>
<dd><code>@xref{</code><em>target-name</em><code>,</code>
<em>cross-reference-name</em><code>}</code>
<p>produces:</p>
<p><code>*Note</code> <em>cross-reference-name</em><code>:</code>
<em>target-name</em></p>
<p>and</p>
<p><code>See Section</code> <em>target-section</em>
<code>[</code><em>target-name</em><code>],</code> <code>page</code>
<em>target-page</em></p>
</dd>
<dt><strong><a name="item_Three_Arguments">Three Arguments</a></strong><br>
</dt>
<dd><code>@xref{</code><em>target-name</em><code>,</code>
<em>cross-reference-name</em><code>,</code>
<em>title-or-topic</em><code>}</code>
<p>produces:</p>
<p><code>*Note</code> <em>cross-reference-name</em><code>:</code>
<em>target-name</em></p>
<p>and</p>
<p><code>See Section</code> <em>target-section</em>
<code>[</code><em>title-or-topic</em><code>],</code> <code>page</code>
<em>target-page</em></p>
</dd>
<dt><strong><a name="item_Five_Arguments">Five Arguments</a></strong><br>
</dt>
<dd><code>@xref{</code><em>target-name</em><code>,</code>
<em>cross-reference-name</em><code>,</code>
<em>title-or-topic</em><code>,</code> <em>info-file-name</em><code>,</code>
<em>printed-manual-title</em><code>}</code>
<p>produces:</p>
<p><code>*Note</code> <em>cross-reference-name</em><code>:</code>
<code>(</code><em>info-file-name</em><code>)</code><em>target-name</em></p>
<p>and</p>
<p><code>See section</code>
<code>"</code><em>title-or-topic</em><code>"</code> <code>in</code>
<em>printed-manual-title</em></p>
</dd>
</dl>
<h3><a name="inline markup">Inline Markup</a></h3>
<p>Texinfo defines a whole bunch of commands to markup special parts of text
as being code, input from the user, a filename, and so on.</p>
<ul>
<li><code>@emph{</code><em>text-in-italics</em><code>}</code>
<p>Render <em>text-in-italics</em> in italics. Info approximates italicization
with underscores that bracket <em>text-in-italics</em>.</p>
<p>Example:</p>
<pre>
Use tex(1), @emph{not} latex(1) to process
your Texinfo files.
</pre>
</li>
<li><code>@strong{</code><em>bold-text</em><code>}</code>
<p>Render <em>bold-text</em> in boldface. Info approximates boldface with
asterisks that bracket <em>bold-text</em>.</p>
<p>Example:</p>
<pre>
Info files @strong{cannot} contain high
resolution graphics.
</pre>
</li>
<li><code>@file{</code><em>filename</em><code>}</code>
<p>Make <em>filename</em> stand out by surrounding it with single quotes, like
<code>`filename'</code>. The printer version typesets <em>filename</em> in
typewriter font.</p>
<p>Example:</p>
<pre>
Ensure the latest version of
@file{texinfo.tex} is installed on your Linux box.
</pre>
</li>
<li><code>@url{</code><em>universal-resource-locator</em><code>}</code>
<p>Identify a universal resource locator (URL). The online version will show
angle brackets around <em>universal-resource-locator</em>. The printed version
does not add angle brackets, but typesets <em>universal-resource-locator</em>
in typewriter font.</p>
<p>Example:</p>
<pre>
More information on Texinfo can be
found at @url{<a href="http://texinfo.org/">http://texinfo.org/</a>}.
</pre>
</li>
<li><code>@code{</code><em>program-code</em><code>}</code>
<p>Mark up short pieces of program code.</p>
<pre>
Prefer the two-argument form of
@code{bless}, this is, always write
@code{bless $objref, $class}.
</pre>
</li>
<li><code>@samp{</code><em>literal-text</em><code>}</code>
<p>Mark up literal characters, literal text, symbol names, and so on.</p>
<pre>
Angle brackets (@samp{<}, @samp{>}) are the
main delimiters used in HTML.
</pre>
</li>
<li><code>@var{</code><em>replaceable-item</em><code>}</code>
<p>Mark up meta-syntactic variables, the famous <code>foo</code> and
<code>bar</code>.</p>
<pre>
The Perl command @code{bless} is best called
with two arguments, like @code{bless
@var{object_reference}, @var{classname}}.
</pre>
</li>
<li><code>@kbd{</code><em>keystrokes</em><code>}</code>
<p>Mark up a single keystroke or a series of keystrokes.</p>
<pre>
Within emacs, type @kbd{C-h i} to start the
built-in Info browser, or type @kbd{M-x
info}.
</pre>
</li>
<li><code>@command{</code><em>command-name</em><code>}</code>
<p>Mark up a command name.</p>
<pre>
The two most important shell commands are
@command{ls} and @command{cd}.
</pre>
</li>
<li><code>@option{</code><em>option-name</em><code>}</code>
<p>Mark up an option name. Use <code>@option</code> in running text like</p>
<pre>
Option @option{--html} forces
@command{makeinfo} to generate HTML output
instead of Info.
</pre>
<p><code>@option</code> is not suited for marking up a command's synopsis. To
mark up a synopsis use the <code>@example</code>-environment. Say</p>
<pre>
@example
makeinfo --html --output=@var{output-filename} @var{input-filename}
@end example
</pre>
<p>and refer to the options in the running text with
<code>@option{--html}</code> and <code>@option{--output}</code>, as well as to
the arguments <code>@var{output-filename}</code> and
<code>@var{input-filename}</code>.</p>
</li>
</ul>
<h3><a name="tools">Tools</a></h3>
<dl>
<dt><strong><a name="item_makeinfo">makeinfo</a></strong><br>
</dt>
<dd>makeinfo transforms Texinfo files (<em>.texi</em>) into
<ol>
<li>Info
<p>By default, makeinfo generates Info files with the filename selected by
<code>@setfilename</code>. Option <code>--no-split</code> prevents
makeinfo from breaking the output in chunks (approximately 50KB in size).</p>
<p>Processing a Texinfo file with makeinfo also thoroughly validates the input
file.</p>
</li>
<li>Plain ASCII
<p>Option <code>--no-headers</code> makes makeinfo generate plain ASCII
files. Plain ASCII is a useful format for proofreading the online version and
also for applying spelling checkers like, for example, diction(1).</p>
</li>
</ol>
</dd>
<dt><strong><a name="item_texi2html">texi2html</a></strong><br>
</dt>
<dd>As you might have guessed from the command's name, texi2html transforms
Texinfo into HTML. Option <code>-monolithic</code> forces the output of a
single file. Option <code>-split</code> on the other hand forces one file
per node.
<p>texi2html by default converts <code>@iftex</code> sections and not
<code>@ifinfo</code> ones. You can reverse this behavior with the
<code>-expandinfo</code> option.</p>
<p>Note that all of texi2html's options start with a single dash.</p>
</dd>
<dt><strong><a name="item_texi2dvi">texi2dvi</a></strong><br>
</dt>
<dd>Produce a device independent file <em>.dvi</em> form Texinfo source.
To get Postscript, apply <code>dvips(1)</code> to the <em>.dvi</em> file.
I have found the options <code>--clean</code> and <code>--quiet</code> useful.
The first removes all intermediate files, leaving only the final
<em>.dvi</em> file. The second suppresses all non-essential messages
(``No gnews is good gnews!'').</dd>
<dt><strong><a name="item_texi2pdf">texi2pdf</a></strong><br>
</dt>
<dd>texi2pdf makes a Portable Document File (<em>.pdf</em>) from Texinfo
source in one shot. It accepts the same options as texi2dvi does. However, I
found, it definitely wants to see option <code>--pdf</code> or it stops,
crying for a <em>.dvi</em> file even if this very file exists. Argh! So,
my typical calls are
<pre>
texi2pdf --quiet --clean --pdf foobar.texi
</pre>
</dd>
</dl>
<h3><a name="browsers">Browsers</a></h3>
<p>Texinfo differs from all the document preparation systems that we have had
a look at so far, for Texinfo can be translated in an online viewing format
different from HTML, namely: Info. Having an online viewing format, we need
browsers to actually view it!</p>
<dl>
<dt><strong><a name="item_info">info</a></strong><br>
</dt>
<dd>
<p><code>info</code>, the mother of all Info browsers, is a simple but
efficient browser for <a href="misc/spiel/info-screenshot.png">viewing Info
files</a> at a console.</p>
<p>To view the Info pages of <em>topic</em>, use</p>
<pre>
info topic
</pre>
<p>To browse Info file <em>info-file</em>, add
<code>--file=</code><em>info-file</em> to the invocation of info, where
<em>info-file</em> contains the complete path to the Info file.</p>
<p>If you would like to start browsing at specific
node <em>node-name</em>, add <code>--node=</code><em>node-name</em>.</p>
<p>My favorite mistake is mixing up <em>topic</em> with <em>info-file</em>,
this is saying</p>
<pre>
info ./cache-profiler.info
</pre>
<p>when I really mean</p>
<pre>
info --file=./cache-profiler.info
</pre>
</dd>
<dt><strong><a name="item_pinfo">pinfo</a></strong><br>
</dt>
<dd>
<p>pinfo is a <code>curses(3)</code> based Info browser with
<code>lynx(1)</code> like navigation. pinfo does a <a href=
"misc/spiel/pinfo-screenshot.png">nice job colorizing</a> Info pages.</p>
</dd>
<dt><strong><a name="item_emacs">emacs</a></strong><br>
</dt>
<dd>
<p>Emacs version 21.x features an improved Info browsing mode as proves this
<a href="misc/spiel/emacs-screenshot.png">screen shot</a>.</p>
<blockquote><em>I know, it's only Emacs Info, but I like it, like it! Yes, I
do!</em></blockquote>
<p>You browse the installed Info documents (`<code>C-h i</code>', <a href=
"#item_info"><code>info</code></a>). Or you load an Info file into Emacs and
turn the buffer an Info-browser with <code>Info-on-current-buffer</code> (note
the capital "I"). If you dislike switching between the Info buffer and you
working buffers, open the file to browse in another frame (`<code>C-x 5
f</code>', <code>find-file-other-frame</code>). To open a new frame with an
Info browser in it, switch to the <code>*info*</code> buffer in your
current emacs and issue <code>view-buffer-other-frame</code>.</p>
<p>For additional browsing pleasure, try
<code>Info-speedbar-browser</code>.</p>
</dd>
<dt><strong><a name="item_xinfo">xinfo</a></strong><br>
</dt>
<dd>xinfo is an ancient Info browser for the use under X11. It does not do any
colorization. What bothers me most about xinfo -- to the degree that I refuse to
use this browser -- is the separation of navigation hot spots and display.
This means you have to click in the topmost pane to navigate a menu shown in
the second pane. Clicking directly on the menu item in the second pane has no
effect.
<p>Here is a <a href="misc/spiel/xinfo-screenshot.png">screen shot</a>.</p>
</dd>
<dt><strong><a name="item_tkinfo">tkinfo</a></strong><br>
</dt>
<dd>
<p>My favorite X-based Info browser! It has all the nice features of
<code>info(1)</code>, starts up fast and has a <a href=
"misc/spiel/tkinfo-screenshot.png">compact layout</a>.</p>
</dd>
<dt><strong><a name=
"item_gnome%2Dhelp%2Dbrowser">gnome-help-browser</a></strong><br>
</dt>
<dd>
<p>If you are a Gnome user, you probably know the
<code>gnome-help-browser(1x)</code>. It <a href=
"misc/spiel/ghb-screenshot.png">displays Info pages</a>, too.</p>
</dd>
<dt><strong><a name="item_kdehelp">kdehelp</a></strong><br>
</dt>
<dd>
<p>Same for KDE users... You probably know <code>kdehelp(1x)</code>. Amongst
various other formats it also <a href=
"misc/spiel/kdehelp-screenshot.png">displays Info pages</a>.</p>
<p>kdehelp is easily convinced to browse a specific Info file:</p>
<pre>
kdehelp ./cache-profiler.info
</pre>
<p>Thumbs up!</p>
<p><CODE>konqueror</CODE> also displays info files (at least konqueror 2.2.2);
just type "info:" in the Location: bar.</p>
</dd>
</dl>
<H4>Overview of Common Info Browsers</H4>
<center>
<table border="1" summary="Overview of important features of some common Info
browsers.">
<caption align="left">Overview of Common Info Browsers. Multi-format browser
accept other formats than Info. X11-based browsers require X11 to run.
<code>info</code>-like navigation duplicates the navigation commands of
<code>info(1)</code>.</caption>
<tr>
<th scope="col">Application</th>
<th scope="col">Multi-format</th>
<th scope="col">X11-based</th>
<th scope="col"><code>info</code> Navigation</th>
</tr>
<tr>
<td><code>info</code></td>
<td align="center">no</td>
<td align="center">no</td>
<td align="center">yes</td>
</tr>
<tr>
<td><code>pinfo</code></td>
<td align="center">no</td>
<td align="center">no</td>
<td align="center">no</td>
</tr>
<tr>
<td><code>emacs</code></td>
<td align="center">no</td>
<td align="center">no</td>
<td align="center">yes</td>
</tr>
<tr>
<td><code>xinfo</code></td>
<td align="center">no</td>
<td align="center">yes</td>
<td align="center">yes</td>
</tr>
<tr>
<td><code>tkinfo</code></td>
<td align="center">no</td>
<td align="center">yes</td>
<td align="center">yes</td>
</tr>
<tr>
<td><code>gnome-help-browser</code></td>
<td align="center">yes</td>
<td align="center">yes</td>
<td align="center">no</td>
</tr>
<tr>
<td><code>kdehelp</code></td>
<td align="center">yes</td>
<td align="center">yes</td>
<td align="center">no</td>
</tr>
</table>
</center>
<h2><a name="pros and cons">Pros and Cons</a></h2>
<dl>
<dt><strong><a name="item_Pros">Pros</a></strong><br>
</dt>
<dd>
<ul>
<li>Texinfo format: user definable macros (not shown in this article)</li>
<li>TeX output: perfect typesetting, fantastic hardcopy quality</li>
<li>Info format: alternative to ubiquitous HTML</li>
<li>Info browsers: uniform, fast and easy navigation</li>
</ul>
</dd>
<dt><strong><a name="item_Cons">Cons</a></strong><br>
</dt>
<dd>
<ul>
<li>Texinfo source format:
<ul>
<li>4-argument nodes difficult to maintain without emacs(1). (In this article,
I have not shown the 4-argument form, but introduced the simplified 1-argument
form of nodes.)</li>
<li>1-argument nodes plus sectioning commands more difficult than
necessary</li>
</ul>
</li>
<li>Info format: Info is rendered statically, this is, browsers do not refill
paragraphs if the line width in a browser is different from the linewidth when
the Info page was generated. HTML browsers usually handle this automatic
refilling.</li>
</ul>
</dd>
</dl>
<h2><a name="further reading">Further Reading</a></h2>
<p>The home page of Texinfo, with lots of references and all that,
is located at <a
href="http://texinfo.org/">http://texinfo.org/</a></p>
<p>Available converters for Texinfo are listed at <a href=
"http://www.fido.de/kama/texinfo/texinfo-en.html">http://www.fido.de/kama/texinfo/texinfo-en.html</a></p>
<!-- *** BEGIN bio *** -->
<SPACER TYPE="vertical" SIZE="30">
<P>
<H4><IMG ALIGN=BOTTOM ALT="" SRC="../gx/note.gif">Christoph Spiel</H4>
<EM>Chris runs an Open Source Software consulting company in Upper Bavaria, Germany.
Despite being trained as a physicist -- he holds a PhD in physics from Munich
University of Technology -- his main interests revolve around numerics,
heterogenous programming environments, and software engineering. He can be
reached at
<A
HREF="mailto:cspiel@hammersmith-consulting.com">cspiel@hammersmith-consulting.com</A>.</EM>
<!-- *** END bio *** -->
<!-- *** BEGIN copyright *** -->
<P> <hr> <!-- P -->
<H5 ALIGN=center>
Copyright © 2002, Christoph Spiel.<BR>
Copying license <A HREF="../copying.html">http://www.linuxgazette.com/copying.html</A><BR>
Published in Issue 76 of <i>Linux Gazette</i>, March 2002</H5>
<!-- *** END copyright *** -->
<H4 ALIGN="center">
"Linux Gazette...<I>making Linux just a little more fun!</I>"
</H4>
<P> <HR> <P>
<!--===================================================================-->
<center>
<H1><font color="maroon">Poetry Requiem</font></H1>
<H4>By <a href="mailto:mv@liisa.pp.fi">Martin Vermeer</a></H4>
</center>
<P> <HR> <P>
<!-- END header -->
<BLOCKQUOTE>
<H3>Business Model, Failed</H3>
Today, poetry went into receivership.<br>
Which is why this poem doesn't rhyme,<br>
so the creditors won't notice.
</BLOCKQUOTE>
<P> Linux, like poetry, is not contingent upon the existence of successful
business models. It cannot actually go bankrupt. Its success is
unrelated to business success.
<P> Previous LG articles by Martin (both allegorical stories):
<UL>
<LI><A HREF="../issue28/vermeer2.html">A Tale in Writing</A>
<LI><A HREF="../issue32/vermeer.html">It Takes a Toll</A>
</UL>
<!-- *** BEGIN bio *** -->
<SPACER TYPE="vertical" SIZE="30">
<P>
<H4><IMG ALIGN=BOTTOM ALT="" SRC="../gx/note.gif">Martin Vermeer</H4>
<EM>Martin is a European citizen born in The Netherlands in 1953
and living with his wife in Helsinki, Finland, since 1981. He is
professor of Geodesy at the Department of Surveying, Helsinki University of Technology.
His first UNIX experience was in 1984 with OS-9, running on a Dragon
MC6809E home computer (64k memory, 720k disk!). He is a relative newcomer
to Linux, installing RH4.0 February 1997 on his home PC and, encouraged,
only a week later on his job PC. Now he runs Red Hat 6.2 exclusively at both home and work.
Special Linux interests: LyX and Tcl/Tk.</EM>
<!-- *** END bio *** -->
<!-- *** BEGIN copyright *** -->
<P> <hr> <!-- P -->
<H5 ALIGN=center>
Copyright © 2002, Martin Vermeer.<BR>
Copying license <A HREF="../copying.html">http://www.linuxgazette.com/copying.html</A><BR>
Published in Issue 76 of <i>Linux Gazette</i>, March 2002</H5>
<!-- *** END copyright *** -->
<H4 ALIGN="center">
"Linux Gazette...<I>making Linux just a little more fun!</I>"
</H4>
<P> <HR> <P>
<!--===================================================================-->
<center>
<H1><font color="maroon">Implementing a Bridging Firewall</font></H1>
<H4>By <a href="mailto:david.whitmarsh@sparkle-consultancy.co.uk">David Whitmarsh</a></H4>
</center>
<P> <HR> <P>
<!-- END header -->
What is the difference between a bridging firewall and a conventional firewall?
Usually a firewall also acts as a router: systems on the inside are configured
to see the firewall as a gateway to the network outside, and routers outside
are configured to see the firewall as the gateway to the protected network. A
bridge is piece of equipment that connects two (or more) network segments
together and passes packets back and forth without the rest of the network
being aware of its existence. In other words, a router connects two networks
together and translates between them; a bridge is like a patch cable,
connecting two portions of one network together. A bridging firewall acts as a
bridge but also filters the packets it passes, while remaining unseen by either
side.<p>
Why might you want to so such a thing? A couple of reasons spring to mind:<p>
<ul>
<li>You can plug in a firewall without changing any of your existing network software configuration.
<li>You may want to protect part of a network where you do not have control of the external routing into your network.
</ul>
<h2>My Problem</h2>
In my office I had a shiny new ADSL connection from Demon Internet
with an assigned 16 address subnet (less base, broadcast and router IP
= 13 IP addresses). Because of the vagaries of the UK commercial and
regulatory environment, the line and router were installed and owned by
British Telecom plc. and there was no facility to configure the router
to use an internal gateway. This left me two choices:
<ul>
<li>Connect every host directly to the ADSL router and set up iptables separately for each one.
<li>Use a firewall with ip masquerading to present a single ip address to the outside world.
</ul>
The first was untenable. Multiplying the number of iptable configurations
multiplied the chances of error and the administration overhead.
The second had its own drawbacks. While most things can be set up to
work quite happily with IP masquerading, there are exceptions, including
some technologies that I wished to explore, such as VPNs. A bridging
firewall would solve this problem. The firewall could stand between the
ADSL router and the rest of the router and protect the network without
reconfiguring the router. The one remaining obstacle was that the bridging
code in the standard Linux kernel completely bypasses iptables, so you
can have a box which is either a bridge, or a firewall, but not both.
<h2>The Solution</h2>
Fortunately, there is a <a href="http://bridge.sourceforge.net">project</a>
to implement bridging in conjunction with iptables, so that any packets
transmitted across the bridge can be subject to iptables rules. The
result is a firewall that can be totally transparent to the network,
requiring no special routing. As far as the Internet is concerned, the
firewall does not exist, except that certain connections are blocked. The
bridge software is a kernel patch to allow the existing bridge code to
work inside iptables. Conveniently, the developers have made available
a Redhat 7.2 kernel rpm with the patch installed. Less conveniently,
documentation on how to use it is minimal, so I thought to document this
implementation as an aid to anyone else following the same path.<p>
<h2>Bridging and Routing - how it works</h2>
Briefly. the linux bridge implementation works by tying together two
or more network interfaces. By monitoring activity on all the attached
network segments the bridge code learns which MAC addresses are accessible
from each interface and uses this information to decide which packets to
send out on each interface. The interfaces attached to the bridge to not
normally have an IP address associated with them, but the entire bridge
is configured as a single interface to the firewall.
<img src="misc/whitmarsh/flows.png" alt="packet flows within the firewall"><p>
<h2>Network topology</h2>
My allocated static IP addresses are in the range xxx.xxx.xxx.48-63,
i.e. a subnet mask of 255.255.255.240. I decided to split this range
into two network segments,xx.xxx.xxx.48-56 would be used outside the
firewall, and this includes the IP address of the ADSL router itself
(xxx.xxx.xxx.49). xxx.xxx.xxx.57-62 would be the secure section behind
the firewall. Note that these are not truly subnets as they are linked
by a bridge rather than a router.<p>
<img src="misc/whitmarsh/network.png" alt="network topology"><p>
<h2>Firewall Rules</h2>
The <a href="misc/whitmarsh/rc.firewall.sh.txt">sample firewall script</a>
is broadly similar to a conventional firewall setup (cribbed from
<a href="http://www.boingworld.com/workshops/linux/iptables-tutorial/iptables-tutorial/iptables-tutorial.html">
Oskar Andreasson's iptables tutorial</a>. The basic firewall policy is:
<ol>
<li>Block packets from unlikely IP addresses
<li>Allow any outgoing connections from behind the firewall
<li>Allow packets in that belong to established connections
<li>Allow connections to specified ports and hosts from outside
</ol>
<h3>Variable definitions</h3>
For clarity and maintainability it is a good idea to keep interface names
and IP addresses as variables. The values used for these examples are:<p>
<pre>
BR_IP="xxx.xxx.xxx.57"
BR_IFACE=br0
LAN_BCAST_ADDRESS="xxx.xxx.xxx.63"
INTERNAL_ADDRESS_RANGE="xxx.xxx.xxx.56/29"
INET_IFACE="eth1"
LAN_IFACE="eth0"
LO_IFACE="lo"
LO_IP="127.0.0.1"
</pre>
"xxx.xxx.xxx" represents the first three bytes of the network IP
addresses. $INTERNAL_ADDRESS_RANGE is the secure network segment.<p>
<h3>Setting up the bridge</h3>
We have to do a some less conventional things to set up the bridge. First
we shut down our two interfaces and remove any IP address from them.<p>
<pre>
ifdown $INET_IFACE
ifdown $LAN_IFACE
ifconfig $INET_IFACE 0.0.0.0
ifconfig $LAN_IFACE 0.0.0.0
</pre>
If you just executed these commands from a telnet connection (or ssh
as you are so security conscious), get up and cross the room to your
firewall's console.<p>
Next we create a bridge and assign the Ethernet interfaces to it.<p>
<pre>
brctl addbr $BR_IFACE
brctl addif $BR_IFACE $INET_IFACE
brctl addif $BR_IFACE $LAN_IFACE
</pre>
You can now bring up the bridge as an internal interface if you wish:
<pre>
ifconfig $BR_IFACE $BR_IP
</pre>
<h3>Blocking spoofs</h3>
We can block spoofed packets in the mangle PREROUTING chain. By blocking
here we can catch both INPUT and FORWARDED packets at the same time. We
use mangle PREROUTING rather than nat PREROUTING because only the first
packet of each stream is checked in the nat table.<p>
This line ensures that only packets with valid internal addresses are
accepted on the internal interface.<p>
<pre>
$IPTABLES -t mangle -A PREROUTING -i $LAN_IFACE -s $INTERNAL_ADDRESS_RANGE -j ACCEPT
</pre>
And this prevents packets with internal addresses being accepted on the
external interface:<p>
<pre>
$IPTABLES -t mangle -A PREROUTING -i $INET_IFACE ! -s $INTERNAL_ADDRESS_RANGE -j ACCEPT
</pre>
<h3>Accessing the firewall from the internal network</h3>
You may choose to leave your firewall completely invisible to the network,
or you may wish for convenience to allow connections from within.
These commands will allow all connections to the firewall from the
internal network only. You may wish to be more selective depending on
your level of trust of your network systems and users.<p>
<pre>
$IPTABLES -A INPUT -p ALL -i $BR_IFACE -s $INTERNAL_ADDRESS_RANGE -d $LAN_BCAST_ADDRESS -j ACCEPT
$IPTABLES -A INPUT -p ALL -i $BR_IFACE -s $INTERNAL_ADDRESS_RANGE -d $BR_IP -j ACCEPT
</pre>
Remember that we have already eliminated packets that claim to be from
$INTERNAL_ADDRESS_RANGE that appear on the wrong interface.<p>
<h2>More information</h2>
<a href="http://bridge.soureforge.net">The kernel patch</a> without which all your iptables rules are in vain.<br>
Oskar Andreasson's <a href="http://www.boingworld.com/workshops/linux/iptables-tutorial/iptables-tutorial/iptables-tutorial.html">iptables tutorial</a> is recommended reading.<br>
Try <a href="http://netfilter.samba.org/unreliable-guides/">Rusty's Remarkably Unreliable Guides</a>
for background on packet filtering and networking.<br>
<p>
<a href="http://www.sparkle-cc.co.uk/index.html" target=_parent>Sparkle Home Page</a>
(the author's company)
<p>
<h2>Acknowledgments</h2>
Thanks to <a href="mailto:buytenh@gnu.org">Lennert Buytenhek</a> for a
really useful patch, and also for reviewing this article.<p>
<!-- *** BEGIN bio *** -->
<SPACER TYPE="vertical" SIZE="30">
<P>
<H4><IMG ALIGN=BOTTOM ALT="" SRC="../gx/note.gif">David Whitmarsh</H4>
<EM>David is an independent consultant working mostly for
financial institutions in the City of London through his company,
<a href="http://www.sparkle-cc.co.uk/index.html" target=_parent>Sparkle Computer Co Ltd</a>. With four young children,
spare time is a precious commodity, so the daily commute from Sussex is
his main opportunity for tinkering with Linux and open source software
on his laptop.</EM>
<!-- *** END bio *** -->
<!-- *** BEGIN copyright *** -->
<P> <hr> <!-- P -->
<H5 ALIGN=center>
Copyright © 2002, David Whitmarsh.<BR>
Copying license <A HREF="../copying.html">http://www.linuxgazette.com/copying.html</A><BR>
Published in Issue 76 of <i>Linux Gazette</i>, March 2002</H5>
<!-- *** END copyright *** -->
<H4 ALIGN="center">
"Linux Gazette...<I>making Linux just a little more fun!</I>"
</H4>
<P> <hr> <P>
<H1><font color="maroon">The Back Page</font></H1>
<ul>
<li><a HREF="#wacko">Wacko Topic of the Month</a>
<li><a HREF="#nottag">Not The Answer Gang</a>
<li><a HREF="#spam">World of Spam</a>
</ul>
<a name="wacko"></a>
<P> <hr> <P>
<!--====================================================================-->
<center><H3><font color="maroon">Wacko Topic of the Month</font></H3></center>
<P> <HR> <P>
<!--======================================================================-->
<P>
<H3 ALIGN="center"><FONT COLOR="green">Coal port</FONT></H3>
<p align="right"><FONT COLOR="#000000"><strong>Contributed By Thomas Adam
</strong></FONT></p>
My main PC is a 166 pentium with 32MB ram. This beast
also has a "coal" port at the back so that if the
speed starts to dwindle, then you can "stoke" her up.
<IMG ALT=":)" SRC="../gx/dennis/smily.gif" WIDTH="20" HEIGHT="24">
<a name="nottag"></a>
<P> <hr> <P>
<!--====================================================================-->
<center><H3><font color="maroon">Not The Answer Gang</font></H3></center>
<P> <HR> <P>
<!--======================================================================-->
<P>
<H3 ALIGN="center"><FONT COLOR="green">Hacking</FONT></H3>
<p align="right"><FONT COLOR="#000000"><strong>Answered By Jay Ashworth, Iron</A>
</strong></FONT></p>
<STRONG>
hi my name is phill and i am new to hacking i have done a few hacks with
some trojan programs but nothing big and i dont no were to start if you would
be willing to help me with some skills on how to hack that dbe great
i really wanna get some advanced hacking skillsGet more from the Web. FREE
REE MSN Explorer download : http://explorer.msn.com
</STRONG>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Jay]
<P>
Anyone wanna take a swing?
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
I held back because I know Dan Wilder and Ben Okopnik will soon be posting
volumuous pieces of Helpful Advice, and Heather will chime later in with an extra
special spin, maybe with a supermarket analogy or something to surprise us.
<P> What do you have to say, Jay?
<BLOCKQUOTE>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Jay]
Given that I have to *work* with a new trainee consultant who sounds
like this, I don't think it's safe for my blood pressure to say
anything. I work for a living; I suppose I ought to pay the script
kiddies for improving my revenue, but the whole thing sorta galls my
sister.
<P>
</BLOCKQUOTE>
<P> Our last published piece on hacking I could find was:
<A HREF="http://www.linuxgazette.com/issue71/lg_backpage71.html#nottag">http://www.linuxgazette.com/issue71/lg_backpage71.html#nottag</A>
("Help me crack my school")
But I'm sure there were more in 2001 somewhere, either in The Answer Gang
column or on the Back Page.
<P> I do wonder why a hacker-wannabe is using MSN for a mail service....
<BLOCKQUOTE>
The prosecution *rests*.
<P> He's not a "hacker" wannabe. He's a "cracker" wannabe.
Or, if you prefer, a juvenile delinquent.
</BLOCKQUOTE>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
Diving into dry pools head-first is a good start, particularly from the
high board - it's been known to cure incipient crackers. Sure, some - well,
most - end up looking like a squashed bug, but you've got to admit, it's
much better than the alternative. Be sure to try it today!
<P> For advanced hacking skills, take a look at Eric S. Raymond's "How To Become A
Hacker", at
<A HREF="http://www.tuxedo.org/~esr/faqs/hacker-howto.html">http://www.tuxedo.org/~esr/faqs/hacker-howto.html</A>. That takes you
all the way from beginner to advanced... not what you meant? Oh, right, I
forgot; when the cracker maggots invade your brain, language skills are the
first thing to go. <shrug> I guess you'll never be able to explain what you
really want, now. I understand that progression of the disease is difficult to
reverse, deterioration is rapid, and the prognosis is NOT positive.
<P> A friend of mine's got a 10th floor apartment, and the pool might even have
been emptied for the winter. Want me to ask? Really, it wouldn't take long
at all...
<P> Regarding MSN, Good news!!! I've got a *great* cracking opportunity coming up for you;
you'll need to break into MSN and establish a new account. See, you'll
*have* to do this because I'm about to report your criminal activities to
MSN - including your confession of having already "done a few hacks with
some trojan programs", so that even their admin people can have a laugh at
your terminally moronic behavior. All they have to do is look at the
headers in your e-mail (didn't know about those, did you?), compare them
with the copy that will still be on their servers (missed that one too,
huh?), and TOSs your ass so hard that you'll bounce.
<P> You know, if you ask the folks at your local TV or radio station, they
might let you climb their tower - you could get a coupla hundred feet up
that way - and you could always drag up a bathtub. Seriously, give it a
shot: it can't hurt. Well, actually it would, but it's the kind of thing
you're supposed to say...
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Jay]
<P>
Now, *see*? I *knew* Ben would come up with something lyrical.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
I've got to give MSN their due: they actually have humans assigned to
dealing with this stuff, and when these folks LART one, they let you know:
"Hi, my name is X, and I'm the one assigned to this case. I've examined the
information you've sent us, and terminated our former customer on that
basis. Thank you for...", etc. They also seem to pay attention to the info
that you send them in the complaint letter. My "spamkill" file contains
quite a few from them.
<P> <HR> <P>
<!--======================================================================-->
<P>
<H3 ALIGN="center"><FONT COLOR="green">More Tux trivia</FONT></H3>
<p align="right"><FONT COLOR="#000000"><strong>Answered By Iron, Heather Stern,
Rachel Rawlings
</strong></FONT></p>
<H4>This is a follow-up to an important issue we
<A HREF="../issue74/lg_backpage.html#nottag">reported</A> in January, namely:</H4>
<STRONG>
When I gave her a stuffed Tux as a present,
my Girlfriend asked me, what it's sex is?
</STRONG>
<H4>At the time, I commented:</H4>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
Four out of five sexist computer nerds surveyed agree Tux is male.
<H4>Now we have some updated commentary:</H4>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
That might refer to Linus' original comment that penguins are happy
because they have just stuffed themselves full of herring or have been
hanging out with lady penguins. We only <EM>know</EM> that Tux is stuffed full
of herring, but we can assume Tux hangs out with lady penguins.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Rachel]
<P>
Which actually doesn't get say definitively whether Tux is male. Tux
could hang out with lady penguins cf. Marlena Dietrich, or be a
high-class drag king.
<IMG ALT=":>" SRC="../gx/dennis/smily.gif" WIDTH="20" HEIGHT="24">
<P> However, speaking as a dyke with a largish stuffed animal collection
(one of whom is a female Peter Rabbit named Katja), my Tux is male. Other
users' Tuxen may vary according to the needs of the user, much like
their kernel configurations.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
Interesting. I wonder if Eric Raymond's enhanced kernel configurator
will have a question for which sex your kernel should be built as.
<P> <HR> <P>
<!--======================================================================-->
<P>
<H3 ALIGN="center"><FONT COLOR="green">More on Ben's reputation</FONT></H3>
<p align="right"><FONT COLOR="#000000"><strong>Answered By Ben Okopnik, Iron, Faber Fedor</A>
</strong></FONT></p>
<STRONG>
<CITE>Ben writes:</CITE><BR>
You're always
welcome to control "further correspondence from Mr. Ben Okopnik" _in your
mailbox_ via your 'Del' key...
</STRONG>
<BLOCKQUOTE>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
Why, that's mighty fine of you, Ben. You must be getting soft in your old age.
You can't wear those dark menacing LG sunglasses anymore.
</BLOCKQUOTE>
<STRONG>
I'm neither a friend of yours or a paid
consultant for you.
</STRONG>
<BLOCKQUOTE>
Now that sounds right proper curdgemeonly (sp). OK, you can keep the glasses.
</BLOCKQUOTE>
<STRONG>
if you have either a thick head or a thin
skin,
</STRONG>
<BLOCKQUOTE>
And we'll get you a pirate eye patch to go with it. Hey, you can use that on your
sea voyages too! Do you need a flag with a skull and crossbones too or do you already
have that? Or maybe your flag is getting a bit tattered....
<P> By the way, guess what came in the spam today. Just perfect for Ben.
<PRE>
Subject: Your metals sunglasses
One of the world largest Sunglasses company is clearing stock.
Get a pair of Sexy Metals Sunglasses model 2002 for free
while stock last.
</PRE>
</BLOCKQUOTE>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
<Splort> You... you... <Daffy Duck mode> You're dethhhhhhpicable. </DDm>
<P> Besides, you probably wouldn't want "Metals sunglasses"; I understand that
Metal gets mean after a few drinks, and he *really* gets upset about people
that take his sunglasses. Just a warning to the wise.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
Another spam came through too.
<PRE>
From: <RipoffArtist@spamhaven.com>
Subject: Spy Ear Blowout Sale
Oh yeah! What a great way to identify spies; they'll be the ones with their
ears blown out.
- "Excuse me, sir..."
- "What? what? I can't hear you."
- "ARREST THAT MAN!!!"
</PRE>
Of course, Ben knows a lot about how spies operate...
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
<Glare> Your time vill come, Comrade. Ve haff long memories.
<H4>In another thread...</H4>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Faber]
<P>
I hate to do this, but I have to agree with Ben...again! <grumble>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
Why, Faber! I'm cut to the quick by your implications; I'm shocked -
simply shocked, I tell you - by this. <sniffle>
Eh, just admit it; I'm always right.
<H4>In another thread...</H4>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
a) Make the script SUID root (!!! use with caution - this is a *bad* idea
unless you know exactly what you're doing !!!):
<PRE>
chmod 4755 mswin
</PRE>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Dan]
<P>
Ben, which OS are you running that one on ?!?
Last I heard, Linux didn't accomodate setuid scripts.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
Dan's too polite. I told him to ask Ben what drugs he's on.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
Oh, the same as usual. I think it's the mix, though: I just tried using a
little more plutonium and a little less crack, and that's _clearly_ not the
way to go.
<P> (Boy, the FBI is going to be all *over* this one. The only thing that's
missing is a reference to sex and death... ah, there we go. See y'all in
about 20 years.)
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
You can join Don Marti, future political prisoner.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Karl-Heinz]
<P>
You should maybe consider some strong encryption like rot13 to keep the
AFN, SOV and PVN computers occupied ;-)
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
Shhhay! Isthay isway away IGBAY ecretsay!
<P> Now *there's* a Denial of Service attack that'll take'em right down. My
diabolical plan for World Domination is proceeding apace...
<H4>In another thread...</H4>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
I wanted to change "side comments from Ben Okopnik and Heather Stern" to
"with snide comments from Ben Okopnik and Heather Stern", but I refrained.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
My God, Mike. The incredible amount of self-restraint that must have
taken... oh, the feeling of sacrifice... I'm stunned that you managed to
overcome such a temptation. Worse yet, you could have always pretended to
be innocent and blamed it on a simple misspelling.
<P> Want a pair of these dark glasses? <innocently> Just asking.
<P> Heather can put it in her todo list for next month, to sneak the
"for snide comments in" quote when nobody's looking. Which means
you'll have to be extra snide over the next month to give her
material. Do you think you can handle that?
<P> Besides, I can't possibly imagine how you came by that impression. /Moi/,
*snide?* Huh. The very _idea._
<P> If someone *deserves* to be smacked down, however... <rubbing hands
gleefully>
<P> <HR> <P>
<!--======================================================================-->
<P>
<H3 ALIGN="center"><FONT COLOR="green">Debian and World Domination</FONT></H3>
<p align="right"><FONT COLOR="#000000"><strong>Answered By Iron, Jay Ashworth, Ben Okopnik, Heather Stern</A>
</strong></FONT></p>
<STRONG>
<CITE>Jim Dennis writes:</CITE><BR>
This is very reliable when you're Debian system is tracking
"stable". Reasonably robust and reliable when tracking "testing".
Occasionally *very* broken when tracking "unstable."
</STRONG>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
Especially when a package depends on itself! This happens a few times a year
in Unstable.
<P>
<STRONG>
(Note that many agitators and activists *do* have "Linux world
domination" as their goal,
</STRONG>
<P>
But many who support World Domination aren't really activist about it.
<P>
<STRONG>
but there isn't much overlap between the core
developers in free software, and the agitators and activists).
</STRONG>
<P>
<IMG ALT=":)" SRC="../gx/dennis/smily.gif" WIDTH="20" HEIGHT="24">
<IMG ALT=":)" SRC="../gx/dennis/smily.gif" WIDTH="20" HEIGHT="24">
As in sports. There's not a lot of overlap between the hockey players
who score the most goals and the players hired to pick fights.
<H4>Then in another thread...</H4>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Jay]
<P>
Defense in Depth, my revered senior partner.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
<gasp> Jay has called me "senior" and "revered"! *NOW* I shall rule!
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
I don't even have to say anything...
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
"Hello, Central? What's holding up that assassination team? Oh, Seattle
traffic. OK. I'll give them fifteen more minutes..."
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
Tell Mr Okopnik he'd better give us two hours.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
<P>
We're all whippersnappers at some point, Ben, your turn will come.
<wicked grin>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
Why, you young... oh. Never mind.
<P> I'll be turning 40 in a couple of months, so I'm practicing.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Jay]
<P>
I want him to drop and give me 20, myself.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
"Hello, US Air Force? Do you happen to have 20 of those bunker-busters
left? Here are some coordinates in Florida..."
<P> I got done "dropping and doing 20" almost 20 years ago, Jay. Although I've
just started working out again, so that's maybe a reasonable equivalent.
<P> <HR> <P>
<!--======================================================================-->
<P>
<H3 ALIGN="center"><FONT COLOR="green">Esperanto</FONT></H3>
<p align="right"><FONT COLOR="#000000"><strong>Answered By Iron, Ben Okopnik, Jay Ashworth</A>
</strong></FONT></p>
<BLOCKQUOTE><EM>
[I'm working on an Esperanto translation of parts of LG. It'll be another month
or so till it's up. -Iron.]
</EM></BLOCKQUOTE>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Jay]
<P>
Heh. "Dubitando ad veritatem venimus" ("We arrive at the truth by being
sceptical").
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
Malfidante ni trovas la veron. (Untrusting, we find the truth.)<BR>
Malfidante ni malkasxas la veron. (Untrusting, we discover [=unhide] the truth.)<BR>
Per skeptikemo ni atingas la veron. (By our tendency to be skeptical, we achieve the
truth.)
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
<LOL> Well, *that* didn't take long. Do we need a modified version of
<A HREF="http://www.tuxedo.org/~esr/jargon/html/entry/Godwin's-Law.html">Godwin's Law</A>
here, or what?
<P> (For the humor-impaired: Just kidding. I really like Mike's little
Esperanto bits... I also like twitting him about it.
<H4>And in another thread...</H4>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
To support other languages, various 8-bit charsets were introduced. The
ISO-8859-x series ("man iso_8859_1") is the most common on UNIX. -1 (aka
LATIN-1) covers Western Europe (Germanic/Romance languages), -2 (aka LATIN-2)
covers Eastern Europe (Slavic languages), -3 (aka LATIN-3) covers miscellaneous
Europe (and Esperanto :).
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
<narrowed eyes behind the dark glasses> You thought I'd miss that, didn't
you? The Revolution Never Sleeps.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
No, I knew you'd never miss that. You had extensive training, comrade.
<P> <HR> <P>
<!--======================================================================-->
<P>
<H3 ALIGN="center"><FONT COLOR="green">$3 words and <EM>Trainspotting</EM></FONT></H3>
<p align="right"><FONT COLOR="#000000"><strong>Answered By Jay Ashworth, Iron, Ben Okopnik, Dan Wilder</A>
</strong></FONT></p>
<STRONG>
What's the opposite of "concur"? ;-)
</STRONG>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
Since "concur" means "agree", the opposite is "disagree".
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Jay]
<P>
Yeah, but that's only a 49-cent word. I prefer the buck-2.98 ones.
<IMG ALT=":)" SRC="../gx/dennis/smily.gif" WIDTH="20" HEIGHT="24">
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
Down with $3 words! It's ridiculous that children compete in spelling
bees over words that ordinary people would never use and don't know exist.
Just because it's *possible* to derive a fancy Latin word for an ordinary
English word doesn't automatically make it an English word. It's academickese,
not English. There's probably a simple English word or circumlocution that
covers the same terrain perfectly adequately, so why not use it? There's
nothing to be gained by using words Joe Sixpack can't understand, except for
the "few" technical terms that are absolutely necessary for a given field.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Jay]
<P>
I disagree, almost entirely.
It depends, of course, on what your *objective* is, and there are many
objectives in writing: you might be trying to impress people, to inform
them, to persuade them...
Each of these jobs requires a different set of tools, just as there
is no one answer to the question "what kind of computer should I buy"
other than "well, what are you going to *do* with it?"
<P> Certainly, it's possible to use words which are fancier-than-thou, and
lose your audience in the process. But that possibility isn't by any
means justification for not being literate and -- dare I say it --
lyrical in your writing.
<P> But, contrary to many people's belief, I think that people want to read
elegant writing, even if it occasionally makes them need to look up a
word that they can't glark from context.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
True, there is language-for-communication and language-as-art. I would
argue that academic/techical writing is supposedly language-for-communication,
thus, its tendency to fanciness hinders its basic purpose.
<P> An urgent example in US society is the language of laws. Nobody but lawyers
can understand then, and even lawyers don't agree on what the DMCA means. How
are people supposed to obey laws they can't understand and don't have time to
read? How can they evaluate whether the law is just? How can they avoid being
hoodwinked?
<P> Personal writing-as-art is a personal thing. I just don't like the way
it can hinder communication, especially works that end up being read by others
than the author intended. For instance, when non-English speakers read Gazette
articles. That's why try to keep LG as straightforward as possible. I'd love
to clean up the spelling/grammar mistakes if I had the time, but I don't have
50 extra hours per month, so I just do the ones that seriously impede
communication.
<P> I read <EM>Trainspotting</EM> and think, the Scottish phonetic style offends my sense
of clarity, but the author's goal is to convey this style of thought/viewpoint
as much as it is to convey content, so I can accept it.
<P> I read <EM>Star Wars</EM> and think, why does the author have to write in such a
convoluted manner? It adds nothing to the story except to make it "hip".
<P> I read <EM>Ratz Are Nice (PSP)</EM> and think, why does the author have to write in
such a slangy style? "They go weekend hunting looking for ruffboichail'z. They
wontz to be quickened... I Edison basically loseout 3 wayz." Actually, I
never got past the first chapter. I don't have time to sound out what he's
trying to say, much less guess what dialect they're speaking. God forbid a
non-English speaker should take an interest in the book.
I prefer a writing style readable by as wide an audience as possible.
<BLOCKQUOTE>
But, contrary to many people's belief, I think that people want to read
elegant writing, even if it occasionally makes them need to look up a
word that they can't glark from context.
</BLOCKQUOTE>
Funny, you say this, but I find your writing perfectly clear and void of
$3 words. (Oops, I said "void of" rather than "doesn't have".)
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Jay]
<P>
I haven't read <EM>Trainspotting</EM>; I'll assume it's half way to James Joyce.
<P>
I'm not gonna get a bite on "glark", eh?
<IMG ALT=":)" SRC="../gx/dennis/smily.gif" WIDTH="20" HEIGHT="24">
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
<EM>Trainspotting</EM> quotes:
<BLOCKQUOTE>
"That's no the f*****g point," ah sais, but withoot conviction.
"Aye. The point is ah'm really f*****g suffering here, n ma
so-called mate's draggin his feet deliberately, lovin every
f****n minute ay it!" His eyes seem the size ay fitba's n look
hostile, yet pleadin at the same time; poignant testimonies tae
ma supposed betrayal.
<P> At the Fit ay the Walk thir wir nai taxis. They only
congregated here when ye didnae need them.
<P> "See whit yuv done now, ya big-moothed c**t. Next time one ay
us ur walkin home oan oor Jack Jones, wi git hassle fi these wee
radges." Ah wisnae chuffed at Sick Boy.
"Yir no feart ay they wee f****n saps ur ye?"
This c**t's really gittin ma f****n goat. "Aye! Aye ah f****n
am, if ah'm oan ma tod n ah git set oan by a f****n squad ay
shell-suits! Ye think ah'm Jean-Claude Van F****n Damme?
F****n doss c**t, so ye are Simon." Ah called him 'Simon'
rather than 'Si' or 'Sick Boy' tae emphasise the seriousness ay
what ah wis sayin.
</BLOCKQUOTE>
Actually, the book switches between Scots and English pretty much at
random. There are entire passages in English, and recent words like
"taxis" and "dealer" that have no Scots equivalent are just thrown in
unchanged, looking out of place because they're not spelled
phonetically.
<P> Of course, Scottish literature is pretty scarce and underrepresented,
and Irving Welsh is one of the few authors filling the gap.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
I'm fairly close to the middle of this one, but with somewhat of a lean in
Jay's direction: there are times - especially when writing for a techie
audience - when the more spendy variety of verbal pyrotechnics (remember to
always and ever eschew needless and unnecessary word usage!) is called
for... but the reason is the one that Mike mentions: writing to a given
audience.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
Believe it or not, I *am* a fan of writing differently depending on
your audience. I'm just pointing out that sometimes one's audience
ends up being bigger than anticipated, and the assumptions one made
about the audience no longer hold true.
<P> PS. Just in case it's unclear, I'm *not* complaining about anything
anybody's written on TAG. This is just a problem I've seen other places.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Dan]
<P>
Oh darn. Guess I hafta go get out the old thesaurus more often.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
Should be familiar territory by now, Dan; ISTR that you were raised on the
stuff. Or was that brontosaurus? Either way, should be pretty tasty with
just a touch of lemon and Hollandaise sauce...
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Dan]
<P>
Customarily prepared by briefly grilling steaks rubbed with wild onion
directly on top of a hardwood twig fire. Also great as thesaurus tartare.
<P> <HR> <P>
<!--======================================================================-->
<P>
<H3 ALIGN="center"><FONT COLOR="green">Boring documentation</FONT></H3>
<p align="right"><FONT COLOR="#000000"><strong>Answered By John Karns</A>
</strong></FONT></p>
<STRONG>
Anybody please tell me about installation of linux with win2000.
I already installed linux 7 on my pc.
now i want that without format my system i install win2000 on my pc.
<P> any body pls give me any utility. don't tell me FAQ.
this is boring for me. if anybody wants help me out than pls provide me
utility.
</STRONG>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [John]
<P>
If you find reading FAQ's boring, I don't think you're going to like Linux
too much.
<P> <HR> <P>
<!--======================================================================-->
<P>
<H3 ALIGN="center"><FONT COLOR="green">University admissions</FONT></H3>
<p align="right"><FONT COLOR="#000000"><strong>Answered By Dan Wilder</A>
</strong></FONT></p>
<STRONG>
dear sir, i am living in pakistan. a newely institution namely biztek
affliation with girne american university north cuprus in turkey has opened in
pakistan . they said that they r also affliated with u because they r giving
degree of girne american university . sir plz tell me that r u affliated with
girne american university ? . and u can take transfer from biztek in pakistan
to ur university and also tell me the process to take transfer in ur university
.is my cradit hours transfer to ur university. reply me soon.
</STRONG>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Dan]
<P>
We are affilitated with no university. None. Nil.
Nor college, high school, research institute, preschool.
Not even a skateboard park. Nor basketball stadium,
automotive repair garage, not even a pizza parlor.
<P> <HR> <P>
<!--======================================================================-->
<P>
<H3 ALIGN="center"><FONT COLOR="green">Tennis rackets</FONT></H3>
<p align="right"><FONT COLOR="#000000"><strong>Answered By Ben Okopnik, Iron</A>
</strong></FONT></p>
<STRONG>
<CITE>Chris Gianakopoulos writes:</CITE><BR>
I got this information by looking at sendlib.c in the Mutt source code. I
am sorry. I really shouldn't have posted this question. I WAS lazy, and
now I feel bad.
</STRONG>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
Oh... bosh. Chris, you often launch interesting questions, and digging
down to the bottom of those can be fun. Now quit smacking yourself; you're
wearing out that nice new tennis racket.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
Next time, Ben, buy him the plastic racket, not the metal one. He'll be less
likely to hurt himself that way.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Chris]
<P>
I could wear a helmet for extra protection too. That will help during
intense software debug sessions when I keep hitting my head against the
wall.
<P> <HR> <P>
<!--======================================================================-->
<P>
<H3 ALIGN="center"><FONT COLOR="green">Tea</FONT></H3>
<p align="right"><FONT COLOR="#000000"><strong>Answered By Heather Stern, Iron, Ben Okopnik</A>
</strong></FONT></p>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
<P>
Well, the deli counter is that way, but it doesn't serve beer or milk or
tea much less mango lassi or jumbo smoothies. Only coffee and soda pop.
Oh well.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Iron]
<P>
And Rory called my Jasmine tea yesterday "fou-fou". Can you believe it?
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
Well, *yeah*. I keep telling you to get rid of the little plastic umbrella
and the maraschino cherries - they really _do not_ go with jasmine tea -
but would you listen?...
<P> <HR> <P>
<!--======================================================================-->
<P>
<H3 ALIGN="center"><FONT COLOR="green">Iron</FONT></H3>
<p align="right"><FONT COLOR="#000000"><strong>Answered By Ben Okopnik, Jay Ashworth</A>
</strong></FONT></p>
<STRONG>
What flags would you use with " tcpdump " in order to
view the Ethernet source and destination addresses of
three packets with no time stamp data added ?
</STRONG>
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
There's always the "--view-the-Ethernet-source-and-destination-addresses-
of-three-packets-with-no-time-stamp-data-added" switch (one of the standard
GNU long options.) Be sure to type it out every time, too; cut-and-paste
won't work, since the "cut_and_paste_detect()" function will just reject
it.
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Jay]
<P>
<PRE>
tcpdump: command line switch too long.
</PRE>
What do I do now, Unca Ben?
<P>
<IMG SRC="../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
<P>
You probably mistyped it. Try it fifteen or twenty more times. If that
fails, try
<PRE>
tcpdump --irony
</PRE>
(Hint: does not mean "kinda like iron". :)
<a name="spam"></a>
<P> <hr> <P>
<!--====================================================================-->
<center><H3><font color="maroon">World of Spam</font></H3></center>
<P> <HR> <P>
<!--======================================================================-->
<P>
Dear Future Millionaire:<BR>
I'll make you a promise. READ THIS E-MAIL TO THE END! - follow what it says to
the letter - and you will not worry whether a RECESSION is coming or not, who
is President, or whether you keep your current job or not....
<P> ===WHEN YOU PLACE YOUR ORDER, MAKE SURE =====YOU ORDER EACH OF THE 5
REPORTS! ==You will need all 5 reports so that you can save them on your
computer and resell them. YOUR TOTAL COST $5 X 5 = $25.00.
<P> Within a few days you will receive, via e-mail, each of the 5 reports from
these 5 different individuals. Save them on your computer so they will be
accessible for you to send to the 1,000's of people who will order them from
you.
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
<BLOCKQUOTE><EM>
Analysis by Chris Gianacopoulos
</EM></BLOCKQUOTE>
The NON-detectable KISS has arrived!!!
<BLOCKQUOTE><EM>
I wonder if it'll be non-detectable like a computer virus.
</EM></BLOCKQUOTE>
These fantastic new lip products are waterproof
will not smear off, kiss off, or rub off.
<BLOCKQUOTE><EM>
Almost like a clown face!
</EM></BLOCKQUOTE>
Lip-gloss products will not come off until you
TAKE them Off. Look like a movie star all day long.
<BLOCKQUOTE><EM>
Oh no! If I look like a movie star, then, people will know who I am. There
goes my private life.
</EM></BLOCKQUOTE>
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
<BLOCKQUOTE><EM>
Analysis by Ben Okopnik
</EM></BLOCKQUOTE>
From: <RipoffArtist@spamhaven.com><BR>
Subject: Spy Ear Blowout Sale
<BLOCKQUOTE><EM>
Oh yeah! What a great way to identify spies; they'll be the ones with their
ears blown out.
- "Excuse me, sir..."
- "What? what? I can't hear you."
- "ARREST THAT MAN!!!"
</EM></BLOCKQUOTE>
Try the HOTTEST and NEWEST
thing on the market, the discreet ISPY007 SPY EAR Mini Hearing
Enhancer.
It will let you hear up to 20 feet away with crystal clear reception!
<BLOCKQUOTE><EM>
Can we test that? Go ahead and put that thing in your ear, and listen
closely:
***AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHHH!***
<P> Oh, oops. Look at that; your poor eyeballs. Are they supposed to protrude
like that? Say, that ear looks blown out, too. Are you *sure* you're not a
spy? Quick, somebody - ARREST THAT MAN!
</EM></BLOCKQUOTE>
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
Put the Internet to Work for You!
It's easy to turn the internet into your own 24/7 business and earn an
executive's salary!
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
You can make a fortune on Ebay and other auctions sites provided your armed
with the RIGHT information. Get your hands on the closely guarded secrets the
pro's use everyday!
<BLOCKQUOTE><EM>
[Nice grammar there, "your". -Iron.]
</EM></BLOCKQUOTE>
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
XXXXX Publications Co. is broadening its publishing scope by releasing the
first in its series of books designed to cover .NET, Microsoft's new
programming platform, arguably the most important Microsoft innovation since
the introduction of Windows itself. .NET fuses desktop and network-based
development and provides programmers with a unified, language-neutral
framework. It also makes many existing developer skills obsolete and a
transition to .NET inevitable.
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
Get Background Information on anyone!
NOTHING can be hidden from you when you have the power of NetDetective!
You can investigate - Wife, Husband, Boss, Babysitter, Boyfriend, Girlfriend. Do it today!
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
From: IncreaseSalesToday@bigcashtoday.com
<P> Dear linux-questions-only@ssc.com,
<CENTER>
Would you like to send an Email Advertisement to<BR>
OVER 12,000,000 PEOPLE DAILY for FREE?
</CENTER>
<P> Do you have a product or service to sell?
Do you want an extra 100 orders per week?
<P> NOTE: (If you do not already have a product or service to sell, we can
supply you with one).
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
Is your spouse cheating online?
Are your kids talking to dangerous people on instant messenger?
FIND OUT NOW with Big Brother<br>instant software
download.
<P> Big Brother will hide on your computer and secretly record all instant messages,
chat, email, web sites and more! Once you install it, it becomes completely
invisible. Then, after the computer is used, you just enter a secret
key-sequence, and you can see everything that happened!
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
Compressed air cost about 1.25 paise per Cu. Ft. Using air amplifying blow guns
and blow nozzles you can save upto 80% compressed air. That is why pay back period
is in hours.
<P>
***************************************************<BR>
Since India has no anti-spamming law, we follow the US Unsolicited Electronic
Mail Act of 2000, which states that mail cannot be considered Spam if it contains
contact / removal information, which this mail does. If you want to be removed
from the mailing list then you must reply to this mail with "Remove" in the subject
line and e-mail for faster response and action.<BR>
********************************************
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
<BLOCKQUOTE><EM>
[
Here's an evil spam. Not only does it pretend to be a WinXP patch
(making you think it's an official Service Pack), but why is it
base64 if it claims to be an *.htm file?
-Iron.]
</EM></BLOCKQUOTE>
Subject: A WinXP patch
<PRE>
Content-Type: application/octet-stream;
name=NOMODEM.HTM
Content-Transfer-Encoding: base64
PEhUTUw+DQoJPEhFQUQ+DQoJCTxsaW5rIHJlbD1zdHlsZXNoZWV0IHR5cGU9InRleHQvY3Nz
IiBocmVmPSIuLlxzZXR1cFxtc29ic2hlbC5jc3MiPg0KCQk8TUVUQSBodHRwLWVxdWl2PSJD
</PRE>
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
Can't get email out to the masses without losing your ISP??? Don't know how to
get sales for your product??? Can't get traffic to your
site???
<P> I have plenty of fresh verified email names and can get you results.
You simply furnish your message and I do the rest. I guarantee you 100%
delivery. It can even be done in full color at no extra cost.
<BLOCKQUOTE><EM>
[I wonder how he manages to show full-color messages on pine. -Iron.]
</EM></BLOCKQUOTE>
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
We are looking to buy:
Submersible piling hammers for use offshore.
Pile sizes are from 24" to 56". Depth 70-100 meter
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
I am Mrs. Monica Martins, the
wife of late Brigadier Arnold Martins of Angola. I am
writing to you from South Africa.
Your firm was introduced to me by a career diplomat
who I consulted in my search for a reliable individual
/company who can assist my son in transferring a
reasonable sum of money abroad to a company or private
account. I on behalf of my late husband and my only
son Frank decided to solicit for your assistance to
transfer the sum of US$12.6 M (twelve million six
hundred thousand united states dollars) deposited by
my late husband in a private security company in South
Africa.
<BLOCKQUOTE><EM>
[A paltry $12.5 million? I'm sure there'll be a better deal later
in my inbox. -Iron.]
</EM></BLOCKQUOTE>
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
We'd visited your website: info.xxxxx.net. After thorough research, we found
that your web site has not registered on any popular search engines and
directories.
<P> This will definitely be the choke point of raising reputation and business
development deeply of your company.
We fully believe that with our service, visitors of your web
site will increase significantly.
<P> At present, there are about 500,000 search
engines in the whole world, but fortunately XXXXX is the rare breed that
can help you register your website with the famous search engine companies.
<BLOCKQUOTE><EM>
[I admire the quality of your "thorough research". Especially since
<STRONG>Linux Gazette</STRONG> is on plenty of search engines. -Iron.]
</EM></BLOCKQUOTE>
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
Is there pornography on your computer? Are you sure?
FREE PC Check.
<P> Clean it off now !
<HR NOSHADE WIDTH="80%"> <!--*********************** -->
(( This is not SPAM ))
<HR> <!-- ************************************************************** -->
<P> Happy Linuxing!
<P> Mike ("Iron") Orr<br>
Editor, <A HREF="http://www.linuxgazette.com/"><i>Linux Gazette</i></A>, <A
HREF="mailto:gazette@ssc.com">gazette@ssc.com</a>
<BR CLEAR="all">
<!-- *** END Not Linux *** -->
<!-- *** BEGIN copyright *** -->
<P> <hr> <P>
<H5 ALIGN=center>
Copyright © 2002, the Editors of <I>Linux Gazette</I>.<BR>
Copying license <A HREF="../copying.html">http://www.linuxgazette.com/copying.html</A><BR>
Published in Issue 76 of <i>Linux Gazette</i>, March 2002</H5>
<!-- *** END copyright *** -->
</BODY></HTML>
|