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
|
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2020-05-17 17:54+0200\n"
"PO-Revision-Date: 2018-03-25 06:41+0000\n"
"Last-Translator: Galina Anikina <merilaga@yandex.ru>\n"
"Language-Team: Vietnamese <https://hosted.weblate.org/projects/debian-handbook/08_basic-configuration/vi/>\n"
"Language: vi-VN\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Weblate 2.20-dev\n"
msgid "Configuration"
msgstr "Cấu hình"
msgid "Localization"
msgstr "Nội địa hoá"
msgid "Locales"
msgstr "Bản địa"
msgid "Network"
msgstr "Mạng"
msgid "Name resolution"
msgstr "Độ phân giải tên"
msgid "Users"
msgstr "Người sử dụng"
msgid "Groups"
msgstr "Các nhóm"
msgid "Accounts"
msgstr "Tài khoản"
msgid "Command-line interpreter"
msgstr "Thông dịch bằng dòng lệnh"
msgid "Shell"
msgstr "Shell"
msgid "Printing"
msgstr "In"
msgid "Bootloader"
msgstr "Bộ tải khởi động"
msgid "Kernel compiling"
msgstr "Biên dịch hạt nhân"
msgid "Basic Configuration: Network, Accounts, Printing..."
msgstr "Cấu hình cơ bản: Mạng, Tài khoản, In ấn..."
msgid "A computer with a new installation created with <command>debian-installer</command> is intended to be as functional as possible, but many services still have to be configured. Furthermore, it is always good to know how to change certain configuration elements defined during the initial installation process."
msgstr "Một máy tính đã được cài đặt mới bằng <command>debian-installer</command> sẽ được dự định làm tốt chức năng, nhưng nhiều dịch vụ vẫn cần phải được cấu hình. Hơn nữa, bạn luôn phải biết cách thay đổi các cấu hình nhất định được cấu hình sẵn trong quá trình cài đặt ban đầu."
msgid "This chapter reviews everything included in what we could call the “basic configuration”: networking, language and locales, users and groups, printing, mount points, etc."
msgstr "Chương này xem xét tất cả mọi thứ bao gồm những gì chúng ta có thể gọi là “basic configuration”: networking, language và locales, users và groups, printing, mount points, vv."
msgid "Configuring the System for Another Language"
msgstr "Cấu hình Hệ thống cho một Ngôn ngữ Khác"
msgid "<primary>French localization</primary>"
msgstr "<primary>Tiếng Pháp địa phương hóa</primary>"
msgid "If the system was installed using French, the machine will probably already have French set as the default language. But it is good to know what the installer does to set the language, so that later, if the need arises, you can change it."
msgstr "Nếu hệ thống đã được cài đặt bằng tiếng Pháp, máy có lẽ sẽ có bộ tiếng Pháp làm ngôn ngữ mặc định. Nhưng rất tốt để biết những gì trình cài đặt làm gì để thiết lập các ngôn ngữ, để sau này, nếu cần phát sinh, bạn có thể thay đổi nó."
msgid "<emphasis>TOOL</emphasis> The <command>locale</command> command to display the current configuration"
msgstr "<emphasis>TOOL</emphasis> Lệnh <command>locale</command> để hiển thị cấu hình hiện tại"
msgid "The <command>locale</command> command lists a summary of the current configuration of various locale parameters (date format, numbers format, etc.), presented in the form of a group of standard environment variables dedicated to the dynamic modification of these settings."
msgstr "Lệnh <command>locale</command> liệt kê một bản tóm tắt cấu hình hiện tại của các tham số về bản địa hoá khác nhau (định dạng ngày, định dạng số, vv), được trình bày dưới dạng một nhóm các biến môi trường tiêu chuẩn dành cho tính linh động để sửa đổi các thiết lập này."
msgid "Setting the Default Language"
msgstr "Thiết lập ngôn ngữ mặc định"
msgid "<primary>locales</primary>"
msgstr "<primary>locales</primary>"
msgid "<primary>language</primary>"
msgstr "<primary>language</primary>"
msgid "<primary><command>locale-gen</command></primary>"
msgstr "<primary><command>locale-gen</command></primary>"
msgid "A locale is a group of regional settings. This includes not only the language for text, but also the format for displaying numbers, dates, times, and monetary sums, as well as the alphabetical comparison rules (to properly account for accented characters). Although each of these parameters can be specified independently from the others, we generally use a locale, which is a coherent set of values for these parameters corresponding to a “region” in the broadest sense. These locales are usually indicated under the form, <literal><replaceable>language-code</replaceable>_<replaceable>COUNTRY-CODE</replaceable></literal>, sometimes with a suffix to specify the character set and encoding to be used. This enables consideration of idiomatic or typographical differences between different regions with a common language."
msgstr "Một miền bản địa (locale) là một nhóm các thiết lập về khu vực. Điều này bao gồm không chỉ là ngôn ngữ cho văn bản, mà còn là định dạng để hiển thị số, ngày tháng, thời gian và tiền tệ, cũng như các quy tắc so sánh theo bảng chữ cái (để tính đúng các ký tự có dấu). Mặc dù mỗi tham số này có thể được xác định độc lập với các tham số khác, nhưng chúng ta thường sử dụng một miền bản địa, đó là một tập các giá trị mạch lạc cho các tham số này tương ứng với “region” theo nghĩa rộng nhất. Các ngôn ngữ này thường được chỉ định dưới dạng, <literal><replaceable>language-code</replaceable>_<replaceable>COUNTRY-CODE</replaceable></literal>, đôi khi với một hậu tố để xác định tập hợp ký tự và kiểu mã hoá được sử dụng. Điều này cho phép xem xét sự khác biệt về thuật ngữ hoặc thành ngữ giữa các vùng khác nhau với một ngôn ngữ chung."
msgid "<emphasis>CULTURE</emphasis> Character sets"
msgstr "<emphasis>CULTURE</emphasis> Bộ ký tự"
msgid "<primary>character set</primary>"
msgstr "<primary>bộ ký tự</primary>"
msgid "<primary>encoding</primary>"
msgstr "<primary>encoding</primary>"
msgid "<primary>ISO-8859-1</primary>"
msgstr "<primary>ISO-8859-1</primary>"
msgid "<primary>ISO-8859-15</primary>"
msgstr "<primary>ISO-8859-15</primary>"
msgid "<primary>Latin 1</primary>"
msgstr "<primary>Latin 1</primary>"
msgid "<primary>Latin 9</primary>"
msgstr "<primary>Latin 9</primary>"
msgid "Historically, each locale has an associated “character set” (group of known characters) and a preferred “encoding” (internal representation for characters within the computer)."
msgstr "Về mặt lịch sử, mỗi miền bản địa có liên kết giữa mỗi một “character set” (nhóm các ký tự đã biết) và một “encoding” (biểu diễn nội bộ cho các ký tự bên trong máy tính)."
msgid "The most popular encodings for latin-based languages were limited to 256 characters because they opted to use a single byte for each character. Since 256 characters was not enough to cover all European languages, multiple encodings were needed, and that is how we ended up with <emphasis>ISO-8859-1</emphasis> (also known as “Latin 1”) up to <emphasis>ISO-8859-15</emphasis> (also known as “Latin 9”), among others."
msgstr "Mã hóa phổ biến nhất cho các ngôn ngữ dựa trên nền latin được giới hạn ở 256 ký tự vì chọn sử dụng một byte cho mỗi ký tự. Vì 256 ký tự không đủ để bao gồm tất cả các ngôn ngữ Châu Âu, cần phải có nhiều mã hóa hơn, và do đó có thêm <emphasis>ISO-8859-1</emphasis> (còn được gọi là “Latin 1”) đến <emphasis>ISO-8859-15</emphasis> (còn được gọi là “Latin 9”), trong số những thứ khác."
msgid "Working with foreign languages often implied regular switches between various encodings and character sets. Furthermore, writing multilingual documents led to further, almost intractable problems. Unicode (a super-catalog of nearly all writing systems from all of the world's languages) was created to work around this problem. One of Unicode's encodings, UTF-8, retains all 128 ASCII symbols (7-bit codes), but handles other characters differently. Those are preceded by a specific escape sequence of a few bits, which implicitly defines the length of the character. This allows encoding all Unicode characters on a sequence of one or more bytes. Its use has been popularized by the fact that it is the default encoding in XML documents."
msgstr "Làm việc với ngoại ngữ thường thường xuyên chuyển đổi giữa các bảng mã hoá và bộ ký tự khác nhau. Hơn nữa, viết văn bản đa ngôn ngữ đã dẫn đến những vấn đề xa hơn, gần như khó khăn hơn. Unicode (một super-catalog gần như tất cả các hệ thống văn bản từ tất cả các ngôn ngữ trên thế giới) được tạo ra để giải quyết vấn đề này. Một trong các mã hoá của Unicode, UTF-8, giữ lại tất cả 128 ký hiệu ASCII (mã 7-bit), nhưng khác biệt với các ký tự khác. Những điểm này được đặt trước bởi một chuỗi trình tự đặc biệt của một vài bit, ngầm định độ dài của ký tự. Điều này cho phép mã hóa tất cả các ký tự Unicode trên một chuỗi của một hoặc nhiều byte. Nó đã được sử dụng phổ biến, và được sử dụng mặc định mã hóa trong các tài liệu XML."
msgid "<primary>ASCII</primary>"
msgstr "<primary>ASCII</primary>"
msgid "<primary>UTF-8</primary>"
msgstr "<primary>UTF-8</primary>"
msgid "<primary>Unicode</primary>"
msgstr "<primary>Unicode</primary>"
msgid "This is the encoding that should generally be used, and is thus the default on Debian systems."
msgstr "Đây là bảng mã thường được sử dụng, do đó được cài đặt mặc định trên hệ thống Debian."
msgid "The <emphasis role=\"pkg\">locales</emphasis> package includes all the elements required for proper functioning of “localization” of various applications. During installation, this package will ask to select a set of supported languages. This set can be changed at any time by running <command>dpkg-reconfigure locales</command> as root."
msgstr "Gói <emphasis role=\"pkg\">locales</emphasis> bao gồm tất cả các yếu tố cần thiết cho hoạt động đúng đắn của “localization” (bản địa hoá) của các ứng dụng khác nhau. Trong quá trình cài đặt, gói này sẽ yêu cầu chọn một tập hợp các ngôn ngữ được hỗ trợ. Tập này có thể thay đổi bất cứ lúc nào bằng cách chạy lệnh <command>dpkg-reconfigure locales</command> với quyền root."
msgid "The first question invites you to select “locales” to support. Selecting all English locales (meaning those beginning with “<literal>en_</literal>”) is a reasonable choice. Do not hesitate to also enable other locales if the machine will host foreign users. The list of locales enabled on the system is stored in the <filename>/etc/locale.gen</filename> file. It is possible to edit this file by hand, but you should run <command>locale-gen</command> after any modifications. It will generate the necessary files for the added locales to work, and remove any obsolete files."
msgstr "Câu hỏi đầu tiên mời bạn chọn các “locales” hỗ trợ. Chọn tất cả các ngôn ngữ tiếng Anh (bắt đầu với (“<literal>en_</literal>”) là một sự lựa chọn hợp lý. Đừng ngần ngại chọn các bản địa khác nếu có người ngoài cùng sử dụng. Danh sách các ngôn ngữ được kích hoạt trên hệ thống được lưu trong tệp <filename>/etc/locale.gen</filename>. Bạn có thể chỉnh sửa tệp trực tiếp bằng tay nhưng phải chạy <command>locale-gen</command> sau bất kỳ sửa đổi nào. Nó sẽ tạo ra các tập tin cần thiết cho các ngôn ngữ bổ sung, và loại bỏ bất kỳ tập tin lỗi thời."
msgid "The second question, entitled “Default locale for the system environment”, requests a default locale. The recommended choice in the U.S.A. is “<literal>en_US.UTF-8</literal>”. British English speakers will prefer “<literal>en_GB.UTF-8</literal>”, and Canadians will prefer either “<literal>en_CA.UTF-8</literal>” or, for French, “<literal>fr_CA.UTF-8</literal>”. The <filename>/etc/default/locale</filename> file will then be modified to store this choice. From there, it is picked up by all user sessions since PAM will inject its content in the <varname>LANG</varname> environment variable."
msgstr "Câu hỏi thứ hai, có tiêu đề “Default locale for the system environment”, yêu cầu một miền bản địa mặc định. Lựa chọn được đề xuất ở Hoa Kỳ là “<literal>en_US.UTF-8</literal>”. Người nói tiếng Anh Anh sẽ thích “<literal>en_GB.UTF-8</literal>”, và người Canada sẽ thích “<literal>en_CA.UTF-8</literal>” hoặc, đối với tiếng Việt, “<literal>vi_VN.UTF-8</literal>”. Tập tin <filename>/etc/default/locale</filename> sẽ được sửa đổi để lưu trữ lựa chọn này. Từ đây, nó được chọn bởi tất cả các phiên người dùng kể từ khi PAM sẽ chèn nội dung của nó trong biến môi trường <varname>LANG</varname>."
msgid "<primary>environment</primary>"
msgstr "<primary>environment</primary>"
msgid "<primary>locale</primary>"
msgstr "<primary>locale</primary>"
msgid "<primary><varname>LANG</varname></primary>"
msgstr "<primary><varname>LANG</varname></primary>"
msgid "The <emphasis role=\"pkg\">locales-all</emphasis> package contains the precompiled locale data for all supported locales."
msgstr ""
msgid "<emphasis>BEHIND THE SCENES</emphasis> <filename>/etc/environment</filename> and <filename>/etc/default/locale</filename>"
msgstr "<emphasis>BEHIND THE SCENES</emphasis> <filename>/etc/environment</filename> and <filename>/etc/default/locale</filename>"
msgid "The <filename>/etc/environment</filename> file provides the <command>login</command>, <command>gdm</command>, or even <command>ssh</command> programs with the correct environment variables to be created."
msgstr "Tập tin <filename>/etc/environment</filename> cung cấp cho <command>login</command>, <command>gdm</command>, hoặc thậm chí <command>ssh</command> với các biến môi trường chính xác được tạo ra."
msgid "These applications do not create these variables directly, but rather via a PAM (<filename>pam_env.so</filename>) module. PAM (Pluggable Authentication Module) is a modular library centralizing the mechanisms for authentication, session initialization, and password management. See <xref linkend=\"sect.config-pam\" /> for an example of PAM configuration."
msgstr "Các ứng dụng này không tạo ra các biến này trực tiếp, mà là qua module PAM (<filename>pam_env.so</filename>). PAM (Pluggable Authentication Module) là một thư viện module tập trung các cơ chế xác thực, khởi tạo phiên và quản lý mật khẩu. Xem <xref linkend=\"sect.config-pam\" /> về ví dụ cấu hình PAM."
msgid "The <filename>/etc/default/locale</filename> file works in a similar manner, but contains only the <varname>LANG</varname> environment variable. Thanks to this split, some PAM users can inherit a complete environment without localization. Indeed, it is generally discouraged to run server programs with localization enabled; on the other hand, localization and regional settings are recommended for programs that open user sessions."
msgstr "Tệp <filename>/etc/default/locale</filename> hoạt động theo cách tương tự, nhưng chỉ chứa biến môi trường <varname>LANG</varname>. Nhờ sự phân chia này, một số người dùng PAM có thể kế thừa một môi trường hoàn chỉnh mà không có bản địa hoá. Thật vậy, thường không khuyến khích chạy các chương trình máy chủ với bật bản địa hoá; mặt khác, bản địa hóa và cài đặt khu vực được khuyến khích cho các chương trình mở phiên người dùng."
msgid "<primary>PAM</primary>"
msgstr "<primary>PAM</primary>"
msgid "<primary><filename>pam_env.so</filename></primary>"
msgstr "<primary><filename>pam_env.so</filename></primary>"
msgid "Configuring the Keyboard"
msgstr "Cấu hình Bàn phím"
msgid "<primary>keyboard layout</primary>"
msgstr "<primary>keyboard layout</primary>"
msgid "<primary>layout, keyboard</primary>"
msgstr "<primary>layout, keyboard</primary>"
msgid "Even if the keyboard layout is managed differently in console and graphical mode, Debian offers a single configuration interface that works for both: it is based on debconf and is implemented in the <emphasis role=\"pkg\">keyboard-configuration</emphasis> package. Thus the <command>dpkg-reconfigure keyboard-configuration</command> command can be used at any time to reset the keyboard layout."
msgstr "Ngay cả khi bố cục bàn phím được quản lý khác nhau trong chế độ console và đồ hoạ, Debian cung cấp một giao diện cấu hình duy nhất hoạt động cho cả hai: nó dựa trên debconf và được thực hiện trong gói <emphasis role=\"pkg\">keyboard-configuration</emphasis>. Vì vậy, lệnh <command>dpkg-reconfigigure keyboard-configuration</command> có thể được sử dụng bất cứ lúc nào để cài đặt lại bố cục cho bàn phím."
msgid "<primary><emphasis>console-data</emphasis></primary>"
msgstr "<primary><emphasis>console-data</emphasis></primary>"
msgid "<primary><emphasis>console-tools</emphasis></primary>"
msgstr "<primary><emphasis>console-tools</emphasis></primary>"
msgid "<primary><emphasis>keyboard-configuration</emphasis></primary>"
msgstr "<primary><emphasis>keyboard-configuration</emphasis></primary>"
msgid "<indexterm><primary><literal>azerty</literal></primary></indexterm>The questions are relevant to the physical keyboard layout (a standard PC keyboard in the US will be a “Generic 104 key”), then the layout to choose (generally “US”), and then the position of the AltGr key (right Alt). Finally comes the question of the key to use for the “Compose key”, which allows for entering special characters by combining keystrokes. Type successively <keycombo action=\"seq\"><keycap>Compose</keycap><keycap>'</keycap><keycap>e</keycap></keycombo> and produce an e-acute (“é”). All these combinations are described in the <filename>/usr/share/X11/locale/en_US.UTF-8/Compose</filename> file (or another file, determined according to the current locale indicated by <filename>/usr/share/X11/locale/compose.dir</filename>)."
msgstr "<indexterm><primary><literal>azerty</literal></primary></indexterm>Các câu hỏi liên quan đến bố cục bàn phím vật lý (bàn phím máy tính tiêu chuẩn ở Mỹ sẽ là phím “Generic 104 key”), sau đó bố trí để chọn (thường là “US”), và sau đó là vị trí của phím AltGr (bên phải Alt). Cuối cùng là câu hỏi về khoá để sử dụng cho phím “Compose key”, cho phép nhập ký tự đặc biệt bằng cách kết hợp các phím bấm. Bấm phím <keycombo action=\"seq\"><keycap>Compose</keycap><keycap>'</keycap><keycap>e</keycap></keycombo> tạo ra e-acute (“é”). Tất cả các kết hợp này được mô tả trong tệp <filename>/usr/share/X11/locale/en_US.UTF-8/Compose</filename> (hoặc tệp khác, trong thư mục <filename>/usr/share/X11/locale/compose.dir</filename>)."
msgid "<primary><literal>Compose</literal>, key</primary>"
msgstr "<primary><literal>Compose</literal>, key</primary>"
msgid "<primary><literal>Meta</literal>, key</primary>"
msgstr "<primary><literal>Meta</literal>, key</primary>"
msgid "<primary>key</primary><secondary><literal>Meta</literal></secondary>"
msgstr "<primary>key</primary><secondary><literal>Meta</literal></secondary>"
msgid "<primary>key</primary><secondary><literal>Compose</literal></secondary>"
msgstr "<primary>key</primary><secondary><literal>Compose</literal></secondary>"
#, fuzzy
#| msgid "Note that the keyboard configuration for graphical mode described here only affects the default layout; the GNOME and KDE environments, among others, provide a keyboard control panel in their preferences allowing each user to have their own configuration. Some additional options regarding the behavior of some particular keys are also available in these control panels."
msgid "Note that the keyboard configuration for graphical mode described here only affects the default layout; the GNOME and KDE Plasma environments, among others, provide a keyboard control panel in their preferences allowing each user to have their own configuration. Some additional options regarding the behavior of some particular keys are also available in these control panels."
msgstr "Lưu ý rằng cấu hình bàn phím cho chế độ đồ họa được mô tả ở đây chỉ ảnh hưởng đến bố cục mặc định; môi trường GNOME và KDE là trong số các công cụ khác cung cấp bảng điều khiển bằng bàn phím theo sở thích cho phép mỗi người dùng có cấu hình riêng. Một số tùy chọn bổ sung liên quan đến hành vi của một số phím cụ thể cũng có sẵn trong các trình điều khiển này."
msgid "Migrating to UTF-8"
msgstr "Chuyển đổi sang UTF-8"
msgid "The generalization of UTF-8 encoding has been a long awaited solution to numerous difficulties with interoperability, since it facilitates international exchange and removes the arbitrary limits on characters that can be used in a document. The one drawback is that it had to go through a rather difficult transition phase. Since it could not be completely transparent (that is, it could not happen at the same time all over the world), two conversion operations were required: one on file contents, and the other on filenames. Fortunately, the bulk of this migration has been completed and we discuss it largely for reference."
msgstr "Việc tổng quát hoá việc bảng mã UTF-8 là một giải pháp lâu dài để giải quyết nhiều khó khăn trong khả năng tương tác, vì nó tạo thuận lợi cho trao đổi quốc tế và loại bỏ các giới hạn tùy ý về các ký tự có thể được sử dụng trong một tài liệu. Hạn chế nhất là phải trải qua giai đoạn chuyển đổi khá khó khăn. Vì nó không thể hoàn toàn minh bạch (tức là, nó không thể xảy ra cùng một lúc trên toàn thế giới), cần phải thực hiện hai thao tác chuyển đổi: một trong các tệp tin, và một trong các tên tập tin. May thay, phần lớn di chuyển này đã được hoàn thành và chúng tôi thảo luận nó phần lớn là để tham khảo."
msgid "<emphasis>CULTURE</emphasis> <foreignphrase>Mojibake</foreignphrase> and interpretation errors"
msgstr "<emphasis> VĂN BẢN </emphasis> <foreignphrase> Mojibake </foreignphrase> và các lỗi giải thích"
msgid "When a text is sent (or stored) without encoding information, it is not always possible for the recipient to know with certainty what convention to use for determining the meaning of a set of bytes. You can usually get an idea by getting statistics on the distribution of values present in the text, but that doesn't always give a definite answer. When the encoding system chosen for reading differs from that used in writing the file, the bytes are mis-interpreted, and you get, at best, errors on some characters, or, at worst, something completely illegible."
msgstr "Khi một văn bản được gửi đi (hoặc được lưu trữ) mà không cần mã hóa thông tin, người nhận không thể chắc chắn được quy ước nào đang được sử dụng để xác định ý nghĩa của một bộ byte. Bạn thường có thể có được một ý tưởng bằng cách lấy số liệu thống kê về sự phân bố các giá trị có trong văn bản, nhưng điều đó không phải lúc nào cũng đưa ra một câu trả lời xác định. Khi hệ thống mã hoá được chọn để đọc khác với văn bản được sử dụng trong văn bản, các byte sẽ bị giải thích sai. Và bạn có thể nhận được vài lỗi về một số ký tự, hoặc tồi tệ nhất là một cái gì đó hoàn toàn không đọc được."
msgid "Thus, if a French text appears normal with the exception of accented letters and certain symbols which appear to be replaced with sequences of characters like “é” or è” or “ç”, it is probably a file encoded as UTF-8 but interpreted as ISO-8859-1 or ISO-8859-15. This is a sign of a local installation that has not yet been migrated to UTF-8. If, instead, you see question marks instead of accented letters — even if these question marks seem to also replace a character that should have followed the accented letter — it is likely that your installation is already configured for UTF-8 and that you have been sent a document encoded in Western ISO."
msgstr "Do đó, nếu một văn bản tiếng Pháp xuất hiện bình thường với ngoại lệ các chữ cái có dấu và các ký hiệu nhất định được thay thế bằng các chuỗi ký tự như “é” or è” hoặc “ç”, có thể nó là một tập tin được mã hoá là UTF-8 nhưng lại được hiểu là ISO-8859-1 hoặc ISO-8859-15. Đây là dấu hiệu của một cài đặt cục bộ chưa được di chuyển sang UTF-8. Nếu thay vào đó, bạn sẽ thấy các dấu chấm hỏi thay vì các chữ cái có dấu - thậm chí nếu các dấu chấm hỏi này cũng có thể thay thế một ký tự cần theo sau chữ có dấu - có khả năng cài đặt của bạn đã được định cấu hình cho UTF-8 và bạn đã gửi một tài liệu được mã hoá theo tiêu chuẩn Western ISO."
msgid "So much for “simple” cases. These cases only appear in Western culture, since Unicode (and UTF-8) was designed to maximize the common points with historical encodings for Western languages based on the Latin alphabet, which allows recognition of parts of the text even when some characters are missing."
msgstr "Rất nhiều các trường hợp “đơn giản”. Các trường hợp này chỉ xuất hiện trong văn hoá phương Tây, vì Unicode (và UTF-8) được thiết kế để tối đa hóa các điểm chung với mã hoá lịch sử cho các ngôn ngữ phương Tây dựa trên bảng chữ cái Latinh, nên nó cho phép nhận diện các phần của văn bản ngay cả khi một số ký tự bị thiếu."
msgid "In more complex configurations, which, for example, involve two environments corresponding to two different languages that do not use the same alphabet, you often get completely illegible results — a series of abstract symbols that have nothing to do with each other. This is especially common with Asian languages due to their numerous languages and writing systems. The Japanese word <foreignphrase>mojibake</foreignphrase> has been adopted to describe this phenomenon. When it appears, diagnosis is more complex and the simplest solution is often to simply migrate to UTF-8 on both sides."
msgstr "Trong các cấu hình phức tạp hơn, ví dụ liên quan đến hai môi trường tương ứng với hai ngôn ngữ khác nhau không sử dụng cùng một bảng chữ cái, bạn thường nhận được kết quả hoàn toàn không đọc được - một loạt các biểu tượng trừu tượng không liên quan gì đến nhau. Điều này đặc biệt phổ biến với các ngôn ngữ Á Châu do nhiều ngôn ngữ và hệ thống văn bản của họ. Từ tiếng Nhật <foreignphrase>mojibake</foreignphrase> đã được thông qua để mô tả hiện tượng này. Khi xuất hiện, chẩn đoán phức tạp hơn và giải pháp đơn giản nhất chỉ đơn giản là di chuyển sang bảng mã UTF-8 ở cả hai hệ thống."
msgid "As far as file names are concerned, the migration can be relatively simple. The <command>convmv</command> tool (in the package with the same name) was created specifically for this purpose; it allows renaming files from one encoding to another. The use of this tool is relatively simple, but we recommend doing it in two steps to avoid surprises. The following example illustrates a UTF-8 environment containing directory names encoded in ISO-8859-15, and the use of <command>convmv</command> to rename them."
msgstr "Về tên tập tin cũng được quan tâm, việc chuyển đổi có thể tương đối đơn giản. Công cụ <command>convmv</command> (trong gói có cùng tên) được tạo ra cho mục đích này; nó cho phép đổi tên các tập tin từ một mã hóa khác. Việc sử dụng công cụ này tương đối đơn giản, nhưng chúng tôi khuyên bạn nên thực hiện theo hai bước để tránh gây bất ngờ. Ví dụ sau minh hoạ môi trường UTF-8 chứa các tên thư mục được mã hoá trong ISO-8859-15 và sử dụng <command>convmv</command> để đổi tên của chúng."
msgid ""
"<computeroutput>$ </computeroutput><userinput>ls travail/</userinput>\n"
"<computeroutput>Ic?nes ?l?ments graphiques Textes\n"
"$ </computeroutput><userinput>convmv -r -f iso-8859-15 -t utf-8 travail/</userinput>\n"
"<computeroutput>Starting a dry run without changes...\n"
"mv \"travail/�l�ments graphiques\" \"travail/Éléments graphiques\"\n"
"mv \"travail/Ic�nes\" \"travail/Icônes\"\n"
"No changes to your files done. Use --notest to finally rename the files.\n"
"$ </computeroutput><userinput>convmv -r --notest -f iso-8859-15 -t utf-8 travail/</userinput>\n"
"<computeroutput>mv \"travail/�l�ments graphiques\" \"travail/Éléments graphiques\"\n"
"mv \"travail/Ic�nes\" \"travail/Icônes\"\n"
"Ready!\n"
"$ </computeroutput><userinput>ls travail/</userinput>\n"
"<computeroutput>Éléments graphiques Icônes Textes</computeroutput>"
msgstr ""
"<computeroutput>$ </computeroutput><userinput>ls travail/</userinput>\n"
"<computeroutput>Ic?nes ?l?ments graphiques Textes\n"
"$ </computeroutput><userinput>convmv -r -f iso-8859-15 -t utf-8 travail/</userinput>\n"
"<computeroutput>Starting a dry run without changes...\n"
"mv \"travail/�l�ments graphiques\" \"travail/Éléments graphiques\"\n"
"mv \"travail/Ic�nes\" \"travail/Icônes\"\n"
"No changes to your files done. Use --notest to finally rename the files.\n"
"$ </computeroutput><userinput>convmv -r --notest -f iso-8859-15 -t utf-8 travail/</userinput>\n"
"<computeroutput>mv \"travail/�l�ments graphiques\" \"travail/Éléments graphiques\"\n"
"mv \"travail/Ic�nes\" \"travail/Icônes\"\n"
"Ready!\n"
"$ </computeroutput><userinput>ls travail/</userinput>\n"
"<computeroutput>Éléments graphiques Icônes Textes</computeroutput>"
msgid "For the file content, conversion procedures are more complex due to the vast variety of existing file formats. Some file formats include encoding information that facilitates the tasks of the software used to treat them; it is sufficient, then, to open these files and re-save them specifying UTF-8 encoding. In other cases, you have to specify the original encoding (ISO-8859-1 or “Western”, or ISO-8859-15 or “Western (Euro)”, according to the formulations) when opening the file."
msgstr "Đối với nội dung tệp, các thủ tục chuyển đổi phức tạp hơn do nhiều định dạng tệp tin hiện có. Một số định dạng tệp tin bao gồm mã hóa thông tin tạo điều kiện cho các tác vụ của phần mềm được sử dụng để xử lý chúng; đủ để mở những tập tin này và lưu lại chúng chỉ định mã hóa UTF-8. Trong các trường hợp khác, bạn phải xác định mã hoá gốc (ISO-8859-1 hay “Western”, hay ISO-8859-15 hay “Western (Euro)”, theo các công thức) khi mở tệp."
msgid "For simple text files, you can use <command>recode</command> (in the package of the same name) which allows automatic recoding. This tool has numerous options so you can play with its behavior. We recommend you consult the documentation, the <citerefentry> <refentrytitle>recode</refentrytitle> <manvolnum>1</manvolnum> </citerefentry> man page, or the <citerefentry> <refentrytitle>recode</refentrytitle> </citerefentry> info page (more complete)."
msgstr "Đối với các tệp văn bản đơn giản, bạn có thể sử dụng <command>recode</command> (trong gói có cùng tên) cho phép ghi lại tự động. Công cụ này có nhiều lựa chọn để bạn có thể chơi với hành vi của nó. Chúng tôi khuyên bạn nên tham khảo tài liệu, trang <citerefentry> <refentrytitle>recode</refentrytitle><manvolnum>1</manvolnum> </citerefentry>, hoặc trang thông tin <citerefentry> <refentrytitle>recode</refentrytitle> </citerefentry> (đầy đủ hơn)."
msgid "Configuring the Network"
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Essential network concepts (Ethernet, IP address, subnet, broadcast)"
msgstr ""
msgid "<primary>Ethernet</primary>"
msgstr ""
msgid "<primary>10BASE-T</primary>"
msgstr ""
msgid "<primary>100BASE-T</primary>"
msgstr ""
msgid "<primary>1000BASE-T</primary>"
msgstr ""
msgid "<primary>10GBASE-T</primary>"
msgstr ""
msgid "<primary>connector, RJ45</primary>"
msgstr ""
msgid "<primary>RJ45 connector</primary>"
msgstr ""
msgid "Most modern local networks use the Ethernet protocol, where data is split into small blocks called frames and transmitted on the wire one frame at a time. Data speeds vary from 10 Mb/s for older Ethernet cards to 100 Gb/s in the newest cards (with the most common rate currently growing from 100 Mb/s to 10 Gb/s). The most widely used cables are called 10BASE-T, 100BASE-T, 1000BASE-T, 10GBASE-T and 40GBASE-T, depending on the throughput they can reliably provide (the T stands for “twisted pair”); those cables end in an RJ45 connector. There are other cable types, used mostly for speeds of 10 Gb/s and above."
msgstr ""
msgid "<primary>address, IP address</primary>"
msgstr ""
msgid "<primary>IP address</primary>"
msgstr ""
msgid "An IP address is a number used to identify a network interface on a computer on a local network or the Internet. In the currently most widespread version of IP (IPv4), this number is encoded in 32 bits, and is usually represented as 4 numbers separated by periods (e.g. <literal>192.168.0.1</literal>), each number being between 0 and 255 (inclusive, which corresponds to 8 bits of data). The next version of the protocol, IPv6, extends this addressing space to 128 bits, and the addresses are generally represented as a series of hexadecimal numbers separated by colons (e.g., 2001:0db8:13bb:0002:0000:0000:0000:0020, or 2001:db8:13bb:2::20 for short)."
msgstr ""
msgid "<primary>subnet</primary>"
msgstr ""
msgid "<primary>mask</primary><secondary>subnet mask</secondary>"
msgstr ""
msgid "<primary>network</primary><secondary>address</secondary>"
msgstr ""
msgid "A subnet mask (netmask) defines in its binary code which portion of an IP address corresponds to the network, the remainder specifying the machine. In the example of configuring a static IPv4 address given here, the subnet mask, <literal>255.255.255.0</literal> (24 “1”s followed by 8 “0”s in binary representation) indicates that the first 24 bits of the IP address correspond to the network address, and the other 8 are specific to the machine. In IPv6, for readability, only the number of “1”s is expressed; the netmask for an IPv6 network could, thus, be <literal>64</literal>."
msgstr ""
msgid "The network address is an IP address in which the part describing the machine's number is 0. The range of IPv4 addresses in a complete network is often indicated by the syntax, <emphasis>a.b.c.d/e</emphasis>, in which <emphasis>a.b.c.d</emphasis> is the network address and <emphasis>e</emphasis> is the number of bits affected to the network part in an IP address. The example network would thus be written: <literal>192.168.0.0/24</literal>. The syntax is similar in IPv6: <literal>2001:db8:13bb:2::/64</literal>."
msgstr ""
msgid "<primary>router</primary>"
msgstr ""
msgid "<primary>bridge</primary>"
msgstr ""
msgid "A router is a machine that connects several networks to each other. All traffic coming through a router is guided to the correct network. To do this, the router analyzes incoming packets and redirects them according to the IP address of their destination. The router is often known as a gateway; in this configuration, it works as a machine that helps reach out beyond a local network (towards an extended network, such as the Internet)."
msgstr ""
msgid "<primary>broadcast</primary>"
msgstr ""
msgid "The special broadcast address connects all the stations in a network. Almost never “routed”, it only functions on the network in question. Specifically, it means that a data packet addressed to the broadcast never passes through the router."
msgstr ""
msgid "This chapter focuses on IPv4 addresses, since they are currently the most commonly used. The details of the IPv6 protocol are approached in <xref linkend=\"sect.ipv6\" />, but the concepts remain the same."
msgstr ""
msgid "The network is automatically configured during the initial installation. If Network Manager gets installed (which is generally the case for full desktop installations), then it might be that no configuration is actually required (for example, if you rely on DHCP on a wired connection and have no specific requirements). If a configuration is required (for example, for a WiFi interface), then it will create the appropriate file in <filename>/etc/NetworkManager/system-connections/</filename>."
msgstr ""
msgid "If Network Manager is not installed, then the installer will configure <emphasis role=\"pkg\">ifupdown</emphasis> by creating the <filename>/etc/network/interfaces</filename> file. A line starting with <literal>auto</literal> gives a list of interfaces to be automatically configured on boot by the <literal>networking</literal> service. When there are many interfaces, it is good practice to keep the configuration in different files inside <filename>/etc/network/interfaces.d/</filename>."
msgstr ""
msgid "In a server context, <emphasis role=\"pkg\">ifupdown</emphasis> is thus the network configuration tool that you usually get. That is why we will cover it in the next sections."
msgstr ""
msgid "<primary>network</primary><secondary>configuration</secondary>"
msgstr ""
msgid "<primary>configuration</primary><secondary>of the network</secondary>"
msgstr ""
msgid "<primary>interface</primary><secondary>network interface</secondary>"
msgstr ""
msgid "<emphasis>ALTERNATIVE</emphasis> NetworkManager"
msgstr ""
msgid "<primary><emphasis role=\"pkg\">network-manager</emphasis></primary>"
msgstr ""
msgid "If Network Manager is particularly recommended in roaming setups (see <xref linkend=\"sect.roaming-network-config\" />), it is also perfectly usable as the default network management tool. You can create “System connections” that are used as soon as the computer boots either manually with a <filename>.ini</filename>-like file in <filename>/etc/NetworkManager/system-connections/</filename> or through a graphical tool (<command>nm-connection-editor</command>). Just remember to deactivate the entries in <filename>/etc/network/interfaces</filename> that you want Network Manager to handle. <ulink type=\"block\" url=\"https://wiki.gnome.org/Projects/NetworkManager/SystemSettings\" /> <ulink type=\"block\" url=\"https://developer.gnome.org/NetworkManager/1.14/ref-settings.html\" />"
msgstr ""
msgid "Ethernet Interface"
msgstr ""
msgid "If the computer has an Ethernet card, the IP network that is associated with it must be configured by choosing from one of two methods. The simplest method is dynamic configuration with DHCP, and it requires a DHCP server on the local network. It may indicate a desired hostname, corresponding to the <literal>hostname</literal> setting in the example below. The DHCP server then sends configuration settings for the appropriate network."
msgstr ""
msgid "<primary>DHCP</primary>"
msgstr ""
msgid "DHCP configuration"
msgstr ""
msgid ""
"\n"
"auto enp0s31f6\n"
"iface enp0s31f6 inet dhcp\n"
" hostname arrakis"
msgstr ""
#, fuzzy
#| msgid "<emphasis>CULTURE</emphasis> Character sets"
msgid "<emphasis>IN PRACTICE</emphasis> Names of network interfaces"
msgstr "<emphasis>CULTURE</emphasis> Bộ ký tự"
msgid "<primary><literal>eth0</literal></primary>"
msgstr ""
#, fuzzy
#| msgid "<primary><literal>Meta</literal>, key</primary>"
msgid "<primary><literal>en*</literal></primary>"
msgstr "<primary><literal>Meta</literal>, key</primary>"
#, fuzzy
#| msgid "<primary><literal>Meta</literal>, key</primary>"
msgid "<primary><literal>wlan0</literal></primary>"
msgstr "<primary><literal>Meta</literal>, key</primary>"
#, fuzzy
#| msgid "<primary><literal>Meta</literal>, key</primary>"
msgid "<primary><literal>wl*</literal></primary>"
msgstr "<primary><literal>Meta</literal>, key</primary>"
msgid "By default, the kernel attributes generic names such a <literal>eth0</literal> (for wired Ethernet) or <literal>wlan0</literal> (for WiFi) to the network interfaces. The number in those names is a simple incremental counter representing the order in which they have been detected. With modern hardware, that order might change for each reboot and thus the default names are not reliable."
msgstr ""
msgid "Fortunately, systemd and udev are able to rename the interfaces as soon as they appear. The default name policy is defined by <filename>/lib/systemd/network/99-default.link</filename> (see <citerefentry><refentrytitle>systemd.link</refentrytitle><manvolnum>5</manvolnum></citerefentry> for an explanation of the <literal>NamePolicy</literal> entry in that file). In practice, the names are often based on the device's physical location (as guessed by where they are connected) and you will see names starting with <literal>en</literal> for wired ethernet and <literal>wl</literal> for WiFi. In the example above, the rest of the name indicates, in abbreviated form, a PCI (<literal>p</literal>) bus number (<literal>0</literal>), a slot number (<literal>s31</literal>), a function number (<literal>f6</literal>)."
msgstr ""
msgid "Obviously, you are free to override this policy and/or to complement it to customize the names of some specific interfaces. You can find out the names of the network interfaces in the output of <command>ip addr</command> (or as filenames in <filename>/sys/class/net/</filename>)."
msgstr ""
msgid "In some corner cases it might be necessary to disable the consistent naming of network devices as described above. Besides changing the default <emphasis role=\"pkg\">udev</emphasis> rule it is also possible to boot the system using the <command>net.ifnames=0</command> and <command>biosdevname=0</command> kernel parameters to achieve that."
msgstr ""
msgid "A “static” configuration must indicate network settings in a fixed manner. This includes at least the IP address and subnet mask; network and broadcast addresses are also sometimes listed. A router connecting to the exterior will be specified as a gateway."
msgstr ""
msgid "Static configuration"
msgstr ""
msgid ""
"\n"
"auto enp0s31f6\n"
"iface enp0s31f6 inet static\n"
" address 192.168.0.3/24\n"
" broadcast 192.168.0.255\n"
" network 192.168.0.0\n"
" gateway 192.168.0.1"
msgstr ""
msgid "<emphasis>NOTE</emphasis> Multiple addresses"
msgstr ""
msgid "It is possible not only to associate several interfaces to a single, physical network card, but also several IP addresses to a single interface. Remember also that an IP address may correspond to any number of names via DNS, and that a name may also correspond to any number of numerical IP addresses."
msgstr ""
msgid "As you can guess, the configurations can be rather complex, but these options are only used in very special cases. The examples cited here are typical of the usual configurations."
msgstr ""
msgid "Wireless Interface"
msgstr ""
#, fuzzy
#| msgid "<primary>locales</primary>"
msgid "<primary>wireless</primary>"
msgstr "<primary>locales</primary>"
msgid "Getting wireless network cards to work can be a bit more challenging. First of all, they often require the installation of proprietary firmwares which are not installed by default in Debian. Then wireless networks rely on cryptography to restrict access to authorized users only, this implies storing some secret key in the network configuration. Let's tackle those topics one by one."
msgstr ""
msgid "Installing the required firmwares"
msgstr ""
#, fuzzy
#| msgid "<primary>locale</primary>"
msgid "<primary>firmware</primary>"
msgstr "<primary>locale</primary>"
#, fuzzy
#| msgid "<primary>environment</primary>"
msgid "<primary>isenkram</primary>"
msgstr "<primary>environment</primary>"
msgid "First you have to enable the non-free repository in APT's sources.list file: see <xref linkend=\"sect.apt-sources.list\" /> for details about this file. Many firmware are proprietary and are thus located in this repository. You can try to skip this step if you want, but if the next step doesn't find the required firmware, retry after having enabled the non-free section."
msgstr ""
msgid "Then you have to install the appropriate <literal>firmware-*</literal> packages. If you don't know which package you need, you can install the <emphasis role=\"pkg\">isenkram</emphasis> package and run its <command>isenkram-autoinstall-firmware</command> command. The packages are often named after the hardware manufacturer or the corresponding kernel module: <emphasis role=\"pkg\">firmware-iwlwifi</emphasis> for Intel wireless cards, <emphasis role=\"pkg\">firmware-atheros</emphasis> for Qualcomm Atheros, <emphasis role=\"pkg\">firmware-ralink</emphasis> for Ralink, etc. A reboot is then recommended because the kernel driver usually looks for the firmware files when it is first loaded and no longer afterwards."
msgstr ""
msgid "Wireless specific entries in <filename>/etc/network/interfaces</filename>"
msgstr ""
#, fuzzy
#| msgid "<primary>PAM</primary>"
msgid "<primary>WPA</primary>"
msgstr "<primary>PAM</primary>"
msgid "<emphasis>ifupdown</emphasis> is able to manage wireless interfaces but it needs the help of the <emphasis role=\"pkg\">wpasupplicant</emphasis> package which provides the required integration between <emphasis>ifupdown</emphasis> and the <command>wpa_supplicant</command> command used to configure the wireless interfaces (when using WPA/WPA2 encryption). The usual entry in <filename>/etc/network/interfaces</filename> needs to be extended with two supplementary parameters to specify the name of the wireless network (aka its SSID) and the <emphasis>Pre-Shared Key</emphasis> (PSK)."
msgstr ""
msgid "DHCP configuration for a wireless interface"
msgstr ""
msgid ""
"\n"
"auto wlp4s0\n"
"iface wlp4s0 inet dhcp\n"
" wpa-ssid Falcot\n"
" wpa-psk ccb290fd4fe6b22935cbae31449e050edd02ad44627b16ce0151668f5f53c01b"
msgstr ""
msgid "The <literal>wpa-psk</literal> parameter can contain either the plain text passphrase or its hashed version generated with <command>wpa_passphrase <replaceable>SSID</replaceable> <replaceable>passphrase</replaceable></command>. If you use an unencrypted wireless connection, then you should put a <literal>wpa-key-mgmt NONE</literal> and no <literal>wpa-psk</literal> entry. For more information about the possible configuration options, have a look at <filename>/usr/share/doc/wpasupplicant/README.Debian.gz</filename>."
msgstr ""
msgid "At this point, you should consider restricting the read permissions on <filename>/etc/network/interfaces</filename> to the root user only since the file contains a private key that not all users should have access to."
msgstr ""
#, fuzzy
#| msgid "<emphasis>CULTURE</emphasis> Character sets"
msgid "<emphasis>HISTORY</emphasis> WEP encryption"
msgstr "<emphasis>CULTURE</emphasis> Bộ ký tự"
#, fuzzy
#| msgid "<primary>PAM</primary>"
msgid "<primary>WEP</primary>"
msgstr "<primary>PAM</primary>"
msgid "Usage of the deprecated WEP encryption protocol is possible with the <emphasis role=\"pkg\">wireless-tools</emphasis> package. See <filename>/usr/share/doc/wireless-tools/README.Debian</filename> for instructions."
msgstr ""
msgid "Connecting with PPP through a PSTN Modem"
msgstr ""
msgid "<primary>PPP</primary>"
msgstr ""
msgid "<primary>point to point</primary>"
msgstr ""
msgid "<primary>connection</primary><secondary>by PSTN modem</secondary>"
msgstr ""
msgid "<primary>modem</primary><secondary>PSTN</secondary>"
msgstr ""
msgid "A point to point (PPP) connection establishes an intermittent connection; this is the most common solution for connections made with a telephone modem (“PSTN modem”, since the connection goes over the public switched telephone network)."
msgstr ""
msgid "A connection by telephone modem requires an account with an access provider, including a telephone number, username, password, and, sometimes the authentication protocol to be used. Such a connection is configured using the <command>pppconfig</command> tool in the Debian package of the same name. By default, it sets up a connection named <literal>provider</literal> (as in Internet service provider). When in doubt about the authentication protocol, choose <emphasis>PAP</emphasis>: it is offered by the majority of Internet service providers."
msgstr ""
msgid "<primary><command>pppconfig</command></primary>"
msgstr ""
msgid "<primary>PAP</primary>"
msgstr ""
msgid "After configuration, it is possible to connect using the <command>pon</command> command (giving it the name of the connection as a parameter, when the default value of <literal>provider</literal> is not appropriate). The link is disconnected with the <command>poff</command> command. These two commands can be executed by the root user, or by any other user, provided they are in the <literal>dip</literal> group."
msgstr ""
msgid "<primary><command>pon</command></primary>"
msgstr ""
msgid "<primary><command>poff</command></primary>"
msgstr ""
msgid "Connecting through an ADSL Modem"
msgstr ""
msgid "<primary>connection</primary><secondary>by ADSL modem</secondary>"
msgstr ""
msgid "<primary>modem</primary><secondary>ADSL</secondary>"
msgstr ""
msgid "<primary>ADSL, modem</primary>"
msgstr ""
msgid "The generic term “ADSL modem” covers a multitude of devices with very different functions. The modems that are simplest to use with Linux are those that have an Ethernet interface (and not only a USB interface). These tend to be popular; most ADSL Internet service providers lend (or lease) a “box” with Ethernet interfaces. Depending on the type of modem, the configuration required can vary widely."
msgstr ""
msgid "Modems Supporting PPPOE"
msgstr ""
msgid "<primary>PPPOE</primary>"
msgstr ""
msgid "<primary><command>pppoeconf</command></primary>"
msgstr ""
msgid "Some Ethernet modems work with the PPPOE protocol (Point to Point Protocol over Ethernet). The <command>pppoeconf</command> tool (from the package with the same name) will configure the connection. To do so, it modifies the <filename>/etc/ppp/peers/dsl-provider</filename> file with the settings provided and records the login information in the <filename>/etc/ppp/pap-secrets</filename> and <filename>/etc/ppp/chap-secrets</filename> files. It is recommended to accept all modifications that it proposes."
msgstr ""
msgid "Once this configuration is complete, you can open the ADSL connection with the command, <command>pon dsl-provider</command> and disconnect with <command>poff dsl-provider</command>."
msgstr ""
msgid "<primary><literal>dsl-provider</literal></primary>"
msgstr ""
msgid "<emphasis>TIP</emphasis> Starting <command>ppp</command> at boot"
msgstr ""
msgid "<primary><command>systemd</command></primary>"
msgstr ""
msgid "<primary><command>init</command></primary>"
msgstr ""
msgid "PPP connections over ADSL are, by definition, intermittent. Since they are usually not billed according to time, there are few downsides to the temptation of keeping them always open. The standard means to do so is to use the init system."
msgstr ""
msgid "With systemd, adding an automatically restarting task for the ADSL connection is a simple matter of creating a “unit file” such as <filename>/etc/systemd/system/adsl-connection.service</filename>, with contents such as the following:"
msgstr ""
msgid ""
"[Unit]\n"
"Description=ADSL connection\n"
"\n"
"[Service]\n"
"Type=forking\n"
"ExecStart=/usr/sbin/pppd call dsl-provider\n"
"Restart=always\n"
"\n"
"[Install]\n"
"WantedBy=multi-user.target"
msgstr ""
msgid "Once this unit file has been defined, it needs to be enabled with <command>systemctl enable adsl-connection</command>. Then the loop can be started manually with <command>systemctl start adsl-connection</command>; it will also be started automatically on boot."
msgstr ""
msgid "On systems not using <command>systemd</command> (including <emphasis role=\"distribution\">Wheezy</emphasis> and earlier versions of Debian), the standard SystemV init works differently. On such systems, all that is needed is to add a line such as the following at the end of the <filename>/etc/inittab</filename> file; then, any time the connection is disconnected, <command>init</command> will reconnect it."
msgstr ""
msgid ""
"\n"
"adsl:2345:respawn:/usr/sbin/pppd call dsl-provider"
msgstr ""
msgid "For ADSL connections that auto-disconnect on a daily basis, this method reduces the duration of the interruption."
msgstr ""
msgid "Modems Supporting PPTP"
msgstr ""
msgid "<primary>PPTP</primary>"
msgstr ""
msgid "The PPTP (Point-to-Point Tunneling Protocol) protocol was created by Microsoft. Deployed at the beginning of ADSL, it was quickly replaced by PPPOE. If this protocol is forced on you, see <xref linkend=\"sect.pptp\" />."
msgstr ""
msgid "Modems Supporting DHCP"
msgstr ""
msgid "When a modem is connected to the computer by an Ethernet cable (crossover cable) you typically configure a network connection by DHCP on the computer; the modem automatically acts as a gateway by default and takes care of routing (meaning that it manages the network traffic between the computer and the Internet)."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Crossover cable for a direct Ethernet connection"
msgstr ""
msgid "<primary>crossover cable</primary>"
msgstr ""
msgid "Computer network cards expect to receive data on specific wires in the cable, and send their data on others. When you connect a computer to a local network, you usually connect a cable (straight or crossover) between the network card and a repeater or switch. However, if you want to connect two computers directly (without an intermediary switch or repeater), you must route the signal sent by one card to the receiving side of the other card, and vice-versa. This is the purpose of a crossover cable, and the reason it is used."
msgstr ""
msgid "Note that this distinction has become almost irrelevant over time, as modern network cards are able to detect the type of cable present and adapt accordingly, so it won't be unusual that both kinds of cable will work in a given location."
msgstr ""
msgid "Most “ADSL routers” on the market can be used like this, as do most of the ADSL modems provided by Internet services providers."
msgstr ""
msgid "Automatic Network Configuration for Roaming Users"
msgstr ""
msgid "<primary>network</primary><secondary>roaming configuration</secondary>"
msgstr ""
msgid "Many Falcot engineers have a laptop computer that, for professional purposes, they also use at home. The network configuration to use differs according to location. At home, it may be a wifi network (protected by a WPA key), while the workplace uses a wired network for greater security and more bandwidth."
msgstr ""
msgid "To avoid having to manually connect or disconnect the corresponding network interfaces, administrators installed the <emphasis role=\"pkg\">network-manager</emphasis> package on these roaming machines. This software enables a user to easily switch from one network to another using a small icon displayed in the notification area of their graphical desktop. Clicking on this icon displays a list of available networks (both wired and wireless), so they can simply choose the network they wish to use. The program saves the configuration for the networks to which the user has already connected, and automatically switches to the best available network when the current connection drops."
msgstr ""
msgid "In order to do this, the program is structured in two parts: a daemon running as root handles activation and configuration of network interfaces and a user interface controls this daemon. PolicyKit handles the required authorizations to control this program and Debian configured PolicyKit in such a way so that members of the netdev group can add or change Network Manager connections."
msgstr ""
msgid "Network Manager knows how to handle various types of connections (DHCP, manual configuration, local network), but only if the configuration is set with the program itself. This is why it will systematically ignore all network interfaces in <filename>/etc/network/interfaces</filename> and <filename>/etc/network/interfaces.d/</filename> for which it is not suited. Since Network Manager doesn't give details when no network connections are shown, the easy way is to delete from <filename>/etc/network/interfaces</filename> any configuration for all interfaces that must be managed by Network Manager."
msgstr ""
msgid "Note that this program is installed by default when the “Desktop Environment” task is chosen during initial installation."
msgstr ""
msgid "Setting the Hostname and Configuring the Name Service"
msgstr ""
msgid "<primary>name</primary><secondary>attribution and resolution</secondary>"
msgstr ""
msgid "<primary>assignment of names</primary>"
msgstr ""
msgid "The purpose of assigning names to IP numbers is to make them easier for people to remember. In reality, an IP address identifies a network interface associated with a device such as a network card. Since each machine can have several network cards, and several interfaces on each card, one single computer can have several names in the domain name system."
msgstr ""
msgid "Each machine is, however, identified by a main (or “canonical”) name, stored in the <filename>/etc/hostname</filename> file and communicated to the Linux kernel by initialization scripts through the <command>hostname</command> command. The current value is available in a virtual filesystem, and you can get it with the <command>cat /proc/sys/kernel/hostname</command> command."
msgstr ""
msgid "<primary><command>hostname</command></primary>"
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> <filename>/proc/</filename> and <filename>/sys/</filename>, virtual filesystems"
msgstr ""
msgid "<primary><filename>/proc/</filename></primary>"
msgstr ""
msgid "<primary><filename>proc</filename></primary>"
msgstr ""
msgid "<primary><filename>/sys/</filename></primary>"
msgstr ""
msgid "<primary><filename>sys</filename></primary>"
msgstr ""
msgid "The <filename>/proc/</filename> and <filename>/sys/</filename> file trees are generated by “virtual” filesystems. This is a practical means of recovering information from the kernel (by listing virtual files) and communicating them to it (by writing to virtual files)."
msgstr ""
msgid "<filename>/sys/</filename> in particular is designed to provide access to internal kernel objects, especially those representing the various devices in the system. The kernel can, thus, share various pieces of information: the status of each device (for example, if it is in energy saving mode), whether it is a removable device, etc. Note that <filename>/sys/</filename> has only existed since kernel version 2.6. <filename>/proc/</filename> describes the current state of the kernel: the files in this directory contain information about the processes running on the system and its hardware."
msgstr ""
msgid "Surprisingly, the domain name is not managed in the same way, but comes from the complete name of the machine, acquired through name resolution. You can change it in the <filename>/etc/hosts</filename> file; simply write a complete name for the machine there at the beginning of the list of names associated with the address of the machine, as in the following example:"
msgstr ""
msgid ""
"\n"
"127.0.0.1 localhost\n"
"192.168.0.1 arrakis.falcot.com arrakis"
msgstr ""
msgid "<primary><filename>hosts</filename></primary>"
msgstr ""
msgid "<primary><filename>/etc/hosts</filename></primary>"
msgstr ""
msgid "<primary>domain</primary><secondary>name</secondary>"
msgstr ""
msgid "<primary>name</primary><secondary>domain</secondary>"
msgstr ""
msgid "<primary>NSS</primary>"
msgstr ""
msgid "Name Resolution"
msgstr ""
msgid "<primary>resolution</primary><secondary>name</secondary>"
msgstr ""
msgid "<primary>name</primary><secondary>resolution</secondary>"
msgstr ""
msgid "The mechanism for name resolution in Linux is modular and can use various sources of information declared in the <filename>/etc/nsswitch.conf</filename> file. The entry that involves host name resolution is <literal>hosts</literal>. By default, it contains <literal>files dns</literal>, which means that the system consults the <filename>/etc/hosts</filename> file first, then DNS servers. NIS/NIS+ or LDAP servers are other possible sources."
msgstr ""
msgid "<emphasis>NOTE</emphasis> NSS and DNS"
msgstr ""
msgid "Be aware that the commands specifically intended to query DNS (especially <command>host</command>) do not use the standard name resolution mechanism (NSS). As a consequence, they do not take into consideration <filename>/etc/nsswitch.conf</filename>, and thus, not <filename>/etc/hosts</filename> either."
msgstr ""
msgid "Configuring DNS Servers"
msgstr ""
msgid "<primary>DNS</primary>"
msgstr ""
msgid "<primary>Domain Name Service</primary>"
msgstr ""
msgid "DNS (Domain Name Service) is a distributed and hierarchical service mapping names to IP addresses, and vice-versa. Specifically, it can turn a human-friendly name such as <literal>www.eyrolles.com</literal> into the actual IP address, <literal>213.244.11.247</literal>."
msgstr ""
msgid "To access DNS information, a DNS server must be available to relay requests. Falcot Corp has its own, but an individual user is more likely to use the DNS servers provided by their ISP."
msgstr ""
msgid "<primary><filename>resolv.conf</filename></primary>"
msgstr ""
msgid "<primary><literal>nameserver</literal></primary>"
msgstr ""
msgid "The DNS servers to be used are indicated in the <filename>/etc/resolv.conf</filename>, one per line, with the <literal>nameserver</literal> keyword preceding an IP address, as in the following example:"
msgstr ""
msgid ""
"\n"
"nameserver 212.27.32.176\n"
"nameserver 212.27.32.177\n"
"nameserver 8.8.8.8"
msgstr ""
msgid "Note that the <filename>/etc/resolv.conf</filename> file may be handled automatically (and overwritten) when the network is managed by NetworkManager or configured via DHCP."
msgstr ""
msgid "The <filename>/etc/hosts</filename> file"
msgstr ""
msgid "If there is no name server on the local network, it is still possible to establish a small table mapping IP addresses and machine hostnames in the <filename>/etc/hosts</filename> file, usually reserved for local network stations. The syntax of this file as described in <citerefentry><refentrytitle>hosts</refentrytitle> <manvolnum>5</manvolnum></citerefentry> is very simple: each line indicates a specific IP address followed by the list of any associated names (the first being “completely qualified”, meaning it includes the domain name)."
msgstr ""
msgid "This file is available even during network outages or when DNS servers are unreachable, but will only really be useful when duplicated on all the machines on the network. The slightest alteration in correspondence will require the file to be updated everywhere. This is why <filename>/etc/hosts</filename> generally only contains the most important entries."
msgstr ""
msgid "This file will be sufficient for a small network not connected to the Internet, but with 5 machines or more, it is recommended to install a proper DNS server."
msgstr ""
msgid "<emphasis>TIP</emphasis> Bypassing DNS"
msgstr ""
msgid "Since applications check the <filename>/etc/hosts</filename> file before querying DNS, it is possible to include information in there that is different from what the DNS would return, and therefore to bypass normal DNS-based name resolution."
msgstr ""
msgid "This allows, in the event of DNS changes not yet propagated, to test access to a website with the intended name even if this name is not properly mapped to the correct IP address yet."
msgstr ""
msgid "Another possible use is to redirect traffic intended for a specific host to the localhost, thus preventing any communication with the given host. For example, hostnames of servers dedicated to serving ads could be diverted which would bypass these ads resulting in more fluid, less distracting, navigation."
msgstr ""
msgid "User and Group Databases"
msgstr ""
msgid "<primary>user</primary><secondary>database</secondary>"
msgstr ""
msgid "<primary>group</primary><secondary>database</secondary>"
msgstr ""
msgid "<primary>database</primary><secondary>of users</secondary>"
msgstr ""
msgid "<primary>database</primary><secondary>of groups</secondary>"
msgstr ""
msgid "The list of users is usually stored in the <filename>/etc/passwd</filename> file, while the <filename>/etc/shadow</filename> file stores hashed passwords. Both are text files, in a relatively simple format, which can be read and modified with a text editor. Each user is listed there on a line with several fields separated with a colon (“<literal>:</literal>”)."
msgstr ""
msgid "<emphasis>NOTE</emphasis> Editing system files"
msgstr ""
msgid "The system files mentioned in this chapter are all plain text files, and can be edited with a text editor. Considering their importance to core system functionality, it is always a good idea to take extra precautions when editing system files. First, always make a copy or backup of a system file before opening or altering it. Second, on servers or machines where more than one person could potentially access the same file at the same time, take extra steps to guard against file corruption."
msgstr ""
msgid "For this purpose, it is enough to use the <command>vipw</command> command to edit the <filename>/etc/passwd</filename> file, or <command>vigr</command> to edit <filename>/etc/group</filename>. These commands lock the file in question prior to running the text editor, (<command>vi</command> by default, unless the <varname>EDITOR</varname> environment variable has been altered). The <literal>-s</literal> option in these commands allows editing the corresponding <foreignphrase>shadow</foreignphrase> file."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Crypt, a one-way function"
msgstr ""
msgid "<primary>crypt</primary>"
msgstr ""
msgid "<command>crypt</command> is a one-way function that transforms a string (<varname>A</varname>) into another string (<varname>B</varname>) in a way that <varname>A</varname> cannot be derived from <varname>B</varname>. The only way to identify <varname>A</varname> is to test all possible values, checking each one to determine if transformation by the function will produce <varname>B</varname> or not. It uses up to 8 characters as input (string <varname>A</varname>) and generates a string of 13, printable, ASCII characters (string <varname>B</varname>)."
msgstr ""
msgid "User List: <filename>/etc/passwd</filename>"
msgstr ""
msgid "Here is the list of fields in the <filename>/etc/passwd</filename> file:"
msgstr ""
msgid "<primary><command>passwd</command></primary>"
msgstr ""
msgid "<primary><filename>/etc/passwd</filename></primary>"
msgstr ""
msgid "<primary><literal>uid</literal></primary>"
msgstr ""
msgid "<primary><literal>gid</literal></primary>"
msgstr ""
msgid "<primary><literal>GECOS</literal></primary>"
msgstr ""
msgid "<primary><literal>login</literal></primary>"
msgstr ""
msgid "login, for example <literal>rhertzog</literal>;"
msgstr ""
msgid "password: this is a password encrypted by a one-way function (<command>crypt</command>), relying on <literal>DES</literal>, <literal>MD5</literal>, <literal>SHA-256</literal> or <literal>SHA-512</literal>. The special value “<literal>x</literal>” indicates that the encrypted password is stored in <filename>/etc/shadow</filename>;"
msgstr ""
msgid "<literal>uid</literal>: unique number identifying each user;"
msgstr ""
msgid "<literal>gid</literal>: unique number for the user's main group (Debian creates a specific group for each user by default);"
msgstr ""
msgid "<literal>GECOS</literal>: data field usually containing the user's full name;"
msgstr ""
msgid "login directory, assigned to the user for storage of their personal files (the environment variable <varname>$HOME</varname> generally points here);"
msgstr ""
msgid "program to execute upon login. This is usually a command interpreter (shell), giving the user free rein. If you specify <command>/bin/false</command> (which does nothing and returns control immediately), the user cannot login."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Unix group"
msgstr ""
msgid "<primary>group</primary>"
msgstr ""
msgid "A Unix group is an entity including several users so that they can easily share files using the integrated permission system (by benefiting from the same rights). You can also restrict use of certain programs to a specific group."
msgstr ""
msgid "The Hidden and Encrypted Password File: <filename>/etc/shadow</filename>"
msgstr ""
msgid "<primary><filename>shadow</filename></primary>"
msgstr ""
msgid "<primary><filename>/etc/shadow</filename></primary>"
msgstr ""
msgid "The <filename>/etc/shadow</filename> file contains the following fields:"
msgstr ""
msgid "login;"
msgstr ""
msgid "encrypted password;"
msgstr ""
msgid "several fields managing password expiration."
msgstr ""
msgid "<emphasis>DOCUMENTATION</emphasis> <filename>/etc/passwd</filename>, <filename>/etc/shadow</filename> and <filename>/etc/group</filename> file formats"
msgstr ""
msgid "These formats are documented in the following man pages: <citerefentry><refentrytitle>passwd</refentrytitle><manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>shadow</refentrytitle><manvolnum>5</manvolnum></citerefentry>, and <citerefentry><refentrytitle>group</refentrytitle><manvolnum>5</manvolnum></citerefentry>."
msgstr ""
msgid "<emphasis>SECURITY</emphasis> <filename>/etc/shadow</filename> file security"
msgstr ""
msgid "<filename>/etc/shadow</filename>, unlike its alter-ego, <filename>/etc/passwd</filename>, cannot be read by regular users. Any hashed password stored in <filename>/etc/passwd</filename> is readable by anybody; a cracker could try to “break” (or reveal) a password by one of several “brute force” methods which, simply put, guess at commonly used combinations of characters. This attack — called a \"dictionary attack\" — is no longer possible on systems using <filename>/etc/shadow</filename>."
msgstr ""
msgid "Modifying an Existing Account or Password"
msgstr ""
msgid "<primary><command>chsh</command></primary>"
msgstr ""
msgid "<primary><command>chfn</command></primary>"
msgstr ""
msgid "<primary><command>chage</command></primary>"
msgstr ""
msgid "<primary>password</primary>"
msgstr ""
msgid "The following commands allow modification of the information stored in specific fields of the user databases: <command>passwd</command> permits a regular user to change their password, which in turn, updates the <filename>/etc/shadow</filename> file; <command>chfn</command> (CHange Full Name), reserved for the super-user (root), modifies the <literal>GECOS</literal> field. <command>chsh</command> (CHange SHell) allows the user to change their login shell; however, available choices will be limited to those listed in <filename>/etc/shells</filename>; the administrator, on the other hand, is not bound by this restriction and can set the shell to any program of their choosing."
msgstr ""
msgid "Finally, the <command>chage</command> (CHange AGE) command allows the administrator to change the password expiration settings (the <literal>-l <replaceable>user</replaceable></literal> option will list the current settings). You can also force the expiration of a password using the <command>passwd -e <replaceable>user</replaceable></command> command, which will require the user to change their password the next time they log in."
msgstr ""
msgid "Disabling an Account"
msgstr ""
msgid "<primary>Disable an account</primary>"
msgstr ""
msgid "<primary>account</primary><secondary>disable</secondary>"
msgstr ""
msgid "You may find yourself needing to “disable an account” (lock out a user), as a disciplinary measure, for the purposes of an investigation, or simply in the event of a prolonged or definitive absence of a user. A disabled account means the user cannot login or gain access to the machine. The account remains intact on the machine and no files or data are deleted; it is simply inaccessible. This is accomplished by using the command <command>passwd -l <replaceable>user</replaceable></command> (lock). Re-enabling the account is done in similar fashion, with the <literal>-u</literal> option (unlock)."
msgstr ""
msgid "<emphasis>GOING FURTHER</emphasis> NSS and system databases"
msgstr ""
msgid "<primary>Name Service Switch</primary>"
msgstr ""
msgid "Instead of using the usual files to manage lists of users and groups, you could use other types of databases, such as LDAP or <command>db</command>, by using an appropriate NSS (Name Service Switch) module. The modules used are listed in the <filename>/etc/nsswitch.conf</filename> file, under the <literal>passwd</literal>, <literal>shadow</literal> and <literal>group</literal> entries. See <xref linkend=\"sect.config-nss\" /> for a specific example of the use of an NSS module by LDAP."
msgstr ""
msgid "Group List: <filename>/etc/group</filename>"
msgstr ""
msgid "Groups are listed in the <filename>/etc/group</filename> file, a simple textual database in a format similar to that of the <filename>/etc/passwd</filename> file, with the following fields:"
msgstr ""
msgid "group name;"
msgstr ""
msgid "password (optional): This is only used to join a group when one is not a usual member (with the <command>newgrp</command> or <command>sg</command> commands, see sidebar <xref linkend=\"sidebar.working-with-several-groups\" />);"
msgstr ""
msgid "<literal>gid</literal>: unique group identification number;"
msgstr ""
msgid "list of members: list of names of users who are members of the group, separated by commas."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Working with several groups"
msgstr ""
msgid "<primary><command>newgrp</command></primary>"
msgstr ""
msgid "<primary><command>sg</command></primary>"
msgstr ""
msgid "<primary><command>id</command></primary>"
msgstr ""
msgid "<primary>group</primary><secondary>change</secondary>"
msgstr ""
msgid "Each user may be a member of many groups; one of them is their “main group”. A user's main group is, by default, created during initial user configuration. By default, each file that a user creates belongs to them, as well as to their main group. This is not always desirable; for example, when the user needs to work in a directory shared by a group other than their main group. In this case, the user needs to change their main group using one of the following commands: <command>newgrp</command>, which starts a new shell, or <command>sg</command>, which simply executes a command using the supplied alternate group. These commands also allow the user to join a group to which they do not belong. If the group is password protected, they will need to supply the appropriate password before the command is executed."
msgstr ""
msgid "Alternatively, the user can set the <literal>setgid</literal> bit on the directory, which causes files created in that directory to automatically belong to the correct group. For more details, see sidebar <xref linkend=\"sidebar.setgid-dir\" />."
msgstr ""
msgid "The <command>id</command> command displays the current state of a user, with their personal identifier (<varname>uid</varname> variable), current main group (<varname>gid</varname> variable), and the list of groups to which they belong (<varname>groups</varname> variable)."
msgstr ""
msgid "<primary><filename>group</filename></primary>"
msgstr ""
msgid "<primary><filename>/etc/group</filename></primary>"
msgstr ""
msgid "The <command>addgroup</command> and <command>delgroup</command> commands add or delete a group, respectively. The <command>groupmod</command> command modifies a group's information (its <literal>gid</literal> or identifier). The command <command>gpasswd <replaceable>group</replaceable></command> changes the password for the group, while the <command>gpasswd -r <replaceable>group</replaceable></command> command deletes it."
msgstr ""
msgid "<primary><command>addgroup</command></primary>"
msgstr ""
msgid "<primary><command>delgroup</command></primary>"
msgstr ""
msgid "<primary><command>groupmod</command></primary>"
msgstr ""
#, fuzzy
#| msgid "<primary><command>locale-gen</command></primary>"
msgid "<primary><command>gpasswd</command></primary>"
msgstr "<primary><command>locale-gen</command></primary>"
msgid "<primary>group</primary><secondary>creation</secondary>"
msgstr ""
msgid "<primary>creation</primary><secondary>of groups</secondary>"
msgstr ""
msgid "<primary>group</primary><secondary>deletion</secondary>"
msgstr ""
msgid "<primary>deletion of a group</primary>"
msgstr ""
msgid "<emphasis>TIP</emphasis> <command>getent</command>"
msgstr ""
msgid "<primary><command>getent</command></primary>"
msgstr ""
msgid "The <command>getent</command> (get entries) command checks the system databases the standard way, using the appropriate library functions, which in turn call the NSS modules configured in the <filename>/etc/nsswitch.conf</filename> file. The command takes one or two arguments: the name of the database to check, and a possible search key. Thus, the command <command>getent passwd rhertzog</command> will give the information from the user database regarding the user <literal>rhertzog</literal>."
msgstr ""
msgid "Creating Accounts"
msgstr ""
msgid "<primary>account</primary><secondary>creation</secondary>"
msgstr ""
msgid "<primary>creation</primary><secondary>of user accounts</secondary>"
msgstr ""
msgid "One of the first actions an administrator needs to do when setting up a new machine is to create user accounts. This is typically done using the <command>adduser</command> command which takes a user-name for the new user to be created, as an argument."
msgstr ""
msgid "<primary><command>adduser</command></primary>"
msgstr ""
msgid "The <command>adduser</command> command asks a few questions before creating the account, but its usage is fairly straightforward. Its configuration file, <filename>/etc/adduser.conf</filename>, includes all the interesting settings: it can be used to automatically set a quota for each new user by creating a user template, or to change the location of user accounts; the latter is rarely useful, but it comes in handy when you have a large number of users and want to divide their accounts over several disks, for instance. You can also choose a different default shell."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Quota"
msgstr ""
msgid "<primary>quota</primary>"
msgstr ""
msgid "The term “quota” refers to a limit on machine resources that a user is allowed to use. This frequently refers to disk space."
msgstr ""
msgid "The creation of an account populates the user's home directory with the contents of the <filename>/etc/skel/</filename> template. This provides the user with a set of standard directories and configuration files."
msgstr ""
msgid "<primary>group</primary><secondary>add a user</secondary>"
msgstr ""
msgid "<primary>add a user to a group</primary>"
msgstr ""
msgid "In some cases, it will be useful to add a user to a group (other than their default “main” group) in order to grant them additional permissions. For example, a user who is included in the <emphasis>audio</emphasis> group can access audio devices (see sidebar <xref linkend=\"sidebar.special-files\" />). This can be achieved with a command such as <command>adduser <replaceable>user</replaceable> <replaceable>group</replaceable></command>."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Device access permissions"
msgstr ""
msgid "<primary>device</primary><secondary>access permissions</secondary>"
msgstr ""
msgid "<primary>file</primary><secondary>special</secondary>"
msgstr ""
msgid "<primary>mode</primary><secondary>character</secondary>"
msgstr ""
msgid "<primary>mode</primary><secondary>block</secondary>"
msgstr ""
msgid "<primary>block, mode</primary>"
msgstr ""
msgid "<primary>character, mode</primary>"
msgstr ""
msgid "<primary>special, file</primary>"
msgstr ""
msgid "<primary><command>mknod</command></primary>"
msgstr ""
msgid "Each hardware peripheral device is represented under Unix with a special file, usually stored in the file tree under <filename>/dev/</filename> (DEVices). Two types of special files exist according to the nature of the device: “character mode” and “block mode” files, each mode allowing for only a limited number of operations. While character mode limits interaction with read/write operations, block mode also allows seeking within the available data. Finally, each special file is associated with two numbers (“major” and “minor”) that identify the device to the kernel in a unique manner. Such a file, created by the <command>mknod</command> command, simply contains a symbolic (and more human-friendly) name."
msgstr ""
msgid "The permissions of a special file map to the permissions necessary to access the device itself. Thus, a file such as <filename>/dev/mixer</filename>, representing the audio mixer, only has read/write permissions for the root user and members of the <literal>audio</literal> group. Only these users can operate the audio mixer."
msgstr ""
msgid "It should be noted that the combination of <emphasis role=\"pkg\">udev</emphasis> and <emphasis role=\"pkg\">policykit</emphasis> can add additional permissions to allow users physically connected to the console (and not through the network) to access to certain devices."
msgstr ""
msgid "Shell Environment"
msgstr ""
msgid "Command interpreters (or shells) can be a user's first point of contact with the computer, and they must therefore be rather friendly. Most of them use initialization scripts that allow configuration of their behavior (automatic completion, prompt text, etc.)."
msgstr ""
msgid "<primary>command line interface</primary>"
msgstr ""
msgid "<primary>command interpreter</primary>"
msgstr ""
msgid "<primary>shell</primary>"
msgstr ""
msgid "<primary><command>bash</command></primary>"
msgstr ""
msgid "<command>bash</command>, the standard shell, uses the <filename>/etc/bash.bashrc</filename> initialization script for “interactive” shells, and <filename>/etc/profile</filename> for “login” shells."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Login shell and (non) interactive shell"
msgstr ""
msgid "In simple terms, a login shell is invoked when you login to the console either locally or remotely via <command>ssh</command>, or when you run an explicit <command>bash --login</command> command. Regardless of whether it is a login shell or not, a shell can be interactive (in an <command>xterm</command>-type terminal for instance); or non-interactive (when executing a script)."
msgstr ""
msgid "<emphasis>DISCOVERY</emphasis> Other shells, other scripts"
msgstr ""
msgid "Each command interpreter has a specific syntax and its own configuration files. Thus, <command>zsh</command> uses <filename>/etc/zshrc</filename> and <filename>/etc/zshenv</filename>; <command>tcsh</command> uses <filename>/etc/csh.cshrc</filename>, <filename>/etc/csh.login</filename> and <filename>/etc/csh.logout</filename>. The man pages for these programs document which files they use."
msgstr ""
msgid "<primary><command>zsh</command></primary>"
msgstr ""
#, fuzzy
#| msgid "<primary><command>locale-gen</command></primary>"
msgid "<primary><command>tcsh</command></primary>"
msgstr "<primary><command>locale-gen</command></primary>"
msgid "For <command>bash</command>, it is useful to activate “automatic completion” in the <filename>/etc/bash.bashrc</filename> file (simply uncomment a few lines)."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Automatic completion"
msgstr ""
msgid "<primary>automatic completion</primary>"
msgstr ""
msgid "Many command interpreters provide a completion feature, which allows the shell to automatically complete a partially typed command name or argument when the user hits the <keycap>Tab</keycap> key. This lets users work more efficiently and be less error-prone."
msgstr ""
msgid "This function is very powerful and flexible. It is possible to configure its behavior according to each command. Thus, the first argument following <command>apt</command> will be proposed according to the syntax of this command, even if it does not match any file (in this case, the possible choices are <literal>install</literal>, <literal>remove</literal>, <literal>upgrade</literal>, etc.)."
msgstr ""
msgid "The package <emphasis role=\"pkg\">bash-completion</emphasis> contains completions for most common programs."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> The tilde, a shortcut to HOME"
msgstr ""
msgid "<primary>~</primary>"
msgstr ""
msgid "<primary>tilde</primary>"
msgstr ""
msgid "The tilde is often used to indicate the directory to which the environment variable, <varname>HOME</varname>, points (being the user's home directory, such as <filename>/home/rhertzog/</filename>). Command interpreters automatically make the substitution: <filename>~/hello.txt</filename> becomes <filename>/home/rhertzog/hello.txt</filename>."
msgstr ""
msgid "The tilde also allows access to another user's home directory. Thus, <filename>~rmas/bonjour.txt</filename> is synonymous with <filename>/home/rmas/bonjour.txt</filename>."
msgstr ""
msgid "In addition to these common scripts, each user can create their own <filename>~/.bashrc</filename> and <filename>~/.bash_profile</filename> to configure their shell. The most common changes are the addition of aliases; these are words that are automatically replaced with the execution of a command, which makes it faster to invoke that command. For instance, you could create the <literal>la</literal> alias for the command <command>ls -la | less</command> command; then you only have to type <command>la</command> to inspect the contents of a directory in detail."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Environment variables"
msgstr ""
msgid "<primary>environment</primary><secondary>environment variable</secondary>"
msgstr ""
msgid "<primary>variable, environment</primary>"
msgstr ""
msgid "Environment variables allow storage of global settings for the shell or various other programs called. They are contextual (each process has its own set of environment variables) but inheritable. This last characteristic offers the possibility for a login shell to declare variables which will be passed down to all programs it executes."
msgstr ""
msgid "Setting default environment variables is an important element of shell configuration. Leaving aside the variables specific to a shell, it is preferable to place them in the <filename>/etc/environment</filename> file, since it is used by the various programs likely to initiate a shell session. Variables typically defined there include <varname>ORGANIZATION</varname>, which usually contains the name of the company or organization, and <varname>HTTP_PROXY</varname>, which indicates the existence and location of an HTTP proxy."
msgstr ""
msgid "<emphasis>TIP</emphasis> All shells configured identically"
msgstr ""
msgid "Users often want to configure their login and interactive shells in the same way. To do this, they choose to interpret (or “source”) the content from <filename>~/.bashrc</filename> in the <filename>~/.bash_profile</filename> file. It is possible to do the same with files common to all users (by calling <filename>/etc/bash.bashrc</filename> from <filename>/etc/profile</filename>)."
msgstr ""
msgid "Printer Configuration"
msgstr ""
msgid "<primary>configuration</primary><secondary>printing</secondary>"
msgstr ""
msgid "<primary>printing</primary><secondary>configuration</secondary>"
msgstr ""
msgid "Printer configuration used to cause a great many headaches for administrators and users alike. These headaches are now mostly a thing of the past, thanks to CUPS, the free print server using the IPP (Internet Printing Protocol)."
msgstr ""
msgid "<primary>IPP</primary>"
msgstr ""
msgid "<primary>Internet Printing Protocol</primary>"
msgstr ""
msgid "<primary>CUPS</primary>"
msgstr ""
msgid "Debian distributes CUPS divided between several packages. The heart of the system is the scheduler, cupsd, which is in the <emphasis role=\"pkg\">cups-daemon</emphasis> package. <emphasis role=\"pkg\">cups-client</emphasis> contains utility programs to interact with the server, cupsd. lpadmin is probably the most important utility, as it is crucial for setting up a printer, but there are also facilities to disable or enable a printer queue, view or delete print jobs and display or set printer options. The CUPS framework is based on the System V printing system, but there is a compatibility package, <emphasis role=\"pkg\">cups-bsd</emphasis>, allowing use of commands such as <command>lpr</command>, <command>lpq</command> and <command>lprm</command> from the traditional BSD printing system."
msgstr ""
msgid "<primary><command>lpr</command></primary>"
msgstr ""
msgid "<primary><command>lpd</command></primary>"
msgstr ""
msgid "<primary><command>lpq</command></primary>"
msgstr ""
msgid "<emphasis>COMMUNITY</emphasis> CUPS"
msgstr ""
msgid "<primary>Common Unix Printing System</primary>"
msgstr ""
msgid "CUPS is a project and a trademark owned and managed by Apple, Inc. Prior to its acquisition by Apple it was known as the Commmon Unix Printing System. <ulink type=\"block\" url=\"https://www.cups.org/\" />"
msgstr ""
msgid "The scheduler manages print jobs and these jobs traverse a filtering system to produce a file that the printer will understand and print. The filtering system is provided by the <emphasis role=\"pkg\">cups-filters</emphasis> (<ulink url=\"https://salsa.debian.org/printing-team/cups-filters\" />) package in conjunction with <emphasis role=\"pkg\">printer-driver-*</emphasis> packages. CUPS in combination with <emphasis role=\"pkg\">cups-filters</emphasis> and <emphasis role=\"pkg\">printer-driver-*</emphasis> is the basis for the Debian printing system."
msgstr ""
msgid "Modern printers manufactured and sold within the last ten years are nearly always AirPrint-capable, and CUPS and cups-filters on Debian <emphasis role=\"distribution\">Buster</emphasis> have everything which is needed to take advantage of this facility on the network. In essence, these printers are IPP printers and an excellent fit for a driverless printing system, reducing the system to CUPS plus cups-filters. A printer-driver package can be dispensed with, and non-free printing software from vendors like Canon and Brother is no longer required. A USB-connected printer can take advantage of a modern printer with the <emphasis role=\"pkg\">ippusbxd</emphasis> package."
msgstr ""
msgid "The command <command>apt install cups</command> will install CUPS and cups-filters. It will also install the recommended <emphasis role=\"pkg\">printer-driver-gutenprint</emphasis> to provide a driver for a wide range of printers, but, unless the printer is being operated driverlessly, an alternative printer-driver might be needed for the particular device."
msgstr ""
msgid "As a package recommended by <emphasis role=\"pkg\">cups-daemon</emphasis>, <emphasis role=\"pkg\">cups-browsed</emphasis> will be on the system and networked print queues, and modern printers can be automatically discovered and set up from their DNS-SD broadcasts (Bonjour). USB printers will have to be set up manually as described in the next paragraph."
msgstr ""
msgid "The printing system is administered easily through a web interface accessible at the local address <literal>http://localhost:631/</literal>. There you can add and remove USB and network printers and administer most aspects of their behavior. Similar administration tasks can also be carried out via the graphical interface provided by a desktop environment or the <command>system-config-printer</command> graphical interface (from the homonym Debian package)."
msgstr ""
msgid "<primary><command>cups</command></primary><secondary>administration</secondary>"
msgstr ""
msgid "Configuring the Bootloader"
msgstr ""
msgid "<primary>loader</primary><secondary>bootloader</secondary>"
msgstr ""
msgid "<primary>bootloader</primary>"
msgstr ""
msgid "It is probably already functional, but it is always good to know how to configure and install the bootloader in case it disappears from the Master Boot Record. This can occur after installation of another operating system, such as Windows. The following information can also help you to modify the bootloader configuration if needed."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Master boot record"
msgstr ""
msgid "<primary>MBR</primary>"
msgstr ""
msgid "<primary>Master Boot Record</primary>"
msgstr ""
msgid "The Master Boot Record (MBR) occupies the first 512 bytes of the first hard disk, and is the first thing loaded by the BIOS to hand over control to a program capable of booting the desired operating system. In general, a bootloader gets installed in the MBR, removing its previous content."
msgstr ""
msgid "Identifying the Disks"
msgstr ""
msgid "<emphasis>CULTURE</emphasis> <emphasis>udev</emphasis> and <filename>/dev/</filename>"
msgstr ""
msgid "The <filename>/dev/</filename> directory traditionally houses so-called “special” files, intended to represent system peripherals (see sidebar <xref linkend=\"sidebar.special-files\" />). Once upon a time, it used to contain all special files that could potentially be used. This approach had a number of drawbacks among which the fact that it restricted the number of devices that one could use (due to the hardcoded list of names), and that it was impossible to know which special files were actually useful."
msgstr ""
msgid "Nowadays, the management of special files is entirely dynamic and matches better the nature of hot-swappable computer devices. The kernel cooperates with <emphasis>udev</emphasis> (<xref linkend=\"sect.udev\" />) to create and delete them as needed when the corresponding devices appear and disappear. For this reason, <filename>/dev/</filename> doesn't need to be persistent and is thus a RAM-based filesystem that starts empty and contains only the relevant entries."
msgstr ""
msgid "The kernel communicates lots of information about any newly added device and hands out a pair of major/minor numbers to identify it. With this <command>udevd</command> can create the special file under the name and with the permissions that it wants. It can also create aliases and perform additional actions (such as initialization or registration tasks). <command>udevd</command>'s behavior is driven by a large set of (customizable) rules."
msgstr ""
msgid "With dynamically assigned names, you can thus keep the same name for a given device, regardless of the connector used or the connection order, which is especially useful when you use various USB peripherals. The first partition on the first hard drive can then be called <filename>/dev/sda1</filename> for backwards compatibility, or <filename>/dev/root-partition</filename> if you prefer, or even both at the same time since <command>udevd</command> can be configured to automatically create a symbolic link."
msgstr ""
msgid "In ancient times, some kernel modules did automatically load when you tried to access the corresponding device file. This is no longer the case, and the peripheral's special file no longer exists prior to loading the module; this is no big deal, since most modules are loaded on boot thanks to automatic hardware detection. But for undetectable peripherals (such as very old disk drives or PS/2 mice), this doesn't work. Consider adding the modules, <literal>floppy</literal>, <literal>psmouse</literal> and <literal>mousedev</literal> to <filename>/etc/modules</filename> in order to force loading them on boot."
msgstr ""
msgid "<primary>hard drive, names</primary>"
msgstr ""
msgid "<primary>names</primary><secondary>of hard drives</secondary>"
msgstr ""
msgid "Configuration of the bootloader must identify the different hard drives and their partitions. Linux uses “block” special files stored in the <filename>/dev/</filename> directory, for this purpose. Since Debian <emphasis role=\"distribution\">Squeeze</emphasis>, the naming scheme for hard drives has been unified by the Linux kernel, and all hard drives (IDE/PATA, SATA, SCSI, USB, IEEE 1394) are now represented by <filename>/dev/sd*</filename>."
msgstr ""
msgid "Each partition is represented by its number on the disk on which it resides: for instance, <filename>/dev/sda1</filename> is the first partition on the first disk, and <filename>/dev/sdb3</filename> is the third partition on the second disk."
msgstr ""
msgid "<primary>partition</primary><secondary>primary</secondary>"
msgstr ""
msgid "<primary>partition</primary><secondary>extended</secondary>"
msgstr ""
msgid "<primary>partition</primary><secondary>secondary</secondary>"
msgstr ""
msgid "<primary>partition table</primary><secondary>MS-DOS format</secondary>"
msgstr ""
msgid "The PC architecture (or “i386”, including its younger cousin “amd64”) has long been limited to using the “MS-DOS” partition table format, which only allows four “primary” partitions per disk. To go beyond this limitation under this scheme, one of them has to be created as an “extended” partition, and it can then contain additional “secondary” partitions. These secondary partitions are numbered from 5. Thus the first secondary partition could be <filename>/dev/sda5</filename>, followed by <filename>/dev/sda6</filename>, etc."
msgstr ""
msgid "Another restriction of the MS-DOS partition table format is that it only allows disks up to 2 TiB in size, which is becoming a real problem with recent disks."
msgstr ""
msgid "<primary>GPT</primary><secondary>partition table format</secondary>"
msgstr ""
msgid "<primary>partition table</primary><secondary>GPT format</secondary>"
msgstr ""
msgid "A new partition table format called GPT loosens these constraints on the number of partitions (it allows up to 128 partitions when using standard settings) and on the size of the disks (up to 8 ZiB, which is more than 8 billion terabytes). If you intend to create many physical partitions on the same disk, you should therefore ensure that you are creating the partition table in the GPT format when partitioning your disk."
msgstr ""
msgid "It is not always easy to remember what disk is connected to which SATA controller, or in third position in the SCSI chain, especially since the naming of hotplugged hard drives (which includes among others most SATA disks and external disks) can change from one boot to another. Fortunately, <command>udev</command> creates, in addition to <filename>/dev/sd*</filename>, symbolic links with a fixed name, which you could then use if you wished to identify a hard drive in a non-ambiguous manner. These symbolic links are stored in <filename>/dev/disk/by-id</filename>. On a machine with two physical disks, for example, one could find the following:"
msgstr ""
msgid ""
"<computeroutput>mirexpress:/dev/disk/by-id# </computeroutput><userinput>ls -l\n"
"</userinput><computeroutput>total 0\n"
"lrwxrwxrwx 1 root root 9 23 jul. 08:58 ata-STM3500418AS_9VM3L3KP -> ../../sda\n"
"lrwxrwxrwx 1 root root 10 23 jul. 08:58 ata-STM3500418AS_9VM3L3KP-part1 -> ../../sda1\n"
"lrwxrwxrwx 1 root root 10 23 jul. 08:58 ata-STM3500418AS_9VM3L3KP-part2 -> ../../sda2\n"
"[...]\n"
"lrwxrwxrwx 1 root root 9 23 jul. 08:58 ata-WDC_WD5001AALS-00L3B2_WD-WCAT00241697 -> ../../sdb\n"
"lrwxrwxrwx 1 root root 10 23 jul. 08:58 ata-WDC_WD5001AALS-00L3B2_WD-WCAT00241697-part1 -> ../../sdb1\n"
"lrwxrwxrwx 1 root root 10 23 jul. 08:58 ata-WDC_WD5001AALS-00L3B2_WD-WCAT00241697-part2 -> ../../sdb2\n"
"[...]\n"
"lrwxrwxrwx 1 root root 9 23 jul. 08:58 scsi-SATA_STM3500418AS_9VM3L3KP -> ../../sda\n"
"lrwxrwxrwx 1 root root 10 23 jul. 08:58 scsi-SATA_STM3500418AS_9VM3L3KP-part1 -> ../../sda1\n"
"lrwxrwxrwx 1 root root 10 23 jul. 08:58 scsi-SATA_STM3500418AS_9VM3L3KP-part2 -> ../../sda2\n"
"[...]\n"
"lrwxrwxrwx 1 root root 9 23 jul. 08:58 scsi-SATA_WDC_WD5001AALS-_WD-WCAT00241697 -> ../../sdb\n"
"lrwxrwxrwx 1 root root 10 23 jul. 08:58 scsi-SATA_WDC_WD5001AALS-_WD-WCAT00241697-part1 -> ../../sdb1\n"
"lrwxrwxrwx 1 root root 10 23 jul. 08:58 scsi-SATA_WDC_WD5001AALS-_WD-WCAT00241697-part2 -> ../../sdb2\n"
"[...]\n"
"lrwxrwxrwx 1 root root 9 23 jul. 16:48 usb-LaCie_iamaKey_3ed00e26ccc11a-0:0 -> ../../sdc\n"
"lrwxrwxrwx 1 root root 10 23 jul. 16:48 usb-LaCie_iamaKey_3ed00e26ccc11a-0:0-part1 -> ../../sdc1\n"
"lrwxrwxrwx 1 root root 10 23 jul. 16:48 usb-LaCie_iamaKey_3ed00e26ccc11a-0:0-part2 -> ../../sdc2\n"
"[...]\n"
"lrwxrwxrwx 1 root root 9 23 jul. 08:58 wwn-0x5000c50015c4842f -> ../../sda\n"
"lrwxrwxrwx 1 root root 10 23 jul. 08:58 wwn-0x5000c50015c4842f-part1 -> ../../sda1\n"
"[...]\n"
"mirexpress:/dev/disk/by-id# </computeroutput>"
msgstr ""
msgid "Note that some disks are listed several times (because they behave simultaneously as ATA disks and SCSI disks), but the relevant information is mainly in the model and serial numbers of the disks, from which you can find the peripheral file."
msgstr ""
msgid "The example configuration files given in the following sections are based on the same setup: a single SATA disk, where the first partition is an old Windows installation and the second contains Debian GNU/Linux."
msgstr ""
msgid "Configuring LILO"
msgstr ""
msgid "<primary>LILO</primary>"
msgstr ""
msgid "<primary>Linux Loader</primary>"
msgstr ""
msgid "<emphasis>LILO</emphasis> (LInux LOader) is the oldest bootloader — solid but rustic. It writes the physical address of the kernel to boot on the MBR, which is why each update to LILO (or its configuration file) must be followed by the command <command>lilo</command>. Forgetting to do so will render a system unable to boot if the old kernel was removed or replaced as the new one will not be in the same location on the disk."
msgstr ""
msgid "LILO's configuration file is <filename>/etc/lilo.conf</filename>; a simple file for standard configuration is illustrated in the example below."
msgstr ""
msgid "LILO configuration file"
msgstr ""
msgid ""
"\n"
"# The disk on which LILO should be installed.\n"
"# By indicating the disk and not a partition.\n"
"# you order LILO to be installed on the MBR.\n"
"boot=/dev/sda\n"
"# the partition that contains Debian\n"
"root=/dev/sda2\n"
"# the item to be loaded by default\n"
"default=Linux\n"
"\n"
"# the most recent kernel image\n"
"image=/vmlinuz\n"
" label=Linux\n"
" initrd=/initrd.img\n"
" read-only\n"
"\n"
"# Old kernel (if the newly installed kernel doesn't boot)\n"
"image=/vmlinuz.old\n"
" label=LinuxOLD\n"
" initrd=/initrd.img.old\n"
" read-only\n"
" optional\n"
"\n"
"# only for Linux/Windows dual boot\n"
"other=/dev/sda1\n"
" label=Windows"
msgstr ""
msgid "GRUB 2 Configuration"
msgstr ""
msgid "<primary>GRUB</primary>"
msgstr ""
msgid "<primary>GRUB 2</primary>"
msgstr ""
msgid "<emphasis>GRUB</emphasis> (GRand Unified Bootloader) is more recent. It is not necessary to invoke it after each update of the kernel; <emphasis>GRUB</emphasis> knows how to read the filesystems and find the position of the kernel on the disk by itself. To install it on the MBR of the first disk, simply type <command>grub-install /dev/sda</command>. <indexterm><primary><command>grub-install</command></primary></indexterm>"
msgstr ""
msgid "<emphasis>NOTE</emphasis> Disk names for GRUB"
msgstr ""
msgid "GRUB can only identify hard drives based on information provided by the BIOS. <literal>(hd0)</literal> corresponds to the first disk thus detected, <literal>(hd1)</literal> the second, etc. In most cases, this order corresponds exactly to the usual order of disks under Linux, but problems can occur when you associate SCSI and IDE disks. GRUB used to store the correspondences that it detects in the file <filename>/boot/grub/device.map</filename>, GRUB avoids this problem nowadays by using UUIDs or file system labels when generating <filename>grub.cfg</filename>. However, the device map file is not obsolete yet, since it can be used to override when the current environment is different from the one on boot. If you find errors there (because you know that your BIOS detects drives in a different order), correct them manually and run <command>grub-install</command> again. <command>grub-mkdevicemap</command> can help creating a <filename>device.map</filename> file from which to start."
msgstr ""
msgid "Partitions also have a specific name in GRUB. When you use “classical” partitions in MS-DOS format, the first partition on the first disk is labeled, <literal>(hd0,msdos1)</literal>, the second <literal>(hd0,msdos2)</literal>, etc."
msgstr ""
msgid "GRUB 2 configuration is stored in <filename>/boot/grub/grub.cfg</filename>, but this file (in Debian) is generated from others. Be careful not to modify it by hand, since such local modifications will be lost the next time <command>update-grub</command> is run (which may occur upon update of various packages). The most common modifications of the <filename>/boot/grub/grub.cfg</filename> file (to add command line parameters to the kernel or change the duration that the menu is displayed, for example) are made through the variables in <filename>/etc/default/grub</filename>. To add entries to the menu, you can either create a <filename>/boot/grub/custom.cfg</filename> file or modify the <filename>/etc/grub.d/40_custom</filename> file. For more complex configurations, you can modify other files in <filename>/etc/grub.d</filename>, or add to them; these scripts should return configuration snippets, possibly by making use of external programs. These scripts are the ones that will update the list of kernels to boot: <filename>10_linux</filename> takes into consideration the installed Linux kernels; <filename>20_linux_xen</filename> takes into account Xen virtual systems, and <filename>30_os-prober</filename> lists other operating systems (Windows, OS X, Hurd)."
msgstr ""
msgid "Other Configurations: Time Synchronization, Logs, Sharing Access…"
msgstr ""
msgid "The many elements listed in this section are good to know for anyone who wants to master all aspects of configuration of the GNU/Linux system. They are, however, treated briefly and frequently refer to the documentation."
msgstr ""
msgid "Timezone"
msgstr ""
msgid "<primary>timezone</primary>"
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Symbolic links"
msgstr ""
msgid "<primary>link</primary><secondary>symbolic</secondary>"
msgstr ""
msgid "<primary>symbolic link</primary>"
msgstr ""
msgid "<primary><command>ln</command></primary>"
msgstr ""
msgid "A symbolic link is a pointer to another file. When you access it, the file to which it points is opened. Removal of the link will not cause deletion of the file to which it points. Likewise, it does not have its own set of permissions, but rather retains the permissions of its target. Finally, it can point to any type of file: directories, special files (sockets, named pipes, device files, etc.), even other symbolic links."
msgstr ""
msgid "The <command>ln -s <replaceable>target</replaceable> <replaceable>link-name</replaceable></command> command creates a symbolic link, named <replaceable>link-name</replaceable>, pointing to <replaceable>target</replaceable>."
msgstr ""
msgid "If the target does not exist, then the link is “broken” and accessing it will result in an error indicating that the target file does not exist. If the link points to another link, you will have a “chain” of links that turns into a “cycle” if one of the targets points to one of its predecessors. In this case, accessing one of the links in the cycle will result in a specific error (“too many levels of symbolic links”); this means the kernel gave up after several rounds of the cycle."
msgstr ""
msgid "The timezone, configured during initial installation, is a configuration item for the <emphasis role=\"pkg\">tzdata</emphasis> package. To modify it, use the <command>dpkg-reconfigure tzdata</command> command, which allows you to choose the timezone to be used in an interactive manner. Its configuration is stored in the <filename>/etc/timezone</filename> file. Additionally, the corresponding file in the <filename>/usr/share/zoneinfo</filename> directory is copied into <filename>/etc/localtime</filename>; this file contains the rules governing the dates where daylight saving time is active, for countries that use it."
msgstr ""
msgid "<primary><filename>timezone</filename></primary>"
msgstr ""
msgid "<primary><filename>/etc/timezone</filename></primary>"
msgstr ""
msgid "<primary><filename>zoneinfo</filename></primary>"
msgstr ""
msgid "<primary><filename>/usr/share/zoneinfo/</filename></primary>"
msgstr ""
msgid "<primary>DST</primary>"
msgstr ""
msgid "<primary>daylight saving time</primary>"
msgstr ""
msgid "When you need to temporarily change the timezone, use the <varname>TZ</varname> environment variable, which takes priority over the configured system default:"
msgstr ""
msgid "<primary><varname>TZ</varname></primary>"
msgstr ""
msgid ""
"\n"
"<computeroutput>$ </computeroutput><userinput>date</userinput>\n"
"<computeroutput>Thu Feb 19 11:25:18 CET 2015</computeroutput>\n"
"<computeroutput>$ </computeroutput><userinput>TZ=\"Pacific/Honolulu\" date</userinput>\n"
"<computeroutput>Thu Feb 19 00:25:21 HST 2015</computeroutput>"
msgstr ""
msgid "<emphasis>NOTE</emphasis> System clock, hardware clock"
msgstr ""
msgid "There are two time sources in a computer. A computer's motherboard has a hardware clock, called the “CMOS clock”. This clock is not very precise, and provides rather slow access times. The operating system kernel has its own, the software clock, which it keeps up to date with its own means (possibly with the help of time servers, see <xref linkend=\"sect.time-synchronization\" />). This system clock is generally more accurate, especially since it doesn't need access to hardware variables. However, since it only exists in live memory, it is zeroed out every time the machine is booted, contrary to the CMOS clock, which has a battery and therefore “survives” rebooting or halting of the machine. The system clock is, thus, set from the CMOS clock during boot, and the CMOS clock is updated on shutdown (to take into account possible changes or corrections if it has been improperly adjusted)."
msgstr ""
msgid "In practice, there is a problem, since the CMOS clock is nothing more than a counter and contains no information regarding the time zone. There is a choice to make regarding its interpretation: either the system considers it runs in universal time (UTC, formerly GMT), or in local time. This choice could be a simple shift, but things are actually more complicated: as a result of daylight saving time, this offset is not constant. The result is that the system has no way to determine whether the offset is correct, especially around periods of time change. Since it is always possible to reconstruct local time from universal time and the timezone information, we strongly recommend using the CMOS clock in universal time."
msgstr ""
msgid "Unfortunately, Windows systems in their default configuration ignore this recommendation; they keep the CMOS clock on local time, applying time changes when booting the computer by trying to guess during time changes if the change has already been applied or not. This works relatively well, as long as the system has only Windows running on it. But when a computer has several systems (whether it be a “dual-boot” configuration or running other systems via virtual machine), chaos ensues, with no means to determine if the time is correct. If you absolutely must retain Windows on a computer, you should either configure it to keep the CMOS clock as UTC (setting the registry key <literal>HKLM\\SYSTEM\\CurrentControlSet\\Control\\TimeZoneInformation\\RealTimeIsUniversal</literal> to “1” as a DWORD), or use <command>hwclock --localtime --set</command> on the Debian system to set the hardware clock and mark it as tracking the local time (and make sure to manually check your clock in spring and autumn)."
msgstr ""
msgid "Time Synchronization"
msgstr ""
msgid "<primary>time synchronization</primary>"
msgstr ""
msgid "<primary>clock</primary><secondary>synchronization</secondary>"
msgstr ""
msgid "Time synchronization, which may seem superfluous on a computer, is very important on a network. Since users do not have permissions allowing them to modify the date and time, it is important for this information to be precise to prevent confusion. Furthermore, having all of the computers on a network synchronized allows better cross-referencing of information from logs on different machines. Thus, in the event of an attack, it is easier to reconstruct the chronological sequence of actions on the various machines involved in the compromise. Data collected on several machines for statistical purposes won't make a great deal of sense if they are not synchronized."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> NTP"
msgstr ""
msgid "<primary>NTP</primary>"
msgstr ""
msgid "<primary>Network</primary><secondary>Time Protocol</secondary>"
msgstr ""
msgid "NTP (Network Time Protocol) allows a machine to synchronize with others fairly accurately, taking into consideration the delays induced by the transfer of information over the network and other possible offsets."
msgstr ""
msgid "While there are numerous NTP servers on the Internet, the more popular ones may be overloaded. This is why we recommend using the <emphasis>pool.ntp.org</emphasis> NTP server, which is, in reality, a group of machines that have agreed to serve as public NTP servers. You could even limit use to a sub-group specific to a country, with, for example, <emphasis>us.pool.ntp.org</emphasis> for the United States, or <emphasis>ca.pool.ntp.org</emphasis> for Canada, etc."
msgstr ""
msgid "However, if you manage a large network, it is recommended that you install your own NTP server, which will synchronize with the public servers. In this case, all the other machines on your network can use your internal NTP server instead of increasing the load on the public servers. You will also increase homogeneity with your clocks, since all the machines will be synchronized on the same source, and this source is very close in terms of network transfer times."
msgstr ""
msgid "For Workstations"
msgstr ""
msgid "Since work stations are regularly rebooted (even if only to save energy), synchronizing them by NTP at boot is enough. To do so, simply install the <emphasis role=\"pkg\">ntpdate</emphasis> package. You can change the NTP server used if needed by modifying the <filename>/etc/default/ntpdate</filename> file."
msgstr ""
msgid "<primary><filename>ntpdate</filename></primary>"
msgstr ""
msgid "<primary><filename>/etc/default/ntpdate</filename></primary>"
msgstr ""
msgid "For Servers"
msgstr ""
msgid "Servers are only rarely rebooted, and it is very important for their system time to be correct. To permanently maintain correct time, you would install a local NTP server, a service offered in the <emphasis role=\"pkg\">ntp</emphasis> package. In its default configuration, the server will synchronize with <emphasis>pool.ntp.org</emphasis> and provide time in response to requests coming from the local network. You can configure it by editing the <filename>/etc/ntp.conf</filename> file, the most significant alteration being the NTP server to which it refers. If the network has a lot of servers, it may be interesting to have one local time server which synchronizes with the public servers and is used as a time source by the other servers of the network."
msgstr ""
msgid "<primary><emphasis role=\"pkg\">ntp</emphasis></primary>"
msgstr ""
msgid "<primary>server</primary><secondary>NTP</secondary>"
msgstr ""
msgid "<primary>NTP</primary><secondary>server</secondary>"
msgstr ""
msgid "<emphasis>GOING FURTHER</emphasis> GPS modules and other time sources"
msgstr ""
msgid "<primary>GPS</primary>"
msgstr ""
msgid "<primary>DCF-77</primary>"
msgstr ""
msgid "If time synchronization is particularly crucial to your network, it is possible to equip a server with a GPS module (which will use the time from GPS satellites) or a DCF-77 module (which will sync time with the atomic clock near Frankfurt, Germany). In this case, the configuration of the NTP server is a little more complicated, and prior consultation of the documentation is an absolute necessity."
msgstr ""
msgid "Rotating Log Files"
msgstr ""
msgid "<primary>file</primary><secondary>logs, rotation</secondary>"
msgstr ""
msgid "<primary>logs</primary><secondary>files, rotation</secondary>"
msgstr ""
msgid "<primary>rotation of log files</primary>"
msgstr ""
msgid "<primary><command>logrotate</command></primary>"
msgstr ""
msgid "Log files can grow, fast, and it is necessary to archive them. The most common scheme is a rotating archive: the log file is regularly archived, and only the latest <replaceable>X</replaceable> archives are retained. <command>logrotate</command>, the program responsible for these rotations, follows directives given in the <filename>/etc/logrotate.conf</filename> file and all of the files in the <filename>/etc/logrotate.d/</filename> directory. The administrator may modify these files, if they wish to adapt the log rotation policy defined by Debian. The <citerefentry><refentrytitle>logrotate</refentrytitle> <manvolnum>1</manvolnum></citerefentry> man page describes all of the options available in these configuration files. You may want to increase the number of files retained in log rotation, or move the log files to a specific directory dedicated to archiving them rather than delete them. You could also send them by e-mail to archive them elsewhere."
msgstr ""
msgid "The <command>logrotate</command> program is executed daily by the <command>cron</command> scheduling program (described in <xref linkend=\"sect.task-scheduling-cron-atd\" />)."
msgstr ""
msgid "Sharing Administrator Rights"
msgstr ""
msgid "<primary>account</primary><secondary>administrator account</secondary>"
msgstr ""
msgid "<primary>root</primary>"
msgstr ""
msgid "<primary><command>sudo</command></primary>"
msgstr ""
msgid "Frequently, several administrators work on the same network. Sharing the root passwords is not very elegant, and opens the door for abuse due to the anonymity such sharing creates. The solution to this problem is the <command>sudo</command> program, which allows certain users to execute certain commands with special rights. In the most common use case, <command>sudo</command> allows a trusted user to execute any command as root. To do so, the user simply executes <command>sudo <replaceable>command</replaceable></command> and authenticates using their personal password."
msgstr ""
msgid "When installed, the <emphasis role=\"pkg\">sudo</emphasis> package gives full root rights to members of the <literal>sudo</literal> Unix group. To delegate other rights, the administrator must use the <command>visudo</command> command, which allows them to modify the <filename>/etc/sudoers</filename> configuration file (here again, this will invoke the <command>vi</command> editor, or any other editor indicated in the <varname>EDITOR</varname> environment variable). Adding a line with <literal><replaceable>username</replaceable> ALL=(ALL) ALL</literal> allows the user in question to execute any command as root."
msgstr ""
msgid "<primary><command>visudo</command></primary>"
msgstr ""
msgid "<primary><filename>sudoers</filename></primary>"
msgstr ""
msgid "<primary><filename>/etc/sudoers</filename></primary>"
msgstr ""
msgid "More sophisticated configurations allow authorization of only specific commands to specific users. All the details of the various possibilities are given in the <citerefentry><refentrytitle>sudoers</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man page."
msgstr ""
msgid "List of Mount Points"
msgstr ""
msgid "<primary>point, mount</primary>"
msgstr ""
msgid "<primary>mount point</primary>"
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Mounting and unmounting"
msgstr ""
msgid "In a Unix-like system such as Debian, files are organized in a single tree-like hierarchy of directories. The <filename>/</filename> directory is called the “root directory”; all additional directories are sub-directories within this root. “Mounting” is the action of including the content of a peripheral device (often a hard drive) into the system's general file tree. As a consequence, if you use a separate hard drive to store users' personal data, this disk will have to be “mounted” in the <filename>/home/</filename> directory. The root filesystem is always mounted at boot by the kernel; other devices are often mounted later during the startup sequence or manually with the <command>mount</command> command."
msgstr ""
msgid "<primary><command>mount</command></primary>"
msgstr ""
msgid "Some removable devices are automatically mounted when connected, especially when using the GNOME, Plasma or other graphical desktop environments. Others have to be mounted manually by the user. Likewise, they must be unmounted (removed from the file tree). Normal users do not usually have permission to execute the <command>mount</command> and <command>umount</command> commands. The administrator can, however, authorize these operations (independently for each mount point) by including the <literal>user</literal> option in the <filename>/etc/fstab</filename> file."
msgstr ""
msgid "The <command>mount</command> command can be used without arguments to list all mounted filesystems; you can execute <command>findmnt --fstab</command> to show only the filesystems from <filename>/etc/fstab</filename>. The following parameters are required to mount or unmount a device. For the complete list, please refer to the corresponding man pages, <citerefentry><refentrytitle>mount</refentrytitle> <manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>umount</refentrytitle> <manvolnum>8</manvolnum></citerefentry>. For simple cases, the syntax is simple too: for example, to mount the <filename>/dev/sdc1</filename> partition, which has an ext3 filesystem, into the <filename>/mnt/tmp/</filename> directory, you would simply run <command>mount -t ext3 /dev/sdc1 /mnt/tmp/</command>."
msgstr ""
msgid "The <filename>/etc/fstab</filename> file gives a list of all possible mounts that happen either automatically on boot or manually for removable storage devices. Each mount point is described by a line with several space-separated fields: <indexterm><primary><filename>fstab</filename></primary></indexterm> <indexterm><primary><filename>/etc/fstab</filename></primary></indexterm>"
msgstr ""
msgid "file system: this indicates where the filesystem to be mounted can be found, it can be a local device (hard drive partition, CD-ROM) or a remote filesystem (such as NFS)."
msgstr ""
msgid "This field is frequently replaced with the unique ID of the filesystem (which you can determine with <command>blkid <userinput>device</userinput></command>) prefixed with <literal>UUID=</literal>. This guards against a change in the name of the device in the event of addition or removal of disks, or if disks are detected in a different order."
msgstr ""
msgid "mount point: this is the location on the local filesystem where the device, remote system, or partition will be mounted."
msgstr ""
msgid "type: this field defines the filesystem used on the mounted device. <literal>ext4</literal>, <literal>ext3</literal>, <literal>vfat</literal>, <literal>ntfs</literal>, <literal>btrfs</literal>, <literal>xfs</literal> are a few examples."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> NFS, a network filesystem"
msgstr ""
msgid "NFS is a network filesystem; under Linux, it allows transparent access to remote files by including them in the local filesystem."
msgstr ""
msgid "A complete list of known filesystems is available in the <citerefentry><refentrytitle>mount</refentrytitle> <manvolnum>8</manvolnum></citerefentry> man page. The <literal>swap</literal> special value is for swap partitions; the <literal>auto</literal> special value tells the <command>mount</command> program to automatically detect the filesystem (which is especially useful for disk readers and USB keys, since each one might have a different filesystem);"
msgstr ""
msgid "options: there are many of them, depending on the filesystem, and they are documented in the <command>mount</command> man page. The most common are"
msgstr ""
msgid "<literal>rw</literal> or <literal>ro</literal>, meaning, respectively, that the device will be mounted with read/write or read-only permissions."
msgstr ""
msgid "<literal>noauto</literal> deactivates automatic mounting on boot."
msgstr ""
msgid "<literal>nofail</literal> allows the boot to proceed even when the device is not present. Make sure to put this option for external drives that might be unplugged when you boot, because <command>systemd</command> really ensures that all mount points that must be automatically mounted are actually mounted before letting the boot process continue to its end. Note that you can combine this with <literal>x-systemd.device-timeout=5s</literal> to tell <command>systemd</command> to not wait more than 5 seconds for the device to appear (see <citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry>)."
msgstr ""
msgid "<literal>user</literal> authorizes all users to mount this filesystem (an operation which would otherwise be restricted to the root user)."
msgstr ""
msgid "<literal>defaults</literal> means the group of default options: <literal>rw</literal>, <literal>suid</literal>, <literal>dev</literal>, <literal>exec</literal>, <literal>auto</literal>, <literal>nouser</literal> and <literal>async</literal>, each of which can be individually disabled after <literal>defaults</literal> by adding <literal>nosuid</literal>, <literal>nodev</literal> and so on to block <literal>suid</literal>, <literal>dev</literal> and so on. Adding the <literal>user</literal> option reactivates it, since <literal>defaults</literal> includes <literal>nouser</literal>."
msgstr ""
msgid "dump: this field is almost always set to <literal>0</literal>. When it is <literal>1</literal>, it tells the <command>dump</command> tool that the partition contains data that is to be backed up."
msgstr ""
msgid "pass: this last field indicates whether the integrity of the filesystem should be checked on boot, and in which order this check should be executed. If it is <literal>0</literal>, no check is conducted. The root filesystem should have the value <literal>1</literal>, while other permanent filesystems get the value <literal>2</literal>."
msgstr ""
msgid "Example <filename>/etc/fstab</filename> file"
msgstr ""
msgid ""
"\n"
"# /etc/fstab: static file system information.\n"
"#\n"
"# <file system> <mount point> <type> <options> <dump> <pass>\n"
"proc /proc proc defaults 0 0\n"
"# / was on /dev/sda1 during installation\n"
"UUID=c964222e-6af1-4985-be04-19d7c764d0a7 / ext3 errors=remount-ro 0 1\n"
"# swap was on /dev/sda5 during installation\n"
"UUID=ee880013-0f63-4251-b5c6-b771f53bd90e none swap sw 0 0\n"
"/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0\n"
"/dev/fd0 /media/floppy auto rw,user,noauto 0 0\n"
"arrakis:/shared /shared nfs defaults 0 0"
msgstr ""
msgid "The last entry in this example corresponds to a network filesystem (NFS): the <filename>/shared/</filename> directory on the <emphasis>arrakis</emphasis> server is mounted at <filename>/shared/</filename> on the local machine. The format of the <filename>/etc/fstab</filename> file is documented on the <citerefentry><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry> man page."
msgstr ""
msgid "<emphasis>GOING FURTHER</emphasis> Auto-mounting"
msgstr ""
msgid "systemd is able to manage automount points: those are filesystems that are mounted on-demand when a user attempts to access their target mount points. It can also unmount these filesystems when no process is accessing them any longer."
msgstr ""
msgid "Like most concepts in systemd, automount points are managed with dedicated units (using the <literal>.automount</literal> suffix). See <citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry> for their precise syntax."
msgstr ""
msgid "<primary><emphasis>am-utils</emphasis></primary>"
msgstr ""
msgid "<primary><command>amd</command></primary>"
msgstr ""
msgid "<primary><command>automount</command></primary>"
msgstr ""
msgid "<primary><emphasis>autofs</emphasis></primary>"
msgstr ""
msgid "<primary>automounter</primary>"
msgstr ""
msgid "Other auto-mounting utilities exist, such as <command>automount</command> in the <emphasis role=\"pkg\">autofs</emphasis> package or <command>amd</command> in the <emphasis role=\"pkg\">am-utils</emphasis>."
msgstr ""
msgid "Note also that GNOME, Plasma, and other graphical desktop environments work together with <emphasis>udisks</emphasis>, and can automatically mount removable media when they are connected."
msgstr ""
msgid "<command>locate</command> and <command>updatedb</command>"
msgstr ""
msgid "<primary><command>locate</command></primary>"
msgstr ""
msgid "<primary><command>updatedb</command></primary>"
msgstr ""
msgid "<primary><command>mlocate</command></primary>"
msgstr ""
msgid "The <command>locate</command> command can find the location of a file when you only know part of the name. It sends a result almost instantaneously, since it consults a database that stores the location of all the files on the system; this database is updated daily by the <command>updatedb</command> command. There are multiple implementations of the <command>locate</command> command and Debian picked <emphasis role=\"pkg\">mlocate</emphasis> for its standard system."
msgstr ""
msgid "<command>mlocate</command> is smart enough to only return files which are accessible to the user running the command even though it uses a database that knows about all files on the system (since its <command>updatedb</command> implementation runs with root rights). For extra safety, the administrator can use <varname>PRUNEDPATHS</varname> in <filename>/etc/updatedb.conf</filename> to exclude some directories from being indexed."
msgstr ""
msgid "Compiling a Kernel"
msgstr ""
msgid "<primary>compilation</primary><secondary>of a kernel</secondary>"
msgstr ""
msgid "<primary>kernel</primary><secondary>compilation</secondary>"
msgstr ""
msgid "The kernels provided by Debian include the largest possible number of features, as well as the maximum of drivers, in order to cover the broadest spectrum of existing hardware configurations. This is why some users prefer to recompile the kernel in order to only include what they specifically need. There are two reasons for this choice. First, it may be to optimize memory consumption, since the kernel code, even if it is never used, occupies memory for nothing (and never “goes down” on the swap space, since it is actual RAM that it uses), which can decrease overall system performance. A locally compiled kernel can also limit the risk of security problems since only a fraction of the kernel code is compiled and run."
msgstr ""
msgid "<emphasis>NOTE</emphasis> Security updates"
msgstr ""
msgid "If you choose to compile your own kernel, you must accept the consequences: Debian cannot ensure security updates for your custom kernel. By keeping the kernel provided by Debian, you benefit from updates prepared by the Debian Project's security team."
msgstr ""
msgid "Recompilation of the kernel is also necessary if you want to use certain features that are only available as patches (and not included in the standard kernel version)."
msgstr ""
msgid "<emphasis>GOING FURTHER</emphasis> The Debian Kernel Handbook"
msgstr ""
msgid "<primary><emphasis role=\"pkg\">debian-kernel-handbook</emphasis></primary>"
msgstr ""
msgid "The Debian kernel team maintains the “Debian Kernel Handbook” (also available in the <emphasis role=\"pkg\">debian-kernel-handbook</emphasis> package) with comprehensive documentation about most kernel related tasks and about how official Debian kernel packages are handled. This is the first place you should look into if you need more information than what is provided in this section. <ulink type=\"block\" url=\"https://kernel-team.pages.debian.net/kernel-handbook/\" />"
msgstr ""
msgid "Introduction and Prerequisites"
msgstr ""
msgid "Unsurprisingly Debian manages the kernel in the form of a package, which is not how kernels have traditionally been compiled and installed. Since the kernel remains under the control of the packaging system, it can then be removed cleanly, or deployed on several machines. Furthermore, the scripts associated with these packages automate the interaction with the bootloader and the initrd generator."
msgstr ""
msgid "The upstream Linux sources contain everything needed to build a Debian package of the kernel. But you still need to install <emphasis role=\"pkg\">build-essential</emphasis> to ensure that you have the tools required to build a Debian package. Furthermore, the configuration step for the kernel requires the <emphasis role=\"pkg\">libncurses5-dev</emphasis> package. Finally, the <emphasis role=\"pkg\">fakeroot</emphasis> package will enable creation of the Debian package without using administrator's rights."
msgstr ""
msgid "<emphasis>CULTURE</emphasis> The good old days of <emphasis role=\"pkg\">kernel-package</emphasis>"
msgstr ""
msgid "<primary><emphasis role=\"pkg\">kernel-package</emphasis></primary>"
msgstr ""
msgid "Before the Linux build system gained the ability to build proper Debian packages, the recommended way to build such packages was to use <command>make-kpkg</command> from the <emphasis role=\"pkg\">kernel-package</emphasis> package."
msgstr ""
msgid "Getting the Sources"
msgstr ""
msgid "<primary>Linux kernel sources</primary>"
msgstr ""
msgid "<primary>kernel</primary><secondary>sources</secondary>"
msgstr ""
msgid "<primary>source</primary><secondary>of the Linux kernel</secondary>"
msgstr ""
msgid "Like anything that can be useful on a Debian system, the Linux kernel sources are available in a package. To retrieve them, just install the <emphasis role=\"pkg\">linux-source-<replaceable>version</replaceable></emphasis> package. The <command>apt search ^linux-source</command> command lists the various kernel versions packaged by Debian. The latest version is available in the <emphasis role=\"distribution\">Unstable</emphasis> distribution: you can retrieve them without much risk (especially if your APT is configured according to the instructions of <xref linkend=\"sect.apt-mix-distros\" />). Note that the source code contained in these packages does not correspond precisely with that published by Linus Torvalds and the kernel developers; like all distributions, Debian applies a number of patches, which might (or might not) find their way into the upstream version of Linux. These modifications include backports of fixes/features/drivers from newer kernel versions, new features not yet (entirely) merged in the upstream Linux tree, and sometimes even Debian specific changes."
msgstr ""
msgid "The remainder of this section focuses on the 4.19 version of the Linux kernel, but the examples can, of course, be adapted to the particular version of the kernel that you want."
msgstr ""
msgid "We assume the <emphasis role=\"pkg\">linux-source-4.19</emphasis> package has been installed. It contains <filename>/usr/src/linux-source-4.19.tar.xz</filename>, a compressed archive of the kernel sources. You must extract these files in a new directory (not directly under <filename>/usr/src/</filename>, since there is no need for special permissions to compile a Linux kernel): <filename>~/kernel/</filename> is appropriate."
msgstr ""
msgid ""
"\n"
"<computeroutput>$ </computeroutput><userinput>mkdir ~/kernel; cd ~/kernel</userinput>\n"
"<computeroutput>$ </computeroutput><userinput>tar -xaf /usr/src/linux-source-4.19.tar.xz</userinput>"
msgstr ""
msgid "<emphasis>CULTURE</emphasis> Location of kernel sources"
msgstr ""
msgid "Traditionally, Linux kernel sources would be placed in <filename>/usr/src/linux/</filename> thus requiring root permissions for compilation. However, working with administrator rights should be avoided when not needed. There is a <literal>src</literal> group that allows members to work in this directory, but working in <filename>/usr/src/</filename> should be avoided, nevertheless. By keeping the kernel sources in a personal directory, you get security on all counts: no files in <filename>/usr/</filename> unknown to the packaging system, and no risk of misleading programs that read <filename>/usr/src/linux</filename> when trying to gather information on the used kernel."
msgstr ""
msgid "Configuring the Kernel"
msgstr ""
msgid "<primary>kernel</primary><secondary>configuration</secondary>"
msgstr ""
msgid "<primary>configuration</primary><secondary>of the kernel</secondary>"
msgstr ""
msgid "<primary><filename>.config</filename></primary>"
msgstr ""
msgid "The next step consists of configuring the kernel according to your needs. The exact procedure depends on the goals."
msgstr ""
msgid "When recompiling a more recent version of the kernel (possibly with an additional patch), the configuration will most likely be kept as close as possible to that proposed by Debian. In this case, and rather than reconfiguring everything from scratch, it is sufficient to copy the <filename>/boot/config-<replaceable>version</replaceable></filename> file (the version is that of the kernel currently used, which can be found with the <command>uname -r</command> command) into a <filename>.config</filename> file in the directory containing the kernel sources."
msgstr ""
msgid ""
"\n"
"<computeroutput>$ </computeroutput><userinput>cp /boot/config-4.19.0-5-amd64 ~/kernel/linux-source-4.19/.config</userinput>"
msgstr ""
msgid "Unless you need to change the configuration, you can stop here and skip to <xref linkend=\"sect.kernel-build\" />. If you need to change it, on the other hand, or if you decide to reconfigure everything from scratch, you must take the time to configure your kernel. There are various dedicated interfaces in the kernel source directory that can be used by calling the <command>make <replaceable>target</replaceable></command> command, where <replaceable>target</replaceable> is one of the values described below."
msgstr ""
msgid "<command>make menuconfig</command> compiles and executes a text-mode interface (this is where the <emphasis role=\"pkg\">libncurses5-dev</emphasis> package is required) which allows navigating the options available in a hierarchical structure. Pressing the <keycap>Space</keycap> key changes the value of the selected option, and <keycap>Enter</keycap> validates the button selected at the bottom of the screen; <guibutton>Select</guibutton> returns to the selected sub-menu; <guibutton>Exit</guibutton> closes the current screen and moves back up in the hierarchy; <guibutton>Help</guibutton> will display more detailed information on the role of the selected option. The arrow keys allow moving within the list of options and buttons. To exit the configuration program, choose <guibutton>Exit</guibutton> from the main menu. The program then offers to save the changes you've made; accept if you are satisfied with your choices."
msgstr ""
msgid "Other interfaces have similar features, but they work within more modern graphical interfaces; such as <command>make xconfig</command> which uses a Qt graphical interface, and <command>make gconfig</command> which uses GTK+. The former requires <emphasis role=\"pkg\">libqt4-dev</emphasis>, while the latter depends on <emphasis role=\"pkg\">libglade2-dev</emphasis> and <emphasis role=\"pkg\">libgtk2.0-dev</emphasis>."
msgstr ""
msgid "When using one of those configuration interfaces, it is always a good idea to start from a reasonable default configuration. The kernel provides such configurations in <filename>arch/<replaceable>arch</replaceable>/configs/*_defconfig</filename> and you can put your selected configuration in place with a command like <command>make x86_64_defconfig</command> (in the case of a 64-bit PC) or <command>make i386_defconfig</command> (in the case of a 32-bit PC)."
msgstr ""
msgid "<emphasis>TIP</emphasis> Dealing with outdated <filename>.config</filename> files"
msgstr ""
msgid "When you provide a <filename>.config</filename> file that has been generated with another (usually older) kernel version, you will have to update it. You can do so with <command>make oldconfig</command>, it will interactively ask you the questions corresponding to the new configuration options. If you want to use the default answer to all those questions you can use <command>make olddefconfig</command>. With <command>make oldnoconfig</command>, it will assume a negative answer to all questions."
msgstr ""
msgid "Compiling and Building the Package"
msgstr ""
msgid "<primary><command>make deb-pkg</command></primary>"
msgstr ""
msgid "<emphasis>NOTE</emphasis> Clean up before rebuilding"
msgstr ""
msgid "If you have already compiled once in the directory and wish to rebuild everything from scratch (for example, because you substantially changed the kernel configuration), you will have to run <command>make clean</command> to remove the compiled files. <command>make distclean</command> removes even more generated files, including your <filename>.config</filename> file too, so make sure to backup it first. If you copied the configuration from <filename>/boot/</filename>, you must change the system trusted keys option, providing an empty string is enough: <literal>CONFIG_SYSTEM_TRUSTED_KEYS = \"\"</literal>."
msgstr ""
msgid "Once the kernel configuration is ready, a simple <command>make deb-pkg</command> will generate up to 5 Debian packages: <emphasis role=\"pkg\">linux-image-<replaceable>version</replaceable></emphasis> that contains the kernel image and the associated modules, <emphasis role=\"pkg\">linux-headers-<replaceable>version</replaceable></emphasis> which contains the header files required to build external modules, <emphasis role=\"pkg\">linux-firmware-image-<replaceable>version</replaceable></emphasis> which contains the firmware files needed by some drivers (this package might be missing when you build from the kernel sources provided by Debian), <emphasis role=\"pkg\">linux-image-<replaceable>version</replaceable>-dbg</emphasis> which contains the debugging symbols for the kernel image and its modules, and <emphasis role=\"pkg\">linux-libc-dev</emphasis> which contains headers relevant to some user-space libraries like GNU glibc."
msgstr ""
msgid "The <replaceable>version</replaceable> is defined by the concatenation of the upstream version (as defined by the variables <literal>VERSION</literal>, <literal>PATCHLEVEL</literal>, <literal>SUBLEVEL</literal> and <literal>EXTRAVERSION</literal> in the <filename>Makefile</filename>), of the <literal>LOCALVERSION</literal> configuration parameter, and of the <literal>LOCALVERSION</literal> environment variable. The package version reuses the same version string with an appended revision that is regularly incremented (and stored in <filename>.version</filename>), except if you override it with the <literal>KDEB_PKGVERSION</literal> environment variable."
msgstr ""
msgid ""
"<computeroutput>$ </computeroutput><userinput>make deb-pkg LOCALVERSION=-falcot KDEB_PKGVERSION=$(make kernelversion)-1\n"
"</userinput><computeroutput>[...]\n"
"$ </computeroutput><userinput>ls ../*.deb\n"
"</userinput><computeroutput>../linux-headers-4.19.37-falcot_4.19.37-1_amd64.deb\n"
"../linux-image-4.19.37-falcot_4.19.37-1_amd64.deb\n"
"../linux-libc-dev_4.19.37-1_amd64.deb\n"
"</computeroutput>"
msgstr ""
msgid "Compiling External Modules"
msgstr ""
msgid "<primary>kernel</primary><secondary>external modules</secondary>"
msgstr ""
msgid "<primary>modules</primary><secondary>external kernel modules</secondary>"
msgstr ""
msgid "<primary><command>dkms</command></primary>"
msgstr ""
msgid "Some modules are maintained outside of the official Linux kernel. To use them, they must be compiled alongside the matching kernel. A number of common third party modules are provided by Debian in dedicated packages, such as <emphasis role=\"pkg\">vpb-driver-source</emphasis> (extra modules for Voicetronix telefony hardware) or <emphasis role=\"pkg\">leds-alix-source</emphasis> (driver of PCEngines ALIX 2/3 boards)."
msgstr ""
msgid "These packages are many and varied, <command>apt-cache rdepends module-assistant$</command> can show the list provided by Debian. However, a complete list isn't particularly useful since there is no particular reason for compiling external modules except when you know you need it. In such cases, the device's documentation will typically detail the specific module(s) it needs to function under Linux."
msgstr ""
msgid "For example, let's look at the <emphasis role=\"pkg\">dahdi-source</emphasis> package: after installation, a <filename>.tar.bz2</filename> of the module's sources is stored in <filename>/usr/src/</filename>. While we could manually extract the tarball and build the module, in practice we prefer to automate all this using DKMS. Most modules offer the required DKMS integration in a package ending with a <literal>-dkms</literal> suffix. In our case, installing <emphasis role=\"pkg\">dahdi-dkms</emphasis> is all that is needed to compile the kernel module for the current kernel provided that we have the <emphasis role=\"pkg\">linux-headers-*</emphasis> package matching the installed kernel. For instance, if you use <emphasis role=\"pkg\">linux-image-amd64</emphasis>, you would also install <emphasis role=\"pkg\">linux-headers-amd64</emphasis>."
msgstr ""
msgid ""
"\n"
"<computeroutput>$ </computeroutput><userinput>sudo apt install dahdi-dkms</userinput>\n"
"<computeroutput>\n"
"[...]\n"
"Setting up xtables-addons-dkms (2.12-0.1) ...\n"
"Loading new xtables-addons-2.12 DKMS files...\n"
"Building for 4.19.0-5-amd64\n"
"Building initial module for 4.19.0-5-amd64\n"
"Done.\n"
"\n"
"dahdi_dummy.ko:\n"
"Running module version sanity check.\n"
" - Original module\n"
" - No original module exists within this kernel\n"
" - Installation\n"
" - Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/\n"
"[...]\n"
"DKMS: install completed.\n"
"$ </computeroutput><userinput>sudo dkms status</userinput>\n"
"<computeroutput>dahdi, DEB_VERSION, 4.19.0-5-amd64, x86_64: installed\n"
"$ </computeroutput><userinput>sudo modinfo dahdi_dummy</userinput>\n"
"<computeroutput>filename: /lib/modules/4.19.0-5-amd64/updates/dkms/dahdi_dummy.ko\n"
"license: GPL v2\n"
"author: Robert Pleh <robert.pleh@hermes.si>\n"
"description: Timing-Only Driver\n"
"[...]\n"
"</computeroutput>"
msgstr ""
msgid "<emphasis>ALTERNATIVE</emphasis> module-assistant"
msgstr ""
msgid "<primary><emphasis role=\"pkg\">module-assistant</emphasis></primary>"
msgstr ""
msgid "Before DKMS, <emphasis role=\"pkg\">module-assistant</emphasis> was the simplest solution to build and deploy kernel modules. It can still be used, in particular for packages lacking DKMS integration: with a simple command like <command>module-assistant auto-install dadhi</command> (or <command>m-a a-i dahdi</command> for short), the modules are compiled for the current kernel, put in a new Debian package, and that package gets installed on the fly."
msgstr ""
msgid "Applying a Kernel Patch"
msgstr ""
msgid "<primary>kernel</primary><secondary>patch</secondary>"
msgstr ""
msgid "<primary>patch of the kernel</primary>"
msgstr ""
msgid "Some features are not included in the standard kernel due to a lack of maturity or to some disagreement with the kernel maintainers. Such features may be distributed as patches that anyone is then free to apply to the kernel sources."
msgstr ""
msgid "Debian sometimes provides some of these patches in <emphasis role=\"pkg\">linux-patch-*</emphasis> packages but they often don't make it into stable releases (sometimes for the very same reasons that they are not merged into the official upstream kernel). These packages install files in the <filename>/usr/src/kernel-patches/</filename> directory."
msgstr ""
msgid "To apply one or more of these installed patches, use the <command>patch</command> command in the sources directory then start compilation of the kernel as described above."
msgstr ""
msgid ""
"\n"
"<computeroutput>$ </computeroutput><userinput>cd ~/kernel/linux-source-4.9</userinput>\n"
"<computeroutput>$ </computeroutput><userinput>make clean</userinput>\n"
"<computeroutput>$ </computeroutput><userinput>zcat /usr/src/kernel-patches/diffs/grsecurity2/grsecurity-3.1-4.9.11-201702181444.patch.gz | patch -p1</userinput>"
msgstr ""
msgid "Note that a given patch may not necessarily work with every version of the kernel; it is possible for <command>patch</command> to fail when applying them to kernel sources. An error message will be displayed and give some details about the failure; in this case, refer to the documentation available in the Debian package of the patch (in the <filename>/usr/share/doc/linux-patch-*/</filename> directory). In most cases, the maintainer indicates for which kernel versions their patch is intended."
msgstr ""
msgid "Installing a Kernel"
msgstr ""
msgid "<primary>installation</primary><secondary>of a kernel</secondary>"
msgstr ""
msgid "<primary>kernel</primary><secondary>installation</secondary>"
msgstr ""
msgid "Features of a Debian Kernel Package"
msgstr ""
msgid "<primary><filename>vmlinuz</filename></primary>"
msgstr ""
msgid "A Debian kernel package installs the kernel image (<filename>vmlinuz-<replaceable>version</replaceable></filename>), its configuration (<filename>config-<replaceable>version</replaceable></filename>) and its symbols table (<filename>System.map-<replaceable>version</replaceable></filename>) in <filename>/boot/</filename>. The modules are installed in the <filename>/lib/modules/<replaceable>version</replaceable>/</filename> directory."
msgstr ""
#, fuzzy
#| msgid "<emphasis>CULTURE</emphasis> Character sets"
msgid "<emphasis>CULTURE</emphasis> The symbols table"
msgstr "<emphasis>CULTURE</emphasis> Bộ ký tự"
msgid "The symbols table helps developers understand the meaning of a kernel error message; without it, kernel “oopses” (an “oops” is the kernel equivalent of a segmentation fault for user-space programs, in other words messages generated following an invalid pointer dereference) only contain numeric memory addresses, which is useless information without the table mapping these addresses to symbols and function names."
msgstr ""
msgid "The package's configuration scripts automatically generate an initrd image, which is a mini-system designed to be loaded in memory (hence the name, which stands for “init ramdisk”) by the bootloader, and used by the Linux kernel solely for loading the modules needed to access the devices containing the complete Debian system (for example, the driver for SATA disks). Finally, the post-installation scripts update the symbolic links <filename>/vmlinuz</filename>, <filename>/vmlinuz.old</filename>, <filename>/initrd.img</filename> and <filename>/initrd.img.old</filename> so that they point to the latest two kernels installed, respectively, as well as the corresponding initrd images."
msgstr ""
msgid "Most of those tasks are offloaded to hook scripts in the <filename>/etc/kernel/*.d/</filename> directories. For instance, the integration with <command>grub</command> relies on <filename>/etc/kernel/postinst.d/zz-update-grub</filename> and <filename>/etc/kernel/postrm.d/zz-update-grub</filename> to call <command>update-grub</command> when kernels are installed or removed."
msgstr ""
msgid "Installing with <command>dpkg</command>"
msgstr ""
msgid "Using <command>apt</command> is so convenient that it makes it easy to forget about the lower-level tools, but the easiest way of installing a compiled kernel is to use a command such as <command>dpkg -i <replaceable>package</replaceable>.deb</command>, where <literal><replaceable>package</replaceable>.deb</literal> is the name of a <emphasis role=\"pkg\">linux-image</emphasis> package such as <filename>linux-image-4.19.37-falcot_1_amd64.deb</filename>."
msgstr ""
msgid "The configuration steps described in this chapter are basic and can lead both to a server system or a workstation, and it can be massively duplicated in semi-automated ways. However, it is not enough by itself to provide a fully configured system. A few pieces are still in need of configuration, starting with low-level programs known as the “Unix services”."
msgstr ""
|