diff options
| author | Gabor Kovesdan <gabor@FreeBSD.org> | 2012-08-21 19:16:02 +0000 |
|---|---|---|
| committer | Gabor Kovesdan <gabor@FreeBSD.org> | 2012-08-21 19:16:02 +0000 |
| commit | 2e51ec7022b39b6fb3524de08669b20d0d436285 (patch) | |
| tree | 79fbae1d36dfb1cf1c634282cd893ef6532e3abb /pl_PL.ISO8859-2 | |
| parent | b2153405c50aa7276c3b5ad07d50eec1f0b45449 (diff) | |
| download | doc-2e51ec7022b39b6fb3524de08669b20d0d436285.tar.gz doc-2e51ec7022b39b6fb3524de08669b20d0d436285.zip | |
- Strip unnecessary trailing spaces
Approved by: doceng (implicit)
Notes
Notes:
svn path=/projects/sgml2xml/; revision=39416
Diffstat (limited to 'pl_PL.ISO8859-2')
38 files changed, 1568 insertions, 1568 deletions
diff --git a/pl_PL.ISO8859-2/articles/dialup-firewall/article.sgml b/pl_PL.ISO8859-2/articles/dialup-firewall/article.sgml index 30d2f77327..f1c6e0cb56 100644 --- a/pl_PL.ISO8859-2/articles/dialup-firewall/article.sgml +++ b/pl_PL.ISO8859-2/articles/dialup-firewall/article.sgml @@ -269,7 +269,7 @@ $fwcmd add deny log ip from any to any <para>Dlaczego korzystasz z &man.natd.8; i &man.ipfw.8;, a nie z filtrów wbudowanych w &man.ppp.8;?</para> </question> - + <answer> <para>Mówiąc szczerze, nie ma konkretnego powodu dla którego zdecydowałem się na <command>ipfw</command> i diff --git a/pl_PL.ISO8859-2/articles/new-users/article.sgml b/pl_PL.ISO8859-2/articles/new-users/article.sgml index f1de2dc52d..cfa1a6926c 100644 --- a/pl_PL.ISO8859-2/articles/new-users/article.sgml +++ b/pl_PL.ISO8859-2/articles/new-users/article.sgml @@ -42,7 +42,7 @@ </articleinfo> <sect1> - <title>Logowanie się i wychodzenie z systemu</title> + <title>Logowanie się i wychodzenie z systemu</title> <para>Gdy ujrzysz komunikat <prompt >login:</prompt>, zaloguj się jako użytkownik utworzony podczas instalacji lub jako diff --git a/pl_PL.ISO8859-2/books/Makefile.inc b/pl_PL.ISO8859-2/books/Makefile.inc index 9b0603ff02..701110fa82 100644 --- a/pl_PL.ISO8859-2/books/Makefile.inc +++ b/pl_PL.ISO8859-2/books/Makefile.inc @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # Original revision: 1.4 # diff --git a/pl_PL.ISO8859-2/books/handbook/Makefile b/pl_PL.ISO8859-2/books/handbook/Makefile index a3520034eb..e0158899a0 100644 --- a/pl_PL.ISO8859-2/books/handbook/Makefile +++ b/pl_PL.ISO8859-2/books/handbook/Makefile @@ -14,13 +14,13 @@ # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. -# +# # Handbook-specific targets # # pgpkeyring This target will read the contents of # pgpkeys/chapter.sgml and will extract all of # the pgpkeys to standard out. This output can then -# be redirected into a file and distributed as a +# be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # @@ -148,7 +148,7 @@ IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png -# +# # SRCS lists the individual SGML files that make up the document. Changes # to any of these files will force a rebuild # @@ -190,7 +190,7 @@ SRCS+= vinum/chapter.sgml SRCS+= x11/chapter.sgml # Entities -SRCS+= chapters.ent +SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html diff --git a/pl_PL.ISO8859-2/books/handbook/advanced-networking/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/advanced-networking/chapter.sgml index bb04cf1ece..73b4b636ba 100644 --- a/pl_PL.ISO8859-2/books/handbook/advanced-networking/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/advanced-networking/chapter.sgml @@ -2151,7 +2151,7 @@ hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29: <para>SDP involves communication between a SDP server and a SDP client. The server maintains a list of service records that describe the characteristics of services associated with the server. Each service - record contains information about a single service. A client may + record contains information about a single service. A client may retrieve information from a service record maintained by the SDP server by issuing a SDP request. If the client, or an application associated with the client, decides to use a service, it must open a separate @@ -2165,7 +2165,7 @@ hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29: server's service records without any a priori information about the services. This process of looking for any offered services is called <emphasis>browsing</emphasis>.</para> - + <para>The Bluetooth SDP server &man.sdpd.8; and command line client &man.sdpcontrol.8; are included in the standard &os; installation. The following example shows how to perform a SDP browse query.</para> @@ -2564,7 +2564,7 @@ net.link.ether.bridge_cfg=<replaceable>if1</replaceable>,<replaceable>if2</repla net.link.ether.bridge_ipfw=1</programlisting> </sect2> - + <sect2> <title>Other Information</title> @@ -2579,7 +2579,7 @@ net.link.ether.bridge_ipfw=1</programlisting> <para>A bridge can add latency to your &man.ping.8; times, especially for traffic from one segment to another.</para> - + </sect2> </sect1> @@ -2712,7 +2712,7 @@ net.link.ether.bridge_ipfw=1</programlisting> <para>Several operations need to be performed for a successful bootstrap:</para> - + <itemizedlist> <listitem> <para>The machine needs to obtain initial parameters such as its IP diff --git a/pl_PL.ISO8859-2/books/handbook/basics/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/basics/chapter.sgml index 7610f0fa03..6e9d87fded 100644 --- a/pl_PL.ISO8859-2/books/handbook/basics/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/basics/chapter.sgml @@ -26,7 +26,7 @@ </chapterinfo> <title>Podstawy Uniksa</title> - + <sect1 id="basics-synopsis"> <title>Streszczenie</title> @@ -651,7 +651,7 @@ total 530 &man.chflags.1; oraz &man.chflags.2;.</para> </sect2> </sect1> - + <sect1 id="dirstructure"> <title>Struktura katalogów</title> <indexterm><primary>hierarchia katalogów</primary></indexterm> @@ -700,70 +700,70 @@ total 530 <entry><filename class="directory">/</filename></entry> <entry>Główny katalog systemu plików.</entry> </row> - + <row> <entry><filename class="directory">/bin/</filename></entry> <entry>Programy użytkowe wykorzystywane zarówno w trybie jednego użytkownika, jak i w trybie wielu użytkowników.</entry> </row> - + <row> <entry><filename class="directory">/boot/</filename></entry> <entry> Programy i pliki konfiguracyjne używane podczas uruchamiania systemu.</entry> </row> - + <row> <entry><filename class="directory">/boot/defaults/</filename></entry> <entry>Pliki z domyślną konfiguracją uruchamiania systemu; patrz &man.loader.conf.5;.</entry> </row> - + <row> <entry><filename class="directory">/dev/</filename></entry> <entry>Pliki urządzeń; patrz &man.intro.4;.</entry> </row> - + <row> <entry><filename class="directory">/etc/</filename></entry> <entry>Pliki i skrypty konfiguracyjne.</entry> </row> - + <row> <entry><filename class="directory">/etc/defaults/</filename></entry> <entry>Pliki z domyślną konfiguracją systemu; patrz &man.rc.8;.</entry> </row> - + <row> <entry><filename class="directory">/etc/mail/</filename></entry> <entry>Pliki konfiguracyjne dla serwerów poczty, na przykład &man.sendmail.8;.</entry> </row> - + <row> <entry><filename class="directory">/etc/namedb/</filename></entry> <entry>Pliki konfiguracyjne programu <command>named</command>; patrz &man.named.8;.</entry> </row> - + <row> <entry><filename class="directory">/etc/periodic/</filename></entry> <entry>Skrypty uruchamiane raz dziennie, raz na tydzień i raz na miesiąc za pośrednictwem &man.cron.8;; patrz &man.periodic.8;.</entry> </row> - + <row> <entry><filename class="directory">/etc/ppp/</filename></entry> <entry>Pliki konfiguracyjne <command>ppp</command>; patrz &man.ppp.8;.</entry> </row> - + <row> <entry><filename class="directory">/mnt/</filename></entry> <entry>Pusty katalog, najczęściej wykorzystywany przez administratorów jako tymczasowy punkt montowania..</entry> </row> - + <row> <entry><filename class="directory">/proc/</filename></entry> <entry>System plików procesów, patrz &man.procfs.5;, @@ -786,13 +786,13 @@ total 530 <entry>Programy i narzędzia administracyjne wykorzystywane zarówno w trybie jednego użytkownika, jak i w trybie wielu użytkowników.</entry> </row> - + <row> <entry><filename class="directory">/stand/</filename></entry> <entry>Programy używane w samodzielnym środowisku.</entry> </row> - - + + <row> <entry><filename class="directory">/tmp/</filename></entry> <entry>Pliki tymczasowe. Zawartość katalogu @@ -804,39 +804,39 @@ total 530 związane z tmpmfs (bądź za pomocą wpisu w <filename>/etc/fstab</filename>; patrz &man.mdmfs.8;).</entry> </row> - - + + <row> <entry><filename class="directory">/usr/</filename></entry> <entry>Większość programów i aplikacji wykorzystywanych przez użytkowników.</entry> </row> - + <row> <entry><filename class="directory">/usr/bin/</filename></entry> <entry>Najczęściej używane programy, narzędzia programistyczne, aplikacje.</entry> </row> - + <row> <entry><filename class="directory">/usr/include/</filename></entry> <entry>Pliki nagłówkowe C.</entry> </row> - + <row> <entry><filename class="directory">/usr/lib/</filename></entry> <entry>Biblioteki.</entry> </row> - - + + <row> <entry><filename class="directory">/usr/libdata/</filename></entry> <entry>Pliki danych różnych programów użytkowych.</entry> </row> - + <row> <entry><filename class="directory">/usr/libexec/</filename></entry> <entry>Demony i programy systemowe (uruchamiane przez inne programy).</entry> </row> - + <row> <entry><filename class="directory">/usr/local/</filename></entry> @@ -852,40 +852,40 @@ total 530 <filename>share/doc/<replaceable>port</replaceable></filename>. </entry> </row> - + <row> <entry><filename class="directory">/usr/obj/</filename></entry> <entry>Pliki zależne od architektury komputera, tworzone w procesie budowania drzewa <filename>/usr/src</filename>.</entry> </row> - + <row> <entry><filename class="directory">/usr/ports</filename></entry> <entry>Kolekcja portów FreeBSD (opcjonalna).</entry> </row> - + <row> <entry><filename class="directory">/usr/sbin/</filename></entry> <entry>Demony i programy systemowe (dostępne dla użytkowników).</entry> </row> - + <row> <entry><filename class="directory">/usr/share/</filename></entry> <entry>Pliki niezależne od architektury systemu.</entry> </row> - + <row> <entry><filename class="directory">/usr/src/</filename></entry> <entry>Pliki źródłowe BSD, lokalne pliki źródłowe.</entry> </row> - + <row> <entry><filename class="directory">/usr/X11R6/</filename></entry> <entry>Pliki wykonywalne, biblioteki, i inne pliki dystrybucji X11R6 (opcjonalnie).</entry> </row> - + <row> <entry><filename class="directory">/var/</filename></entry> <entry>Rozmaite pliki dzienników systemowych, pliki tymczasowe, @@ -895,29 +895,29 @@ total 530 z varmfs (bądź za pomocą wpisu w <filename>/etc/fstab</filename>; patrz &man.mdmfs.8;).</entry> </row> - - + + <row> <entry><filename class="directory">/var/log/</filename></entry> <entry>Pliki dzienników systemowych.</entry> </row> - + <row> <entry><filename class="directory">/var/mail/</filename></entry> <entry>Skrzynki pocztowe użytkowników.</entry> </row> - + <row> <entry><filename class="directory">/var/spool/</filename></entry> <entry>Katalogi kolejek systemu drukowania i poczty.</entry> </row> - + <row> <entry><filename class="directory">/var/tmp/</filename></entry> <entry>Pliki tymczasowe nie usuwane przy ponownym uruchamianiu systemu.</entry> </row> - + <row> <entry><filename>/var/yp</filename></entry> <entry>Mapy usługi NIS.</entry> @@ -1012,7 +1012,7 @@ total 530 <textobject> <literallayout class="monospaced"> / - | + | +--- A1 | | | +--- B1 @@ -1064,7 +1064,7 @@ total 530 <imageobject> <imagedata fileref="install/example-dir4" format="EPS"/> </imageobject> - + <textobject> <literallayout class="monospaced"> / | @@ -1122,7 +1122,7 @@ total 530 <itemizedlist> <title>Korzyści z kilku systemów plików</title> - + <listitem> <para>Odrębne systemy plików mogą mieć różne <firstterm>opcje montowania</firstterm> (mount options). Na przykład, przy @@ -1145,7 +1145,7 @@ total 530 jest mniej plików o dużych rozmiarach. W przypadku jednego dużego systemu plików taka optymalizacja nie zadziała.</para> </listitem> - + <listitem> <para>Systemy plików FreeBSD są odporne na awarie zasilania. W niesprzyjających okolicznościach może się jednak zdarzyć, @@ -1175,7 +1175,7 @@ total 530 </important> </listitem> </itemizedlist> - + <para>Systemy plików przechowywane są na partycjach. Pojęcie partycji ma tu inne znaczenie niż popularnie stosowane (np. partycja systemu &ms-dos;), ze względu na uniksowy rodowód @@ -1266,7 +1266,7 @@ total 530 w ten sposób segmenty rozszerzone mają numery od 5 wzwyż, zatem <quote>ad0<emphasis>s5</emphasis></quote> odpowiada pierwszemu rozszerzonemu segmentowi na dysku IDE. Urządzenia te są wykorzystywane - przez systemy plików, które zajmują cały segment.</para> + przez systemy plików, które zajmują cały segment.</para> <para>Segmenty, dyski <quote>niebezpiecznie dedykowane</quote> i inne dyski zawierają <firstterm>partycje</firstterm>, @@ -1276,7 +1276,7 @@ total 530 partycji a na pierwszym dysku da, <quote>niebezpiecznie dedykowanym</quote>. Z kolei <quote>ad1s3<emphasis>e</emphasis></quote> oznacza piątą partycję w trzecim segmencie drugiego dysku IDE.</para> - + <para>Własne oznaczenie ma także każdy dysk. Nazwa dysku składa się z symbolu określającego typ dysku, oraz numeru, określającego który to dysk. Dyski, inaczej niż segmenty, numerowane są od zera. @@ -1307,7 +1307,7 @@ total 530 <thead> <row> <entry>Oznaczenie</entry> - + <entry>Znaczenie</entry> </row> </thead> @@ -1321,34 +1321,34 @@ total 530 <row> <entry><devicename>da</devicename></entry> - + <entry>Dysk SCSI o dostępie bezpośrednim</entry> </row> - + <row> <entry><devicename>acd</devicename></entry> - + <entry>CDROM ATAPI (IDE)</entry> </row> - + <row> <entry><devicename>cd</devicename></entry> - + <entry>CDROM SCSI</entry> </row> - + <row> <entry><devicename>fd</devicename></entry> - + <entry>Stacja dyskietek</entry> </row> </tbody> </tgroup> </table> - + <example id="basics-disk-slice-part"> <title>Przykładowe nazwy dysków, segmentów i partycji</title> - + <informaltable frame="none" pgwide="1"> <tgroup cols="2"> <colspec colwidth="1*"/> @@ -1357,15 +1357,15 @@ total 530 <thead> <row> <entry>Nazwa</entry> - + <entry>Znaczenie</entry> </row> </thead> - + <tbody> <row> <entry><literal>ad0s1a</literal></entry> - + <entry>Pierwsza partycja (<literal>a</literal>) w pierwszym segmencie (<literal>s1</literal>) na pierwszym dysku IDE (<literal>ad0</literal>).</entry> @@ -1373,7 +1373,7 @@ total 530 <row> <entry><literal>da1s2e</literal></entry> - + <entry>Piąta partycja <literal>e</literal> w drugim segmencie (<literal>s2</literal>) na drugim dysku SCSI (<literal>da1</literal>).</entry> @@ -1402,7 +1402,7 @@ total 530 <imageobject> <imagedata fileref="install/disk-layout" format="EPS"/> </imageobject> - + <textobject> <literallayout class="monospaced">.-----------------. --. | | | @@ -1419,7 +1419,7 @@ total 530 | | > referred to as ad0s2b | | | | | :-----------------: ==: | Partition c, no -| | | Partition e, used as /var > file system, all +| | | Partition e, used as /var > file system, all | | > referred to as ad0s2e | of FreeBSD slice, | | | | ad0s2c :-----------------: ==: | @@ -1487,24 +1487,24 @@ total 530 <varlistentry> <term><literal>punkt-montowania</literal></term> - + <listitem><para>Katalog (istniejący), w którym system plików ma być zamontowany.</para> </listitem> </varlistentry> - + <varlistentry> <term><literal>typ</literal></term> - + <listitem><para>Typ systemu plików przekazywany poleceniu &man.mount.8;. We FreeBSD domyślnie jest to <literal>ufs</literal>.</para> </listitem> </varlistentry> - + <varlistentry> <term><literal>opcje</literal></term> - + <listitem><para>Pierwszą opcją jest <option>rw</option>, jeśli w systemie plików ma być możliwy odczyt i zapis, albo <option>ro</option>, jeżeli dozwolony ma być tylko odczyt. @@ -1514,10 +1514,10 @@ total 530 Pozostałe opcje opisane są w dokumentacji systemowej &man.mount.8;.</para> </listitem> </varlistentry> - + <varlistentry> <term><literal>archiwizacja</literal></term> - + <listitem><para>Na podstawie tej informacji program &man.dump.8; stwierdza, które systemy plików mają być archiwizowane. Jeśli pole to zostanie pominięte, domyślnie przyjmowana jest wartość zero.</para> @@ -1552,10 +1552,10 @@ total 530 <primary>systemy plików</primary> <secondary>montowanie</secondary> </indexterm> - + <para>Polecenie &man.mount.8; jest głównym poleceniem używanym do montowania systemów plików.</para> - + <para>W najprostszej postaci, używa się go następująco:</para> <informalexample> @@ -1570,7 +1570,7 @@ total 530 <varlistentry> <term><option>-a</option></term> - + <listitem> <para>Montowanie wszystkich systemów plików wymienionych w <filename>/etc/fstab</filename>. @@ -1579,10 +1579,10 @@ total 530 jak również systemy plików już zamontowane.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-d</option></term> - + <listitem> <para>Wykonanie wszystkiego, oprócz faktycznego wywołania funkcji systemowej montowania. W połączeniu z opcją @@ -1590,7 +1590,7 @@ total 530 tak naprawdę &man.mount.8; stara się zrobić.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-f</option></term> @@ -1602,10 +1602,10 @@ total 530 <quote>tylko do odczytu</quote>.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-r</option></term> - + <listitem> <para>Montowanie systemu plików w trybie tylko do odczytu. Taki sam efekt ma zastosowanie opcji <option>-o</option> @@ -1613,7 +1613,7 @@ total 530 w wersjach FreeBSD wcześniejszych niż 5.2).</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-t</option> <replaceable>typ</replaceable></term> @@ -1622,62 +1622,62 @@ total 530 <para>Montowanie systemu plików o określonym typie. Przy zastosowaniu opcji <option>-a</option> montowane są tylko systemy plików podanego typu.</para> - + <para>Domyślnym typem systemu plików jest <quote>ufs</quote>.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-u</option></term> - + <listitem> <para>Uaktualnienie opcji montowania systemu plików.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-v</option></term> - + <listitem> <para>Pokazywanie dodatkowych komunikatów.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-w</option></term> - + <listitem> <para>Montowanie w trybie odczytu i zapisu.</para> </listitem> </varlistentry> </variablelist> - + <para>Opcji <option>-o</option> towarzyszy lista oddzielonych przecinkami parametrów, oto niektóre z nich:</para> - + <variablelist> <varlistentry> <term>nodev</term> - + <listitem> <para>Ignorowanie obecnych w systemie plików urządzeń specjalnych. Przydatna opcja, jeśli chodzi o bezpieczeństwo.</para> </listitem> </varlistentry> - + <varlistentry> <term>noexec</term> - + <listitem> <para>Wyłączenie uruchamiania programów wykonywalnych na systemie plików. Również służy bezpieczeństwu.</para> </listitem> </varlistentry> - + <varlistentry> <term>nosuid</term> - + <listitem> <para>Ignorowanie bitów setuid i setgid w systemie plików. Kolejna opcja służąca bezpieczeństwu.</para> @@ -1692,11 +1692,11 @@ total 530 <primary>systemy plików</primary> <secondary>odmontowywanie</secondary> </indexterm> - + <para>Poleceniu &man.umount.8; należy podać jako parametr punkt montowania, nazwę urządzenia bądź opcję <option>-a</option> lub <option>-A</option>.</para> - + <para>Każdej z form wywołania polecenia można podać opcję <option>-f</option>, która nakazuje dokonać bezwarunkowego odmontowania, oraz opcję <option>-v</option>, powodującą @@ -1705,7 +1705,7 @@ total 530 Bezwarunkowe odmontowywanie systemu plików może doprowadzić do awarii systemu lub uszkodzenia danych znajdujących się w danym systemie plików.</para> - + <para>Opcje <option>-a</option> oraz <option>-A</option> służą do odmontowania wszystkich zamontowanych systemów plików, lub systemów plików wybranych typów, określonych w opcji @@ -1924,7 +1924,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse jak procesy reagują na sygnał <literal>SIGHUP</literal>, dlatego różne demony mogą zachowywać się w różny sposób — w razie niepewności warto zapoznać się z dokumentacją konkretnego demona.</para> - + <para>Sygnały wysyłane są przy użyciu polecenia &man.kill.1;, jak w poniższym przykładzie.</para> @@ -2180,7 +2180,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse <para>Można też skorzystać z <command>chsh</command> z opcją <option>-s</option>, która automatycznie zmieni powłokę, bez uruchamiania edytora. Poniżej przedstawiono wywołanie zmieniające powłokę na <command>bash</command>:</para> - + <screen>&prompt.user; <userinput>chsh -s /usr/local/bin/bash</userinput></screen> <note> @@ -2189,7 +2189,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse <link linkend="ports">kolekcji portów</link> powinna zostać dopisana automatycznie. Jeśli natomiast przeprowadzono ręczną instalację powłoki, trzeba to zrobić samemu.</para> - + <para>Dla przykładu, jeśli powłoka <command>bash</command> została zainstalowana i umieszczona w <filename>/usr/local/bin</filename>, trzeba będzie wydać polecenie:</para> @@ -2316,7 +2316,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse </author> </authorgroup> </sect1info> - + <title>Formaty binarne</title> <para>By zrozumieć czemu FreeBSD używa formatu &man.elf.5;, musimy wpierw diff --git a/pl_PL.ISO8859-2/books/handbook/bibliography/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/bibliography/chapter.sgml index ff48798652..8cf84b069a 100644 --- a/pl_PL.ISO8859-2/books/handbook/bibliography/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/bibliography/chapter.sgml @@ -8,18 +8,18 @@ <appendix id="bibliography"> <title>Bibliografia</title> - + <para>Podczas gdy strony podręcznika systemowego dostarczają szczegółowych informacji odnośnie każdego z elementów systemu operacyjnego FreeBSD, bardzo często nie przedstawiają one jak złożyć wszystkie te elementy razem tak, by usprawnić pracę całego systemu. Z tego właśnie powodu nie istnieje żaden substytut dobrej książki o administracji systemami &unix; i dobrego podręcznika ich użytkowania.</para> - + <sect1 id="bibliography-freebsd"> <title>Książki i czasopisma poświęcone FreeBSD</title> - + <para><emphasis>Międzynarodowe książki i czasopisma:</emphasis></para> - + <itemizedlist> <listitem> <para><ulink @@ -73,34 +73,34 @@ <para>FreeBSD for PC 98'ers (po japońsku), wydany przez SHUWA System Co, LTD. ISBN 4-87966-468-5 C3055 P2900E.</para> </listitem> - + <listitem> <para>FreeBSD (po japońsku), wydany przez CUTT. ISBN 4-906391-22-2 C3055 P2400E.</para> </listitem> - + <listitem> <para><ulink url="http://www.shoeisha.com/book/Detail.asp?bid=650">Complete Introduction to FreeBSD</ulink> (po japońsku), wydany przez <ulink url="http://www.shoeisha.co.jp/">Shoeisha Co., Ltd</ulink>. ISBN 4-88135-473-6 P3600E.</para> </listitem> - + <listitem> <para><ulink url="http://www.ascii.co.jp/pb/book1/shinkan/detail/1322785.html">Personal UNIX Starter Kit FreeBSD</ulink> (po japońsku), wydany przez <ulink url="http://www.ascii.co.jp/">ASCII</ulink>. ISBN 4-7561-1733-3 P3000E.</para> </listitem> - + <listitem> <para>FreeBSD Handbook (japoński przekład), wydany przez <ulink url="http://www.ascii.co.jp/">ASCII</ulink>. ISBN 4-7561-1580-2 P3800E.</para> </listitem> - + <listitem> <para>FreeBSD mit Methode (po niemiecku), wydany przez <ulink url="http://www.cul.de">Computer und Literatur Verlag</ulink>/Vertrieb Hanser, 1998. ISBN 3-932311-31-0.</para> </listitem> - + <listitem> <para><ulink url="http://www.cul.de/freebsd.html">FreeBSD 4 - Installieren, Konfigurieren, Administrieren</ulink> @@ -129,7 +129,7 @@ </listitem> <listitem> - <para>Onno W Purbo, Dodi Maryanto, Syahrial Hubbany, Widjil Widodo + <para>Onno W Purbo, Dodi Maryanto, Syahrial Hubbany, Widjil Widodo <emphasis><ulink url="http://maxwell.itb.ac.id/"> Building Internet Server with FreeBSD</ulink></emphasis> (w języku indonezyjskim), wydany @@ -137,9 +137,9 @@ </listitem> </itemizedlist> - + <para><emphasis>Książki i czasopisma w języku angielskim:</emphasis></para> - + <itemizedlist> <listitem> <para><ulink url="http://www.AbsoluteBSD.com/">Absolute @@ -165,7 +165,7 @@ <listitem> <para><ulink url="http://andrsn.stanford.edu/FreeBSD/introbook/"> - FreeBSD: An Open-Source Operating System for Your Personal + FreeBSD: An Open-Source Operating System for Your Personal Computer</ulink>, wydany przez The Bit Tree Press, 2001. ISBN: 0971204500</para> </listitem> @@ -190,34 +190,34 @@ </itemizedlist> </sect1> - + <sect1 id="bibliography-userguides"> <title>Podręczniki użytkowania</title> - + <itemizedlist> <listitem> <para>Computer Systems Research Group, UC Berkeley. <emphasis>4.4BSD User's Reference Manual</emphasis>. O'Reilly & Associates, Inc., 1994. ISBN 1-56592-075-9</para> </listitem> - + <listitem> <para>Computer Systems Research Group, UC Berkeley. <emphasis>4.4BSD User's Supplementary Documents</emphasis>. O'Reilly & Associates, Inc., 1994. ISBN 1-56592-076-7</para> </listitem> - + <listitem> <para><emphasis>UNIX in a Nutshell</emphasis>. O'Reilly & Associates, Inc., 1990. ISBN 093717520X</para> </listitem> - + <listitem> <para>Mui, Linda. <emphasis>What You Need To Know When You Can't Find Your UNIX System Administrator</emphasis>. O'Reilly & Associates, Inc., 1995. ISBN 1-56592-104-6</para> </listitem> - + <listitem> <para><ulink url="http://www-wks.acs.ohio-state.edu/">Ohio State University</ulink> napisał kurs <ulink @@ -230,7 +230,7 @@ tego dokumentu dostępny jest jako część projektu FreeBSD Italian Documentation Project.</para> </listitem> - + <listitem> <para><ulink url="http://www.jp.FreeBSD.org/">Jpman Project, Japan FreeBSD Users Group</ulink>. <ulink @@ -248,51 +248,51 @@ </listitem> </itemizedlist> </sect1> - + <sect1 id="bibliography-adminguides"> <title>Podręczniki administracji</title> - + <itemizedlist> <listitem> <para>Albitz, Paul and Liu, Cricket. <emphasis>DNS and BIND</emphasis>, 4th Ed. O'Reilly & Associates, Inc., 2001. ISBN 1-59600-158-4</para> </listitem> - + <listitem> <para>Computer Systems Research Group, UC Berkeley. <emphasis>4.4BSD System Manager's Manual</emphasis>. O'Reilly & Associates, Inc., 1994. ISBN 1-56592-080-5</para> </listitem> - + <listitem> <para>Costales, Brian, et al. <emphasis>Sendmail</emphasis>, 2nd Ed. O'Reilly & Associates, Inc., 1997. ISBN 1-56592-222-0</para> </listitem> - + <listitem> <para>Frisch, Æleen. <emphasis>Essential System Administration</emphasis>, 2nd Ed. O'Reilly & Associates, Inc., 1995. ISBN 1-56592-127-5</para> </listitem> - + <listitem> <para>Hunt, Craig. <emphasis>TCP/IP Network Administration</emphasis>, 2nd Ed. O'Reilly & Associates, Inc., 1997. ISBN 1-56592-322-7</para> </listitem> - + <listitem> <para>Nemeth, Evi. <emphasis>UNIX System Administration - Handbook</emphasis>. 3rd Ed. Prentice Hall, 2000. ISBN + Handbook</emphasis>. 3rd Ed. Prentice Hall, 2000. ISBN 0-13-020601-6</para> </listitem> - + <listitem> <para>Stern, Hal <emphasis>Managing NFS and NIS</emphasis> O'Reilly & Associates, Inc., 1991. ISBN 0-937175-75-7</para> </listitem> - + <listitem> <para><ulink url="http://www.jp.FreeBSD.org/">Jpman Project, Japan FreeBSD Users Group</ulink>. <ulink @@ -310,51 +310,51 @@ </listitem> </itemizedlist> </sect1> - + <sect1 id="bibliography-programmers"> <title>Podręczniki programowania</title> - + <itemizedlist> <listitem> <para>Asente, Paul, Converse, Diana, and Swick, Ralph. <emphasis>X Window System Toolkit</emphasis>. Digital Press, 1998. ISBN 1-55558-178-1</para> </listitem> - + <listitem> <para>Computer Systems Research Group, UC Berkeley. <emphasis>4.4BSD Programmer's Reference Manual</emphasis>. O'Reilly & Associates, Inc., 1994. ISBN 1-56592-078-3</para> </listitem> - + <listitem> <para>Computer Systems Research Group, UC Berkeley. <emphasis>4.4BSD Programmer's Supplementary Documents</emphasis>. O'Reilly & Associates, Inc., 1994. ISBN 1-56592-079-1</para> </listitem> - + <listitem> <para>Harbison, Samuel P. and Steele, Guy L. Jr. <emphasis>C: A - Reference Manual</emphasis>. 4th ed. Prentice Hall, 1995. + Reference Manual</emphasis>. 4th ed. Prentice Hall, 1995. ISBN 0-13-326224-3</para> </listitem> - + <listitem> <para>Kernighan, Brian and Dennis M. Ritchie. <emphasis>The C Programming Language</emphasis>. 2nd Ed. PTR Prentice Hall, 1988. ISBN 0-13-110362-8</para> </listitem> - + <listitem> <para>Lehey, Greg. <emphasis>Porting UNIX Software</emphasis>. O'Reilly & Associates, Inc., 1995. ISBN 1-56592-126-7</para> </listitem> - + <listitem> <para>Plauger, P. J. <emphasis>The Standard C Library</emphasis>. Prentice Hall, 1992. ISBN 0-13-131509-9</para> </listitem> - + <listitem> <para>Spinellis, Diomidis. <ulink url="http://www.spinellis.gr/codereading/"><emphasis>Code @@ -376,13 +376,13 @@ Reading, Mass. : Addison-Wesley, 2005. ISBN 0-201-43307-9</para> </listitem> - + <listitem> <para>Stevens, W. Richard. <emphasis>UNIX Network Programming</emphasis>. 2nd Ed, PTR Prentice Hall, 1998. ISBN 0-13-490012-X</para> </listitem> - + <listitem> <para>Wells, Bill. <quote>Writing Serial Drivers for UNIX</quote>. <emphasis>Dr. Dobb's Journal</emphasis>. 19(15), December 1994. @@ -390,37 +390,37 @@ </listitem> </itemizedlist> </sect1> - + <sect1 id="bibliography-osinternals"> <title>Komponenty systemu operacyjnego</title> - + <itemizedlist> <listitem> <para>Andleigh, Prabhat K. <emphasis>UNIX System - Architecture</emphasis>. Prentice-Hall, Inc., 1990. ISBN + Architecture</emphasis>. Prentice-Hall, Inc., 1990. ISBN 0-13-949843-5</para> </listitem> - + <listitem> <para>Jolitz, William. <quote>Porting UNIX to the 386</quote>. <emphasis>Dr. Dobb's Journal</emphasis>. January 1991-July 1992.</para> </listitem> - + <listitem> <para>Leffler, Samuel J., Marshall Kirk McKusick, Michael J Karels i John Quarterman <emphasis>The Design and Implementation of the 4.3BSD UNIX Operating System</emphasis>. Reading, Mass. : Addison-Wesley, 1989. ISBN 0-201-06196-1</para> </listitem> - + <listitem> <para>Leffler, Samuel J., Marshall Kirk McKusick, <emphasis>The Design and Implementation of the 4.3BSD UNIX Operating System: Answer - Book</emphasis>. Reading, Mass. : Addison-Wesley, 1991. ISBN + Book</emphasis>. Reading, Mass. : Addison-Wesley, 1991. ISBN 0-201-54629-9</para> </listitem> - + <listitem> <para>McKusick, Marshall Kirk, Keith Bostic, Michael J Karels i John Quarterman. <emphasis>The Design and Implementation of the @@ -433,7 +433,7 @@ url="http://www.netapp.com/tech_library/nfsbook.html"> tutaj</ulink>.)</para> </listitem> - + <listitem> <para>Marshall Kirk McKusick, George V. Neville-Neil <emphasis>The Design and Implementation of the FreeBSD Operating System</emphasis>. @@ -445,26 +445,26 @@ The Protocols</emphasis>. Reading, Mass. : Addison-Wesley, 1996. ISBN 0-201-63346-9</para> </listitem> - + <listitem> <para>Schimmel, Curt. <emphasis>Unix Systems for Modern Architectures</emphasis>. Reading, Mass. : Addison-Wesley, 1994. ISBN 0-201-63338-8</para> </listitem> - + <listitem> <para>Stevens, W. Richard. <emphasis>TCP/IP Illustrated, Volume 3: TCP for Transactions, HTTP, NNTP and the UNIX Domain Protocols</emphasis>. Reading, Mass. : Addison-Wesley, 1996. ISBN 0-201-63495-3</para> </listitem> - + <listitem> <para>Vahalia, Uresh. <emphasis>UNIX Internals -- The New - Frontiers</emphasis>. Prentice Hall, 1996. ISBN + Frontiers</emphasis>. Prentice Hall, 1996. ISBN 0-13-101908-2</para> </listitem> - + <listitem> <para>Wright, Gary R. i W. Richard Stevens. <emphasis>TCP/IP Illustrated, Volume 2: The Implementation</emphasis>. Reading, @@ -472,10 +472,10 @@ </listitem> </itemizedlist> </sect1> - + <sect1 id="bibliography-security"> <title>Bezpieczeństwo</title> - + <itemizedlist> <listitem> <para>Cheswick, William R. i Steven M. Bellovin. <emphasis>Firewalls @@ -483,63 +483,63 @@ Reading, Mass. : Addison-Wesley, 1995. ISBN 0-201-63357-4</para> </listitem> - + <listitem> <para>Garfinkel, Simson i Gene Spafford. <emphasis>Practical UNIX & Internet Security</emphasis>. 2nd Ed. O'Reilly & Associates, Inc., 1996. ISBN 1-56592-148-8</para> </listitem> - + <listitem> <para>Garfinkel, Simson. <emphasis>PGP Pretty Good - Privacy</emphasis> O'Reilly & Associates, Inc., 1995. ISBN + Privacy</emphasis> O'Reilly & Associates, Inc., 1995. ISBN 1-56592-098-8</para> </listitem> </itemizedlist> </sect1> - + <sect1 id="bibliography-hardware"> <title>Sprzęt</title> - + <itemizedlist> <listitem> <para>Anderson, Don i Tom Shanley. <emphasis>Pentium Processor System Architecture</emphasis>. 2nd Ed. Reading, Mass. : Addison-Wesley, 1995. ISBN 0-201-40992-5</para> </listitem> - + <listitem> <para>Ferraro, Richard F. <emphasis>Programmer's Guide to the EGA, VGA, and Super VGA Cards</emphasis>. 3rd ed. Reading, Mass. : Addison-Wesley, 1995. ISBN 0-201-62490-7</para> </listitem> - + <listitem> <para>Firma Intel Corporation publikuje dokumentacje ich procesorów, chipsetów i standardów na <ulink url="http://developer.intel.com/">stronie projektantów</ulink>; z reguły jako pliki PDF.</para> </listitem> - + <listitem> <para>Shanley, Tom. <emphasis>80486 System Architecture</emphasis>. 3rd ed. Reading, Mass. : Addison-Wesley, 1995. ISBN 0-201-40994-1</para> </listitem> - + <listitem> <para>Shanley, Tom. <emphasis>ISA System Architecture</emphasis>. 3rd ed. Reading, Mass. : Addison-Wesley, 1995. ISBN 0-201-40996-8</para> </listitem> - + <listitem> <para>Shanley, Tom. <emphasis>PCI System Architecture</emphasis>. 4th ed. Reading, Mass. : Addison-Wesley, 1999. ISBN 0-201-30974-2</para> </listitem> - + <listitem> <para>Van Gilluwe, Frank. <emphasis>The Undocumented PC</emphasis>, 2nd Ed. Reading, Mass: Addison-Wesley Pub. Co., 1996. ISBN @@ -554,17 +554,17 @@ </itemizedlist> </sect1> - + <sect1 id="bibliography-history"> <title>Historia systemów &unix;</title> - + <itemizedlist> <listitem> <para>Lion, John <emphasis>Lion's Commentary on UNIX, 6th Ed. With Source Code</emphasis>. ITP Media Group, 1996. ISBN 1573980137</para> </listitem> - + <listitem> <para>Raymond, Eric S. <emphasis>The New Hacker's Dictionary, 3rd edition</emphasis>. MIT Press, 1996. ISBN @@ -572,13 +572,13 @@ url="http://www.catb.org/~esr/jargon/html/index.html">Jargon File</ulink></para> </listitem> - + <listitem> <para>Salus, Peter H. <emphasis>A quarter century of UNIX</emphasis>. Addison-Wesley Publishing Company, Inc., 1994. ISBN 0-201-54777-5</para> </listitem> - + <listitem> <para>Simon Garfinkel, Daniel Weise, Steven Strassmann. <emphasis>The UNIX-HATERS Handbook</emphasis>. IDG Books Worldwide, Inc., @@ -587,30 +587,30 @@ url="http://research.microsoft.com/~daniel/unix-haters.html"> online</ulink>.</para> </listitem> - + <listitem> <para>Don Libes, Sandy Ressler <emphasis>Life with UNIX</emphasis> - — special edition. Prentice-Hall, Inc., 1989. ISBN + — special edition. Prentice-Hall, Inc., 1989. ISBN 0-13-536657-7</para> </listitem> - + <listitem> <para><emphasis>The BSD family tree</emphasis>. <ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi/src/share/misc/bsd-family-tree"></ulink> lub <ulink type="html" url="file://localhost/usr/share/misc/bsd-family-tree"><filename>/usr/share/misc/bsd-family-tree</filename></ulink> w systemie FreeBSD.</para> </listitem> - + <listitem> <para><emphasis>The BSD Release Announcements collection</emphasis>. 1997. <ulink url="http://www.de.FreeBSD.org/de/ftp/releases/"></ulink></para> </listitem> - + <listitem> <para><emphasis>Networked Computer Science Technical Reports Library</emphasis>. <ulink url="http://www.ncstrl.org/"></ulink></para> </listitem> - + <listitem> <para><emphasis>Stare wydania BSD od Computer Systems Research group (CSRG)</emphasis>. @@ -621,16 +621,16 @@ </listitem> </itemizedlist> </sect1> - + <sect1 id="bibliography-journals"> <title>Czasopisma</title> - + <itemizedlist> <listitem> <para><emphasis>The C/C++ Users Journal</emphasis>. R&D Publications Inc. ISSN 1075-2838</para> </listitem> - + <listitem> <para><emphasis>Sys Admin — The Journal for UNIX System Administrators</emphasis> Miller Freeman, Inc., ISSN diff --git a/pl_PL.ISO8859-2/books/handbook/book.sgml b/pl_PL.ISO8859-2/books/handbook/book.sgml index 63336825ab..ce579788b5 100644 --- a/pl_PL.ISO8859-2/books/handbook/book.sgml +++ b/pl_PL.ISO8859-2/books/handbook/book.sgml @@ -19,13 +19,13 @@ <book lang="pl"> <bookinfo> <title>Podręcznik FreeBSD</title> - + <corpauthor>Projekt Dokumentacji FreeBSD</corpauthor> - + <pubdate>Luty 1999</pubdate> <releaseinfo>$FreeBSD$</releaseinfo> - + <copyright> <year>1995</year> <year>1996</year> @@ -85,7 +85,7 @@ &tm-attrib.xiph; &tm-attrib.general; </legalnotice> - + <abstract> <para>Witamy w świecie FreeBSD! Zadaniem niniejszego podręcznika jest opisanie procesu instalacji i czynności związanych z codziennym @@ -100,7 +100,7 @@ url="http://www.FreeBSD.org/">stronie domowej FreeBSD</ulink> (wersje wcześniejsze dostępne są pod adresem <ulink url="http://docs.FreeBSD.org/doc/"></ulink>). Podręcznik dostępny jest - również w innych formatach dokumentów oraz w postaci skompresowanej z <ulink + również w innych formatach dokumentów oraz w postaci skompresowanej z <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">serwera FTP Projektu FreeBSD</ulink> bądź jednego z wielu <link linkend="mirrors-ftp">serwerów lustrzanych</link>. Dla osób zainteresowanych, @@ -115,7 +115,7 @@ <part id="getting-started"> <title>Pierwsze kroki</title> - + <partintro> <para>Ta część Podręcznika FreeBSD adresowana jest do użytkowników i administratorów, który nie mieli dotychczas kontaktu z systemem FreeBSD. @@ -157,10 +157,10 @@ &chap.ports; &chap.x11; </part> - + <part id="common-tasks"> <title>Codzienne czynności</title> - + <partintro> <para>Skoro podstawy zostały już omówione, ta część Podręcznika zajmie się kilkoma z najczęściej wykorzystywanych funkcji FreeBSD. Niniejsze @@ -281,10 +281,10 @@ &chap.advanced-networking; </part> - + <part id="appendices"> <title>Dodatki</title> - + &chap.mirrors; &chap.bibliography; &chap.eresources; diff --git a/pl_PL.ISO8859-2/books/handbook/boot/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/boot/chapter.sgml index 8f7d536dc9..d3d56fb886 100644 --- a/pl_PL.ISO8859-2/books/handbook/boot/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/boot/chapter.sgml @@ -39,7 +39,7 @@ <para>The options you can give to the components in the FreeBSD bootstrap to control the boot process.</para> </listitem> - + <listitem> <para>The basics of &man.device.hints.5;.</para> </listitem> @@ -209,11 +209,11 @@ label=FreeBSD</programlisting> <command>/sbin/lilo -v</command> to commit your new changes to the system; this should be verified by checking its screen messages.</para> </sect2> - + <sect2 id="boot-boot1"> <title>Stage One, <filename>/boot/boot1</filename>, and Stage Two, <filename>/boot/boot2</filename></title> - + <para>Conceptually the first and second stages are part of the same program, on the same area of the disk. Because of space constraints they have been split into two, but you would always install them @@ -233,7 +233,7 @@ label=FreeBSD</programlisting> in size, and knows just enough about the FreeBSD <firstterm>bsdlabel</firstterm>, which stores information about the slice, to find and execute <filename>boot2</filename>.</para> - + <para><filename>boot2</filename> is slightly more sophisticated, and understands the FreeBSD file system enough to find files on it, and can provide a simple interface to choose the kernel or loader to @@ -256,7 +256,7 @@ boot:</screen> <para>If you ever need to replace the installed <filename>boot1</filename> and <filename>boot2</filename> use &man.bsdlabel.8;:</para> - + <screen>&prompt.root; <userinput>bsdlabel -B <replaceable>diskslice</replaceable></userinput></screen> <para>where <replaceable>diskslice</replaceable> is the disk and slice @@ -282,15 +282,15 @@ boot:</screen> <para>The loader is the final stage of the three-stage bootstrap, and is located on the file system, usually as <filename>/boot/loader</filename>.</para> - + <para>The loader is intended as a user-friendly method for configuration, using an easy-to-use built-in command set, backed up by a more powerful interpreter, with a more complex - command set.</para> + command set.</para> <sect3 id="boot-loader-flow"> <title>Loader Program Flow</title> - + <para>During initialization, the loader will probe for a console and for disks, and figure out what disk it is booting from. It will set variables accordingly, and an @@ -316,10 +316,10 @@ boot:</screen> finally boot or reboot.</para> </sect3> - + <sect3 id="boot-loader-commands"> <title>Loader Built-In Commands</title> - + <para>These are the most commonly used loader commands. For a complete discussion of all available commands, please see &man.loader.8;.</para> @@ -517,7 +517,7 @@ boot:</screen> <primary>kernel</primary> <secondary>boot interaction</secondary> </indexterm> - + <para>Once the kernel is loaded by either <link linkend="boot-loader">loader</link> (as usual) or <link linkend="boot-boot1">boot2</link> (bypassing the loader), it @@ -585,11 +585,11 @@ boot:</screen> <!-- <sect2 id="boot-kernel-userconfig"> <title>UserConfig: the Boot-time Kernel Configurator</title> - + <para> </para> </sect2> --> </sect1> - + <sect1 id="device-hints"> <sect1info> <authorgroup> @@ -616,7 +616,7 @@ boot:</screen> known as variables, sometimes referred to as <quote>device hints</quote>. These <quote>device hints</quote> are used by device drivers for device configuration.</para> - + <para>Device hints may also be specified at the <link linkend="boot-loader"> Stage 3 boot loader</link> prompt. Variables can be added using <command>set</command>, removed with <command>unset</command>, and viewed @@ -685,7 +685,7 @@ boot:</screen> <indexterm> <primary><command>init</command></primary> </indexterm> - + <para>Once the kernel has finished booting, it passes control to the user process &man.init.8;, which is located at <filename>/sbin/init</filename>, or the program path specified @@ -694,7 +694,7 @@ boot:</screen> <sect2 id="boot-autoreboot"> <title>Automatic Reboot Sequence</title> - + <para>The automatic reboot sequence makes sure that the file systems available on the system are consistent. If they are not, and &man.fsck.8; cannot fix the @@ -708,7 +708,7 @@ boot:</screen> <title>Single-User Mode</title> <indexterm><primary>single-user mode</primary></indexterm> <indexterm><primary>console</primary></indexterm> - + <para>This mode can be reached through the <link linkend="boot-autoreboot">automatic reboot sequence</link>, or by the user booting with the @@ -747,11 +747,11 @@ console none unknown off insecure</programlisting> not <literal>secure</literal>.</para> </note> </sect2> - + <sect2 id="boot-multiuser"> <title>Multi-User Mode</title> <indexterm><primary>multi-user mode</primary></indexterm> - + <para>If &man.init.8; finds your file systems to be in order, or once the user has finished in <link linkend="boot-singleuser">single-user mode</link>, the @@ -790,8 +790,8 @@ console none unknown off insecure</programlisting> <para>Upon controlled shutdown, via &man.shutdown.8;, &man.init.8; will attempt to run the script <filename>/etc/rc.shutdown</filename>, and then proceed to send - all processes the <literal>TERM</literal> signal, and subsequently - the <literal>KILL</literal> signal to any that do not terminate + all processes the <literal>TERM</literal> signal, and subsequently + the <literal>KILL</literal> signal to any that do not terminate timely.</para> <para>To power down a FreeBSD machine on architectures and systems diff --git a/pl_PL.ISO8859-2/books/handbook/chapters.ent b/pl_PL.ISO8859-2/books/handbook/chapters.ent index 65bc0842f1..82d26f7eeb 100644 --- a/pl_PL.ISO8859-2/books/handbook/chapters.ent +++ b/pl_PL.ISO8859-2/books/handbook/chapters.ent @@ -1,12 +1,12 @@ <?xml version="1.0" encoding="ISO8859-2"?> -<!-- +<!-- Creates entities for each chapter in the FreeBSD Handbook. Each entity is named chap.foo, where foo is the value of the id attribute on that chapter, and corresponds to the name of the directory in which that chapter's .sgml file is stored. - + Chapters should be listed in the order in which they are referenced. - + $FreeBSD$ Original revision: 1.35 --> diff --git a/pl_PL.ISO8859-2/books/handbook/config/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/config/chapter.sgml index 0e87815257..8791973f1d 100644 --- a/pl_PL.ISO8859-2/books/handbook/config/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/config/chapter.sgml @@ -533,8 +533,8 @@ run_rc_command "$1"</programlisting> important security feature.</para> <note> - <para>User crontabs allow individual users to schedule tasks without the - need for <username>root</username> privileges. Commands in a user's crontab run with the + <para>User crontabs allow individual users to schedule tasks without the + need for <username>root</username> privileges. Commands in a user's crontab run with the permissions of the user who owns the crontab.</para> <para>The <username>root</username> user can have a user crontab just like @@ -638,7 +638,7 @@ HOME=/var/log <para>You must not use the procedure described here to edit/install the system crontab. Simply use your favorite editor: the <command>cron</command> utility will notice that the file - has changed and immediately begin using the updated version. + has changed and immediately begin using the updated version. See <ulink url="&url.books.faq;/admin.html#ROOT-NOT-FOUND-CRON-ERRORS"> this FAQ entry </ulink> for more information.</para> @@ -651,7 +651,7 @@ HOME=/var/log is:</para> <screen>&prompt.user; <userinput>crontab crontab-file</userinput></screen> - + <para>In this example, <filename>crontab-file</filename> is the filename of a <filename>crontab</filename> that was previously created.</para> @@ -666,7 +666,7 @@ HOME=/var/log with an empty file. When the file is saved, it will be automatically installed by the <command>crontab</command> command. </para> - + <para>If you later want to remove your user <filename>crontab</filename> completely, use <command>crontab</command> with the <option>-r</option> option. diff --git a/pl_PL.ISO8859-2/books/handbook/cutting-edge/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/cutting-edge/chapter.sgml index 52d4f4cce2..56f4758ae5 100644 --- a/pl_PL.ISO8859-2/books/handbook/cutting-edge/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/cutting-edge/chapter.sgml @@ -77,7 +77,7 @@ software (<xref linkend="ports"/>).</para></listitem> </itemizedlist> </sect1> - + <sect1 id="current-stable"> <title>&os.current; vs. &os.stable;</title> <indexterm><primary>-CURRENT</primary></indexterm> @@ -185,7 +185,7 @@ <sect3> <title>Using &os.current;</title> - + <indexterm> <primary>-CURRENT</primary> <secondary>using</secondary> @@ -235,10 +235,10 @@ This is the most recommended method, since it allows you to grab the entire collection once and then only what has changed from then - on. Many people run <command>cvsup</command> from + on. Many people run <command>cvsup</command> from <command>cron</command> and keep their - sources up-to-date automatically. You have to - customize the sample <filename>supfile</filename> above, and configure + sources up-to-date automatically. You have to + customize the sample <filename>supfile</filename> above, and configure <link linkend="cvsup">cvsup</link> for your environment.</para> </listitem> @@ -284,7 +284,7 @@ that sometimes become necessary as we move toward the next release.</para> </listitem> - + <listitem> <para>Be active! If you are running &os.current;, we want to know what you have to say about it, especially if you @@ -295,7 +295,7 @@ </orderedlist> </sect3> </sect2> - + <sect2 id="stable"> <title>Staying Stable with &os;</title> @@ -357,7 +357,7 @@ <sect3> <title>Using &os.stable;</title> - + <orderedlist> <listitem> <indexterm> @@ -420,7 +420,7 @@ This is the most recommended method, since it allows you to grab the entire collection once and then only what has changed from then - on. Many people run <command>cvsup</command> from + on. Many people run <command>cvsup</command> from <command>cron</command> to keep their sources up-to-date automatically. You have to customize the sample <filename>supfile</filename> above, @@ -473,7 +473,7 @@ <sect1 id="synching"> <title>Synchronizing Your Source</title> - + <para>There are various ways of using an Internet (or email) connection to stay up-to-date with any given area of the &os; project sources, or all areas, depending on what interests you. The @@ -500,7 +500,7 @@ <para><application>Anonymous CVS</application> and <application>CVSup</application> use the <emphasis>pull</emphasis> model of updating sources. In the case of - <application>CVSup</application> the user (or a + <application>CVSup</application> the user (or a <command>cron</command> script) invokes the <command>cvsup</command> program, and it interacts with a <command>cvsupd</command> server somewhere to bring your files @@ -664,7 +664,7 @@ <important> <para>Reading <filename>UPDATING</filename> is not an acceptable - substitute for subscribing to the correct mailing list, as described + substitute for subscribing to the correct mailing list, as described previously. The two requirements are complementary, not exclusive.</para> </important> @@ -694,7 +694,7 @@ to <filename>/etc/make.conf</filename> and uncomment them.</para> - <para>Examine the other definitions (<makevar>COPTFLAGS</makevar>, + <para>Examine the other definitions (<makevar>COPTFLAGS</makevar>, <makevar>NOPORTDOCS</makevar> and so on) and decide if they are relevant to you.</para> </sect2> @@ -845,9 +845,9 @@ when the process has finished.</para> <screen>&prompt.root; <userinput>script /var/tmp/mw.out</userinput> -Script started, output file is /var/tmp/mw.out +Script started, output file is /var/tmp/mw.out &prompt.root; <userinput>make TARGET</userinput> -<emphasis>… compile, compile, compile …</emphasis> +<emphasis>… compile, compile, compile …</emphasis> &prompt.root; <userinput>exit</userinput> Script done, …</screen> @@ -937,13 +937,13 @@ Script done, …</screen> <maketarget>installworld</maketarget> part in single user mode, though.</para> - <para>Secondly, it allows you to use NFS mounts to upgrade + <para>Secondly, it allows you to use NFS mounts to upgrade multiple machines on your network. If you have three machines, <hostid>A</hostid>, <hostid>B</hostid> and <hostid>C</hostid> that you want to upgrade, run <command>make buildworld</command> and <command>make installworld</command> on <hostid>A</hostid>. <hostid>B</hostid> and <hostid>C</hostid> should then NFS mount <filename>/usr/src</filename> and <filename>/usr/obj</filename> from <hostid>A</hostid>, and you can then run - <command>make installworld</command> to install the results of + <command>make installworld</command> to install the results of the build on <hostid>B</hostid> and <hostid>C</hostid>.</para> <para>Although the <maketarget>world</maketarget> target still exists, @@ -952,7 +952,7 @@ Script done, …</screen> <para>Run</para> <screen>&prompt.root; <userinput>make buildworld</userinput></screen> - + <para>It is possible to specify a <option>-j</option> option to <command>make</command> which will cause it to spawn several simultaneous processes. This is most useful on multi-CPU machines. @@ -960,7 +960,7 @@ Script done, …</screen> than CPU bound it is also useful on single CPU machines.</para> <para>On a typical single-CPU machine you would run:</para> - + <screen>&prompt.root; <userinput>make -j4 buildworld</userinput></screen> <para>&man.make.1; will then have up to 4 processes running at any one @@ -971,7 +971,7 @@ Script done, …</screen> configured kernel try values between 6 and 10 and see how they speed things up.</para> </sect3> - + <sect3> <title>Timings</title> <indexterm> @@ -985,7 +985,7 @@ Script done, …</screen> process. A &os.current; tree will take somewhat longer.</para> </sect3> </sect2> - + <sect2> <title>Compile and Install a New Kernel</title> <indexterm> @@ -1062,7 +1062,7 @@ Script done, …</screen> line. This does not necessarily hold true for other options; for example, <option>-j</option> must never be used with <maketarget>installworld</maketarget>.</para> - + <para>For example, if you ran:</para> <screen>&prompt.root; <userinput>make -DNO_PROFILE buildworld</userinput></screen> @@ -1079,7 +1079,7 @@ Script done, …</screen> <sect2> <title>Update Files Not Updated by <command>make installworld</command></title> - + <para>Remaking the world will not update certain directories (in particular, <filename>/etc</filename>, <filename>/var</filename> and <filename>/usr</filename>) with new or changed configuration files.</para> @@ -1178,7 +1178,7 @@ Script done, …</screen> <para>The simplest way to do this by hand is to install the files into a new directory, and then work through them looking for differences.</para> - + <warning> <title>Backup Your Existing <filename>/etc</filename></title> @@ -1192,7 +1192,7 @@ Script done, …</screen> <para><option>-R</option> does a recursive copy, <option>-p</option> preserves times, ownerships on files and suchlike.</para> </warning> - + <para>You need to build a dummy set of directories to install the new <filename>/etc</filename> and other files into. <filename>/var/tmp/root</filename> is a reasonable choice, and @@ -1207,10 +1207,10 @@ Script done, …</screen> files. A lot of the subdirectories that have been created under <filename>/var/tmp/root</filename> are empty and should be deleted. The simplest way to do this is to:</para> - + <screen>&prompt.root; <userinput>cd /var/tmp/root</userinput> &prompt.root; <userinput>find -d . -type d | xargs rmdir 2>/dev/null</userinput></screen> - + <para>This will remove all empty directories. (Standard error is redirected to <filename>/dev/null</filename> to prevent the warnings about the directories that are not empty.)</para> @@ -1219,7 +1219,7 @@ Script done, …</screen> should be placed in appropriate locations below <filename>/</filename>. You now have to go through each of these files, determining how they differ with your existing files.</para> - + <para>Note that some of the files that will have been installed in <filename>/var/tmp/root</filename> have a leading <quote>.</quote>. At the time of writing the only files like this are shell startup files in @@ -1227,18 +1227,18 @@ Script done, …</screen> <filename>/var/tmp/root/root/</filename>, although there may be others (depending on when you are reading this). Make sure you use <command>ls -a</command> to catch them.</para> - + <para>The simplest way to do this is to use &man.diff.1; to compare the two files:</para> - + <screen>&prompt.root; <userinput>diff /etc/shells /var/tmp/root/etc/shells</userinput></screen> - + <para>This will show you the differences between your <filename>/etc/shells</filename> file and the new <filename>/var/tmp/root/etc/shells</filename> file. Use these to decide whether to merge in changes that you have made or whether to copy over your old file.</para> - + <tip> <title>Name the New Root Directory (<filename>/var/tmp/root</filename>) with a Time Stamp, so You Can @@ -1259,22 +1259,22 @@ Script done, …</screen> target directory a name based on the current date. If you were doing this on the 14th of February 1998 you could do the following:</para> - + <screen>&prompt.root; <userinput>mkdir /var/tmp/root-19980214</userinput> &prompt.root; <userinput>cd /usr/src/etc</userinput> &prompt.root; <userinput>make DESTDIR=/var/tmp/root-19980214 \ distrib-dirs distribution</userinput></screen> </step> - + <step> <para>Merge in the changes from this directory as outlined above.</para> - + <para><emphasis>Do not</emphasis> remove the <filename>/var/tmp/root-19980214</filename> directory when you have finished.</para> </step> - + <step> <para>When you have downloaded the latest version of the source and remade it, follow step 1. This will give you a new @@ -1282,15 +1282,15 @@ Script done, …</screen> <filename>/var/tmp/root-19980221</filename> (if you wait a week between doing updates).</para> </step> - + <step> <para>You can now see the differences that have been made in the intervening week using &man.diff.1; to create a recursive diff between the two directories:</para> - + <screen>&prompt.root; <userinput>cd /var/tmp</userinput> &prompt.root; <userinput>diff -r root-19980214 root-19980221</userinput></screen> - + <para>Typically, this will be a much smaller set of differences than those between <filename>/var/tmp/root-19980221/etc</filename> and @@ -1298,14 +1298,14 @@ Script done, …</screen> smaller, it is easier to migrate those changes across into your <filename>/etc</filename> directory.</para> </step> - + <step> <para>You can now remove the older of the two <filename>/var/tmp/root-*</filename> directories:</para> - + <screen>&prompt.root; <userinput>rm -rf /var/tmp/root-19980214</userinput></screen> </step> - + <step> <para>Repeat this process every time you need to merge in changes to <filename>/etc</filename>.</para> @@ -1314,15 +1314,15 @@ Script done, …</screen> <para>You can use &man.date.1; to automate the generation of the directory names:</para> - + <screen>&prompt.root; <userinput>mkdir /var/tmp/root-`date "+%Y%m%d"`</userinput></screen> </tip> </sect3> </sect2> - + <sect2 id="cutting-edge-rebooting"> <title>Rebooting</title> - + <para>You are now done. After you have verified that everything appears to be in the right place you can reboot the system. A simple &man.shutdown.8; should do it:</para> @@ -1332,10 +1332,10 @@ Script done, …</screen> <sect2> <title>Finished</title> - + <para>You should now have successfully upgraded your &os; system. Congratulations.</para> - + <para>If things went slightly wrong, it is easy to rebuild a particular piece of the system. For example, if you accidentally deleted <filename>/etc/magic</filename> as part of the upgrade or merge of @@ -1344,8 +1344,8 @@ Script done, …</screen> <screen>&prompt.root; <userinput>cd /usr/src/usr.bin/file</userinput> &prompt.root; <userinput>make all install</userinput></screen> - </sect2> - + </sect2> + <sect2> <title>Questions</title> @@ -1359,7 +1359,7 @@ Script done, …</screen> <para>There is no easy answer to this one, as it depends on the nature of the change. For example, if you just ran <application>CVSup</application>, and it has shown the following files as being updated:</para> - + <screen><filename>src/games/cribbage/instr.c</filename> <filename>src/games/sail/pl_main.c</filename> <filename>src/release/sysinstall/config.c</filename> @@ -1374,13 +1374,13 @@ Script done, …</screen> re-make the world, or at least those parts of it that are statically linked (as well as anything else you might have added that is statically linked).</para> - + <para>At the end of the day, it is your call. You might be happy re-making the world every fortnight say, and let changes accumulate over that fortnight. Or you might want to re-make just those things that have changed, and be confident you can spot all the dependencies.</para> - + <para>And, of course, this all depends on how often you want to upgrade, and whether you are tracking &os.stable; or &os.current;.</para> @@ -1401,10 +1401,10 @@ Script done, …</screen> hardware, and will frequently throw up memory problems. These normally manifest themselves as the compiler mysteriously dying on receipt of strange signals.</para> - + <para>A sure indicator of this is if you can restart the make and it dies at a different point in the process.</para> - + <para>In this instance there is little you can do except start swapping around the components in your machine to determine which one is failing.</para> @@ -1416,10 +1416,10 @@ Script done, …</screen> <para>Can I remove <filename>/usr/obj</filename> when I have finished?</para> </question> - + <answer> <para>The short answer is yes.</para> - + <para><filename>/usr/obj</filename> contains all the object files that were produced during the compilation phase. Normally, one of the first steps in the <command>make buildworld</command> process is to @@ -1427,7 +1427,7 @@ Script done, …</screen> <filename>/usr/obj</filename> around after you have finished makes little sense, and will free up a large chunk of disk space (currently about 340 MB).</para> - + <para>However, if you know what you are doing you can have <command>make buildworld</command> skip this step. This will make subsequent builds run much faster, since most of sources will not need to @@ -1478,7 +1478,7 @@ Building everything.. <para>in the <command>make buildworld</command> output then it is probably fairly safe to do so.</para> - + <para>If you do not see that message, or you are not sure, then it is always better to be safe than sorry, and restart the build from scratch.</para> @@ -1495,26 +1495,26 @@ Building everything.. <listitem> <para>Run in single user mode.</para> </listitem> - + <listitem> <para>Put the <filename>/usr/src</filename> and <filename>/usr/obj</filename> directories on separate file systems held on separate disks. If possible, put these disks on separate disk controllers.</para> </listitem> - + <listitem> <para>Better still, put these file systems across multiple disks using the &man.ccd.4; (concatenated disk driver) device.</para> </listitem> - + <listitem> <para>Turn off profiling (set <quote>NO_PROFILE=true</quote> in <filename>/etc/make.conf</filename>). You almost certainly do not need it.</para> </listitem> - + <listitem> <para>Also in <filename>/etc/make.conf</filename>, set <makevar>CFLAGS</makevar> to something like <option>-O @@ -1525,22 +1525,22 @@ Building everything.. pipes rather than temporary files for communication, which saves disk access (at the expense of memory).</para> </listitem> - + <listitem> <para>Pass the <option>-j<replaceable>n</replaceable></option> option to &man.make.1; to - run multiple processes in parallel. This usually helps + run multiple processes in parallel. This usually helps regardless of whether you have a single or a multi processor machine.</para> </listitem> - + <listitem><para>The file system holding <filename>/usr/src</filename> can be mounted (or remounted) with the <option>noatime</option> option. This prevents the file system from recording the file access time. You probably do not need this information anyway.</para> - + <screen>&prompt.root; <userinput>mount -u -o noatime /usr/src</userinput></screen> - + <warning> <para>The example assumes <filename>/usr/src</filename> is on its own file system. If it is not (if it is a part of @@ -1549,7 +1549,7 @@ Building everything.. <filename>/usr/src</filename>.</para> </warning> </listitem> - + <listitem> <para>The file system holding <filename>/usr/obj</filename> can be mounted (or remounted) with the <option>async</option> @@ -1564,16 +1564,16 @@ Building everything.. more fragile. With this option there is an increased chance that, should power fail, the file system will be in an unrecoverable state when the machine restarts.</para> - + <para>If <filename>/usr/obj</filename> is the only thing on this file system then it is not a problem. If you have other, valuable data on the same file system then ensure your backups are fresh before you enable this option.</para> </warning> - + <screen>&prompt.root; <userinput>mount -u -o async /usr/obj</userinput></screen> - + <warning> <para>As above, if <filename>/usr/obj</filename> is not on its own file system, replace it in the example with the @@ -1631,7 +1631,7 @@ Building everything.. <primary>NFS</primary> <secondary>installing multiple machines</secondary> </indexterm> - + <para>If you have multiple machines that you want to track the same source tree, then having all of them download sources and rebuild everything seems like a waste of resources: disk space, @@ -1667,7 +1667,7 @@ Building everything.. as well. If you have multiple build sets, <filename>/usr/src</filename> should be on one build machine, and NFS mounted on the rest.</para> - + <para>Finally make sure that <filename>/etc/make.conf</filename> on all the machines in the build set agrees with the build machine. That means that @@ -1721,7 +1721,7 @@ Building everything.. local build directory. Finally, if you are going to be building and distributing packages, you should set <makevar>PACKAGES</makevar> to a directory similar to - <makevar>DISTDIR</makevar>.</para> + <makevar>DISTDIR</makevar>.</para> </sect2> </sect1> </chapter> diff --git a/pl_PL.ISO8859-2/books/handbook/desktop/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/desktop/chapter.sgml index 25e0a64481..327f4c7239 100644 --- a/pl_PL.ISO8859-2/books/handbook/desktop/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/desktop/chapter.sgml @@ -169,7 +169,7 @@ <entry>długa</entry> <entry><application>Gtk+</application></entry> </row> - + <row> <entry><application>Konqueror</application></entry> <entry>średnie</entry> @@ -234,7 +234,7 @@ <screen>&prompt.user; <userinput>mozilla -mail</userinput></screen> </sect2> - + <sect2> <title>Firefox</title> <indexterm> @@ -450,7 +450,7 @@ </tbody> </tgroup> </informaltable> - + <sect2> <title>KOffice</title> <indexterm> @@ -809,7 +809,7 @@ czy <application>Excel</application>.</para> <para>Sekcja ta omawia następujące aplikacje:</para> - + <informaltable frame="none" pgwide="1"> <tgroup cols="4"> <thead> @@ -845,7 +845,7 @@ </tbody> </tgroup> </informaltable> - + <sect2> <title>GnuCash</title> <indexterm> diff --git a/pl_PL.ISO8859-2/books/handbook/disks/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/disks/chapter.sgml index 1708418449..66bed45936 100644 --- a/pl_PL.ISO8859-2/books/handbook/disks/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/disks/chapter.sgml @@ -3824,7 +3824,7 @@ device crypto</screen> the data source for key file will be <filename>/dev/random</filename>. The sector size of <filename>/dev/da2.eli</filename>, which we call provider, - will be 4kB.</para> + will be 4kB.</para> <screen>&prompt.root; <userinput>dd if=/dev/random of=/root/da2.key bs=64 count=1</userinput> &prompt.root; <userinput>geli init -s 4096 -K /root/da2.key /dev/da2</userinput> @@ -3917,7 +3917,7 @@ geli_da2_flags="-p -k /root/da2.key"</screen> <link linkend="configtuning-rcd">rc.d</link> section of the Handbook.</para> </sect3> - </sect2> + </sect2> </sect1> diff --git a/pl_PL.ISO8859-2/books/handbook/geom/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/geom/chapter.sgml index f2032b20be..756a535bcd 100644 --- a/pl_PL.ISO8859-2/books/handbook/geom/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/geom/chapter.sgml @@ -171,7 +171,7 @@ <screen>&prompt.root; <userinput>gstripe label -v st0 /dev/ad2 /dev/ad3</userinput></screen> -<!-- +<!-- <para>A message should be returned explaining that meta data has been stored on the devices. XXX: What message? Put it inside the screen output above. diff --git a/pl_PL.ISO8859-2/books/handbook/install/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/install/chapter.sgml index 0964b7c3f9..2355c4b69b 100644 --- a/pl_PL.ISO8859-2/books/handbook/install/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/install/chapter.sgml @@ -56,7 +56,7 @@ <listitem> <para>W jaki sposób tworzy się dyskietki instalacyjne FreeBSD.</para> </listitem> - + <listitem> <para>Jak FreeBSD odwołuje się do dysku i jak go dzieli.</para> </listitem> @@ -222,7 +222,7 @@ <sect2> <title>Przygotowanie kopii danych</title> - + <para>Jeśli komputer, na którym będzie przeprowadzana instalacja zawiera cenne dane, powinniśmy koniecznie przygotować ich kopię zapasową, oraz sprawdzić stan tychże kopii przed instalacją FreeBSD. @@ -393,7 +393,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen> <para>Powyższy przykład pochodzi z komputera Digital Personal Workstation 433au i pokazuje trzy dyski. Pierwszym z nich jest CDROM opisany nazwą <devicename>DKA0</devicename>, - natomiast dwa pozostałe to twarde dyski o nazwach + natomiast dwa pozostałe to twarde dyski o nazwach <devicename>DKC0</devicename> i <devicename>DKC100</devicename>.</para> @@ -483,7 +483,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen> </sect2> <sect2> <title>Sprawdzenie erraty FreeBSD</title> - + <para>W pracy nad FreeBSD podejmowane są wszelkie starania, aby każde wydanie FreeBSD było jak najbardziej niezawodne, jednakże od czasu do czasu zdarzają się błędy. W pewnych bardzo rzadkich @@ -510,7 +510,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen> <itemizedlist> <title>Nośniki lokalne</title> - + <listitem> <para>Płyta CDROM lub DVD</para> </listitem> @@ -558,7 +558,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen> <sect2 id="install-floppies"> <title>Przygotowanie dyskietek do instalacji</title> - + <para>Instalacja FreeBSD rozpoczyna się uruchomieniem programu instalacyjnego podczas startu komputera — nie jest to program, który można uruchomić w innym systemie operacyjnym. @@ -576,13 +576,13 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen> zawierające FreeBSD mogą być użyte jako dyski startowe bez dodatkowego przygotowania.</para> </tip> - + <para>By utworzyć zestaw dyskietek startowych, należy:</para> <procedure> <step> <title>Zdobyć obrazy dyskietek startowych</title> - + <para>Dyskietki startowe znaleźć można wśród plików instalacyjnych w katalogu <filename>floppies/</filename> bądź pobrać z serwera @@ -620,7 +620,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen> <step> <title>Przygotować dyskietki startowe</title> - + <para>Dla każdego pliku z obrazem przygotowujemy jedną dyskietkę. Dyskietki nie mogą być w jakikolwiek sposób uszkodzone. Najprostszym sposobem samodzielnego sprawdzenia, czy dyskietka @@ -672,12 +672,12 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen> url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">katalogu <filename class="directory">tools</filename></ulink> na serwerze FTP FreeBSD.</para> - + <para>Jeżeli natomiast dyskietki nagrywamy w systemie uniksowym (na przykład w innym FreeBSD), do zapisania plików obrazów na dyskietkach możemy wykorzystać polecenie &man.dd.1;. We FreeBSD wpisalibyśmy:</para> - + <screen>&prompt.root; <userinput>dd if=kern.flp of=/dev/fd0</userinput></screen> <para>W systemie FreeBSD <filename>/dev/fd0</filename> odpowiada @@ -787,12 +787,12 @@ We can take no responsibility for lost disk contents!</literallayout> </listitem> </orderedlist> </step> - + <step> <para>Rozpocznie się ładowanie FreeBSD. Podczas ładowania z płyty CD pojawi się tekst podobny do poniższego (pominięto informacje o wersji)::</para> - + <screen>Verifying DMI Pool Data ........ Boot from ATAPI CD-ROM : 1. FD 2.88MB System Type-(00) @@ -813,19 +813,19 @@ FreeBSD/i386 bootstrap loader, Revision 0.8 | Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... _</screen> - + <para>Natomiast ładując z dyskietki, zobaczymy tekst w rodzaju (pominięto informacje o wersji):</para> - - <screen>Verifying DMI Pool Data ........ -BTX loader 1.00 BTX version is 1.01 -Console: internal video/keyboard -BIOS drive A: is disk0 -BIOS drive C: is disk1 -BIOS 639kB/261120kB available memory + <screen>Verifying DMI Pool Data ........ -FreeBSD/i386 bootstrap loader, Revision 0.8 +BTX loader 1.00 BTX version is 1.01 +Console: internal video/keyboard +BIOS drive A: is disk0 +BIOS drive C: is disk1 +BIOS 639kB/261120kB available memory + +FreeBSD/i386 bootstrap loader, Revision 0.8 /kernel text=0x277391 data=0x3268c+0x332a8 | @@ -845,7 +845,7 @@ Please insert MFS root floppy and press enter:</screen> <para>Niezależnie, czy uruchamiamy komputer z dyskietki czy z płyty, podczas ładowania ujrzymy komunikat:</para> - <screen>Hit [Enter] to boot immediately, or any other key for command prompt. + <screen>Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... _</screen> <para>Albo czekamy dziesięć sekund, albo wciskamy <keycap>Enter</keycap>.</para> @@ -885,7 +885,7 @@ Booting [kernel] in 9 seconds... _</screen> <screen>>>><userinput>BOOT DKA0 -FLAGS '' -FILE ''</userinput></screen> </step> - + <step> <para>Rozpocznie się ładowanie FreeBSD. Podczas ładowania z dyskietki, zobaczymy tekst w rodzaju:</para> @@ -902,7 +902,7 @@ Booting [kernel] in 9 seconds... _</screen> <para>Niezależnie, czy uruchamiamy komputer z dyskietki czy z płyty, podczas ładowania ujrzymy komunikat:</para> - <screen>Hit [Enter] to boot immediately, or any other key for command prompt. + <screen>Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... _</screen> <para>Czekamy dziesięć sekund, albo wciskamy <keycap>Enter</keycap>. @@ -936,15 +936,15 @@ Booting [kernel] in 9 seconds... _</screen> <figure id="install-dev-probe"> <title>Przykład wyników rozpoznania urządzeń</title> - <screen>avail memory = 253050880 (247120K bytes) + <screen>avail memory = 253050880 (247120K bytes) Preloaded elf kernel "kernel" at 0xc0817000. Preloaded mfs_root "/mfsroot" at 0xc0817084. md0: Preloaded image </mfsroot> 4423680 bytes at 0xc03ddcd4 md1: Malloc disk Using $PIR table, 4 entries at 0xc00fde60 -npx0: <math processor> on motherboard -npx0: INT 16 interface +npx0: <math processor> on motherboard +npx0: INT 16 interface pcib0: <Host to PCI bridge> on motherboard pci0: <PCI bus> on pcib0 pcib1:<VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0 @@ -1024,8 +1024,8 @@ Mounting root from ufs:/dev/md0c komunikat:</para> - <screen> User Confirmation Requested - Are you sure you wish to exit? The system will reboot + <screen> User Confirmation Requested + Are you sure you wish to exit? The system will reboot (be sure to remove any floppies from the drives). [ Yes ] No</screen> @@ -1274,7 +1274,7 @@ Mounting root from ufs:/dev/md0c <sidebar> <title>Fragment z Archiwum Wyjątkowych Przygód Bolka i Lolka:</title> - + <para>Bolek ma przygotować dla Lolka komputer z FreeBSD. Bolek montuje jeden dysk SCSI jako urządzenie SCSI zero, i instaluje na nim FreeBSD.</para> @@ -1356,8 +1356,8 @@ Mounting root from ufs:/dev/md0c the disk(s) selected) then use the (A)ll command to select the default partitioning scheme followed by a (Q)uit. If you wish to allocate only free space to FreeBSD, move to a partition marked "unused" and use the - (C)reate command. - [ OK ] + (C)reate command. + [ OK ] [ Press enter or space ]</screen> @@ -1394,7 +1394,7 @@ Mounting root from ufs:/dev/md0c (np. <devicename>ad1s1a</devicename>), mogłoby się nagle okazać, że niektóre systemy plików nie działają poprawnie. Aby to poprawić, musielibyśmy zmienić konfigurację systemu.</para> - + <para>Aby zapobiec takim sytuacjom, jądro FreeBSD może być skonfigurowane tak, by przydzielać dyskom IDE numery zgodne z ich rzeczywistym umiejscowieniem, niezależnie od kolejności wykrywania. Tym sposobem @@ -1473,7 +1473,7 @@ Mounting root from ufs:/dev/md0c <keycap>Enter</keycap>. Wartość domyślna stanowi największy możliwy rozmiar segmentu, czyli np. wolną przestrzeń na dysku bądź całą pojemność dysku twardego.</para> - + <para>Wolne miejsce dla FreeBSD mogliśmy także przygotować wcześniej (na przykład przy użyciu programu <application>&partitionmagic;</application>), w takim wypadku po @@ -1579,7 +1579,7 @@ Mounting root from ufs:/dev/md0c <sect2 id="bsdlabeleditor"> <title>Tworzenie partycji z wykorzystaniem <application>Disklabel</application></title> - + <para>W nowoutworzonych segmentach musimy stworzyć kilka partycji. Pamiętajmy, że każda partycja oznaczona jest literą od <literal>a</literal> do <literal>h</literal>, a partycje @@ -1610,7 +1610,7 @@ Mounting root from ufs:/dev/md0c <thead> <row> <entry>Partycja</entry> - + <entry>System plików</entry> <entry>Rozmiar</entry> @@ -1690,7 +1690,7 @@ Mounting root from ufs:/dev/md0c </tbody> </tgroup> </table> - + <para>Jeżeli instalujemy FreeBSD na dwóch lub więcej dyskach, musimy utworzyć partycje także w innych przygotowanych segmentach. Najłatwiej jest po prostu przygotować na każdym z kolejnych dysków dwie partycje, @@ -1708,7 +1708,7 @@ Mounting root from ufs:/dev/md0c <thead> <row> <entry>Partycja</entry> - + <entry>System plików</entry> <entry>Rozmiar</entry> @@ -1768,7 +1768,7 @@ Mounting root from ufs:/dev/md0c space (200MB or more) and don't have any special requirements, simply use the (A)uto command to allocate space automatically. If you have more specific needs or just don't care for the layout chosen by - (A)uto, press F1 for more information on manual layout. + (A)uto, press F1 for more information on manual layout. [ OK ] [ Press enter or space ]</screen> @@ -1871,7 +1871,7 @@ Mounting root from ufs:/dev/md0c wartość klawiszem <keycap>Backspace</keycap>, i wpisujemy 64M, <xref linkend="sysinstall-label-add2"/>. Następnie wybieramy &gui.ok;.</para> - + <figure id="sysinstall-label-add2"> <title>Zmiana rozmiaru głównej partycji</title> @@ -1890,14 +1890,14 @@ Mounting root from ufs:/dev/md0c <figure id="sysinstall-label-type"> <title>Wybór typu głównej partycji</title> - + <mediaobject> <imageobject> <imagedata fileref="install/disklabel-fs" format="PNG"/> </imageobject> </mediaobject> </figure> - + <para>Ponieważ na partycji znajdować się będzie system plików, <application>Disklabel</application> musi wiedzieć, gdzie będzie on zamontowany. <xref linkend="sysinstall-label-mount"/> przedstawia @@ -1930,7 +1930,7 @@ Mounting root from ufs:/dev/md0c <figure id="sysinstall-label4"> <title>Edytor Disklabel</title> - + <mediaobject> <imageobject> <imagedata fileref="install/disklabel-ed2" format="PNG"/> @@ -2014,21 +2014,21 @@ Mounting root from ufs:/dev/md0c &ports.size;.</para> <screen> User Confirmation Requested - Would you like to install the FreeBSD ports collection? + Would you like to install the FreeBSD ports collection? This will give you ready access to over &os.numports; ported software packages, at a cost of around &ports.size; of disk space when "clean" and possibly much more than that if a lot of the distribution tarballs are loaded (unless you have the extra CDs from a FreeBSD CD/DVD distribution available and can mount it on /cdrom, in which case this is far less - of a problem). + of a problem). The Ports Collection is a very valuable resource and well worth having - on your /usr partition, so it is advisable to say Yes to this option. + on your /usr partition, so it is advisable to say Yes to this option. For more information on the Ports Collection & the latest ports, - visit: - http://www.FreeBSD.org/ports + visit: + http://www.FreeBSD.org/ports [ Yes ] No</screen> @@ -2064,7 +2064,7 @@ Mounting root from ufs:/dev/md0c (instalacja z CD/DVD). Upewniwszy się, że zaznaczone jest &gui.ok;, naciskamy <keycap>Enter</keycap> przechodząc do następnego etapu instalacji.</para> - + <para>Jeżeli stosujemy inną metodę instalacji, wybieramy odpowiednią pozycję i postępujemy zgodnie ze wskazówkami.</para> @@ -2090,7 +2090,7 @@ Mounting root from ufs:/dev/md0c <secondary>sieć</secondary> <tertiary>FTP</tertiary> </indexterm> - + <para>Można wybrać jeden z trzech trybów instalacji przez FTP: aktywne FTP, pasywne FTP lub pośrednio przez HTTP proxy.</para> @@ -2099,7 +2099,7 @@ Mounting root from ufs:/dev/md0c <varlistentry> <term>Aktywne FTP: <guimenuitem>Install from an FTP server</guimenuitem></term> - + <listitem> <para>Wybór tego wariantu spowoduje, że przesyłanie danych przez FTP odbywać się będzie w trybie @@ -2111,11 +2111,11 @@ Mounting root from ufs:/dev/md0c spróbujmy aktywnego!</para> </listitem> </varlistentry> - + <varlistentry> <term>Pasywne FTP: <guimenuitem>Install from an FTP server through a firewall</guimenuitem></term> - + <listitem> <indexterm> <primary>FTP</primary> @@ -2130,17 +2130,17 @@ Mounting root from ufs:/dev/md0c </para> </listitem> </varlistentry> - + <varlistentry> <term>FTP przez proxy HTTP: <guimenuitem>Install from an FTP server through a http proxy</guimenuitem></term> - + <listitem> <indexterm> <primary>FTP</primary> <secondary>przez proxy HTTP</secondary> </indexterm> - + <para>Ten wariant instruuje <application>sysinstall</application> do wykorzystania protokołu HTTP (podobnie jak przeglądarka stron WWW) do połączenia się z serwerem proxy pośredniczącym @@ -2153,7 +2153,7 @@ Mounting root from ufs:/dev/md0c </listitem> </varlistentry> </variablelist> - + <para>Korzystając z pośredniczącego serwera FTP proxy, zwykle podajemy nazwę serwera docelowego jako część nazwy użytkownika, po znaku <quote>@</quote>. Serwer proxy <quote>udaje</quote> @@ -2161,7 +2161,7 @@ Mounting root from ufs:/dev/md0c zainstalować system z <hostid role="fqdn">ftp.FreeBSD.org</hostid>, za pośrednictwem serwera proxy FTP <hostid role="fqdn">foo.example.com</hostid>, nasłuchującego na porcie 1024.</para> - + <para>W takiej sytuacji przechodzimy do menu opcji, jako nazwę użytkownika FTP wpisujemy <literal>ftp@ftp.FreeBSD.org</literal>, a jako hasło podajemy nasz adres email. Jako nośnik instalacji @@ -2186,12 +2186,12 @@ Mounting root from ufs:/dev/md0c zawartości dysku twardego.</para> <screen> User Confirmation Requested - Last Chance! Are you SURE you want to continue the installation? + Last Chance! Are you SURE you want to continue the installation? If you're running this on a disk with data you wish to save then WE - STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding! + STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding! - We can take no responsibility for lost disk contents! + We can take no responsibility for lost disk contents! [ Yes ] No</screen> @@ -2201,21 +2201,21 @@ Mounting root from ufs:/dev/md0c <para>Czas trwania instalacji zależy od wybranych komponentów, używanego nośnika instalacji oraz prędkości komputera. Szereg komunikatów informować będzie o przebiegu procesu instalacji.</para> - + <para>Po zakończeniu instalacji wyświetlony zostanie następujący komunikat:</para> - <screen> Message + <screen> Message -Congratulations! You now have FreeBSD installed on your system. +Congratulations! You now have FreeBSD installed on your system. -We will now move on to the final configuration questions. -For any option you do not wish to configure, simply select No. +We will now move on to the final configuration questions. +For any option you do not wish to configure, simply select No. If you wish to re-enter this utility after the system is up, you may -do so by typing: /stand/sysinstall . +do so by typing: /stand/sysinstall . - [ OK ] + [ OK ] [ Press enter to continue ]</screen> @@ -2229,9 +2229,9 @@ do so by typing: /stand/sysinstall . <screen> Message Installation complete with some errors. You may wish to scroll -through the debugging messages on VTY1 with the scroll-lock feature. +through the debugging messages on VTY1 with the scroll-lock feature. You can also choose "No" at the next prompt and go back into the -installation menus to retry whichever operations have failed. +installation menus to retry whichever operations have failed. [ OK ]</screen> @@ -2265,7 +2265,7 @@ installation menus to retry whichever operations have failed. linkend="advanced-networking">Zaawansowana konfiguracja sieciowa</link>.</para> - <screen> User Confirmation Requested + <screen> User Confirmation Requested Would you like to configure any Ethernet or SLIP/PPP network devices? [ Yes ] No</screen> @@ -2287,7 +2287,7 @@ installation menus to retry whichever operations have failed. <para>Klawiszami kursora wybieramy interfejs, który będziemy konfigurować i wciskamy <keycap>Enter</keycap>.</para> - <screen> User Confirmation Requested + <screen> User Confirmation Requested Do you want to try IPv6 configuration of the interface? Yes [ No ]</screen> @@ -2300,7 +2300,7 @@ installation menus to retry whichever operations have failed. wybieramy &gui.yes; i naciskamy <keycap>Enter</keycap>. Przez chwilę będzie się odbywać poszukiwanie serwerów <acronym>RA</acronym>.</para> - <screen> User Confirmation Requested + <screen> User Confirmation Requested Do you want to try DHCP configuration of the interface? Yes [ No ]</screen> @@ -2409,7 +2409,7 @@ installation menus to retry whichever operations have failed. wybieramy &gui.ok; i naciskamy <keycap>Enter</keycap>.</para> - <screen> User Confirmation Requested + <screen> User Confirmation Requested Would you like to Bring Up the ed0 interface right now? [ Yes ] No</screen> @@ -2422,7 +2422,7 @@ installation menus to retry whichever operations have failed. <sect2 id="gateway"> <title>Konfiguracja bramy</title> - <screen> User Confirmation Requested + <screen> User Confirmation Requested Do you want this machine to function as a network gateway? [ Yes ] No</screen> @@ -2512,13 +2512,13 @@ use the current settings. </indexterm> <screen> User Confirmation Requested - Do you want to have anonymous FTP access to this machine? + Do you want to have anonymous FTP access to this machine? Yes [ No ]</screen> <sect3 id="deny-anon"> <title>Wyłączenie anonimowego FTP</title> - + <para>Wybranie zaznaczonego domyślnie &gui.no; pozwoli na dostęp do komputera poprzez FTP tylko tym użytkownikom, którzy mają własne konta chronione hasłem.</para> @@ -2579,7 +2579,7 @@ Upload subdirectory: <para>Po wybraniu odpowiadających nam ustawień naciskamy <keycap>Enter</keycap>.</para> - <screen> User Confirmation Requested + <screen> User Confirmation Requested Create a welcome message file for anonymous FTP users? [ Yes ] No</screen> @@ -2628,7 +2628,7 @@ Upload subdirectory: <title>Serwer NFS</title> <screen> User Confirmation Requested - Do you want to configure this machine as an NFS server? + Do you want to configure this machine as an NFS server? Yes [ No ]</screen> @@ -2648,7 +2648,7 @@ Press [Enter] now to invoke an editor on /etc/exports [ OK ]</screen> <para>Naciskamy <keycap>Enter</keycap>. Zostanie uruchomiony - edytor tekstu, w którym będziemy mogli przygotować plik + edytor tekstu, w którym będziemy mogli przygotować plik <filename>exports</filename>.</para> <figure id="nfs-server-edit"> @@ -2679,7 +2679,7 @@ Press [Enter] now to invoke an editor on /etc/exports <para>Instalacja klienta NFS pozwoli naszemu komputerowi łączyć się z serwerami NFS.</para> <screen> User Confirmation Requested - Do you want to configure this machine as an NFS client? + Do you want to configure this machine as an NFS client? Yes [ No ]</screen> @@ -2790,7 +2790,7 @@ Press [Enter] now to invoke an editor on /etc/exports <screen> User Confirmation Requested Do you want to select a default security profile for this host (select - No for "medium" security)? + No for "medium" security)? [ Yes ] No</screen> @@ -2874,7 +2874,7 @@ To change any of these settings later, edit /etc/rc.conf <para>Kilka opcji służy do konfiguracji konsoli systemowej.</para> - <screen> User Confirmation Requested + <screen> User Confirmation Requested Would you like to customize your system console settings? [ Yes ] No</screen> @@ -2958,7 +2958,7 @@ To change any of these settings later, edit /etc/rc.conf Zjednoczonych. Rzeczywiste ustawienia będą zależeć od naszego położenia geograficznego.</para> - <screen> User Confirmation Requested + <screen> User Confirmation Requested Would you like to set this machine's time zone now? [ Yes ] No</screen> @@ -2968,7 +2968,7 @@ To change any of these settings later, edit /etc/rc.conf <screen> User Confirmation Requested Is this machine's CMOS clock set to UTC? If it is set to local time - or you don't know, please choose NIE here! + or you don't know, please choose NIE here! Yes [ No ]</screen> @@ -3015,7 +3015,7 @@ To change any of these settings later, edit /etc/rc.conf <para>Klawiszami kursora wybieramy właściwą strefę czasową i wciskamy <keycap>Enter</keycap>.</para> - <screen> Confirmation + <screen> Confirmation Does the abbreviation 'EDT' look reasonable? [ Yes ] No</screen> @@ -3029,7 +3029,7 @@ To change any of these settings later, edit /etc/rc.conf <sect2 id="linuxcomp"> <title>Kompatybilność z Linuksem</title> - <screen> User Confirmation Requested + <screen> User Confirmation Requested Would you like to enable Linux binary compatibility? [ Yes ] No</screen> @@ -3056,7 +3056,7 @@ To change any of these settings later, edit /etc/rc.conf przycisków. W naszym przykładzie konfigurujemy myszkę nie podłączoną przez USB (np. przez złącze PS/2 lub port COM)::</para> - <screen> User Confirmation Requested + <screen> User Confirmation Requested Does this system have a non-USB mouse attached to it? [ Yes ] No </screen> @@ -3416,7 +3416,7 @@ To change any of these settings later, edit /etc/rc.conf zajrzeć na stronę WWW <ulink url="http://www.xfree86.org/">&xfree86;</ulink>.</para> - <screen> User Confirmation Requested + <screen> User Confirmation Requested Would you like to configure your X server at this time? [ Yes ] No</screen> @@ -3464,9 +3464,9 @@ To change any of these settings later, edit /etc/rc.conf zapewne różnić od opcji pokazanych w przykładzie:</para> <screen> Message - You have configured and been running the mouse daemon. + You have configured and been running the mouse daemon. Choose "/dev/sysmouse" as the mouse port and "SysMouse" or - "MouseSystems" as the mouse protocol in the X configuration utility. + "MouseSystems" as the mouse protocol in the X configuration utility. [ OK ] @@ -3551,31 +3551,31 @@ Mouse device: /dev/sysmouse</screen> description of your keyboard. If nothing really matches, choose 1 (Generic 101-key PC) - 1 Generic 101-key PC - 2 Generic 102-key (Intl) PC - 3 Generic 104-key PC - 4 Generic 105-key (Intl) PC - 5 Dell 101-key PC - 6 Everex STEPnote - 7 Keytronic FlexPro - 8 Microsoft Natural - 9 Northgate OmniKey 101 - 10 Winbook Model XP5 - 11 Japanese 106-key - 12 PC-98xx Series - 13 Brazilian ABNT2 - 14 HP Internet - 15 Logitech iTouch - 16 Logitech Cordless Desktop Pro - 17 Logitech Internet Keyboard - 18 Logitech Internet Navigator Keyboard - 19 Compaq Internet - 20 Microsoft Natural Pro - 21 Genius Comfy KB-16M - 22 IBM Rapid Access - 23 IBM Rapid Access II - 24 Chicony Internet Keyboard - 25 Dell Internet Keyboard + 1 Generic 101-key PC + 2 Generic 102-key (Intl) PC + 3 Generic 104-key PC + 4 Generic 105-key (Intl) PC + 5 Dell 101-key PC + 6 Everex STEPnote + 7 Keytronic FlexPro + 8 Microsoft Natural + 9 Northgate OmniKey 101 + 10 Winbook Model XP5 + 11 Japanese 106-key + 12 PC-98xx Series + 13 Brazilian ABNT2 + 14 HP Internet + 15 Logitech iTouch + 16 Logitech Cordless Desktop Pro + 17 Logitech Internet Keyboard + 18 Logitech Internet Navigator Keyboard + 19 Compaq Internet + 20 Microsoft Natural Pro + 21 Genius Comfy KB-16M + 22 IBM Rapid Access + 23 IBM Rapid Access II + 24 Chicony Internet Keyboard + 25 Dell Internet Keyboard Enter a number to choose the keyboard. @@ -3585,24 +3585,24 @@ Enter a number to choose the keyboard. Please select the layout corresponding to your keyboard - 1 U.S. English - 2 U.S. English w/ ISO9995-3 - 3 U.S. English w/ deadkeys - 4 Albanian - 5 Arabic - 6 Armenian - 7 Azerbaidjani - 8 Belarusian - 9 Belgian - 10 Bengali - 11 Brazilian - 12 Bulgarian - 13 Burmese - 14 Canadian - 15 Croatian - 16 Czech - 17 Czech (qwerty) - 18 Danish + 1 U.S. English + 2 U.S. English w/ ISO9995-3 + 3 U.S. English w/ deadkeys + 4 Albanian + 5 Arabic + 6 Armenian + 7 Azerbaidjani + 8 Belarusian + 9 Belgian + 10 Bengali + 11 Brazilian + 12 Bulgarian + 13 Burmese + 14 Canadian + 15 Croatian + 16 Czech + 17 Czech (qwerty) + 18 Danish Enter a number to choose the country. Press enter for the next page @@ -3858,11 +3858,11 @@ Enter your choice: 4 Please specify which color depth you want to use by default: - 1 1 bit (monochrome) - 2 4 bits (16 colors) - 3 8 bits (256 colors) - 4 16 bits (65536 colors) - 5 24 bits (16 million colors) + 1 1 bit (monochrome) + 2 4 bits (16 colors) + 3 8 bits (256 colors) + 4 16 bits (65536 colors) + 5 24 bits (16 million colors) Enter a number to choose the default depth. @@ -3983,7 +3983,7 @@ failed. Would you like to try again? <screen> User Confirmation Requested The FreeBSD package collection is a collection of hundreds of ready-to-run applications, from text editors to games to WEB servers - and more. Would you like to browse the collection now? + and more. Would you like to browse the collection now? [ Yes ] No</screen> @@ -4083,7 +4083,7 @@ failed. Would you like to try again? Would you like to add any initial user accounts to the system? Adding at least one account for yourself at this stage is suggested since working as the "root" user is dangerous (it is easy to do things which - adversely affect the entire system). + adversely affect the entire system). [ Yes ] No</screen> @@ -4128,7 +4128,7 @@ failed. Would you like to try again? <varlistentry> <term>UID</term> - + <listitem> <para>Numer będący identyfikatorem użytkownika (wypełniany automatycznie, jeśli pole pozostanie puste).</para> @@ -4226,10 +4226,10 @@ failed. Would you like to try again? <title>Hasło użytkownika <username>root</username></title> <screen> Message - Now you must set the system manager's password. - This is the password you'll use to log in as "root". + Now you must set the system manager's password. + This is the password you'll use to log in as "root". - [ OK ] + [ OK ] [ Press enter to continue ]</screen> @@ -4241,8 +4241,8 @@ failed. Would you like to try again? się nam je zapomnieć. Zwróćmy uwagę, że w trakcie wpisywania hasła nie pojawią się żadne znaki, nawet gwiazdki.</para> - <screen>Changing local password for root. -New password : + <screen>Changing local password for root. +New password : Retype new password :</screen> <para>Po pomyślnym wprowadzeniu hasła przejdziemy do kolejnego etapu @@ -4260,7 +4260,7 @@ Retype new password :</screen> <screen> User Confirmation Requested Visit the general configuration menu for a chance to set any last - options? + options? Yes [ No ]</screen> @@ -4282,8 +4282,8 @@ Retype new password :</screen> zakończenia instalacji:</para> <screen> User Confirmation Requested - Are you sure you wish to exit? The system will reboot (be sure to - remove any floppies from the drives). + Are you sure you wish to exit? The system will reboot (be sure to + remove any floppies from the drives). [ Yes ] No</screen> @@ -4320,131 +4320,131 @@ Retype new password :</screen> <para>Typowe komunikaty pokazywane podczas uruchamiania systemu (pominięto informacje o wersji):</para> -<screen>Copyright (c) 1992-2002 The FreeBSD Project. +<screen>Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 - The Regents of the University of California. All rights reserved. + The Regents of the University of California. All rights reserved. Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 - Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX> - AMD Features=0x80000800<SYSCALL,3DNow!> -real memory = 268435456 (262144K bytes) -config> di sn0 -config> di lnc0 -config> di le0 -config> di ie0 -config> di fe0 -config> di cs0 -config> di bt0 -config> di aic0 -config> di aha0 -config> di adv0 -config> q + Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX> + AMD Features=0x80000800<SYSCALL,3DNow!> +real memory = 268435456 (262144K bytes) +config> di sn0 +config> di lnc0 +config> di le0 +config> di ie0 +config> di fe0 +config> di cs0 +config> di bt0 +config> di aic0 +config> di aha0 +config> di adv0 +config> q avail memory = 256311296 (250304K bytes) -Preloaded elf kernel "kernel" at 0xc0491000. -Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c. -md0: Malloc disk +Preloaded elf kernel "kernel" at 0xc0491000. +Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c. +md0: Malloc disk Using $PIR table, 4 entries at 0xc00fde60 -npx0: <math processor> on motherboard -npx0: INT 16 interface -pcib0: <Host to PCI bridge> on motherboard -pci0: <PCI bus> on pcib0 -pcib1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0 -pci1: <PCI bus> on pcib1 -pci1: <Matrox MGA G200 AGP graphics accelerator> at 0.0 irq 11 -isab0: <VIA 82C586 PCI-ISA bridge> at device 7.0 on pci0 -isa0: <ISA bus> on isab0 -atapci0: <VIA 82C586 ATA33 controller> port 0xe000-0xe00f at device 7.1 on pci0 -ata0: at 0x1f0 irq 14 on atapci0 -ata1: at 0x170 irq 15 on atapci0 -uhci0: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 10 at device 7.2 on pci0 -usb0: <VIA 83C572 USB controller> on uhci0 -usb0: USB revision 1.0 -uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 -uhub0: 2 ports with 2 removable, self powered -chip1: <VIA 82C586B ACPI interface> at device 7.3 on pci0 +npx0: <math processor> on motherboard +npx0: INT 16 interface +pcib0: <Host to PCI bridge> on motherboard +pci0: <PCI bus> on pcib0 +pcib1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0 +pci1: <PCI bus> on pcib1 +pci1: <Matrox MGA G200 AGP graphics accelerator> at 0.0 irq 11 +isab0: <VIA 82C586 PCI-ISA bridge> at device 7.0 on pci0 +isa0: <ISA bus> on isab0 +atapci0: <VIA 82C586 ATA33 controller> port 0xe000-0xe00f at device 7.1 on pci0 +ata0: at 0x1f0 irq 14 on atapci0 +ata1: at 0x170 irq 15 on atapci0 +uhci0: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 10 at device 7.2 on pci0 +usb0: <VIA 83C572 USB controller> on uhci0 +usb0: USB revision 1.0 +uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 +uhub0: 2 ports with 2 removable, self powered +chip1: <VIA 82C586B ACPI interface> at device 7.3 on pci0 ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xe800-0xe81f irq 9 at -device 10.0 on pci0 -ed0: address 52:54:05:de:73:1b, type NE2000 (16 bit) -isa0: too many dependant configs (8) -isa0: unexpected small tag 14 +device 10.0 on pci0 +ed0: address 52:54:05:de:73:1b, type NE2000 (16 bit) +isa0: too many dependant configs (8) +isa0: unexpected small tag 14 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 -fdc0: FIFO enabled, 8 bytes threshold -fd0: <1440-KB 3.5" drive> on fdc0 drive 0 -atkbdc0: <keyboard controller (i8042)> at port 0x60-0x64 on isa0 -atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 -kbd0 at atkbd0 -psm0: <PS/2 Mouse> irq 12 on atkbdc0 -psm0: model Generic PS/2 mouse, device ID 0 +fdc0: FIFO enabled, 8 bytes threshold +fd0: <1440-KB 3.5" drive> on fdc0 drive 0 +atkbdc0: <keyboard controller (i8042)> at port 0x60-0x64 on isa0 +atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 +kbd0 at atkbd0 +psm0: <PS/2 Mouse> irq 12 on atkbdc0 +psm0: model Generic PS/2 mouse, device ID 0 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 -sc0: <System console> at flags 0x1 on isa0 -sc0: VGA <16 virtual consoles, flags=0x300> -sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 -sio0: type 16550A -sio1 at port 0x2f8-0x2ff irq 3 on isa0 -sio1: type 16550A -ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 -ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode -ppc0: FIFO with 16/16/15 bytes threshold +sc0: <System console> at flags 0x1 on isa0 +sc0: VGA <16 virtual consoles, flags=0x300> +sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 +sio0: type 16550A +sio1 at port 0x2f8-0x2ff irq 3 on isa0 +sio1: type 16550A +ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 +ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode +ppc0: FIFO with 16/16/15 bytes threshold ppbus0: IEEE1284 device found /NIBBLE -Probing for PnP devices on ppbus0: -plip0: <PLIP network interface> on ppbus0 -lpt0: <Printer> on ppbus0 -lpt0: Interrupt-driven port +Probing for PnP devices on ppbus0: +plip0: <PLIP network interface> on ppbus0 +lpt0: <Printer> on ppbus0 +lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 -ad0: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata0-master using UDMA33 -ad2: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata1-master using UDMA33 -acd0: CDROM <DELTA OTC-H101/ST3 F/W by OIPD> at ata0-slave using PIO4 -Mounting root from ufs:/dev/ad0s1a -swapon: adding /dev/ad0s1b as swap device -Automatic boot in progress... -/dev/ad0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS +ad0: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata0-master using UDMA33 +ad2: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata1-master using UDMA33 +acd0: CDROM <DELTA OTC-H101/ST3 F/W by OIPD> at ata0-slave using PIO4 +Mounting root from ufs:/dev/ad0s1a +swapon: adding /dev/ad0s1b as swap device +Automatic boot in progress... +/dev/ad0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1a: clean, 48752 free (552 frags, 6025 blocks, 0.9% fragmentation) -/dev/ad0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS +/dev/ad0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1f: clean, 128997 free (21 frags, 16122 blocks, 0.0% fragmentation) /dev/ad0s1g: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1g: clean, 3036299 free (43175 frags, 374073 blocks, 1.3% fragmentation) -/dev/ad0s1e: filesystem CLEAN; SKIPPING CHECKS +/dev/ad0s1e: filesystem CLEAN; SKIPPING CHECKS /dev/ad0s1e: clean, 128193 free (17 frags, 16022 blocks, 0.0% fragmentation) -Doing initial network setup: hostname. +Doing initial network setup: hostname. ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::5054::5ff::fede:731b%ed0 prefixlen 64 tentative scopeid 0x1 ether 52:54:05:de:73:1b -lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 - inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 - inet6 ::1 prefixlen 128 - inet 127.0.0.1 netmask 0xff000000 +lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 + inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 + inet6 ::1 prefixlen 128 + inet 127.0.0.1 netmask 0xff000000 Additional routing options: IP gateway=TAK TCP keepalive=TAK -routing daemons:. -additional daemons: syslogd. -Doing additional network setup:. -Starting final network daemons: creating ssh RSA host key +routing daemons:. +additional daemons: syslogd. +Doing additional network setup:. +Starting final network daemons: creating ssh RSA host key Generating public/private rsa1 key pair. -Your identification has been saved in /etc/ssh/ssh_host_key. -Your public key has been saved in /etc/ssh/ssh_host_key.pub. -The key fingerprint is: +Your identification has been saved in /etc/ssh/ssh_host_key. +Your public key has been saved in /etc/ssh/ssh_host_key.pub. +The key fingerprint is: cd:76:89:16:69:0e:d0:6e:f8:66:d0:07:26:3c:7e:2d root@k6-2.example.com - creating ssh DSA host key + creating ssh DSA host key Generating public/private dsa key pair. -Your identification has been saved in /etc/ssh/ssh_host_dsa_key. -Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub. -The key fingerprint is: +Your identification has been saved in /etc/ssh/ssh_host_dsa_key. +Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub. +The key fingerprint is: f9:a1:a9:47:c4:ad:f9:8d:52:b8:b8:ff:8c:ad:2d:e6 root@k6-2.example.com. setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib -/usr/local/lib -a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout +/usr/local/lib +a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout starting standard daemons: inetd cron sshd usbd sendmail. -Initial rc.i386 initialization:. -rc.i386 configuring syscons: blank_time screensaver moused. -Additional ABI support: linux. -Local package initialization:. -Additional TCP options:. +Initial rc.i386 initialization:. +rc.i386 configuring syscons: blank_time screensaver moused. +Additional ABI support: linux. +Local package initialization:. +Additional TCP options:. FreeBSD/i386 (k6-2.example.com) (ttyv0) -login: rpratt +login: rpratt Password:</screen> <para>Generowanie kluczy RSA i DSA na niezbyt szybkich komputerach @@ -4493,7 +4493,7 @@ Password:</screen> zalogować się jako <username>root</username>. Następnie wydajemy polecenie <command>shutdown -h now</command>.</para> - <screen>The operating system has halted. + <screen>The operating system has halted. Please press any key to reboot.</screen> <para>Po takim wyłączeniu systemu i pojawieniu się komunikatu <quote>Please press any @@ -4621,7 +4621,7 @@ Please press any key to reboot.</screen> prawdopodobne, że będziemy chcieli zbudować <link linkend="kernelconfig">niestandardowe jądro</link>.</para> </sect2> - + <sect2> <title>Jak poradzić sobie z istniejącymi partycjami &ms-dos;</title> @@ -4840,7 +4840,7 @@ Please press any key to reboot.</screen> <primary><command>cu</command></primary> </indexterm> <para>Z komputerem łączymy się korzystając z - &man.cu.1;:</para> + &man.cu.1;:</para> <screen>&prompt.root; <userinput>cu -l /dev/cuaa0</userinput></screen> </step> @@ -4942,7 +4942,7 @@ Please press any key to reboot.</screen> <tbody> <row> <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-miniinst.iso</filename></entry> - + <entry>Wszystko, co jest potrzebne do zainstalowania FreeBSD.</entry> </row> @@ -4990,7 +4990,7 @@ Please press any key to reboot.</screen> <row> <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-miniinst.iso</filename></entry> - + <entry>Wszystko, co jest potrzebne do zainstalowania FreeBSD.</entry> </row> @@ -5025,7 +5025,7 @@ Please press any key to reboot.</screen> <para>Z obrazu ISO miniinst warto jest skorzystać, gdy mamy niedrogi dostęp do Internetu. Za jego pomocą możemy zainstalować - FreeBSD, natomiast niezależne oprogramowanie instalujemy przez + FreeBSD, natomiast niezależne oprogramowanie instalujemy przez Internet, przy pomocy systemu portów i pakietów (patrz: <xref linkend="ports"/>).</para> @@ -5062,7 +5062,7 @@ Please press any key to reboot.</screen> <sect2 id="install-ftp"> <title>Przygotowanie lokalnego serwera FTP z dyskiem FreeBSD</title> - + <indexterm> <primary>instalacja</primary> <secondary>sieć</secondary> @@ -5207,7 +5207,7 @@ Please press any key to reboot.</screen> <para>W przykładzie założyliśmy, że miejsce dla FreeBSD mamy na dysku <devicename>C:</devicename>, a napęd CDROM dostępny jest jako dysk <devicename>E:</devicename>.</para> - + <para>Jeśli nie dysponujemy napędem CDROM, pliki dystrybucyjne możemy pobrać z <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">ftp.FreeBSD.org</ulink>. diff --git a/pl_PL.ISO8859-2/books/handbook/introduction/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/introduction/chapter.sgml index 31775b9982..dfd602556b 100644 --- a/pl_PL.ISO8859-2/books/handbook/introduction/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/introduction/chapter.sgml @@ -60,7 +60,7 @@ <sect1 id="nutshell"> <title>Witamy w świecie FreeBSD!</title> - <indexterm><primary>4.4BSD-Lite</primary></indexterm> + <indexterm><primary>4.4BSD-Lite</primary></indexterm> <para>FreeBSD jest systemem operacyjnym bazującym na 4.4BSD-Lite, a przeznaczonym dla komputerów pracujących na platformach Intela (x86 i @@ -117,7 +117,7 @@ użytkowników, co z kolei pozwala na zabezpieczenie krytycznych zasobów systemowych przed nadużyciami.</para> </listitem> - + <listitem> <indexterm><primary>sieci TCP/IP</primary></indexterm> @@ -141,7 +141,7 @@ Innymi słowy, awaria danego programu w żaden sposób nie wpływa na działanie pozostałych.</para> </listitem> - + <listitem> <para>FreeBSD jest <emphasis>32-bitowym</emphasis> systemem operacyjnym (64-bitowym na platformach Alpha, &itanium;, AMD64 i &ultrasparc;) @@ -185,14 +185,14 @@ typu &unix;. FreeBSD posiada możliwość uruchamiania programów skompilowanych dla Linuksa, SCO, SVR4, BSDI i NetBSD.</para> </listitem> - + <listitem> <para>Tysiące aplikacji <emphasis>gotowych do pracy</emphasis>, dostępnych z kolekcji <emphasis>portów</emphasis> i <emphasis>pakietów</emphasis> FreeBSD. Czemu szukać w sieci, skoro wszystko można znaleźć właśnie tutaj?</para> </listitem> - + <listitem> <para>Tysiące dodatkowych i <emphasis>łatwych do przeniesienia</emphasis> programów dostępnych @@ -201,7 +201,7 @@ programów wymaga zaledwie kilku, jeśli w ogóle, zmian w kodzie aby poprawnie skompilować i uruchomić.</para> </listitem> - + <listitem> <indexterm><primary>pamięć wirtualna</primary></indexterm> @@ -211,7 +211,7 @@ dużym apetytem na pamięć, przy jednoczesnym zapewnieniu ciągłej interakcji systemu z użytkownikami.</para> </listitem> - + <listitem> <indexterm> <primary>Symmetric Multi-Processing (SMP)</primary> @@ -249,17 +249,17 @@ rozwiązań własnościowych i być skazanym na łaskę dostarczyciela systemu, kiedy można mieć prawdziwie otwarty system?</para> </listitem> - + <listitem> <para>Obszerną <emphasis>dokumentację</emphasis> dostępną w Internecie..</para> </listitem> - + <listitem> <para><emphasis>I wiele więcej!</emphasis></para> </listitem> </itemizedlist> - + <indexterm><primary>4.4BSD-Lite</primary></indexterm> <indexterm> <primary>Computer Systems Research Group (CSRG)</primary> @@ -294,7 +294,7 @@ projektów oraz zastosowań, co jest niemożliwe w przypadku wielu systemów komercyjnych. Oto krótka lista aplikacji, z którymi najczęściej używany jest FreeBSD:</para> - + <itemizedlist> <listitem> <para><emphasis>Usługi internetowe:</emphasis> doskonała obsługa @@ -306,7 +306,7 @@ <indexterm><primary>serwery FTP</primary></indexterm> <para>Serwery FTP</para> </listitem> - + <listitem> <indexterm><primary>serwery WWW</primary></indexterm> @@ -332,12 +332,12 @@ </indexterm> <para>Serwery poczty elektronicznej</para> </listitem> - + <listitem> <indexterm><primary>USENET</primary></indexterm> <para>Serwery USENET bądź systemy Forum</para> </listitem> - + <listitem> <para>I więcej...</para> </listitem> @@ -348,7 +348,7 @@ i rozwijać bazę sprzętową swojego przedsiębiorstwa aż do cztero-procesorowego Xeona z macierzą RAID.</para> </listitem> - + <listitem> <para><emphasis>Edukacja:</emphasis> jesteś studentem informatyki bądź pokrewnej dziedziny techniki? Nie ma @@ -360,7 +360,7 @@ głównym zainteresowaniem w komputerach jest aby zmusić je do pracy <emphasis>za nas</emphasis>!</para> </listitem> - + <listitem> <para><emphasis>Badania:</emphasis> oferując dostęp do kodu źródłowego całego systemu, FreeBSD stanowi doskonałą platformę @@ -370,7 +370,7 @@ pomagając zapomnieć im o problemach związanych ze specjalnymi warunkami licencyjnymi oraz ograniczeniami.</para> </listitem> - + <listitem> <indexterm><primary>ruter</primary></indexterm> <indexterm><primary>Serwer DNS</primary></indexterm> @@ -403,7 +403,7 @@ systemach <quote>bezdyskowych</quote> zmniejszając tym samym cenę komputerów służących za terminale.</para> </listitem> - + <listitem> <indexterm><primary>Kolekcja kompilatorów GNU</primary></indexterm> @@ -412,7 +412,7 @@ sławny kompilator oraz debugger GNU C/C++.</para> </listitem> </itemizedlist> - + <para>FreeBSD jest dostępny zarówno w postaci kodu źródłowego jak i skompilowanych binariów dostępnych na płytach CDROM, DVD i poprzez anonimowy serwer FTP. <xref linkend="mirrors"/> zawiera więcej informacji @@ -510,7 +510,7 @@ </sect2> </sect1> - + <sect1 id="history"> <title>O Projekcie FreeBSD</title> @@ -544,14 +544,14 @@ zestawu łat dla 386BSD</quote> (patchkit). Stworzony został przez trzech ostatnich koordynatorów zestawu: Nate'a Williamsa, Roda Grimesa i mnie.</para> - + <indexterm><primary>386BSD</primary></indexterm> <para>Naszym pierwotnym celem było przygotowanie migawki z rozwoju 386BSD, wprowadzającej szereg poprawek, których mechanizm zestawu łat nie był w stanie zrealizować. Niektórzy z czytających mogą pamiętać wczesną nazwę projektu <quote>386BSD 0.5</quote> bądź <quote>386BSD Interim</quote>.</para> - + <indexterm><primary>Jolitz, Bill</primary></indexterm> <para>386BSD był systemem operacyjnym Billa Jolitza, cierpiącym w tym okresie z powodu przeszło rocznego zastoju. W wyniku puchnięcia @@ -682,7 +682,7 @@ <ulink url="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/">serwera migawkowego</ulink> jak również na płytach CD.</para> </sect2> - + <sect2 id="goals"> <sect2info> <authorgroup> @@ -695,7 +695,7 @@ </sect2info> <title>Cele Projektu FreeBSD</title> - + <indexterm> <primary>FreeBSD Project</primary> <secondary>goals</secondary> @@ -730,7 +730,7 @@ dystrybuowanemu przy wykorzystaniu mniej restrykcyjnej licencji BSD.</para> </sect2> - + <sect2 id="development"> <sect2info> <authorgroup> @@ -743,7 +743,7 @@ </sect2info> <title>Model rozwoju FreeBSD</title> - + <indexterm> <primary>Projekt FreeBSD</primary> <secondary>model rozwoju</secondary> @@ -795,11 +795,11 @@ drzewa kodu źródłowego</link>.</para> </listitem> </varlistentry> - + <varlistentry> <term>Lista twórców<anchor id="development-committers"/></term> - + <listitem> <indexterm><primary>twórcy</primary></indexterm> @@ -815,7 +815,7 @@ e-mail bezpośrednio na &a.pl.committers.b;.</para> </listitem> </varlistentry> - + <varlistentry> <term>Główni projektanci FreeBSD<anchor id="development-core"/></term> @@ -852,7 +852,7 @@ </note> </listitem> </varlistentry> - + <varlistentry> <term>Zewnętrzni współpracownicy</term> @@ -867,7 +867,7 @@ FreeBSD jest subskrypcja &a.pl.hackers.d;. <xref linkend="eresources"/> zawiera więcej informacji o różnorodnych listach dyskusyjnych FreeBSD.</para> - + <para><citetitle><ulink url="&url.articles.contributors;/article.html">Lista współpracowników FreeBSD</ulink></citetitle> cały czas rośnie. Czemu by nie dołączyć @@ -880,7 +880,7 @@ </listitem> </varlistentry> </variablelist> - + <para>Reasumując, nasz model rozwoju zorganizowany jest jako niezależne, współcentryczne okręgi. Scentralizowany model ma za zadanie ułatwić <emphasis>użytkownikom</emphasis> FreeBSD śledzenie zmian w kodzie. @@ -888,7 +888,7 @@ Pragniemy dostarczać stabilny system operacyjny z dużą bazą łatwych do instalacji i wykorzystania <link linkend="ports">programów</link> — ten model doskonale się w tym spisuje.</para> - + <para>Jedyne o co prosimy tych, którzy mieliby wstąpić w szeregi projektantów FreeBSD, jest oddanie takie same jakie cechuje ich obecnych twórców.</para> @@ -967,7 +967,7 @@ url="file://localhost/usr/share/doc/handbook/index.html"><filename>/usr/share/doc/handbook/index.html</filename></ulink></para> </listitem> </varlistentry> - + <varlistentry> <term>FAQ FreeBSD (ang.)</term> @@ -977,7 +977,7 @@ </listitem> </varlistentry> </variablelist> - + <para>Główne i najczęściej aktualizowane wersje dokumentów dostępne są na stronie <ulink url="http://www.FreeBSD.org/"></ulink>.</para> diff --git a/pl_PL.ISO8859-2/books/handbook/kernelconfig/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/kernelconfig/chapter.sgml index 83731c10a7..ca798abfc2 100644 --- a/pl_PL.ISO8859-2/books/handbook/kernelconfig/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/kernelconfig/chapter.sgml @@ -201,7 +201,7 @@ <screen>&prompt.root; <userinput>cd /usr/src/sys/<replaceable>i386</replaceable>/conf</userinput> &prompt.root; <userinput>mkdir /root/kernels</userinput> -&prompt.root; <userinput>cp GENERIC /root/kernels/<replaceable>MYKERNEL</replaceable></userinput> +&prompt.root; <userinput>cp GENERIC /root/kernels/<replaceable>MYKERNEL</replaceable></userinput> &prompt.root; <userinput>ln -s /root/kernels/<replaceable>MYKERNEL</replaceable></userinput></screen> </tip> @@ -255,7 +255,7 @@ </para> </listitem> </itemizedlist> - + <indexterm> <primary><command>cvsup</command></primary> </indexterm> @@ -277,10 +277,10 @@ <procedure> <title>Procedura 1. Budowanie jądra w <quote>tradycyjny</quote> sposób.</title> - + <step> <para>By wygenerować kod źródłowy jądra, należy uruchomić &man.config.8;.</para> - + <screen>&prompt.root; <userinput>/usr/sbin/config <replaceable>MYKERNEL</replaceable></userinput></screen> </step> @@ -293,30 +293,30 @@ <step> <para>Skompilujmy jądro.</para> - + <screen>&prompt.root; <userinput>make depend</userinput> &prompt.root; <userinput>make</userinput></screen> </step> <step> <para>Zainstalujmy nowe jądro.</para> - + <screen>&prompt.root; <userinput>make install</userinput></screen> </step> </procedure> <procedure> <title>Procedura 2. Budowanie jądra w <quote>nowy</quote> sposób.</title> - + <step> <para>Wejdźmy do katalogu <filename>/usr/src</filename>.</para> - + <screen>&prompt.root; <userinput>cd /usr/src</userinput></screen> </step> <step> <para>Skompilujmy jądro.</para> - + <screen>&prompt.root; <userinput>make buildkernel KERNCONF=<replaceable>MYKERNEL</replaceable></userinput></screen> </step> @@ -326,7 +326,7 @@ <screen>&prompt.root; <userinput>make installkernel KERNCONF=<replaceable>MYKERNEL</replaceable></userinput></screen> </step> </procedure> - + <note> <para>Ta metoda kompilacji jądra wymaga wszystkich plików źródłowych. Jeśli zainstalowaliśmy jedynie źródła jądra, powinniśmy skorzystać z opisanej powyżej metody tradycyjnej.</para> @@ -348,7 +348,7 @@ <indexterm> <primary><filename class="directory">/boot/kernel.old</filename></primary> - </indexterm> + </indexterm> <para>Nowe jądro zostanie skopiowane do katalogu <filename class="directory">/boot/kernel</filename> jako <filename>/boot/kernel/kernel</filename> @@ -1166,7 +1166,7 @@ device fwe # Ethernet over FireWire (non-standard!)</programl Virtual Address, <acronym>KVA</acronym>). Z tego właśnie powodu Intel dodał w procesorach serii &pentium; Pro i późniejszych obsługę 36-bitowej przestrzeni adresów pamięci fizycznej.</para> - + <para>Rozszerzenie <acronym>PAE</acronym> (ang. Physical Address Extension) procesorów &intel; &pentium; Pro i późniejszych pozwala na instalację do 64 gigabajtów pamięci. &os; potrafi obsługiwać te rozszerzenie @@ -1178,7 +1178,7 @@ device fwe # Ethernet over FireWire (non-standard!)</programl <para>By aktywować obsługę <acronym>PAE</acronym> w jądrze, wystarczy dodać poniższy wiersz do pliku konfiguracyjnego naszego jądra:</para> - + <programlisting>options PAE</programlisting> <note> @@ -1190,7 +1190,7 @@ device fwe # Ethernet over FireWire (non-standard!)</programl </note> <para>Obsługa <acronym>PAE</acronym> we &os; posiada również pewne ograniczenia:</para> - + <itemizedlist> <listitem> <para>Dany proces nie ma dostępu do więcej jak 4 gigabajtów przestrzeni diff --git a/pl_PL.ISO8859-2/books/handbook/l10n/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/l10n/chapter.sgml index 8de3441f02..5635d7baf7 100644 --- a/pl_PL.ISO8859-2/books/handbook/l10n/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/l10n/chapter.sgml @@ -68,7 +68,7 @@ <primary>internationalization</primary> <see>localization</see> </indexterm> - <indexterm><primary>localization</primary></indexterm> + <indexterm><primary>localization</primary></indexterm> <para>Developers shortened internationalization into the term I18N, counting the number of letters between the first and the last @@ -169,7 +169,7 @@ usually do recognize 8-bit characters. Depending on the implementation, users may be required to compile an application with wide or multibyte characters support, or configure it correctly. - To be able to input and process wide or multibyte characters, the <ulink + To be able to input and process wide or multibyte characters, the <ulink url="&url.base;/ports/index.html">FreeBSD Ports Collection</ulink> has provided each language with different programs. Refer to the I18N documentation in the respective FreeBSD Port.</para> @@ -281,7 +281,7 @@ :lang=de_DE.ISO8859-1:</programlisting> <indexterm><primary>Traditional Chinese</primary><secondary>BIG-5 encoding</secondary></indexterm> - <para>Here is an example of a + <para>Here is an example of a <filename>.login_conf</filename> that sets the variables for Traditional Chinese in BIG-5 encoding. Notice the many more variables set because some software does not respect @@ -292,14 +292,14 @@ me:\ :lang=zh_TW.Big5:\ :lc_all=zh_TW.Big:\ - :lc_collate=zh_TW.Big5:\ + :lc_collate=zh_TW.Big5:\ :lc_ctype=zh_TW.Big5:\ :lc_messages=zh_TW.Big5:\ :lc_monetary=zh_TW.Big5:\ :lc_numeric=zh_TW.Big5:\ :lc_time=zh_TW.Big5:\ :charset=big5:\ - :xmodifiers="@im=xcin": #Setting the XIM Input Server</programlisting> + :xmodifiers="@im=xcin": #Setting the XIM Input Server</programlisting> <para>See <link linkend="adm-setup">Administrator Level Setup</link> and &man.login.conf.5; for more details.</para> @@ -364,7 +364,7 @@ me:\ <listitem> <para>An alternative variant is answering the specified - language each time that + language each time that <screen><prompt>Enter login class: default []: </prompt></screen> appears from &man.adduser.8;.</para> </listitem> @@ -471,7 +471,7 @@ font8x8=<replaceable>font_name</replaceable></programlisting> <programlisting>scrnmap=<replaceable>screenmap_name</replaceable> keymap=<replaceable>keymap_name</replaceable> keychange="<replaceable>fkey_number sequence</replaceable>"</programlisting> - + <para>The <replaceable>screenmap_name</replaceable> here is taken from the <filename>/usr/share/syscons/scrnmaps</filename> directory, without the <filename>.scm</filename> suffix. A @@ -681,7 +681,7 @@ keychange="<replaceable>fkey_number sequence</replaceable>"</programlisting> <indexterm> <primary><application>MySQL</application></primary> </indexterm> - <para>However, some applications such as + <para>However, some applications such as <application>MySQL</application> need to be have the <filename>Makefile</filename> configured with the specific charset. This is usually done in the @@ -689,7 +689,7 @@ keychange="<replaceable>fkey_number sequence</replaceable>"</programlisting> <application>configure</application> in the source.</para> </sect1> - <sect1 id="lang-setup"> + <sect1 id="lang-setup"> <title>Localizing FreeBSD to Specific Languages</title> <sect2 id="ru-localize"> diff --git a/pl_PL.ISO8859-2/books/handbook/linuxemu/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/linuxemu/chapter.sgml index 619f8f29ae..c98cc12435 100644 --- a/pl_PL.ISO8859-2/books/handbook/linuxemu/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/linuxemu/chapter.sgml @@ -709,7 +709,7 @@ FEATURE Maple maplelmg 2000.0831 permanent 1 XXXXXXXXXXXX \ <sect2> <title>Installing &matlab;</title> - <para>To install <application>&matlab;</application>, do the + <para>To install <application>&matlab;</application>, do the following:</para> <procedure> @@ -774,7 +774,7 @@ FEATURE Maple maplelmg 2000.0831 permanent 1 XXXXXXXXXXXX \ <screen>&prompt.root; <userinput>ln -s $MATLAB/etc/lmboot /usr/local/etc/lmboot_TMW</userinput> &prompt.root; <userinput>ln -s $MATLAB/etc/lmdown /usr/local/etc/lmdown_TMW</userinput></screen> </step> - + <step> <para>Create a startup file at <filename>/usr/local/etc/rc.d/flexlm.sh</filename>. The @@ -1282,7 +1282,7 @@ export PATH</programlisting> <entry>EXPORT3</entry> <entry>51010210</entry> <entry>IDES / DB-Export / Disc 3 of 6</entry> </row> - + <row> <entry>EXPORT4</entry> <entry>51010211</entry> <entry>IDES / DB-Export / Disc 4 of 6</entry> @@ -1899,14 +1899,14 @@ Shell: bash (/compat/linux/bin/bash)</programlisting> <para>and for <quote>&oracle; Administrator</quote>:</para> - <programlisting>Name: ora<replaceable>sid</replaceable> -Password: ****** + <programlisting>Name: ora<replaceable>sid</replaceable> +Password: ****** Fullname: Oracle Administrator <replaceable>SID</replaceable> -Uid: 1002 -Gid: 100 (dba) -Class: -Groups: dba -HOME: /oracle/<replaceable>sid</replaceable> +Uid: 1002 +Gid: 100 (dba) +Class: +Groups: dba +HOME: /oracle/<replaceable>sid</replaceable> Shell: bash (/compat/linux/bin/bash)</programlisting> <para>This should also include group @@ -1933,9 +1933,9 @@ Shell: bash (/compat/linux/bin/bash)</programlisting> &prompt.root; <userinput>chown <replaceable>sid</replaceable>adm:sapsys /compat/linux/usr/sap</userinput> &prompt.root; <userinput>chmod 775 /compat/linux/usr/sap</userinput></screen> - <para>Second we will create directories as user + <para>Second we will create directories as user <username>ora<replaceable>sid</replaceable></username>. These - will all be subdirectories of + will all be subdirectories of <filename>/oracle/<replaceable>SID</replaceable></filename>:</para> <screen>&prompt.root; <userinput>su - ora<replaceable>sid</replaceable></userinput> @@ -1961,7 +1961,7 @@ Shell: bash (/compat/linux/bin/bash)</programlisting> with exactly this name. Do not replace the <emphasis>x</emphasis> with some number or anything.</para></note> - <para>In the third step we create directories as user + <para>In the third step we create directories as user <username><replaceable>sid</replaceable>adm</username>:</para> <screen>&prompt.root; <userinput>su - <replaceable>sid</replaceable>adm</userinput> @@ -2046,12 +2046,12 @@ options SHMMAXPGS=262144 #max amount of shared mem. pages #options SHMMAXPGS=393216 #use this for the 46C inst.parameters options SHMMNI=256 #max number of shared memory ident if. options SHMSEG=100 #max shared mem.segs per process -options SYSVMSG #SYSV-style message queues -options MSGSEG=32767 #max num. of mes.segments in system +options SYSVMSG #SYSV-style message queues +options MSGSEG=32767 #max num. of mes.segments in system options MSGSSZ=32 #size of msg-seg. MUST be power of 2 options MSGMNB=65535 #max char. per message queue options MSGTQL=2046 #max amount of msgs in system -options SYSVSEM #SYSV-style semaphores +options SYSVSEM #SYSV-style semaphores options SEMMNU=256 #number of semaphore UNDO structures options SEMMNS=1024 #number of semaphores in system options SEMMNI=520 #number of semaphore identifiers @@ -2066,8 +2066,8 @@ options SEMUME=100 #number of UNDO keys</programlisting> number of shared memory pages.</para> <note><para>With the default installation of FreeBSD on &i386;, - leave <literal>MAXDSIZ</literal> and <literal>DFLDSIZ</literal> at 1 GB maximum. Otherwise, strange - errors like <errorname>ORA-27102: out of memory</errorname> and + leave <literal>MAXDSIZ</literal> and <literal>DFLDSIZ</literal> at 1 GB maximum. Otherwise, strange + errors like <errorname>ORA-27102: out of memory</errorname> and <errorname>Linux Error: 12: Cannot allocate memory</errorname> might happen.</para></note> </sect3> @@ -2086,10 +2086,10 @@ options SEMUME=100 #number of UNDO keys</programlisting> <programlisting>/oracle/<replaceable>SID</replaceable>/sapreorg/<replaceable>cd-name</replaceable></programlisting> - <para>where <replaceable>cd-name</replaceable> was one of <filename>KERNEL</filename>, + <para>where <replaceable>cd-name</replaceable> was one of <filename>KERNEL</filename>, <filename>RDBMS</filename>, <filename>EXPORT1</filename>, <filename>EXPORT2</filename>, <filename>EXPORT3</filename>, - <filename>EXPORT4</filename>, <filename>EXPORT5</filename> and + <filename>EXPORT4</filename>, <filename>EXPORT5</filename> and <filename>EXPORT6</filename> for the 4.6B/IDES installation, and <filename>KERNEL</filename>, <filename>RDBMS</filename>, <filename>DISK1</filename>, <filename>DISK2</filename>, @@ -2141,12 +2141,12 @@ options SEMUME=100 #number of UNDO keys</programlisting> only, not the fully qualified domain name. So either set the hostname accordingly, or set an alias with <command>alias hostname='hostname -s'</command> for - both <username>ora<replaceable>sid</replaceable></username> and + both <username>ora<replaceable>sid</replaceable></username> and <username><replaceable>sid</replaceable>adm</username> (and for <username>root</username> at least during installation - steps performed as <username>root</username>). It is also + steps performed as <username>root</username>). It is also possible to adjust the installed <filename>.profile</filename> and <filename>.login</filename> files of - both users that are installed during + both users that are installed during <application>&sap;</application> installation.</para> </sect3> @@ -2157,7 +2157,7 @@ options SEMUME=100 #number of UNDO keys</programlisting> <screen>&prompt.root; <userinput>export LD_LIBRARY_PATH=/oracle/IDS/lib:/sapmnt/IDS/exe:/oracle/805_32/lib</userinput></screen> - <para>Start <command>R3SETUP</command> as <username>root</username> from + <para>Start <command>R3SETUP</command> as <username>root</username> from installation directory:</para> <screen>&prompt.root; <userinput>cd /oracle/IDS/sapreorg/install</userinput> @@ -2329,13 +2329,13 @@ options SEMUME=100 #number of UNDO keys</programlisting> </tbody> </tgroup> </informaltable> - + <para>If you had not copied the CDs to the different locations, then the <application>&sap;</application> installer cannot find the CD needed (identified by the <filename>LABEL.ASC</filename> file on the CD) and would then ask you to insert and mount the CD and confirm or enter the mount path.</para> - + <para>The <filename>CENTRDB.R3S</filename> might not be error free. In our case, it requested EXPORT4 CD again but indicated the correct key (6_LOCATION, then 7_LOCATION @@ -2477,13 +2477,13 @@ options SEMUME=100 #number of UNDO keys</programlisting> </tbody> </tgroup> </informaltable> - + <para>So far, creation of users gives an error during installation in phases OSUSERDBSID_IND_ORA (for creating - user <username>ora<replaceable>sid</replaceable></username>) and - OSUSERSIDADM_IND_ORA (creating user + user <username>ora<replaceable>sid</replaceable></username>) and + OSUSERSIDADM_IND_ORA (creating user <username><replaceable>sid</replaceable>adm</username>).</para> - + <para>Apart from some problems mentioned below, everything should go straight through up to the point where the &oracle; database software needs to be installed.</para> @@ -2583,9 +2583,9 @@ options SEMUME=100 #number of UNDO keys</programlisting> <sect2 id="continuewithsapr4installation"> <title>Continue with &sap.r3; Installation</title> - <para>First check the environment settings of users + <para>First check the environment settings of users <username>idsamd</username> - (<replaceable>sid</replaceable>adm) and + (<replaceable>sid</replaceable>adm) and <username>oraids</username> (ora<replaceable>sid</replaceable>). They should now both have the files <filename>.profile</filename>, <filename>.login</filename> and <filename>.cshrc</filename> @@ -2599,7 +2599,7 @@ options SEMUME=100 #number of UNDO keys</programlisting> <para>Afterwards, <command>R3SETUP</command> can either be restarted or continued (depending on whether exit was chosen or not). <command>R3SETUP</command> then - creates the tablespaces and loads the data (for 46B IDES, from + creates the tablespaces and loads the data (for 46B IDES, from EXPORT1 to EXPORT6, for 46C from DISK1 to DISK4) with <command>R3load</command> into the database.</para> @@ -2645,7 +2645,7 @@ options SEMUME=100 #number of UNDO keys</programlisting> </tgroup> </informaltable> - <para>At this point We had a few problems with + <para>At this point We had a few problems with <command>dipgntab</command> during the 4.6B installation.</para> </sect3> @@ -2653,7 +2653,7 @@ options SEMUME=100 #number of UNDO keys</programlisting> <sect3 id="listener"> <title>Listener</title> - <para>Start the <application>&oracle;</application> Listener as user + <para>Start the <application>&oracle;</application> Listener as user <username>ora<replaceable>sid</replaceable></username> as follows:</para> <screen>&prompt.user; <userinput>umask 0; lsnrctl start</userinput></screen> @@ -2682,14 +2682,14 @@ options SEMUME=100 #number of UNDO keys</programlisting> <para>You have to request your <application>&sap.r3;</application> License Key. This is needed, as the temporary license that was installed during installation - is only valid for four weeks. First get the hardware key. Log - on as user <username>idsadm</username> and call + is only valid for four weeks. First get the hardware key. Log + on as user <username>idsadm</username> and call <command>saplicense</command>:</para> <screen>&prompt.root; <userinput>/sapmnt/IDS/exe/saplicense -get</userinput></screen> - <para>Calling <command>saplicense</command> without parameters gives - a list of options. Upon receiving the license key, it can be + <para>Calling <command>saplicense</command> without parameters gives + a list of options. Upon receiving the license key, it can be installed using:</para> <screen>&prompt.root; <userinput>/sapmnt/IDS/exe/saplicense -install</userinput></screen> @@ -2759,8 +2759,8 @@ LICENSE KEY = <replaceable>license key, 24 chars</replaceable></programlisti <title>Edit <filename>init<replaceable>sid</replaceable>.sap</filename> (<filename>initIDS.sap</filename>)</title> <para>The file <filename>/oracle/IDS/dbs/initIDS.sap</filename> - contains the <application>&sap;</application> backup profile. Here the size of the tape to - be used, type of compression and so on need to be defined. To + contains the <application>&sap;</application> backup profile. Here the size of the tape to + be used, type of compression and so on need to be defined. To get this running with <command>sapdba</command> / <command>brbackup</command>, we changed the following values:</para> @@ -2788,9 +2788,9 @@ tape_address_rew = /dev/sa0</programlisting> sets block size to 5120 Bytes. For DLT Tapes, HP recommends at least 32 K block size, so we used <option>--block-size=128</option> for 64 K. <option>--format=newc</option> is needed because we have inode numbers greater than - 65535. The last option <option>--quiet</option> is needed as otherwise + 65535. The last option <option>--quiet</option> is needed as otherwise <command>brbackup</command> - complains as soon as <command>cpio</command> outputs the + complains as soon as <command>cpio</command> outputs the numbers of blocks saved.</para> <para><varname>cpio_in_flags</varname>: Flags needed for @@ -2929,14 +2929,14 @@ tape_address_rew = /dev/sa0</programlisting> <note><para>At some stages, <command>R3SETUP</command> assumes that both database and <application>&sap;</application> processes are up and running (as those were steps it - already completed). Should errors occur and for example the - database could not be started, you have to start both database - and <application>&sap;</application> by hand after you fixed the errors and before starting + already completed). Should errors occur and for example the + database could not be started, you have to start both database + and <application>&sap;</application> by hand after you fixed the errors and before starting <command>R3SETUP</command> again.</para> - <para>Do not forget to also start the <application>&oracle;</application> listener again (as + <para>Do not forget to also start the <application>&oracle;</application> listener again (as <username>ora<replaceable>sid</replaceable></username> with <command>umask 0; lsnrctl start</command>) if it was also - stopped (for example due to a necessary reboot of the + stopped (for example due to a necessary reboot of the system).</para> </note> </sect3> @@ -2964,7 +2964,7 @@ STATUS=OK (had status ERROR) <title>OSUSERDBSID_IND_ORA during <command>R3SETUP</command></title> <para>Possibly <command>R3SETUP</command> also complains at this stage. The error - here is similar to the one in phase OSUSERSIDADM_IND_ORA. + here is similar to the one in phase OSUSERSIDADM_IND_ORA. Just edit the template file <command>R3SETUP</command> used at that time (<filename>CENTRDB.R3S</filename> (4.6B) or either @@ -3017,7 +3017,7 @@ Speicherzugriffsfehler</programlisting> <para>This behavior is due to <application>&sap.r3;</application> being unable to correctly assign a locale and also not being properly configured itself (missing entries in some database tables). To be able to connect - to <application>&sap;</application>, add the following entries to file + to <application>&sap;</application>, add the following entries to file <filename>DEFAULT.PFL</filename> (see Note 0043288):</para> <programlisting>abap/set_etct_env_at_new_mode = 0 @@ -3035,7 +3035,7 @@ rscp/TCP0B = TCP0B</programlisting> <sect3 id="ora-00001"> <title><errorcode>ORA-00001</errorcode></title> - <para>This error only happened with + <para>This error only happened with <application>&oracle; 8.1.7</application> on FreeBSD. The reason was that the <application>&oracle;</application> database could not initialize itself properly and crashed, leaving semaphores and shared memory on the @@ -3051,10 +3051,10 @@ rscp/TCP0B = TCP0B</programlisting> <para>This error happened with <application>&oracle; 8.1.7</application>. This error is reported if the database is started with the usual <command>startsap</command> script (for example - <command>startsap_majestix_00</command>) as user + <command>startsap_majestix_00</command>) as user <username>prdadm</username>.</para> - <para>A possible workaround is to start the database as user + <para>A possible workaround is to start the database as user <username>oraprd</username> instead with <command>svrmgrl</command>:</para> @@ -3082,14 +3082,14 @@ SVRMGR> <userinput>exit</userinput></screen> <para>This error happened whilst trying to use values for <literal>MAXDSIZ</literal> and <literal>DFLDSIZ</literal> - greater than 1 GB (1024x1024x1024). Additionally, we got + greater than 1 GB (1024x1024x1024). Additionally, we got <errorname>Linux Error 12: Cannot allocate memory</errorname>.</para> </sect3> <sect3 id="dipgntabindind"> <title>[DIPGNTAB_IND_IND] during <command>R3SETUP</command></title> - <para>In general, see &sap; Note 0130581 (<command>R3SETUP</command> step + <para>In general, see &sap; Note 0130581 (<command>R3SETUP</command> step <literal>DIPGNTAB</literal> terminates). During the IDES-specific installation, for some reason the installation process was not using the proper <application>&sap;</application> system name <quote>IDS</quote>, but @@ -3118,7 +3118,7 @@ drwxr-x--x 5 idsadm sapsys 512 May 5 11:35 IDS lrwxr-xr-x 1 root sapsys 7 May 5 11:35 SYS -> IDS/SYS drwxrwxr-x 2 idsadm sapsys 512 May 5 13:00 tmp drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans</screen> - + <para>We also found &sap; Notes (0029227 and 0008401) describing this behavior. We did not encounter any of these problems with the <application>&sap; 4.6C</application> installation.</para> @@ -3134,7 +3134,7 @@ drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans</screen> problem.</para> <para>If after looking through the logfiles this error is - indeed the correct one (check the &sap; Notes), you can set + indeed the correct one (check the &sap; Notes), you can set <literal>STATUS</literal> of the offending step from <literal>ERROR</literal> to <literal>OK</literal> (file <filename>CENTRDB.R3S</filename>) and restart <command>R3SETUP</command>. After installation, you have to execute the report @@ -3150,7 +3150,7 @@ drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans</screen> through the logfiles, that this error is not caused by some previous problems.</para> - <para>If you can confirm that &sap; Note 0162266 applies, just + <para>If you can confirm that &sap; Note 0162266 applies, just set <literal>STATUS</literal> of the offending step from <literal>ERROR</literal> to <literal>OK</literal> (file <filename>CENTRDB.R3S</filename>) and restart <command>R3SETUP</command>. After installation, you have to execute the report @@ -3168,13 +3168,13 @@ drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans</screen> if something goes wrong.</para> <para>To check whether the <application>&sap;</application> processes did start properly, - have a look at the process status with + have a look at the process status with <command>ps ax | grep <replaceable>SID</replaceable></command>, which will give you a list of all <application>&oracle;</application> and <application>&sap;</application> processes. If it looks like some processes are missing or if you cannot connect to the <application>&sap;</application> system, look at the corresponding logfiles which can be found at <filename>/usr/sap/<replaceable>SID</replaceable>/DVEBMGS<replaceable>nr</replaceable>/work/</filename>. - The files to look at are <filename>dev_ms</filename> and + The files to look at are <filename>dev_ms</filename> and <filename>dev_disp</filename>.</para> <para>Signal 31 happens here if the amount of shared memory used by @@ -3185,13 +3185,13 @@ drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans</screen> options SHMMAXPGS=393216 # smaller value sufficient for 46B: #options SHMMAXPGS=262144</programlisting> - + </sect3> <sect3 id="saposcolfails"> <title>Start of <command>saposcol</command> Failed</title> <para>There are some problems with the program <command>saposcol</command> (version 4.6D). - The <application>&sap;</application> system is using <command>saposcol</command> to collect data about the + The <application>&sap;</application> system is using <command>saposcol</command> to collect data about the system performance. This program is not needed to use the <application>&sap;</application> system, so this problem can be considered a minor one. The older versions (4.6B) does work, but does not collect all the data (many calls will diff --git a/pl_PL.ISO8859-2/books/handbook/mac/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/mac/chapter.sgml index 9f811d3aa0..24130901c3 100644 --- a/pl_PL.ISO8859-2/books/handbook/mac/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/mac/chapter.sgml @@ -701,7 +701,7 @@ test: biba/high</screen> implement the labeling feature, including the Biba, Lomac, <acronym>MLS</acronym> and <acronym>SEBSD</acronym> policies.</para> - + <para>In many cases, the <option>multilabel</option> may not need to be set at all. Consider the following situation and security model:</para> @@ -1661,7 +1661,7 @@ test: biba/low</screen> utilities. While other users would be grouped into other categories such as testers, designers, or just ordinary users and would only be permitted read access.</para> - + <para>With its natural security control, a lower integrity subject is unable to write to a higher integrity subject; a higher integrity subject cannot observe or read a lower integrity @@ -1824,7 +1824,7 @@ mac_seeotheruids_load="YES"</programlisting> <username>www</username> users into the insecure class:</para> <screen>&prompt.root; <userinput>pw usermod nagios -L insecure</userinput></screen> - <screen>&prompt.root; <userinput>pw usermod www -L insecure</userinput></screen> + <screen>&prompt.root; <userinput>pw usermod www -L insecure</userinput></screen> </sect2> <sect2> diff --git a/pl_PL.ISO8859-2/books/handbook/mail/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/mail/chapter.sgml index a19ca3eb14..dda5064a87 100644 --- a/pl_PL.ISO8859-2/books/handbook/mail/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/mail/chapter.sgml @@ -254,7 +254,7 @@ FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org</screen> Once mail has been stored, it may either be read locally using applications such as &man.mail.1; or <application>mutt</application>, or remotely accessed and - collected using protocols such as + collected using protocols such as <acronym>POP</acronym> or <acronym>IMAP</acronym>. This means that should you only wish to read mail locally, you are not required to install a @@ -760,7 +760,7 @@ postmaster@example.com postmaster@noc.example.net <para>in <filename>/etc/rc.conf</filename>. However, if incoming mail is disabled, local delivery will still - function. More information on + function. More information on <application>sendmail</application>'s startup options is available from the &man.rc.sendmail.8; manual page.</para> </sect3> diff --git a/pl_PL.ISO8859-2/books/handbook/mirrors/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/mirrors/chapter.sgml index 6a4c1fd772..5c902ef7aa 100644 --- a/pl_PL.ISO8859-2/books/handbook/mirrors/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/mirrors/chapter.sgml @@ -493,7 +493,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host <itemizedlist> <listitem> - <para><ulink + <para><ulink url="http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/cvs/">CVS Tutorial</ulink> from Cal Poly.</para> </listitem> @@ -510,8 +510,8 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host </itemizedlist> </sect2> </sect1> - - + + <sect1 id="ctm"> <title>Using CTM</title> @@ -562,7 +562,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host <para>You will need two things: The <application>CTM</application> program, and the initial deltas to feed it (to get up to <quote>current</quote> levels).</para> - + <para>The <application>CTM</application> program has been part of FreeBSD ever since version 2.0 was released, and lives in <filename>/usr/src/usr.sbin/ctm</filename> if you have a copy @@ -792,7 +792,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host <sect2 id="mirrors-ctm"> <title>CTM Mirrors</title> - + <para><link linkend="ctm">CTM</link>/FreeBSD is available via anonymous FTP from the following mirror sites. If you choose to obtain <application>CTM</application> via anonymous FTP, please try to use a site near you.</para> @@ -853,17 +853,17 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host <sect1 id="cvsup"> <title>Using CVSup</title> - + <sect2 id="cvsup-intro"> <title>Introduction</title> - + <para><application>CVSup</application> is a software package for distributing and updating source trees from a master CVS repository on a remote server host. The FreeBSD sources are maintained in a CVS repository on a central development machine in California. With <application>CVSup</application>, FreeBSD users can easily keep their own source trees up to date.</para> - + <para><application>CVSup</application> uses the so-called <emphasis>pull</emphasis> model of updating. Under the pull model, each client asks the server for updates, if and when they @@ -873,7 +873,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host run the <application>CVSup</application> client manually to get an update, or they must set up a <command>cron</command> job to run it automatically on a regular basis.</para> - + <para>The term <application>CVSup</application>, capitalized just so, refers to the entire software package. Its main components are the client <command>cvsup</command> which runs on each @@ -894,7 +894,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host <sect2 id="cvsup-install"> <title>Installation</title> - + <para>The easiest way to install <application>CVSup</application> is to use the precompiled <filename role="package">net/cvsup</filename> package from the FreeBSD <link linkend="ports">packages collection</link>. @@ -917,37 +917,37 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host <sect2 id="cvsup-config"> <title>CVSup Configuration</title> - + <para><application>CVSup</application>'s operation is controlled by a configuration file called the <filename>supfile</filename>. There are some sample <filename>supfiles</filename> in the directory <ulink type="html" url="file://localhost/usr/share/examples/cvsup/"><filename>/usr/share/examples/cvsup/</filename></ulink>.</para> - + <para>The information in a <filename>supfile</filename> answers the following questions for <application>CVSup</application>:</para> - + <itemizedlist> <listitem> <para><link linkend="cvsup-config-files">Which files do you want to receive?</link></para> </listitem> - + <listitem> <para><link linkend="cvsup-config-vers">Which versions of them do you want?</link></para> </listitem> - + <listitem> <para><link linkend="cvsup-config-where">Where do you want to get them from?</link></para> </listitem> - + <listitem> <para><link linkend="cvsup-config-dest">Where do you want to put them on your own machine?</link></para> </listitem> - + <listitem> <para><link linkend="cvsup-config-status">Where do you want to put your status files?</link></para> @@ -963,7 +963,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host begin with <literal>#</literal> and extend to the end of the line. Lines that are blank and lines that contain only comments are ignored.</para> - + <para>Each remaining line describes a set of files that the user wishes to receive. The line begins with the name of a <quote>collection</quote>, a logical grouping of files defined by @@ -977,7 +977,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host keyword, but the keyword is followed without intervening white space by <literal>=</literal> and a second word. For example, <literal>release=cvs</literal> is a value field.</para> - + <para>A <filename>supfile</filename> typically specifies more than one collection to receive. One way to structure a <filename>supfile</filename> is to specify all of the relevant @@ -1004,7 +1004,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host <listitem> <para><anchor id="cvsup-config-files"/>Which files do you want to receive?</para> - + <para>The files available via <application>CVSup</application> are organized into named groups called <quote>collections</quote>. The collections that are @@ -1034,7 +1034,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host specify which one of them you want using the <literal>tag=</literal> and <option>date=</option> value fields.</para> - + <warning> <para>Be very careful to specify any <literal>tag=</literal> fields correctly. Some tags are valid only for certain @@ -1055,7 +1055,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host a branch tag does not refer to a specific revision, it may mean something different tomorrow than it means today.</para> - + <para><xref linkend="cvs-tags"/> contains branch tags that users might be interested in. When specifying a tag in <application>CVSup</application>'s configuration file, it @@ -1085,7 +1085,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host <para>For our example, we wish to receive FreeBSD-CURRENT. We add this line at the beginning of our <filename>supfile</filename>:</para> - + <programlisting>*default tag=.</programlisting> <para>There is an important special case that comes into play @@ -1104,7 +1104,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host <listitem> <para><anchor id="cvsup-config-where"/>Where do you want to get them from?</para> - + <para>We use the <literal>host=</literal> field to tell <command>cvsup</command> where to obtain its updates. Any of the <link linkend="cvsup-mirrors">CVSup mirror @@ -1114,7 +1114,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host <hostid role="fqdn">cvsup99.FreeBSD.org</hostid>:</para> <programlisting>*default host=cvsup99.FreeBSD.org</programlisting> - + <para>You will need to change the host to one that actually exists before running <application>CVSup</application>. On any particular run of @@ -1122,11 +1122,11 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host on the command line, with <option>-h <replaceable>hostname</replaceable></option>.</para> </listitem> - + <listitem> <para><anchor id="cvsup-config-dest"/>Where do you want to put them on your own machine?</para> - + <para>The <literal>prefix=</literal> field tells <command>cvsup</command> where to put the files it receives. In this example, we will put the source files directly into @@ -1134,7 +1134,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host <filename>src</filename> directory is already implicit in the collections we have chosen to receive, so this is the correct specification:</para> - + <programlisting>*default prefix=/usr</programlisting> </listitem> @@ -1161,7 +1161,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host <listitem> <para>Miscellaneous <filename>supfile</filename> settings:</para> - + <para>There is one more line of boiler plate that normally needs to be present in the <filename>supfile</filename>:</para> @@ -1173,7 +1173,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host repository. This is virtually always the case, but there are other possibilities which are beyond the scope of this discussion.</para> - + <para><literal>delete</literal> gives <application>CVSup</application> permission to delete files. You should always specify this, so that @@ -1182,7 +1182,7 @@ Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known host careful to delete only those files for which it is responsible. Any extra files you happen to have will be left strictly alone.</para> - + <para><literal>use-rel-suffix</literal> is ... arcane. If you really want to know about it, see the &man.cvsup.1; manual page. Otherwise, just specify it and do not worry about @@ -1244,7 +1244,7 @@ src-all</programlisting> <filename><replaceable>base</replaceable>/sup/</filename>. <replaceable>base</replaceable> is defined in your <filename>supfile</filename>; our defined <replaceable>base</replaceable> is - <filename>/var/db</filename>, + <filename>/var/db</filename>, which means that by default the <filename>refuse</filename> file is <filename>/var/db/sup/refuse</filename>.</para> @@ -1283,25 +1283,25 @@ doc/zh_*</screen> to download files that they will never use. For more information on <filename>refuse</filename> files and other neat features of <application>CVSup</application>, please view its - manual page.</para> + manual page.</para> </sect3> </sect2> - + <sect2> <title>Running <application>CVSup</application></title> - + <para>You are now ready to try an update. The command line for doing this is quite simple:</para> <screen>&prompt.root; <userinput>cvsup <replaceable>supfile</replaceable></userinput></screen> <para>where <filename><replaceable>supfile</replaceable></filename> - is of course the name of the <filename>supfile</filename> you have just created. + is of course the name of the <filename>supfile</filename> you have just created. Assuming you are running under X11, <command>cvsup</command> will display a GUI window with some buttons to do the usual things. Press the <guibutton>go</guibutton> button, and watch it run.</para> - + <para>Since you are updating your actual <filename>/usr/src</filename> tree in this example, you will need to run the program as <username>root</username> so that @@ -1315,7 +1315,7 @@ doc/zh_*</screen> <screen>&prompt.root; <userinput>mkdir /var/tmp/dest</userinput> &prompt.root; <userinput>cvsup supfile /var/tmp/dest</userinput></screen> - + <para>The directory you specify will be used as the destination directory for all file updates. <application>CVSup</application> will examine your usual files @@ -1328,25 +1328,25 @@ doc/zh_*</screen> directory. As long as you have read access to <filename>/usr/src</filename>, you do not even need to be <username>root</username> to perform this kind of trial run.</para> - + <para>If you are not running X11 or if you just do not like GUIs, you should add a couple of options to the command line when you run <command>cvsup</command>:</para> - + <screen>&prompt.root; <userinput>cvsup -g -L 2 <replaceable>supfile</replaceable></userinput></screen> - + <para>The <option>-g</option> tells <application>CVSup</application> not to use its GUI. This is automatic if you are not running X11, but otherwise you have to specify it.</para> - - <para>The <option>-L 2</option> tells + + <para>The <option>-L 2</option> tells <application>CVSup</application> to print out the details of all the file updates it is doing. There are three levels of verbosity, from <option>-L 0</option> to <option>-L 2</option>. The default is 0, which means total silence except for error messages.</para> - + <para>There are plenty of other options available. For a brief list of them, type <command>cvsup -H</command>. For more detailed descriptions, see the manual page.</para> @@ -1360,7 +1360,7 @@ doc/zh_*</screen> <sect2 id="cvsup-collec"> <title><application>CVSup</application> File Collections</title> - + <para>The file collections available via <application>CVSup</application> are organized hierarchically. There are a few large collections, and they are divided into @@ -1368,31 +1368,31 @@ doc/zh_*</screen> equivalent to receiving each of its sub-collections. The hierarchical relationships among collections are reflected by the use of indentation in the list below.</para> - + <para>The most commonly used collections are <literal>src-all</literal>, and <literal>ports-all</literal>. The other collections are used only by small groups of people for specialized purposes, and some mirror sites may not carry all of them.</para> - + <variablelist> <varlistentry> <term><literal>cvs-all release=cvs</literal></term> - + <listitem> <para>The main FreeBSD CVS repository, including the cryptography code.</para> - + <variablelist> <varlistentry> <term><literal>distrib release=cvs</literal></term> - + <listitem> <para>Files related to the distribution and mirroring of FreeBSD.</para> </listitem> </varlistentry> - + <varlistentry> <term><literal>doc-all release=cvs</literal></term> <listitem> @@ -1431,7 +1431,7 @@ doc/zh_*</screen> <important id="cvsup-collec-index-warn"> <para>If you are going to be building your own local copy of <filename>ports/INDEX</filename>, you - <emphasis>must</emphasis> accept + <emphasis>must</emphasis> accept <literal>ports-all</literal> (the whole ports tree). Building <filename>ports/INDEX</filename> with a partial tree is not supported. See the @@ -1461,7 +1461,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-archivers release=cvs</literal></term> - + <listitem> <para>Archiving tools.</para> </listitem> @@ -1470,7 +1470,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-astro release=cvs</literal></term> - + <listitem> <para>Astronomical ports.</para> </listitem> @@ -1479,7 +1479,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-audio release=cvs</literal></term> - + <listitem> <para>Sound support.</para> </listitem> @@ -1488,7 +1488,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-base release=cvs</literal></term> - + <listitem> <para>The Ports Collection build infrastructure - various files located in the @@ -1510,7 +1510,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-benchmarks release=cvs</literal></term> - + <listitem> <para>Benchmarks.</para> </listitem> @@ -1528,7 +1528,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-cad release=cvs</literal></term> - + <listitem> <para>Computer aided design tools.</para> </listitem> @@ -1537,7 +1537,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-chinese release=cvs</literal></term> - + <listitem> <para>Chinese language support.</para> </listitem> @@ -1546,7 +1546,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-comms release=cvs</literal></term> - + <listitem> <para>Communication software.</para> </listitem> @@ -1555,7 +1555,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-converters release=cvs</literal></term> - + <listitem> <para>character code converters.</para> </listitem> @@ -1564,16 +1564,16 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-databases release=cvs</literal></term> - + <listitem> <para>Databases.</para> </listitem> </varlistentry> - + <varlistentry> <term><literal>ports-deskutils release=cvs</literal></term> - + <listitem> <para>Things that used to be on the desktop before computers were invented.</para> @@ -1597,7 +1597,7 @@ doc/zh_*</screen> <para>DNS related software.</para> </listitem> </varlistentry> - + <varlistentry> <term><literal>ports-editors release=cvs</literal></term> @@ -1610,7 +1610,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-emulators release=cvs</literal></term> - + <listitem> <para>Emulators for other operating systems.</para> @@ -1620,7 +1620,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-finance release=cvs</literal></term> - + <listitem> <para>Monetary, financial and related applications.</para> </listitem> @@ -1629,7 +1629,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-ftp release=cvs</literal></term> - + <listitem> <para>FTP client and server utilities.</para> </listitem> @@ -1638,16 +1638,16 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-games release=cvs</literal></term> - + <listitem> <para>Games.</para> </listitem> </varlistentry> - + <varlistentry> <term><literal>ports-german release=cvs</literal></term> - + <listitem> <para>German language support.</para> </listitem> @@ -1674,7 +1674,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-hungarian release=cvs</literal></term> - + <listitem> <para>Hungarian language support.</para> </listitem> @@ -1697,7 +1697,7 @@ doc/zh_*</screen> <para>Japanese language support.</para> </listitem> </varlistentry> - + <varlistentry> <term><literal>ports-java release=cvs</literal></term> @@ -1773,7 +1773,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-net release=cvs</literal></term> - + <listitem> <para>Networking software.</para> </listitem> @@ -1809,16 +1809,16 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-news release=cvs</literal></term> - + <listitem> <para>USENET news software.</para> </listitem> </varlistentry> - + <varlistentry> <term><literal>ports-palm release=cvs</literal></term> - + <listitem> <para>Software support for <trademark class="trade">Palm</trademark> series.</para> @@ -1828,16 +1828,16 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-polish release=cvs</literal></term> - + <listitem> <para>Polish language support.</para> </listitem> </varlistentry> - + <varlistentry> <term><literal>ports-portuguese release=cvs</literal></term> - + <listitem> <para>Portuguese language support.</para> </listitem> @@ -1846,7 +1846,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-print release=cvs</literal></term> - + <listitem> <para>Printing software.</para> </listitem> @@ -1855,7 +1855,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-russian release=cvs</literal></term> - + <listitem> <para>Russian language support.</para> </listitem> @@ -1873,7 +1873,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-security release=cvs</literal></term> - + <listitem> <para>Security utilities.</para> </listitem> @@ -1882,7 +1882,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-shells release=cvs</literal></term> - + <listitem> <para>Command line shells.</para> </listitem> @@ -1891,7 +1891,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-sysutils release=cvs</literal></term> - + <listitem> <para>System utilities.</para> </listitem> @@ -1900,7 +1900,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-textproc release=cvs</literal></term> - + <listitem> <para>text processing utilities (does not include desktop publishing).</para> @@ -1919,7 +1919,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-vietnamese release=cvs</literal></term> - + <listitem> <para>Vietnamese language support.</para> </listitem> @@ -1928,7 +1928,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-www release=cvs</literal></term> - + <listitem> <para>Software related to the World Wide Web.</para> @@ -1938,7 +1938,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-x11 release=cvs</literal></term> - + <listitem> <para>Ports to support the X window system.</para> @@ -1948,7 +1948,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-x11-clocks release=cvs</literal></term> - + <listitem> <para>X11 clocks.</para> </listitem> @@ -1966,7 +1966,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-x11-fonts release=cvs</literal></term> - + <listitem> <para>X11 fonts and font utilities.</para> </listitem> @@ -1984,7 +1984,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-x11-servers release=cvs</literal></term> - + <listitem> <para>X11 servers.</para> </listitem> @@ -2002,7 +2002,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>ports-x11-wm release=cvs</literal></term> - + <listitem> <para>X11 window managers.</para> </listitem> @@ -2020,7 +2020,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>src-all release=cvs</literal></term> - + <listitem> <para>The main FreeBSD sources, including the cryptography code.</para> @@ -2071,7 +2071,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>src-eBones release=cvs</literal></term> - + <listitem> <para>Kerberos and DES (<filename>/usr/src/eBones</filename>). Not @@ -2092,7 +2092,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>src-games release=cvs</literal></term> - + <listitem> <para>Games (<filename>/usr/src/games</filename>).</para> @@ -2112,7 +2112,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>src-include release=cvs</literal></term> - + <listitem> <para>Header files (<filename>/usr/src/include</filename>).</para> @@ -2122,7 +2122,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>src-kerberos5 release=cvs</literal></term> - + <listitem> <para>Kerberos5 security package (<filename>/usr/src/kerberos5</filename>).</para> @@ -2132,7 +2132,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>src-kerberosIV release=cvs</literal></term> - + <listitem> <para>KerberosIV security package (<filename>/usr/src/kerberosIV</filename>).</para> @@ -2159,11 +2159,11 @@ doc/zh_*</screen> (<filename>/usr/src/libexec</filename>).</para> </listitem> </varlistentry> - + <varlistentry> <term><literal>src-release release=cvs</literal></term> - + <listitem> <para>Files required to produce a FreeBSD release @@ -2179,7 +2179,7 @@ doc/zh_*</screen> (<filename>/usr/src/sbin</filename>).</para> </listitem> </varlistentry> - + <varlistentry> <term><literal>src-secure release=cvs</literal></term> @@ -2214,7 +2214,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>src-sys-crypto release=cvs</literal></term> - + <listitem> <para>Kernel cryptography code (<filename>/usr/src/sys/crypto</filename>).</para> @@ -2245,7 +2245,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>src-usrsbin release=cvs</literal></term> - + <listitem> <para>System utilities (<filename>/usr/src/usr.sbin</filename>).</para> @@ -2254,10 +2254,10 @@ doc/zh_*</screen> </variablelist> </listitem> </varlistentry> - + <varlistentry> <term><literal>www release=cvs</literal></term> - + <listitem> <para>The sources for the FreeBSD WWW site.</para> </listitem> @@ -2265,12 +2265,12 @@ doc/zh_*</screen> </variablelist> </listitem> </varlistentry> - + <varlistentry> <term><literal>distrib release=self</literal></term> <listitem> - <para>The <application>CVSup</application> server's own + <para>The <application>CVSup</application> server's own configuration files. Used by <application>CVSup</application> mirror sites.</para> </listitem> @@ -2286,7 +2286,7 @@ doc/zh_*</screen> <varlistentry> <term><literal>mail-archive release=current</literal></term> - + <listitem> <para>FreeBSD mailing list archive.</para> </listitem> @@ -2306,7 +2306,7 @@ doc/zh_*</screen> <sect2> <title>For More Information</title> - <para>For the <application>CVSup</application> FAQ and other + <para>For the <application>CVSup</application> FAQ and other information about <application>CVSup</application>, see <ulink url="http://www.polstra.com/projects/freeware/CVSup/">The CVSup Home Page</ulink>.</para> @@ -2315,7 +2315,7 @@ doc/zh_*</screen> <application>CVSup</application> takes place on the &a.hackers;. New versions of the software are announced there, as well as on the &a.announce;.</para> - + <para>Questions and bug reports should be addressed to the author of the program at <email>cvsup-bugs@polstra.com</email>.</para> </sect2> @@ -2329,7 +2329,7 @@ doc/zh_*</screen> &chap.mirrors.cvsup.inc; </sect2> </sect1> - + <sect1 id="portsnap"> <title>Using Portsnap</title> @@ -2586,7 +2586,7 @@ doc/zh_*</screen> <term>RELENG_5_5</term> <listitem> - <para>The release branch for FreeBSD-5.5, used only + <para>The release branch for FreeBSD-5.5, used only for security advisories and other critical fixes.</para> </listitem> </varlistentry> @@ -2595,7 +2595,7 @@ doc/zh_*</screen> <term>RELENG_5_4</term> <listitem> - <para>The release branch for FreeBSD-5.4, used only + <para>The release branch for FreeBSD-5.4, used only for security advisories and other critical fixes.</para> </listitem> </varlistentry> @@ -2604,7 +2604,7 @@ doc/zh_*</screen> <term>RELENG_5_3</term> <listitem> - <para>The release branch for FreeBSD-5.3, used only + <para>The release branch for FreeBSD-5.3, used only for security advisories and other critical fixes.</para> </listitem> </varlistentry> @@ -2613,7 +2613,7 @@ doc/zh_*</screen> <term>RELENG_5_2</term> <listitem> - <para>The release branch for FreeBSD-5.2 and FreeBSD-5.2.1, used only + <para>The release branch for FreeBSD-5.2 and FreeBSD-5.2.1, used only for security advisories and other critical fixes.</para> </listitem> </varlistentry> @@ -2622,7 +2622,7 @@ doc/zh_*</screen> <term>RELENG_5_1</term> <listitem> - <para>The release branch for FreeBSD-5.1, used only + <para>The release branch for FreeBSD-5.1, used only for security advisories and other critical fixes.</para> </listitem> </varlistentry> @@ -2631,7 +2631,7 @@ doc/zh_*</screen> <term>RELENG_5_0</term> <listitem> - <para>The release branch for FreeBSD-5.0, used only + <para>The release branch for FreeBSD-5.0, used only for security advisories and other critical fixes.</para> </listitem> </varlistentry> @@ -2658,7 +2658,7 @@ doc/zh_*</screen> <term>RELENG_4_10</term> <listitem> - <para>The release branch for FreeBSD-4.10, used only + <para>The release branch for FreeBSD-4.10, used only for security advisories and other critical fixes.</para> </listitem> </varlistentry> @@ -2667,7 +2667,7 @@ doc/zh_*</screen> <term>RELENG_4_9</term> <listitem> - <para>The release branch for FreeBSD-4.9, used only + <para>The release branch for FreeBSD-4.9, used only for security advisories and other critical fixes.</para> </listitem> </varlistentry> @@ -2676,7 +2676,7 @@ doc/zh_*</screen> <term>RELENG_4_8</term> <listitem> - <para>The release branch for FreeBSD-4.8, used only + <para>The release branch for FreeBSD-4.8, used only for security advisories and other critical fixes.</para> </listitem> </varlistentry> @@ -2685,7 +2685,7 @@ doc/zh_*</screen> <term>RELENG_4_7</term> <listitem> - <para>The release branch for FreeBSD-4.7, used only + <para>The release branch for FreeBSD-4.7, used only for security advisories and other critical fixes.</para> </listitem> </varlistentry> @@ -2957,7 +2957,7 @@ doc/zh_*</screen> <para>FreeBSD 4.0</para> </listitem> </varlistentry> - + <varlistentry> <term>RELENG_3_5_0_RELEASE</term> @@ -3097,7 +3097,7 @@ doc/zh_*</screen> much the same way as the &man.rcp.1; command, but has more options and uses the rsync remote-update protocol which transfers only the differences between two sets of files, - thus greatly speeding up the synchronization over the network. + thus greatly speeding up the synchronization over the network. This is most useful if you are a mirror site for the FreeBSD FTP server, or the CVS repository. The <application>rsync</application> suite is available for many @@ -3179,7 +3179,7 @@ doc/zh_*</screen> <listitem><para>FreeBSD: The master archive of the FreeBSD FTP server.</para></listitem> <listitem><para>acl: The FreeBSD master ACL - list.</para></listitem> + list.</para></listitem> </itemizedlist> <para>rsync://ftp13.FreeBSD.org/</para> @@ -3192,5 +3192,5 @@ doc/zh_*</screen> </listitem> </varlistentry> </variablelist> - </sect1> + </sect1> </appendix> diff --git a/pl_PL.ISO8859-2/books/handbook/multimedia/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/multimedia/chapter.sgml index f929f8c5fb..db30f40bba 100644 --- a/pl_PL.ISO8859-2/books/handbook/multimedia/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/multimedia/chapter.sgml @@ -129,7 +129,7 @@ </sect1info> <title>Setting Up the Sound Card</title> - + <sect2 id="sound-device"> <title>Configuring the System</title> @@ -465,10 +465,10 @@ kld snd_ich (1p/2r/0v channels duplex default)</screen> <title>MP3 Players</title> <para>By far, the most popular X11 MP3 player is - <application>XMMS</application> (X Multimedia System). + <application>XMMS</application> (X Multimedia System). <application>Winamp</application> skins can be used with <application>XMMS</application> since the - GUI is almost identical to that of Nullsoft's + GUI is almost identical to that of Nullsoft's <application>Winamp</application>. <application>XMMS</application> also has native plug-in support.</para> @@ -802,7 +802,7 @@ screen #0 Adaptor #0: "Savage Streams Engine" number of ports: 1 port base: 43 - operations supported: PutImage + operations supported: PutImage supported visuals: depth 16, visualID 0x22 depth 16, visualID 0x23 @@ -942,7 +942,7 @@ no adaptors present</screen> <listitem> <para>An application cannot playback a file which another application produced.</para> - </listitem> + </listitem> <listitem> <para>An application cannot playback a file which the @@ -981,7 +981,7 @@ no adaptors present</screen> applications. These issues are not always noticed and worked around by the port maintainers, which can lead to problems like these:</para> - + <orderedlist> <listitem> @@ -1217,7 +1217,7 @@ zoom=yes</programlisting> same time, takes some of the more fine-grained control away from the user. The <application>xine</application> video player performs best on XVideo interfaces.</para> - + <para>By default, <application>xine</application> player will start up in a graphical user interface. The menus can then be used to open a specific file:</para> @@ -1286,7 +1286,7 @@ WITH_MJPEG=yes -DWITH_XVID=yes</userinput></screen> and use a few different applications. This section exists to give the reader pointers to such additional information.</para> - <para>The + <para>The <ulink url="http://www.mplayerhq.hu/DOCS/">MPlayer documentation</ulink> is very technically informative. These documents should probably be consulted by anyone wishing @@ -1386,7 +1386,7 @@ WITH_MJPEG=yes -DWITH_XVID=yes</userinput></screen> <para>Alternatively, you may statically compile the support for the TV card in your kernel, in that case add the following lines to your kernel configuration:</para> - + <programlisting>device bktr device iicbus device iicbb diff --git a/pl_PL.ISO8859-2/books/handbook/network-servers/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/network-servers/chapter.sgml index d98dc497b9..5c0a9206c7 100644 --- a/pl_PL.ISO8859-2/books/handbook/network-servers/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/network-servers/chapter.sgml @@ -3439,7 +3439,7 @@ zone "1.168.192.in-addr.arpa" { <primary>BIND</primary> <secondary>zone files</secondary> </indexterm> - + <para>An example master zone file for <hostid role="domainname">example.org</hostid> (existing within <filename>/etc/namedb/master/example.org</filename>) is as @@ -3833,7 +3833,7 @@ www IN CNAME @</programlisting> <listitem> <para>This specifies the default directory hierarchy for the <application>Apache</application> installation. Binaries are stored in the - <filename class="directory">bin</filename> and + <filename class="directory">bin</filename> and <filename class="directory">sbin</filename> subdirectories of the server root, and configuration files are stored in <filename class="directory">etc/apache</filename>.</para> diff --git a/pl_PL.ISO8859-2/books/handbook/ports/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/ports/chapter.sgml index 5329b0df7d..96ee8bec7d 100644 --- a/pl_PL.ISO8859-2/books/handbook/ports/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/ports/chapter.sgml @@ -154,7 +154,7 @@ <itemizedlist> <title>Zalety pakietów</title> - + <listitem> <para>Skompresowany plik pakietu zajmuje z reguły mniej miejsca niż skompresowany plik zawierający kod źródłowy.</para> @@ -176,7 +176,7 @@ <itemizedlist> <title>Zalety portów</title> - + <listitem> <para>Pakiety są z reguły kompilowane z dość typowymi opcjami, ponieważ powinny być przydatne do wykorzystania na maksymalnej @@ -326,7 +326,7 @@ Path: /usr/ports/sysutils/lsof Info: Lists information about open files (similar to fstat(1)) Maint: obrien@FreeBSD.org Index: sysutils -B-deps: +B-deps: R-deps: </screen> <para>Część wyniku, która nas interesuje to wiersz zaczynający @@ -353,7 +353,7 @@ R-deps: </screen> </sect1> <sect1 id="packages-using"> - <sect1info> + <sect1info> <authorgroup> <author> <firstname>Chern</firstname> @@ -386,7 +386,7 @@ R-deps: </screen> <primary>pakiety</primary> <secondary>instalacja</secondary> </indexterm> - + <indexterm> <primary><command>pkg_add</command></primary> </indexterm> @@ -530,7 +530,7 @@ docbook = <entry>=</entry> <entry>Wersja odnaleziona w portach jest identyczna.</entry> </row> - + <row><entry><</entry> <entry>Wersja jest starsza, niż ta odnaleziona w portach.</entry> </row> @@ -573,7 +573,7 @@ docbook = </para> </sect2> </sect1> - + <sect1 id="ports-using"> <sect1info> <authorgroup> @@ -830,7 +830,7 @@ docbook = &man.md5.1; potrafi sprawdzić, czy pliki nie uległy uszkodzeniu w trakcie pobierania z sieci.</para> </listitem> - + <listitem> <para>Katalog <filename>files</filename>, który zawiera łaty pozwalające skompilować i zainstalować program w naszym @@ -849,7 +849,7 @@ docbook = <para>Plik opisu <filename>pkg-descr</filename>. Jest to bardziej szczegółowy, nierzadko wieloliniowy opis programu.</para> </listitem> - + <listitem> <para>Plik listy <filename>pkg-plist</filename>. Jest to lista wszystkich plików, które zostaną zainstalowane przez port. Jest to także lista plików, @@ -946,7 +946,7 @@ docbook = ===> Generating temporary packing list ===> Compressing manual pages for lsof-4.57 ===> Registering installation for lsof-4.57 -===> SECURITY NOTE: +===> SECURITY NOTE: This port has installed the following binaries which execute with increased privileges. &prompt.root;</screen> @@ -1387,7 +1387,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen> w wyniku polecenia</para> <screen>&prompt.root; <userinput>pkg_info <replaceable>foopackage-1.0.0</replaceable></userinput></screen> - + <para>Wiersz <literal>WWW:</literal>, jeśli w ogóle jest podany, powinien zawierać informacje o adresie witryny.</para> </listitem> diff --git a/pl_PL.ISO8859-2/books/handbook/ppp-and-slip/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/ppp-and-slip/chapter.sgml index 9fcb2d1a14..85ea9ec268 100644 --- a/pl_PL.ISO8859-2/books/handbook/ppp-and-slip/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/ppp-and-slip/chapter.sgml @@ -60,11 +60,11 @@ <indexterm id="ppp-ppp-user"> <primary>PPP</primary> <secondary>user PPP</secondary> - </indexterm> + </indexterm> <indexterm id="ppp-ppp-kernel"> <primary>PPP</primary> <secondary>kernel PPP</secondary> - </indexterm> + </indexterm> <indexterm id="ppp-ppp-ethernet"> <primary>PPP</primary> <secondary>over Ethernet</secondary> @@ -234,7 +234,7 @@ peer assign whatever IP address it sees fit.</para> </listitem> </itemizedlist> - + <para>If you do not have any of the required information, contact your ISP.</para> @@ -430,7 +430,7 @@ first number first and only use the other numbers if the first number fails, use the pipe character. Always quote the entire set of phone numbers as shown.</para> - + <para>You must enclose the phone number in quotation marks (<literal>"</literal>) if there is any intention on using spaces in the phone number. This can cause a simple, yet @@ -781,10 +781,10 @@ exec /usr/sbin/ppp -direct $IDENT</programlisting> <sect4> <title>Setting Up <filename>ppp.conf</filename> for Dynamic-IP Users</title> - + <para>The <filename>/etc/ppp/ppp.conf</filename> file should contain something along the lines of:</para> - + <programlisting>default: set debug phase lcp chat set timeout 0 @@ -891,7 +891,7 @@ exec /usr/sbin/ppp -direct pap$IDENT</programlisting> above.</para> <programlisting>pap: - enable pap + enable pap set ifaddr 203.14.100.1 203.14.100.20-203.14.100.40 enable proxy</programlisting> @@ -912,7 +912,7 @@ exec /usr/sbin/ppp -direct pap$IDENT</programlisting> <sect4> <title>MS Extensions</title> - <indexterm><primary>DNS</primary></indexterm> + <indexterm><primary>DNS</primary></indexterm> <indexterm><primary>NetBIOS</primary></indexterm> <indexterm><primary>PPP</primary><secondary>Microsoft extensions</secondary></indexterm> <para>It is possible to configure PPP to supply DNS and @@ -942,8 +942,8 @@ set nbns 203.14.100.5</programlisting> <sect4 id="userppp-PAPnCHAP"> <title>PAP and CHAP Authentication</title> - <indexterm><primary>PAP</primary></indexterm> - <indexterm><primary>CHAP</primary></indexterm> + <indexterm><primary>PAP</primary></indexterm> + <indexterm><primary>CHAP</primary></indexterm> <para>Some ISPs set their system up so that the authentication part of your connection is done using either of the PAP or CHAP authentication mechanisms. If this is the case, your ISP @@ -985,7 +985,7 @@ set nbns 203.14.100.5</programlisting> will need to insert the correct value for <replaceable>MyPassword</replaceable>. You may want to add an additional line, such as:</para> - + <programlisting>16 accept PAP</programlisting> <para>or</para> @@ -1039,14 +1039,14 @@ set nbns 203.14.100.5</programlisting> <indexterm><primary>PPP</primary><secondary>NAT</secondary></indexterm> <para>PPP has ability to use internal NAT without kernel diverting - capabilities. This functionality may be enabled by the following + capabilities. This functionality may be enabled by the following line in <filename>/etc/ppp/ppp.conf</filename>:</para> <programlisting>nat enable yes</programlisting> <para>Alternatively, PPP NAT may be enabled by command-line - option <literal>-nat</literal>. There is also - <filename>/etc/rc.conf</filename> knob named + option <literal>-nat</literal>. There is also + <filename>/etc/rc.conf</filename> knob named <literal>ppp_nat</literal>, which is enabled by default.</para> <para>If you use this feature, you may also find useful @@ -1317,7 +1317,7 @@ ifconfig_tun0=</programlisting> </author> </authorgroup> </sect2info> - + <title>Using <command>pppd</command> as a Client</title> <indexterm><primary>PPP</primary><secondary>client</secondary></indexterm> <indexterm><primary>Cisco</primary></indexterm> @@ -1369,7 +1369,7 @@ defaultroute # put this if you want that PPP server will be your fails, you can add the <option>debug</option> option to the <filename>/etc/ppp/options</filename> file, and check console messages to track the problem.</para> - + <para>Following <filename>/etc/ppp/pppup</filename> script will make all 3 stages automatic:</para> @@ -1462,7 +1462,7 @@ exit</programlisting> <para>Here is an alternate method using <command>chat</command> instead of <command>kermit</command>:</para> - <para>The following two files are sufficient to accomplish a + <para>The following two files are sufficient to accomplish a <command>pppd</command> connection.</para> <para><filename>/etc/ppp/options</filename>:</para> @@ -1514,7 +1514,7 @@ netmask 255.255.255.0 # netmask (not required) # local ip must be different from one # you assigned to the Ethernet (or other) # interface on your machine. - # remote IP is IP address that will be + # remote IP is IP address that will be # assigned to the remote machine domain ppp.foo.com # your domain passive # wait for LCP @@ -1524,7 +1524,7 @@ modem # modem line</programlisting> will tell <application>pppd</application> to behave as a server:</para> - <programlisting>#!/bin/sh + <programlisting>#!/bin/sh ps ax |grep pppd |grep -v grep pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'` if [ "X${pid}" != "X" ] ; then @@ -1551,7 +1551,7 @@ pppd /dev/tty01 19200</programlisting> <para>Use this <filename>/etc/ppp/pppservdown</filename> script to stop the server:</para> - <programlisting>#!/bin/sh + <programlisting>#!/bin/sh ps ax |grep pppd |grep -v grep pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'` if [ "X${pid}" != "X" ] ; then @@ -2195,7 +2195,7 @@ ppp_profile="adsl"</programlisting> <para>For this to work correctly you will need to have used the sample <filename>ppp.conf</filename> which is supplied with the <filename role="package">net/pppoa</filename> port.</para> - + </sect2> <sect2> @@ -2235,15 +2235,15 @@ adsl: set bundle password <replaceable>password</replaceable> <co id="co-mpd-ex-pass"/> set bundle disable multilink - + set link no pap acfcomp protocomp set link disable chap set link accept chap set link keep-alive 30 10 - + set ipcp no vjcomp set ipcp ranges 0.0.0.0/0 0.0.0.0/0 - + set iface route default set iface disable on-demand set iface enable proxy-arp @@ -2297,19 +2297,19 @@ adsl: <screen>&prompt.user; <userinput>ifconfig <replaceable>ng0</replaceable></userinput> ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1500 inet 216.136.204.117 --> 204.152.186.171 netmask 0xffffffff</screen> - + <para>Using <application>mpd</application> is the recommended way to connect to an ADSL service with &os;.</para> - + </sect2> <sect2> <title>Using pptpclient</title> - + <para>It is also possible to use FreeBSD to connect to other PPPoA services using <filename role="package">net/pptpclient</filename>.</para> - + <para>To use <filename role="package">net/pptpclient</filename> to connect to a DSL service, install the port or package and edit your <filename>/etc/ppp/ppp.conf</filename>. You will need to be @@ -2364,7 +2364,7 @@ ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1500 end of the previous command because <application>pptp</application> will not return your prompt to you otherwise.</para> </tip> - + <para>A <devicename>tun</devicename> virtual tunnel device will be created for interaction between the <application>pptp</application> and <application>ppp</application> processes. Once you have been @@ -2374,7 +2374,7 @@ ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1500 <screen>&prompt.user; <userinput>ifconfig <replaceable>tun0</replaceable></userinput> tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 - inet 216.136.204.21 --> 204.152.186.171 netmask 0xffffff00 + inet 216.136.204.21 --> 204.152.186.171 netmask 0xffffff00 Opened by PID 918</screen> <para>If you are unable to connect, check the configuration of @@ -2437,7 +2437,7 @@ tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 <para>Make sure you have the following in your kernel configuration file:</para> - + <programlisting>device sl</programlisting> <para>It is included in the <filename>GENERIC</filename> kernel, so @@ -2478,7 +2478,7 @@ tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 <listitem> <para>Set your hostname by editing the line that says:</para> - + <programlisting>hostname="myname.my.domain"</programlisting> <para>Your machine's full Internet hostname should be @@ -2516,7 +2516,7 @@ nameserver 128.32.136.12</programlisting> </step> <step> - <para>Set the password for <username>root</username> and + <para>Set the password for <username>root</username> and <username>toor</username> (and any other accounts that do not have a password).</para> </step> @@ -2576,7 +2576,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting> <para>If you are able to <command>ping</command> hosts on the other side of the router, you are connected! If it does not work, you might want to try <option>-a</option> instead of - <option>-c</option> as an argument to + <option>-c</option> as an argument to <command>slattach</command>.</para> </step> </procedure> @@ -2595,8 +2595,8 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting> exit from it (<keycap>q</keycap>).</para> - <para>The &man.slattach.8; manual page says you have - to use <command>ifconfig sl0 down</command> + <para>The &man.slattach.8; manual page says you have + to use <command>ifconfig sl0 down</command> to mark the interface down, but this does not seem to make any difference. (<command>ifconfig sl0</command> reports the same thing.)</para> @@ -2792,7 +2792,7 @@ water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438 will have to edit the <filename>/etc/rc.conf</filename> file and change the setting of the <literal>gateway_enable</literal> variable to <option>YES</option>.</para> - + <para>You will then need to reboot for the new settings to take effect.</para> @@ -2853,7 +2853,7 @@ water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438 this:</para> <programlisting># -# login local-addr remote-addr mask opt1 opt2 +# login local-addr remote-addr mask opt1 opt2 # (normal,compress,noicmp) # Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting> @@ -2952,7 +2952,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting # 1 2 3 4 5 6 7-n # slipunit ttyspeed loginname local-addr remote-addr mask opt-args # -/sbin/ifconfig sl$1 inet $4 $5 netmask $6 +/sbin/ifconfig sl$1 inet $4 $5 netmask $6 # Answer ARP requests for the SLIP client with our Ethernet addr /usr/sbin/arp -s $5 00:11:22:33:44:55 pub</programlisting> @@ -3055,7 +3055,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting </indexterm> <para>If you are not using the <quote>proxy ARP</quote> method for routing packets between your SLIP clients and the rest of your - network (and perhaps the Internet), you will probably + network (and perhaps the Internet), you will probably have to add static routes to your closest default router(s) to route your SLIP clients subnet via your SLIP server.</para> @@ -3082,10 +3082,10 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting </indexterm> <note> - <para><application>&gated;</application> is proprietary software now and - will not be available as source code to the public anymore + <para><application>&gated;</application> is proprietary software now and + will not be available as source code to the public anymore (more info on the <ulink - url="http://www.gated.org/">&gated;</ulink> website). This + url="http://www.gated.org/">&gated;</ulink> website). This section only exists to ensure backwards compatibility for those that are still using an older version.</para> </note> @@ -3094,7 +3094,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting install <application>&gated;</application> on your FreeBSD SLIP server and configure it to use the appropriate routing protocols (RIP/OSPF/BGP/EGP) to tell other routers about your SLIP - subnet. + subnet. You will need to write a <filename>/etc/gated.conf</filename> file to configure your <application>&gated;</application>; here is a sample, similar to what the author used on a FreeBSD SLIP server:</para> @@ -3132,7 +3132,7 @@ export proto rip interface ed { # # Accept routes from RIP via ed Ethernet interfaces - + import proto rip interface ed { all ; } ;</programlisting> diff --git a/pl_PL.ISO8859-2/books/handbook/preface/preface.sgml b/pl_PL.ISO8859-2/books/handbook/preface/preface.sgml index 70888ebf4b..695c919b75 100644 --- a/pl_PL.ISO8859-2/books/handbook/preface/preface.sgml +++ b/pl_PL.ISO8859-2/books/handbook/preface/preface.sgml @@ -8,7 +8,7 @@ <preface id="book-preface"> <title>Przedmowa</title> - + <bridgehead id="preface-audience" renderas="sect1">Docelowy czytelnik</bridgehead> diff --git a/pl_PL.ISO8859-2/books/handbook/printing/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/printing/chapter.sgml index 31c1cb6485..2da98aa762 100644 --- a/pl_PL.ISO8859-2/books/handbook/printing/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/printing/chapter.sgml @@ -90,7 +90,7 @@ <itemizedlist> <listitem> - <para>Know how to configure and install a new kernel + <para>Know how to configure and install a new kernel (<xref linkend="kernelconfig"/>).</para> </listitem> </itemizedlist> @@ -107,12 +107,12 @@ chapter introduces <application>LPD</application> and will guide you through its configuration.</para> - <para>If you are already familiar with + <para>If you are already familiar with <application>LPD</application> or another printer spooling system, you may wish to skip to section <link linkend="printing-intro-setup">Basic Setup</link>.</para> - <para><application>LPD</application> controls everything about a + <para><application>LPD</application> controls everything about a host's printers. It is responsible for a number of things:</para> <itemizedlist> @@ -147,7 +147,7 @@ </listitem> <listitem> - <para>It can send jobs over the network to a + <para>It can send jobs over the network to a <application>LPD</application> spooler on another host.</para> </listitem> @@ -186,7 +186,7 @@ <listitem> <indexterm><primary>&tex;</primary></indexterm> - <para><application>LPD</application> can conveniently run a job + <para><application>LPD</application> can conveniently run a job to be printed through filters to add date/time headers or convert a special file format (such as a &tex; DVI file) into a format the printer will @@ -210,14 +210,14 @@ <para>To use printers with the <application>LPD</application> spooling system, you will need to - set up both your printer hardware and the + set up both your printer hardware and the <application>LPD</application> software. This document describes two levels of setup:</para> <itemizedlist> <listitem> <para>See section <link linkend="printing-simple">Simple Printer - Setup</link> to learn how to connect a printer, tell + Setup</link> to learn how to connect a printer, tell <application>LPD</application> how to communicate with it, and print plain text files to the printer.</para> @@ -236,7 +236,7 @@ <title>Simple Printer Setup</title> <para>This section tells how to configure printer hardware and the - <application>LPD</application> software to use the printer. + <application>LPD</application> software to use the printer. It teaches the basics:</para> <itemizedlist> @@ -248,7 +248,7 @@ <listitem> <para>Section <link linkend="printing-software">Software - Setup</link> shows how to set up the + Setup</link> shows how to set up the <application>LPD</application> spooler configuration file (<filename>/etc/printcap</filename>).</para> </listitem> @@ -377,7 +377,7 @@ two values and you know how much paper to charge to the user.</para> </sect4> - + <sect4 id="printing-parallel"> <title>Parallel Ports</title> @@ -483,7 +483,7 @@ </step> <step> - <para>Set up <application>LPD</application> for the printer by + <para>Set up <application>LPD</application> for the printer by modifying the file <filename>/etc/printcap</filename>. You will find out how to do this later in this chapter.</para> @@ -521,11 +521,11 @@ sio2: type 16550A</screen> <para>Where <replaceable>N</replaceable> is the number of the parallel port, starting from zero. If you see output similar to the following:</para> - + <screen>ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold</screen> - + <para>then the kernel supports the port.</para> <para>You might have to reconfigure your kernel in order for the @@ -872,7 +872,7 @@ showpage</programlisting> to your printer.</para> <para>You configure <application>LPD</application> by editing the file - <filename>/etc/printcap</filename>. The + <filename>/etc/printcap</filename>. The <application>LPD</application> spooling system reads this file each time the spooler is used, so updates to the file take immediate effect.</para> @@ -896,7 +896,7 @@ showpage</programlisting> <step> <para>Pick a name (and a few convenient aliases) for the printer, and put them in the - <filename>/etc/printcap</filename> file; see the + <filename>/etc/printcap</filename> file; see the <link linkend="printing-naming">Naming the Printer</link> section for more information on naming.</para> </step> @@ -980,7 +980,7 @@ showpage</programlisting> <literal>lp</literal>. This is the default printer's name. If users do not have the <envar>PRINTER</envar> environment variable nor specify a printer name on the command line of any - of the <application>LPD</application> commands, + of the <application>LPD</application> commands, then <literal>lp</literal> will be the default printer they get to use.</para> @@ -1025,7 +1025,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:</programlisting> <secondary>header pages</secondary> </indexterm> - <para>The <application>LPD</application> spooling system will + <para>The <application>LPD</application> spooling system will by default print a <emphasis>header page</emphasis> for each job. The header page contains the user name who requested the job, the host @@ -1079,7 +1079,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ <para>However, if you have a lot of printers on your network, you might want to put the spooling directories under a single - directory that you reserve just for printing with + directory that you reserve just for printing with <application>LPD</application>. We will do this for our two example printers <literal>rattan</literal> and @@ -1135,7 +1135,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ Entries for the Ports section, we identified which entry in the <filename>/dev</filename> directory FreeBSD will use to - communicate with the printer. Now, we tell + communicate with the printer. Now, we tell <application>LPD</application> that information. When the spooling system has a job to print, it will open the specified device on behalf of the filter program @@ -1266,7 +1266,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ what text filter to use to send jobs to the printer. A <emphasis>text filter</emphasis>, also known as an <emphasis>input filter</emphasis>, is a - program that <application>LPD</application> runs when it + program that <application>LPD</application> runs when it has a job to print. When <application>LPD</application> runs the text filter for a printer, it sets the filter's standard input to the job to print, and its standard output to @@ -1350,16 +1350,16 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ <screen>&prompt.root; <userinput>lpd</userinput></screen> </sect4> - + <sect4 id="printing-trying"> <title>Trying It Out</title> - <para>You have reached the end of the simple + <para>You have reached the end of the simple <application>LPD</application> setup. Unfortunately, congratulations are not quite yet in order, since we still have to test the setup and correct any problems. To test the setup, try printing something. To - print with the <application>LPD</application> system, you + print with the <application>LPD</application> system, you use the command &man.lpr.1;, which submits a job for printing.</para> @@ -1374,7 +1374,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ <para>Type:</para> <screen>&prompt.root; <userinput>lptest 20 5 | lpr -P<replaceable>printer-name</replaceable></userinput></screen> - + <para>Where <replaceable>printer-name</replaceable> is a the name of a printer (or an alias) specified in <filename>/etc/printcap</filename>. To test the default @@ -1382,7 +1382,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ argument. Again, if you are testing a printer that expects &postscript;, send a &postscript; program in that language instead of using &man.lptest.1;. You can do so by putting the program - in a file and typing <command>lpr + in a file and typing <command>lpr <replaceable>file</replaceable></command>.</para> <para>For a &postscript; printer, you should get the results of @@ -1408,10 +1408,10 @@ $%&'()*+,-./01234567 </sect3> </sect2> </sect1> - + <sect1 id="printing-advanced"> <title>Advanced Printer Setup</title> - + <para>This section describes filters for printing specially formatted files, header pages, printing across networks, and restricting and accounting for printer usage.</para> @@ -1422,7 +1422,7 @@ $%&'()*+,-./01234567 <primary>printing</primary> <secondary>filters</secondary> </indexterm> - + <para>Although <application>LPD</application> handles network protocols, queuing, access control, and other aspects of printing, most of the <emphasis>real</emphasis> @@ -1433,7 +1433,7 @@ $%&'()*+,-./01234567 should work with most printers (section <link linkend="printing-textfilter">Installing the Text Filter</link>).</para> - + <para>However, in order to take advantage of format conversion, printer accounting, specific printer quirks, and so on, you should understand how filters work. It will ultimately be the filter's responsibility @@ -1441,16 +1441,16 @@ $%&'()*+,-./01234567 <emphasis>you</emphasis> have to provide filters yourself. The good news is that many are generally available; when they are not, they are usually easy to write.</para> - + <para>Also, FreeBSD comes with one, <filename>/usr/libexec/lpr/lpf</filename>, that works with many printers that can print plain text. (It handles backspacing and tabs in the file, and does accounting, but that is about all it does.) There are also several filters and filter components in the FreeBSD Ports Collection.</para> - + <para>Here is what you will find in this section:</para> - + <itemizedlist> <listitem> <para>Section <link linkend="printing-advanced-filters">How Filters @@ -1462,9 +1462,9 @@ $%&'()*+,-./01234567 and debug problems you might encounter as you install more and more filters on each of your printers.</para> </listitem> - + <listitem> - <para><application>LPD</application> expects every printer to be + <para><application>LPD</application> expects every printer to be able to print plain text by default. This presents a problem for &postscript; (or other language-based printers) which cannot directly print plain text. @@ -1485,7 +1485,7 @@ $%&'()*+,-./01234567 <emphasis>non &postscript;</emphasis> printer. You should read this section if you do not have a &postscript; printer.</para> </listitem> - + <listitem> <para>Section <link linkend="printing-advanced-convfilters">Conversion @@ -1498,10 +1498,10 @@ $%&'()*+,-./01234567 -v</command> to print raster image data, and so forth. I recommend reading this section.</para> </listitem> - + <listitem> <para>Section <link linkend="printing-advanced-of">Output - Filters</link> tells all about a not often used feature of + Filters</link> tells all about a not often used feature of <application>LPD</application>: output filters. Unless you are printing header pages (see <link linkend="printing-advanced-header-pages">Header Pages</link>), @@ -1519,7 +1519,7 @@ $%&'()*+,-./01234567 <command>lpf</command>.</para> </listitem> </itemizedlist> - + <note> <para>A copy of the various scripts described below can be found in the <filename @@ -1533,22 +1533,22 @@ $%&'()*+,-./01234567 <para>As mentioned before, a filter is an executable program started by <application>LPD</application> to handle the device-dependent part of communicating with the printer.</para> - - <para>When <application>LPD</application> wants to print a file in a + + <para>When <application>LPD</application> wants to print a file in a job, it starts a filter program. It sets the filter's standard input to the file to print, its standard output to the printer, and its standard error to the error logging file (specified in the <literal>lf</literal> capability in <filename>/etc/printcap</filename>, or <filename>/dev/console</filename> by default).</para> - + <indexterm> <primary><command>troff</command></primary> </indexterm> - <para>Which filter <application>LPD</application> starts and the + <para>Which filter <application>LPD</application> starts and the filter's arguments depend on what is listed in the <filename>/etc/printcap</filename> file and - what arguments the user specified for the job on the + what arguments the user specified for the job on the &man.lpr.1; command line. For example, if the user typed <command>lpr -t</command>, <application>LPD</application> would start the troff filter, listed @@ -1564,9 +1564,9 @@ $%&'()*+,-./01234567 <itemizedlist> <listitem> <para>The <emphasis>text filter</emphasis>, confusingly called the - <emphasis>input filter</emphasis> in + <emphasis>input filter</emphasis> in <application>LPD</application> documentation, handles - regular text printing. Think of it as the default filter. + regular text printing. Think of it as the default filter. <application>LPD</application> expects every printer to be able to print plain text by default, and it is the text filter's job to make sure backspaces, tabs, @@ -1589,7 +1589,7 @@ $%&'()*+,-./01234567 </cmdsynopsis> where - + <variablelist> <varlistentry> <term><option>-c</option></term> @@ -1599,56 +1599,56 @@ $%&'()*+,-./01234567 -l</command></para> </listitem> </varlistentry> - + <varlistentry> <term><replaceable>width</replaceable></term> - + <listitem> <para>is the value from the <literal>pw</literal> (page width) capability specified in <filename>/etc/printcap</filename>, default 132</para> </listitem> </varlistentry> - + <varlistentry> <term><replaceable>length</replaceable></term> - + <listitem> <para>is the value from the <literal>pl</literal> (page length) capability, default 66</para> </listitem> </varlistentry> - + <varlistentry> <term><replaceable>indent</replaceable></term> - + <listitem> <para>is the amount of the indentation from <command>lpr -i</command>, default 0</para> </listitem> </varlistentry> - + <varlistentry> <term><replaceable>login</replaceable></term> - + <listitem> <para>is the account name of the user printing the file</para> </listitem> </varlistentry> - + <varlistentry> <term><replaceable>host</replaceable></term> - + <listitem> <para>is the host name from which the job was submitted</para> </listitem> </varlistentry> - + <varlistentry> <term><replaceable>acct-file</replaceable></term> - + <listitem> <para>is the name of the accounting file from the <literal>af</literal> capability.</para> @@ -1690,7 +1690,7 @@ $%&'()*+,-./01234567 <replaceable>pixel-height</replaceable> is the value from the <literal>py</literal> capability (default 0).</para> </listitem> - + <listitem> <para>The <emphasis>output filter</emphasis> is used only if there is no text filter, or if header pages are enabled. In my @@ -1711,7 +1711,7 @@ $%&'()*+,-./01234567 <para>Filters should also <emphasis>exit</emphasis> with the following exit status:</para> - + <variablelist> <varlistentry> <term>exit 0</term> @@ -1720,24 +1720,24 @@ $%&'()*+,-./01234567 <para>If the filter printed the file successfully.</para> </listitem> </varlistentry> - + <varlistentry> <term>exit 1</term> - + <listitem> - <para>If the filter failed to print the file but wants + <para>If the filter failed to print the file but wants <application>LPD</application> to try to print the file again. <application>LPD</application> will restart a filter if it exits with this status.</para> </listitem> </varlistentry> - + <varlistentry> <term>exit 2</term> - + <listitem> <para>If the filter failed to print the file and does not want - <application>LPD</application> to try again. + <application>LPD</application> to try again. <application>LPD</application> will throw out the file.</para> </listitem> </varlistentry> @@ -1754,7 +1754,7 @@ $%&'()*+,-./01234567 If you plan on writing filters for general use, then have them support the same argument lists and exit codes.</para> </sect3> - + <sect3 id="printing-advanced-if-conversion"> <title>Accommodating Plain Text Jobs on &postscript; Printers</title> <indexterm><primary>print jobs</primary></indexterm> @@ -1764,7 +1764,7 @@ $%&'()*+,-./01234567 text to your printer and to never use features of various programs that will want to send plain text to your printer, then you do not need to worry about this section at all.</para> - + <para>But, if you would like to send both &postscript; and plain text jobs to the printer, then you are urged to augment your printer setup. To do so, we have the text filter detect if the arriving job @@ -1774,7 +1774,7 @@ $%&'()*+,-./01234567 we have &postscript;, and can pass the rest of the job directly. If those are not the first two characters in the file, then the filter will convert the text into &postscript; and print the result.</para> - + <para>How do we do this?</para> <indexterm> @@ -1793,7 +1793,7 @@ $%&'()*+,-./01234567 <command>textps</command> (another program that comes with <command>lprps</command>) to convert it to &postscript;. It then uses <command>lprps</command> to send the job to the printer.</para> - + <para><command>lprps</command> is part of the FreeBSD Ports Collection (see <link linkend="ports">The Ports Collection</link>). You can fetch, build and install it yourself, of course. After installing @@ -1803,13 +1803,13 @@ $%&'()*+,-./01234567 from the Ports Collection, use the following in the serial &postscript; printer's entry in <filename>/etc/printcap</filename>:</para> - + <programlisting>:if=/usr/local/libexec/psif:</programlisting> <para>You should also specify the <literal>rw</literal> capability; - that tells <application>LPD</application> to open the printer in + that tells <application>LPD</application> to open the printer in read-write mode.</para> - + <para>If you have a parallel &postscript; printer (and therefore cannot use two-way communication with the printer, which <command>lprps</command> needs), you can use the following shell @@ -1838,7 +1838,7 @@ else ( echo "$first_line"; cat ) | /usr/local/bin/textps && printf "\004" && exit 0 exit 2 fi</programlisting> - + <para>In the above script, <command>textps</command> is a program we installed separately to convert plain text to &postscript;. You can use any text-to-&postscript; program you wish. The FreeBSD Ports @@ -1846,7 +1846,7 @@ fi</programlisting> includes a full featured text-to-&postscript; program called <literal>a2ps</literal> that you might want to investigate.</para> </sect3> - + <sect3 id="printing-advanced-ps"> <title>Simulating &postscript; on Non &postscript; Printers</title> <indexterm> @@ -1865,17 +1865,17 @@ fi</programlisting> non-PostScript printers. By installing Ghostscript and using a special text filter for your printer, you can make your non &postscript; printer act like a real &postscript; printer.</para> - + <para>Ghostscript is in the FreeBSD Ports Collection, if you would like to install it from there. You can fetch, build, and install it quite easily yourself, as well.</para> - + <para>To simulate &postscript;, we have the text filter detect if it is printing a &postscript; file. If it is not, then the filter will pass the file directly to the printer; otherwise, it will use Ghostscript to first convert the file into a format the printer will understand.</para> - + <para>Here is an example: the following script is a text filter for Hewlett Packard DeskJet 500 printers. For other printers, substitute the <option>-sDEVICE</option> argument to the @@ -1911,22 +1911,22 @@ else # Plain text or HP/PCL, so just print it directly; print a form feed # at the end to eject the last page. # - echo "$first_line" && cat && printf "\033&l0H" && + echo "$first_line" && cat && printf "\033&l0H" && exit 0 fi exit 2</programlisting> - <para>Finally, you need to notify <application>LPD</application> of + <para>Finally, you need to notify <application>LPD</application> of the filter via the <literal>if</literal> capability:</para> - + <programlisting>:if=/usr/local/libexec/ifhp:</programlisting> <para>That is it. You can type <command>lpr plain.text</command> and <filename>lpr whatever.ps</filename> and both should print successfully.</para> </sect3> - + <sect3 id="printing-advanced-convfilters"> <title>Conversion Filters</title> @@ -1934,38 +1934,38 @@ exit 2</programlisting> linkend="printing-simple">Simple Printer Setup</link>, the first thing you will probably want to do is install conversion filters for your favorite file formats (besides plain ASCII text).</para> - + <sect4> <title>Why Install Conversion Filters?</title> <indexterm> <primary>&tex;</primary> <secondary>printing DVI files</secondary> </indexterm> - + <para>Conversion filters make printing various kinds of files easy. As an example, suppose we do a lot of work with the &tex; typesetting system, and we have a &postscript; printer. Every time we generate a DVI file from &tex;, we cannot print it directly until we convert the DVI file into &postscript;. The command sequence goes like this:</para> - + <screen>&prompt.user; <userinput>dvips seaweed-analysis.dvi</userinput> &prompt.user; <userinput>lpr seaweed-analysis.ps</userinput></screen> - + <para>By installing a conversion filter for DVI files, we can skip - the hand conversion step each time by having + the hand conversion step each time by having <application>LPD</application> do it for us. Now, each time we get a DVI file, we are just one step away from printing it:</para> - + <screen>&prompt.user; <userinput>lpr -d seaweed-analysis.dvi</userinput></screen> - - <para>We got <application>LPD</application> to do the DVI file + + <para>We got <application>LPD</application> to do the DVI file conversion for us by specifying the <option>-d</option> option. Section <link linkend="printing-lpr-options-format">Formatting and Conversion Options</link> lists the conversion options.</para> - + <para>For each of the conversion options you want a printer to support, install a <emphasis>conversion filter</emphasis> and specify its pathname in <filename>/etc/printcap</filename>. A @@ -1978,13 +1978,13 @@ exit 2</programlisting> <sect4> <title>Which Conversion Filters Should I Install?</title> - + <para>You should install the conversion filters you expect to use. If you print a lot of DVI data, then a DVI conversion filter is in order. If you have got plenty of troff to print out, then you probably want a troff filter.</para> - - <para>The following table summarizes the filters that + + <para>The following table summarizes the filters that <application>LPD</application> works with, their capability entries for the <filename>/etc/printcap</filename> file, and how to invoke them @@ -1999,50 +1999,50 @@ exit 2</programlisting> <entry><command>lpr</command> option</entry> </row> </thead> - + <tbody> <row> <entry>cifplot</entry> <entry><literal>cf</literal></entry> <entry><option>-c</option></entry> </row> - + <row> <entry>DVI</entry> <entry><literal>df</literal></entry> <entry><option>-d</option></entry> </row> - + <row> <entry>plot</entry> <entry><literal>gf</literal></entry> <entry><option>-g</option></entry> </row> - + <row> <entry>ditroff</entry> <entry><literal>nf</literal></entry> <entry><option>-n</option></entry> </row> - + <row> <entry>FORTRAN text</entry> <entry><literal>rf</literal></entry> <entry><option>-f</option></entry> </row> - + <row> <entry>troff</entry> <entry><literal>tf</literal></entry> <entry><option>-f</option></entry> </row> - + <row> <entry>raster</entry> <entry><literal>vf</literal></entry> <entry><option>-v</option></entry> </row> - + <row> <entry>plain text</entry> <entry><literal>if</literal></entry> @@ -2052,11 +2052,11 @@ exit 2</programlisting> </tbody> </tgroup> </informaltable> - + <para>In our example, using <command>lpr -d</command> means the printer needs a <literal>df</literal> capability in its entry in <filename>/etc/printcap</filename>.</para> - + <indexterm><primary>FORTRAN</primary></indexterm> <para>Despite what others might contend, formats like FORTRAN text and plot are probably obsolete. At your site, you can give new @@ -2072,19 +2072,19 @@ exit 2</programlisting> <sect4> <title>Installing Conversion Filters</title> - + <para>Since conversion filters are programs you install outside of the base FreeBSD installation, they should probably go under <filename>/usr/local</filename>. The directory <filename>/usr/local/libexec</filename> is a popular location, - since they are specialized programs that only + since they are specialized programs that only <application>LPD</application> will run; regular users should not ever need to run them.</para> - + <para>To enable a conversion filter, specify its pathname under the appropriate capability for the destination printer in <filename>/etc/printcap</filename>.</para> - + <para>In our example, we will add the DVI conversion filter to the entry for the printer named <literal>bamboo</literal>. Here is the example <filename>/etc/printcap</filename> file again, with @@ -2123,20 +2123,20 @@ exec /usr/local/bin/dvips -f | /usr/local/libexec/lprps "$@"</programlisting> to print. It then starts the &postscript; printer filter <command>lprps</command> (see section <link linkend="printing-advanced-if-conversion">Accommodating Plain - Text Jobs on &postscript; Printers</link>) with the arguments + Text Jobs on &postscript; Printers</link>) with the arguments <application>LPD</application> passed to this script. <command>lprps</command> will use those arguments to account for the pages printed.</para> </sect4> - + <sect4> <title>More Conversion Filter Examples</title> - + <para>Since there is no fixed set of steps to install conversion filters, let me instead provide more examples. Use these as guidance to making your own filters. Use them directly, if appropriate.</para> - + <para>This example script is a raster (well, GIF file, actually) conversion filter for a Hewlett Packard LaserJet III-Si printer:</para> @@ -2145,7 +2145,7 @@ exec /usr/local/bin/dvips -f | /usr/local/libexec/lprps "$@"</programlisting> # # hpvf - Convert GIF files into HP/PCL, then print # Installed in /usr/local/libexec/hpvf - + PATH=/usr/X11R6/bin:$PATH; export PATH giftopnm | ppmtopgm | pgmtopbm | pbmtolj -resolution 300 \ && exit 0 \ @@ -2155,7 +2155,7 @@ giftopnm | ppmtopgm | pgmtopbm | pbmtolj -resolution 300 \ converting that into a portable graymap, converting that into a portable bitmap, and converting that into LaserJet/PCL-compatible data.</para> - + <para>Here is the <filename>/etc/printcap</filename> file with an entry for a printer using the above filter:</para> @@ -2166,7 +2166,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ :lp=/dev/lpt0:sh:sd=/var/spool/lpd/teak:mx#0:\ :if=/usr/local/libexec/hpif:\ :vf=/usr/local/libexec/hpvf:</programlisting> - + <para>The following script is a conversion filter for troff data from the groff typesetting system for the &postscript; printer named <literal>bamboo</literal>:</para> @@ -2177,7 +2177,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ # Installed in /usr/local/libexec/pstf # exec grops | /usr/local/libexec/lprps "$@"</programlisting> - + <para>The above script makes use of <command>lprps</command> again to handle the communication with the printer. If the printer were on a parallel port, we would use this script instead:</para> @@ -2188,12 +2188,12 @@ exec grops | /usr/local/libexec/lprps "$@"</programlisting> # Installed in /usr/local/libexec/pstf # exec grops</programlisting> - + <para>That is it. Here is the entry we need to add to <filename>/etc/printcap</filename> to enable the filter:</para> - + <programlisting>:tf=/usr/local/libexec/pstf:</programlisting> - + <para>Here is an example that might make old hands at FORTRAN blush. It is a FORTRAN-text filter for any printer that can directly print plain text. We will install it for the printer @@ -2208,21 +2208,21 @@ exec grops</programlisting> printf "\033&k2G" && fpr && printf "\033&l0H" && exit 0 exit 2</programlisting> - + <para>And we will add this line to the <filename>/etc/printcap</filename> for the printer <literal>teak</literal> to enable this filter:</para> - + <programlisting>:rf=/usr/local/libexec/hprf:</programlisting> - + <para>Here is one final, somewhat complex example. We will add a DVI filter to the LaserJet printer <literal>teak</literal> introduced earlier. First, the easy part: updating <filename>/etc/printcap</filename> with the location of the DVI filter:</para> - + <programlisting>:df=/usr/local/libexec/hpdf:</programlisting> - + <para>Now, for the hard part: making the filter. For that, we need a DVI-to-LaserJet/PCL conversion program. The FreeBSD Ports Collection (see <link linkend="ports">The Ports Collection</link>) @@ -2230,7 +2230,7 @@ exit 2</programlisting> Installing this package gives us the program we need, <command>dvilj2p</command>, which converts DVI into LaserJet IIp, LaserJet III, and LaserJet 2000 compatible codes.</para> - + <para><command>dvilj2p</command> makes the filter <command>hpdf</command> quite complex since <command>dvilj2p</command> cannot read from standard input. It @@ -2241,7 +2241,7 @@ exit 2</programlisting> temporary file name (one that ends in <filename>.dvi</filename>) to <filename>/dev/fd/0</filename>, thereby forcing <command>dvilj2p</command> to read from standard input.</para> - + <para>The only other fly in the ointment is the fact that we cannot use <filename>/tmp</filename> for the temporary link. Symbolic links are owned by user and group <username>bin</username>. The @@ -2250,7 +2250,7 @@ exit 2</programlisting> filter can create the link, but it will not be able clean up when done and remove it since the link will belong to a different user.</para> - + <para>Instead, the filter will make the symbolic link in the current working directory, which is the spooling directory (specified by the <literal>sd</literal> capability in @@ -2258,7 +2258,7 @@ exit 2</programlisting> filters to do their work, especially since there is (sometimes) more free disk space in the spooling directory than under <filename>/tmp</filename>.</para> - + <para>Here, finally, is the filter:</para> <programlisting>#!/bin/sh @@ -2292,7 +2292,7 @@ fatal() { # If user removes the job, LPD will send SIGINT, so trap SIGINT # (and a few other signals) to clean up after ourselves. # -trap cleanup 1 2 15 +trap cleanup 1 2 15 # # Make sure we are not colliding with any existing files. @@ -2309,7 +2309,7 @@ ln -s /dev/fd/0 hpdf$$.dvi || fatal "Cannot symlink /dev/fd/0" # printf "\033&k2G" || fatal "Cannot initialize printer" -# +# # Convert and print. Return value from dvilj2p does not seem to be # reliable, so we ignore it. # @@ -2325,7 +2325,7 @@ exit 0</programlisting> <sect4 id="printing-advanced-autoconv"> <title>Automated Conversion: an Alternative to Conversion Filters</title> - + <para>All these conversion filters accomplish a lot for your printing environment, but at the cost forcing the user to specify (on the &man.lpr.1; command line) which one to use. @@ -2334,7 +2334,7 @@ exit 0</programlisting> though, is that an incorrectly specified filter option may run a filter on the wrong type of file and cause your printer to spew out hundreds of sheets of paper.</para> - + <para>Rather than install conversion filters at all, you might want to try having the text filter (since it is the default filter) detect the type of file it has been asked to print and then @@ -2343,7 +2343,7 @@ exit 0</programlisting> be hard to determine the differences between <emphasis>some</emphasis> file types—and, of course, you can still provide conversion filters just for them.</para> - + <indexterm><primary>apsfilter</primary></indexterm> <indexterm> <primary>printing</primary> @@ -2356,11 +2356,11 @@ exit 0</programlisting> conversions, and print.</para> </sect4> </sect3> - + <sect3 id="printing-advanced-of"> <title>Output Filters</title> - <para>The <application>LPD</application> spooling system supports one + <para>The <application>LPD</application> spooling system supports one other type of filter that we have not yet explored: an output filter. An output filter is intended for printing plain text only, like the text filter, but @@ -2373,25 +2373,25 @@ exit 0</programlisting> for the entire job instead of once for each file in the job.</para> </listitem> - + <listitem> <para><application>LPD</application> does not make any provision to identify the start or the end of files within the job for the output filter.</para> </listitem> - + <listitem> - <para><application>LPD</application> does not pass the user's + <para><application>LPD</application> does not pass the user's login or host to the filter, so it is not intended to do accounting. In fact, it gets only two arguments:</para> - + <cmdsynopsis> <command>filter-name</command> <arg choice="plain">-w<replaceable>width</replaceable></arg> <arg choice="plain">-l<replaceable>length</replaceable></arg> </cmdsynopsis> - + <para>Where <replaceable>width</replaceable> is from the <literal>pw</literal> capability and <replaceable>length</replaceable> is from the @@ -2409,15 +2409,15 @@ exit 0</programlisting> complex</emphasis> in that it has to examine the byte stream being sent to it for special flag characters and must send signals to itself on behalf of <application>LPD</application>.</para> - + <para>However, an output filter is <emphasis>necessary</emphasis> if you want header pages and need to send escape sequences or other initialization strings to be able to print the header page. (But it is also <emphasis>futile</emphasis> if you want to charge header - pages to the requesting user's account, since + pages to the requesting user's account, since <application>LPD</application> does not give any user or host information to the output filter.)</para> - + <para>On a single printer, <application>LPD</application> allows both an output filter and text or other filters. In such cases, <application>LPD</application> will start the @@ -2429,11 +2429,11 @@ exit 0</programlisting> itself</emphasis> by sending two bytes to the filter: ASCII 031 followed by ASCII 001. When an output filter sees these two bytes (031, 001), it should stop by sending <literal>SIGSTOP</literal> - to itself. When + to itself. When <application>LPD</application>'s done running other filters, it will restart the output filter by sending <literal>SIGCONT</literal> to it.</para> - + <para>If there is an output filter but <emphasis>no</emphasis> text filter and <application>LPD</application> is working on a plain text job, <application>LPD</application> uses the output @@ -2442,7 +2442,7 @@ exit 0</programlisting> feeds or other paper advancement, and this is probably <emphasis>not</emphasis> what you want. In almost all cases, you need a text filter.</para> - + <para>The program <command>lpf</command>, which we introduced earlier as a text filter, can also run as an output filter. If you need a quick-and-dirty output filter but do not want to write the byte @@ -2450,7 +2450,7 @@ exit 0</programlisting> can also wrap <command>lpf</command> in a shell script to handle any initialization codes the printer might require.</para> </sect3> - + <sect3 id="printing-advanced-lpf"> <title><command>lpf</command>: a Text Filter</title> @@ -2461,13 +2461,13 @@ exit 0</programlisting> with <command>lpr -l</command>), adjust the printing position for backspaces and tabs in the job, and account for pages printed. It can also act like an output filter.</para> - + <para><command>lpf</command> is suitable for many printing environments. And although it has no capability to send initialization sequences to a printer, it is easy to write a shell script to do the needed initialization and then execute <command>lpf</command>.</para> - + <indexterm><primary>page accounting</primary></indexterm> <indexterm> <primary>accounting</primary> @@ -2483,14 +2483,14 @@ exit 0</programlisting> Usage</link>.</para> </sect3> </sect2> - + <sect2 id="printing-advanced-header-pages"> <title>Header Pages</title> - + <para>If you have <emphasis>lots</emphasis> of users, all of them using various printers, then you probably want to consider <emphasis>header pages</emphasis> as a necessary evil.</para> - + <indexterm> <primary>banner pages</primary> <see>header pages</see> @@ -2507,7 +2507,7 @@ exit 0</programlisting> minutes, ultimately finding themselves in a recycling bin or rubbish heap. (Note that header pages go with each job, not each file in a job, so the paper waste might not be that bad.)</para> - + <para>The <application>LPD</application> system can provide header pages automatically for your printouts <emphasis>if</emphasis> your printer can directly print @@ -2515,7 +2515,7 @@ exit 0</programlisting> external program to generate the header page; see <link linkend="printing-advanced-header-pages-ps">Header Pages on &postscript; Printers</link>.</para> - + <sect3 id="printing-advanced-header-pages-enabling"> <title>Enabling Header Pages</title> @@ -2539,12 +2539,12 @@ exit 0</programlisting> printf "\033&k2G" || exit 2 exec /usr/libexec/lpr/lpf</programlisting> - + <para>Specify the path to the output filter in the <literal>of</literal> capability. See the <link linkend="printing-advanced-of">Output Filters</link> section for more information.</para> - + <para>Here is an example <filename>/etc/printcap</filename> file for the printer <literal>teak</literal> that we introduced earlier; we enabled header pages and added the above output filter:</para> @@ -2557,7 +2557,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ :if=/usr/local/libexec/hpif:\ :vf=/usr/local/libexec/hpvf:\ :of=/usr/local/libexec/hpof:</programlisting> - + <para>Now, when users print jobs to <literal>teak</literal>, they get a header page with each job. If users want to spend time searching for their printouts, they can suppress header pages by submitting @@ -2573,7 +2573,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ capability in <filename>/etc/printcap</filename>.</para> </note> </sect3> - + <sect3 id="printing-advanced-header-pages-controlling"> <title>Controlling Header Pages</title> @@ -2582,7 +2582,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ header</emphasis>, a full page of large letters identifying the user, host, and job. Here is an example (kelly printed the job named outline from host <hostid>rose</hostid>):</para> - + <programlisting> k ll ll k l l k l l @@ -2636,13 +2636,13 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ new page (unless you have <literal>sf</literal> (suppress form feeds) in the destination printer's entry in <filename>/etc/printcap</filename>).</para> - - <para>If you prefer, <application>LPD</application> can make a + + <para>If you prefer, <application>LPD</application> can make a <emphasis>short header</emphasis>; specify <literal>sb</literal> (short banner) in the <filename>/etc/printcap</filename> file. The header page will look like this:</para> - + <programlisting>rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995</programlisting> <para>Also by default, <application>LPD</application> prints the @@ -2650,7 +2650,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ To reverse that, specify <literal>hl</literal> (header last) in <filename>/etc/printcap</filename>.</para> </sect3> - + <sect3 id="printing-advanced-header-pages-accounting"> <title>Accounting for Header Pages</title> @@ -2658,7 +2658,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ enforces a particular paradigm when it comes to printer accounting: header pages must be <emphasis>free of charge</emphasis>.</para> - + <para>Why?</para> <para>Because the output filter is the only external program that will @@ -2673,7 +2673,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ Basically, <command>lpr -h</command> will be the preferred option of environmentally-minded users, but you cannot offer any incentive to use it.</para> - + <para>It is <emphasis>still not enough</emphasis> to have each of the filters generate their own header pages (thereby being able to charge for them). If users wanted the option of suppressing the @@ -2691,17 +2691,17 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ <para>Accept <application>LPD</application>'s paradigm and make header pages free.</para> </listitem> - + <listitem> <para>Install an alternative to <application>LPD</application>, - such as + such as <application>LPRng</application>. Section <link linkend="printing-lpd-alternatives">Alternatives to the Standard Spooler</link> tells more about other spooling software you can substitute for <application>LPD</application>. </para> </listitem> - + <listitem> <para>Write a <emphasis>smart</emphasis> output filter. Normally, an output filter is not meant to do anything more than @@ -2727,24 +2727,24 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ </listitem> </itemizedlist> </sect3> - + <sect3 id="printing-advanced-header-pages-ps"> <title>Header Pages on &postscript; Printers</title> <para>As described above, <application>LPD</application> can generate a plain text header page suitable for many printers. Of course, &postscript; cannot directly - print plain text, so the header page feature of + print plain text, so the header page feature of <application>LPD</application> is useless—or mostly so.</para> - + <para>One obvious way to get header pages is to have every conversion filter and the text filter generate the header page. The filters should use the user and host arguments to generate a suitable header page. The drawback of this method is that users will always get a header page, even if they submit jobs with <command>lpr -h</command>.</para> - + <para>Let us explore this method. The following script takes three arguments (user login name, host name, and job name) and makes a simple &postscript; header page:</para> @@ -2841,7 +2841,7 @@ EOF</programlisting> # # Invoked by lpd when user runs lpr -d # - + orig_args="$@" fail() { @@ -2872,36 +2872,36 @@ done different set of arguments, though (see section <link linkend="printing-advanced-filters">How Filters Work</link>).</para> - + <para>As we have mentioned before, the above scheme, though fairly simple, disables the <quote>suppress header page</quote> option (the <option>-h</option> option) to <command>lpr</command>. If users wanted to save a tree (or a few pennies, if you charge for header pages), they would not be able to do so, since every filter's going to print a header page with every job.</para> - + <para>To allow users to shut off header pages on a per-job basis, you will need to use the trick introduced in section <link linkend="printing-advanced-header-pages-accounting">Accounting for Header Pages</link>: write an output filter that parses the LPD-generated header page and produces a &postscript; version. If the - user submits the job with <command>lpr -h</command>, then + user submits the job with <command>lpr -h</command>, then <application>LPD</application> will not generate a header page, and neither will your output filter. - Otherwise, your output filter will read the text from + Otherwise, your output filter will read the text from <application>LPD</application> and send the appropriate header page &postscript; code to the printer.</para> - + <para>If you have a &postscript; printer on a serial line, you can make use of <command>lprps</command>, which comes with an output filter, <command>psof</command>, which does the above. Note that <command>psof</command> does not charge for header pages.</para> </sect3> </sect2> - + <sect2 id="printing-advanced-network-printers"> <title>Networked Printing</title> - + <indexterm> <primary>printers</primary> <secondary>network</secondary> @@ -2910,12 +2910,12 @@ done <para>FreeBSD supports networked printing: sending jobs to remote printers. Networked printing generally refers to two different things:</para> - + <itemizedlist> <listitem> <para>Accessing a printer attached to a remote host. You install a printer that has a conventional serial or parallel interface on - one host. Then, you set up <application>LPD</application> to + one host. Then, you set up <application>LPD</application> to enable access to the printer from other hosts on the network. Section <link linkend="printing-advanced-network-rm">Printers Installed on @@ -2927,19 +2927,19 @@ done printer has a network interface in addition (or in place of) a more conventional serial or parallel interface. Such a printer might work as follows:</para> - + <itemizedlist> <listitem> <para>It might understand the <application>LPD</application> protocol and can even queue jobs from remote hosts. In this case, it acts just like a - regular host running <application>LPD</application>. Follow + regular host running <application>LPD</application>. Follow the same procedure in section <link linkend="printing-advanced-network-rm">Printers Installed on Remote Hosts</link> to set up such a printer.</para> </listitem> - + <listitem> <para>It might support a data stream network connection. In this case, you <quote>attach</quote> the printer to one host on the @@ -2952,40 +2952,40 @@ done </itemizedlist> </listitem> </itemizedlist> - + <sect3 id="printing-advanced-network-rm"> <title>Printers Installed on Remote Hosts</title> <para>The <application>LPD</application> spooling system has built-in support for sending jobs to - other hosts also running <application>LPD</application> (or are + other hosts also running <application>LPD</application> (or are compatible with <application>LPD</application>). This feature enables you to install a printer on one host and make it accessible from other hosts. It also works with printers that have - network interfaces that understand the + network interfaces that understand the <application>LPD</application> protocol.</para> - + <para>To enable this kind of remote printing, first install a printer on one host, the <emphasis>printer host</emphasis>, using the simple printer setup described in the <link linkend="printing-simple">Simple Printer Setup</link> section. Do any advanced setup in <link linkend="printing-advanced">Advanced Printer Setup</link> that you need. Make sure to test the printer and see if it works with the - features of <application>LPD</application> you have enabled. + features of <application>LPD</application> you have enabled. Also ensure that the - <emphasis>local host</emphasis> has authorization to use the + <emphasis>local host</emphasis> has authorization to use the <application>LPD</application> service in the <emphasis>remote host</emphasis> (see <link linkend="printing-advanced-restricting-remote">Restricting Jobs from Remote Printers</link>).</para> - + <indexterm> <primary>printers</primary> <secondary>network</secondary> </indexterm> <indexterm><primary>network printing</primary></indexterm> <para>If you are using a printer with a network interface that is - compatible with <application>LPD</application>, then the + compatible with <application>LPD</application>, then the <emphasis>printer host</emphasis> in the discussion below is the printer itself, and the <emphasis>printer name</emphasis> is the name you configured for the @@ -2998,7 +2998,7 @@ done CRLF conversion for you, so you will not require the <filename>hpif</filename> script.</para> </tip> - + <para>Then, on the other hosts you want to have access to the printer, make an entry in their <filename>/etc/printcap</filename> files with the following:</para> @@ -3009,24 +3009,24 @@ done you probably want to use the same name and aliases as on the printer host.</para> </listitem> - + <listitem> <para>Leave the <literal>lp</literal> capability blank, explicitly (<literal>:lp=:</literal>).</para> </listitem> - + <listitem> <para>Make a spooling directory and specify its location in the <literal>sd</literal> capability. <application>LPD</application> will store jobs here before they get sent to the printer host.</para> </listitem> - + <listitem> <para>Place the name of the printer host in the <literal>rm</literal> capability.</para> </listitem> - + <listitem> <para>Place the printer name on the <emphasis>printer host</emphasis> in the <literal>rp</literal> @@ -3076,29 +3076,29 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ <para>Then, we just need to make spooling directories on <hostid>orchid</hostid>:</para> - + <screen>&prompt.root; <userinput>mkdir -p /var/spool/lpd/rattan /var/spool/lpd/bamboo</userinput> &prompt.root; <userinput>chmod 770 /var/spool/lpd/rattan /var/spool/lpd/bamboo</userinput> &prompt.root; <userinput>chown daemon:daemon /var/spool/lpd/rattan /var/spool/lpd/bamboo</userinput></screen> - + <para>Now, users on <hostid>orchid</hostid> can print to <literal>rattan</literal> and <literal>bamboo</literal>. If, for example, a user on <hostid>orchid</hostid> typed - + <screen>&prompt.user; <userinput>lpr -P bamboo -d sushi-review.dvi</userinput></screen> the <application>LPD</application> system on <hostid>orchid</hostid> would copy the job to the spooling directory <filename>/var/spool/lpd/bamboo</filename> and note that it was a DVI job. As soon as the host <hostid>rose</hostid> has room in its - <literal>bamboo</literal> spooling directory, the two + <literal>bamboo</literal> spooling directory, the two <application>LPDs</application> would transfer the file to <hostid>rose</hostid>. The file would wait in <hostid>rose</hostid>'s queue until it was finally printed. It would be converted from DVI to &postscript; (since <literal>bamboo</literal> is a &postscript; printer) on <hostid>rose</hostid>.</para> </sect3> - + <sect3 id="printing-advanced-network-net-if"> <title>Printers with Networked Data Stream Interfaces</title> @@ -3110,14 +3110,14 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ expensive one, see the previous section <link linkend="printing-advanced-network-rm">Printers Installed on Remote Hosts</link>.</para> - + <para>The format of the <filename>/etc/printcap</filename> file lets you specify what serial or parallel interface to use, and (if you are using a serial interface), what baud rate, whether to use flow control, delays for tabs, conversion of newlines, and more. But there is no way to specify a connection to a printer that is listening on a TCP/IP or other network port.</para> - + <para>To send data to a networked printer, you need to develop a communications program that can be called by the text and conversion filters. Here is one such example: the script @@ -3153,7 +3153,7 @@ socket(PRINTER, &PF_INET, &SOCK_STREAM, $protocol) connect(PRINTER, $sockaddr) || die "Can't contact $printer_host: $!"; while (<STDIN>) { print PRINTER; } exit 0;</programlisting> - + <para>We can then use this script in various filters. Suppose we had a Diablo 750-N line printer connected to the network. The printer accepts data to print on port number 5100. The host name of the @@ -3168,10 +3168,10 @@ exit 0;</programlisting> exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100</programlisting> </sect3> </sect2> - + <sect2 id="printing-advanced-restricting"> <title>Restricting Printer Usage</title> - + <indexterm> <primary>printers</primary> <secondary>restricting access to</secondary> @@ -3181,7 +3181,7 @@ exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100</pro a printer, both locally or remotely, whether they can print multiple copies, how large their jobs can be, and how large the printer queues can get.</para> - + <sect3 id="printing-advanced-restricting-copies"> <title>Restricting Multiple Copies</title> @@ -3190,13 +3190,13 @@ exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100</pro of a file. Users can print jobs with <command>lpr -#5</command> (for example) and get five copies of each file in the job. Whether this is a good thing is up to you.</para> - + <para>If you feel multiple copies cause unnecessary wear and tear on your printers, you can disable the <option>-#</option> option to &man.lpr.1; by adding the <literal>sc</literal> capability to the <filename>/etc/printcap</filename> file. When users submit jobs with the <option>-#</option> option, they will see:</para> - + <screen>lpr: multiple copies are not allowed</screen> @@ -3229,7 +3229,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:rw:\ :if=/usr/local/libexec/psif:\ :df=/usr/local/libexec/psdf:</programlisting> - + <para>Now, we also need to add the <literal>sc</literal> capability on the host <hostid>orchid</hostid>'s <filename>/etc/printcap</filename> (and while we are at it, let us @@ -3250,19 +3250,19 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ :lp=:rm=rose:rp=bamboo:sd=/var/spool/lpd/bamboo:sc:</programlisting> - + <para>By using the <literal>sc</literal> capability, we prevent the use of <command>lpr -#</command>, but that still does not prevent users from running &man.lpr.1; multiple times, or from submitting the same file multiple times in one job like this:</para> - + <screen>&prompt.user; <userinput>lpr forsale.sign forsale.sign forsale.sign forsale.sign forsale.sign</userinput></screen> - + <para>There are many ways to prevent this abuse (including ignoring it) which you are free to explore.</para> </sect3> - + <sect3 id="printing-advanced-restricting-access"> <title>Restricting Access to Printers</title> @@ -3271,12 +3271,12 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ <filename>/etc/printcap</filename>. Just place the users you want to have access to a printer in a certain group, and then name that group in the <literal>rg</literal> capability.</para> - + <para>Users outside the group (including <username>root</username>) will be greeted with - + <errorname>lpr: Not a member of the restricted group</errorname> - + if they try to print to the controlled printer.</para> <para>As with the <literal>sc</literal> (suppress multiple copies) @@ -3285,7 +3285,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ appropriate (see section <link linkend="printing-advanced-network-rm">Printers Installed on Remote Hosts</link>).</para> - + <para>For example, we will let anyone access the printer <literal>rattan</literal>, but only those in group <literal>artists</literal> can use <literal>bamboo</literal>. Here @@ -3318,7 +3318,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ <para>There can be only one restricted group per printer.</para> </note> </sect3> - + <sect3 id="printing-advanced-restricting-sizes"> <title>Controlling Sizes of Jobs Submitted</title> @@ -3328,7 +3328,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ print. After all, there is only so much free space on the filesystem that houses the spooling directories, and you also need to make sure there is room for the jobs of other users.</para> - + <indexterm> <primary>print jobs</primary> <secondary>controlling</secondary> @@ -3353,7 +3353,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ to the limit, which will then get printed. The rest will be discarded. Whether this is correct behavior is up for debate.</para> - + <para>Let us add limits to our example printers <literal>rattan</literal> and <literal>bamboo</literal>. Since those artists' &postscript; files tend to be large, we will limit them @@ -3389,26 +3389,26 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ linkend="printing-advanced-network-rm">Printers Installed on Remote Hosts</link> for more information on remote printing.</para> - + <para>There is another specialized way to limit job sizes from remote printers; see section <link linkend="printing-advanced-restricting-remote">Restricting Jobs from Remote Printers</link>.</para> </sect3> - + <sect3 id="printing-advanced-restricting-remote"> <title>Restricting Jobs from Remote Printers</title> - <para>The <application>LPD</application> spooling system provides + <para>The <application>LPD</application> spooling system provides several ways to restrict print jobs submitted from remote hosts:</para> - + <variablelist> <varlistentry> <term>Host restrictions</term> <listitem> - <para>You can control from which remote hosts a local + <para>You can control from which remote hosts a local <application>LPD</application> accepts requests with the files <filename>/etc/hosts.equiv</filename> and <filename>/etc/hosts.lpd</filename>. @@ -3416,13 +3416,13 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ incoming request is from a host listed in either one of these files. If not, <application>LPD</application> refuses the request.</para> - + <para>The format of these files is simple: one host name per line. Note that the file <filename>/etc/hosts.equiv</filename> is also used by the &man.ruserok.3; protocol, and affects programs like &man.rsh.1; and &man.rcp.1;, so be careful.</para> - + <para>For example, here is the <filename>/etc/hosts.lpd</filename> file on the host <hostid>rose</hostid>:</para> @@ -3438,10 +3438,10 @@ madrigal.fishbaum.de</programlisting> <application>LPD</application>, the job will be refused.</para> </listitem> </varlistentry> - + <varlistentry> <term>Size restrictions</term> - + <listitem> <para>You can control how much free space there needs to remain on the filesystem where a spooling directory resides. Make a @@ -3449,19 +3449,19 @@ madrigal.fishbaum.de</programlisting> directory for the local printer. Insert in that file a number representing how many disk blocks (512 bytes) of free space there has to be for a remote job to be accepted.</para> - + <para>This lets you insure that remote users will not fill your filesystem. You can also use it to give a certain priority to local users: they will be able to queue jobs long after the free disk space has fallen below the amount specified in the <filename>minfree</filename> file.</para> - + <para>For example, let us add a <filename>minfree</filename> file for the printer <literal>bamboo</literal>. We examine <filename>/etc/printcap</filename> to find the spooling directory for this printer; here is <literal>bamboo</literal>'s entry:</para> - + <programlisting>bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ :sh:sd=/var/spool/lpd/bamboo:sc:rg=artists:mx#5000:\ :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:rw:mx#5000:\ @@ -3472,15 +3472,15 @@ madrigal.fishbaum.de</programlisting> capability. We will make three megabytes (which is 6144 disk blocks) the amount of free disk space that must exist on the filesystem for <application>LPD</application> to accept remote jobs:</para> - + <screen>&prompt.root; <userinput>echo 6144 > /var/spool/lpd/bamboo/minfree </userinput></screen> </listitem> </varlistentry> - + <varlistentry> <term>User restrictions</term> - + <listitem> <para>You can control which remote users can print to local printers by specifying the <literal>rs</literal> capability in @@ -3491,7 +3491,7 @@ madrigal.fishbaum.de</programlisting> hosts <emphasis>if</emphasis> the user submitting the job also has an account of the same login name on the local host. Otherwise, <application>LPD</application> refuses the job.</para> - + <para>This capability is particularly useful in an environment where there are (for example) different departments sharing a network, and some users transcend departmental boundaries. By @@ -3506,10 +3506,10 @@ madrigal.fishbaum.de</programlisting> </variablelist> </sect3> </sect2> - + <sect2 id="printing-advanced-acct"> <title>Accounting for Printer Usage</title> - + <indexterm> <primary>accounting</primary> <secondary>printer</secondary> @@ -3520,23 +3520,23 @@ madrigal.fishbaum.de</programlisting> your printers, usage patterns, and maintenance fees and have come up with a per-page (or per-foot, per-meter, or per-whatever) cost. Now, how do you actually start accounting for printouts?</para> - + <para>Well, the bad news is the <application>LPD</application> spooling system does not provide much help in this department. Accounting is highly dependent on the kind of printer in use, the formats being printed, and <emphasis>your</emphasis> requirements in charging for printer usage.</para> - + <para>To implement accounting, you have to modify a printer's text filter (to charge for plain text jobs) and the conversion filters (to charge for other file formats), to count pages or query the printer for pages printed. You cannot get away with using the simple output filter, since it cannot do accounting. See section <link linkend="printing-advanced-filter-intro">Filters</link>.</para> - + <para>Generally, there are two ways to do accounting:</para> - + <itemizedlist> <listitem> <para><emphasis>Periodic accounting</emphasis> is the more common @@ -3548,7 +3548,7 @@ madrigal.fishbaum.de</programlisting> for usage. Then you truncate all the logging files, starting with a clean slate for the next period.</para> </listitem> - + <listitem> <para><emphasis>Timely accounting</emphasis> is less common, probably because it is more difficult. This method has the @@ -3560,8 +3560,8 @@ madrigal.fishbaum.de</programlisting> code to track users and their quotas.</para> </listitem> </itemizedlist> - - <para>The <application>LPD</application> spooling system supports both + + <para>The <application>LPD</application> spooling system supports both methods easily: since you have to provide the filters (well, most of the time), you also have to provide the accounting code. But there is a bright side: you have @@ -3571,7 +3571,7 @@ madrigal.fishbaum.de</programlisting> square footage of paper used, how long the job took to print, and so forth. And you do so by modifying the filters to save this information.</para> - + <sect3> <title>Quick and Dirty Printer Accounting</title> @@ -3583,7 +3583,7 @@ madrigal.fishbaum.de</programlisting> entries from printer accounting files.</para> <para>As mentioned in the section on filters (<link - linkend="printing-advanced-filters">Filters</link>), + linkend="printing-advanced-filters">Filters</link>), <application>LPD</application> starts the text and the conversion filters with the name of the accounting file to use on the filter command line. The filters can use this @@ -3605,7 +3605,7 @@ madrigal.fishbaum.de</programlisting> 3.00 orchid:mary 5.00 orchid:mary 2.00 orchid:zhang</programlisting> - + <para>You should use a separate accounting file for each printer, as <command>lpf</command> has no file locking logic built into it, and two <command>lpf</command>s might corrupt each other's entries if @@ -3614,12 +3614,12 @@ madrigal.fishbaum.de</programlisting> <literal>af=acct</literal> in <filename>/etc/printcap</filename>. Then, each accounting file will be in the spooling directory for a printer, in a file named <filename>acct</filename>.</para> - + <para>When you are ready to charge users for printouts, run the &man.pac.8; program. Just change to the spooling directory for the printer you want to collect on and type <literal>pac</literal>. You will get a dollar-centric summary like the following:</para> - + <screen> Login pages/feet runs price orchid:kelly 5.00 1 $ 0.10 orchid:mary 31.00 3 $ 0.62 @@ -3630,7 +3630,7 @@ rose:mary 87.00 32 $ 1.74 rose:root 26.00 12 $ 0.52 total 337.00 154 $ 6.74</screen> - + <para>These are the arguments &man.pac.8; expects:</para> <variablelist> @@ -3644,19 +3644,19 @@ total 337.00 154 $ 6.74</screen> <filename>/etc/printcap</filename>.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-c</option></term> - + <listitem> <para>Sort the output by cost instead of alphabetically by user name.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-m</option></term> - + <listitem> <para>Ignore host name in the accounting files. With this option, user <username>smith</username> on host @@ -3665,10 +3665,10 @@ total 337.00 154 $ 6.74</screen> Without, they are different users.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-p<replaceable>price</replaceable></option></term> - + <listitem> <para>Compute charges with <replaceable>price</replaceable> dollars per page or per foot instead of the price from the @@ -3678,28 +3678,28 @@ total 337.00 154 $ 6.74</screen> a floating point number.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-r</option></term> - + <listitem> <para>Reverse the sort order.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-s</option></term> - + <listitem> <para>Make an accounting summary file and truncate the accounting file.</para> </listitem> </varlistentry> - + <varlistentry> <term><replaceable>name</replaceable> <replaceable>…</replaceable></term> - + <listitem> <para>Print accounting information for the given user <replaceable>names</replaceable> only.</para> @@ -3712,7 +3712,7 @@ total 337.00 154 $ 6.74</screen> your site, host does not matter (because users can use any host), run <command>pac -m</command>, to produce the following summary:</para> - + <screen> Login pages/feet runs price andy 2.00 1 $ 0.04 kelly 182.00 105 $ 3.64 @@ -3721,7 +3721,7 @@ root 26.00 12 $ 0.52 zhang 9.00 1 $ 0.18 total 337.00 154 $ 6.74</screen> - + <para>To compute the dollar amount due, &man.pac.8; uses the <literal>pc</literal> capability in the @@ -3732,9 +3732,9 @@ total 337.00 154 $ 6.74</screen> <option>-p</option> option. The units for the <option>-p</option> option are in dollars, though, not hundredths of cents. For example, - + <screen>&prompt.root; <userinput>pac -p1.50</userinput></screen> - + makes each page cost one dollar and fifty cents. You can really rake in the profits by using this option.</para> @@ -3746,26 +3746,26 @@ total 337.00 154 $ 6.74</screen> summary file to get starting totals, then adds information from the regular accounting file.</para> </sect3> - + <sect3> <title>How Can You Count Pages Printed?</title> <para>In order to perform even remotely accurate accounting, you need to be able to determine how much paper a job uses. This is the essential problem of printer accounting.</para> - + <para>For plain text jobs, the problem is not that hard to solve: you count how many lines are in a job and compare it to how many lines per page your printer supports. Do not forget to take into account backspaces in the file which overprint lines, or long logical lines that wrap onto one or more additional physical lines.</para> - + <para>The text filter <command>lpf</command> (introduced in <link linkend="printing-advanced-lpf">lpf: a Text Filter</link>) takes into account these things when it does accounting. If you are writing a text filter which needs to do accounting, you might want to examine <command>lpf</command>'s source code.</para> - + <para>How do you handle other file formats, though?</para> <para>Well, for DVI-to-LaserJet or DVI-to-&postscript; conversion, you @@ -3778,7 +3778,7 @@ total 337.00 154 $ 6.74</screen> actually print all those pages. For example, it could jam, run out of toner, or explode—and the user would still get charged.</para> - + <para>So, what can you do?</para> <para>There is only one <emphasis>sure</emphasis> way to do @@ -3791,7 +3791,7 @@ total 337.00 154 $ 6.74</screen> accounting information based on that value <emphasis>only</emphasis>. There is no line counting nor error-prone file examination required.</para> - + <para>Of course, you can always be generous and make all printouts free.</para> </sect3> @@ -3800,7 +3800,7 @@ total 337.00 154 $ 6.74</screen> <sect1 id="printing-using"> <title>Using Printers</title> - + <indexterm> <primary>printers</primary> <secondary>usage</secondary> @@ -3816,7 +3816,7 @@ total 337.00 154 $ 6.74</screen> <para>Print jobs</para> </listitem> </varlistentry> - + <varlistentry> <term>&man.lpq.1;</term> @@ -3824,7 +3824,7 @@ total 337.00 154 $ 6.74</screen> <para>Check printer queues</para> </listitem> </varlistentry> - + <varlistentry> <term>&man.lprm.1;</term> @@ -3833,7 +3833,7 @@ total 337.00 154 $ 6.74</screen> </listitem> </varlistentry> </variablelist> - + <para>There is also an administrative command, &man.lpc.8;, described in the section <link linkend="printing-lpc">Administering Printers</link>, used to @@ -3854,14 +3854,14 @@ total 337.00 154 $ 6.74</screen> means the printer named in the <envar>PRINTER</envar> environment variable, or the printer named <literal>lp</literal> when there is no <envar>PRINTER</envar> environment variable.</para> - + <sect2 id="printing-lpr"> <title>Printing Jobs</title> - + <para>To print files, type:</para> - + <screen>&prompt.user; <userinput>lpr <replaceable>filename</replaceable> <replaceable>...</replaceable></userinput></screen> - + <indexterm><primary>printing</primary></indexterm> <para>This prints each of the listed files to the default printer. If you list no files, &man.lpr.1; reads data to @@ -3869,34 +3869,34 @@ total 337.00 154 $ 6.74</screen> important system files:</para> <screen>&prompt.user; <userinput>lpr /etc/host.conf /etc/hosts.equiv</userinput></screen> - + <para>To select a specific printer, type:</para> - + <screen>&prompt.user; <userinput>lpr -P <replaceable>printer-name</replaceable> <replaceable>filename</replaceable> <replaceable>...</replaceable></userinput></screen> <para>This example prints a long listing of the current directory to the printer named <literal>rattan</literal>:</para> - + <screen>&prompt.user; <userinput>ls -l | lpr -P rattan</userinput></screen> - + <para>Because no files were listed for the &man.lpr.1; command, <command>lpr</command> read the data to print from standard input, which was the output of the <command>ls -l</command> command.</para> - + <para>The &man.lpr.1; command can also accept a wide variety of options to control formatting, apply file conversions, generate multiple copies, and so forth. For more information, see the section <link linkend="printing-lpr-options">Printing Options</link>.</para> </sect2> - + <sect2 id="printing-lpq"> <title>Checking Jobs</title> - + <indexterm><primary>print jobs</primary></indexterm> <para>When you print with &man.lpr.1;, the data you wish to print is put together in a package called a <quote>print job</quote>, which is sent - to the <application>LPD</application> spooling system. Each printer + to the <application>LPD</application> spooling system. Each printer has a queue of jobs, and your job waits in that queue along with other jobs from yourself and from other users. The printer prints those jobs in a first-come, @@ -3911,20 +3911,20 @@ total 337.00 154 $ 6.74</screen> shows the queue for the printer named <literal>bamboo</literal>. Here is an example of the output of the <command>lpq</command> command:</para> - + <screen>bamboo is ready and printing Rank Owner Job Files Total Size active kelly 9 /etc/host.conf, /etc/hosts.equiv 88 bytes 2nd kelly 10 (standard input) 1635 bytes 3rd mary 11 ... 78519 bytes</screen> - + <para>This shows three jobs in the queue for <literal>bamboo</literal>. The first job, submitted by user kelly, got assigned <quote>job number</quote> 9. Every job for a printer gets a unique job number. Most of the time you can ignore the job number, but you will need it if you want to cancel the job; see section <link linkend="printing-lprm">Removing Jobs</link> for details.</para> - + <para>Job number nine consists of two files; multiple files given on the &man.lpr.1; command line are treated as part of a single job. It is the currently active job (note the word <literal>active</literal> @@ -3936,13 +3936,13 @@ active kelly 9 /etc/host.conf, /etc/hosts.equiv 88 bytes fit, so the &man.lpq.1; command just shows three dots.</para> <para>The very first line of the output from &man.lpq.1; is also useful: - it tells what the printer is currently doing (or at least what + it tells what the printer is currently doing (or at least what <application>LPD</application> thinks the printer is doing).</para> <para>The &man.lpq.1; command also support a <option>-l</option> option to generate a detailed long listing. Here is an example of <command>lpq -l</command>:</para> - + <screen>waiting for bamboo to become ready (offline ?) kelly: 1st [job 009rose] /etc/host.conf 73 bytes @@ -3957,25 +3957,25 @@ mary: 3rd [job 011rose] <sect2 id="printing-lprm"> <title>Removing Jobs</title> - + <para>If you change your mind about printing a job, you can remove the job from the queue with the &man.lprm.1; command. Often, you can even use &man.lprm.1; to remove an active job, but some or all of the job might still get printed.</para> - + <para>To remove a job from the default printer, first use &man.lpq.1; to find the job number. Then type:</para> - + <screen>&prompt.user; <userinput>lprm <replaceable>job-number</replaceable></userinput></screen> - + <para>To remove the job from a specific printer, add the <option>-P</option> option. The following command removes job number 10 from the queue for the printer <literal>bamboo</literal>:</para> - + <screen>&prompt.user; <userinput>lprm -P bamboo 10</userinput></screen> - + <para>The &man.lprm.1; command has a few shortcuts:</para> - + <variablelist> <varlistentry> <term>lprm -</term> @@ -3988,7 +3988,7 @@ mary: 3rd [job 011rose] <varlistentry> <term>lprm <replaceable>user</replaceable></term> - + <listitem> <para>Removes all jobs (for the default printer) belonging to <replaceable>user</replaceable>. The superuser can remove other @@ -3998,7 +3998,7 @@ mary: 3rd [job 011rose] <varlistentry> <term>lprm</term> - + <listitem> <para>With no job number, user name, or <option>-</option> appearing on the command line, @@ -4008,21 +4008,21 @@ mary: 3rd [job 011rose] </listitem> </varlistentry> </variablelist> - + <para>Just use the <option>-P</option> option with the above shortcuts to operate on a specific printer instead of the default. For example, the following command removes all jobs for the current user in the queue for the printer named <literal>rattan</literal>:</para> - + <screen>&prompt.user; <userinput>lprm -P rattan -</userinput></screen> - + <note> <para>If you are working in a networked environment, &man.lprm.1; will let you remove jobs only from the host from which the jobs were submitted, even if the same printer is available from other hosts. The following command sequence demonstrates this:</para> - + <screen>&prompt.user; <userinput>lpr -P rattan myfile</userinput> &prompt.user; <userinput>rlogin orchid</userinput> &prompt.user; <userinput>lpq -P rattan</userinput> @@ -4038,15 +4038,15 @@ cfA013rose dequeued </screen> </note> </sect2> - + <sect2 id="printing-lpr-options"> <title>Beyond Plain Text: Printing Options</title> - + <para>The &man.lpr.1; command supports a number of options that control formatting text, converting graphic and other file formats, producing multiple copies, handling of the job, and more. This section describes the options.</para> - + <sect3 id="printing-lpr-options-format"> <title>Formatting and Conversion Options</title> @@ -4054,14 +4054,14 @@ cfA013rose dequeued files in the job. Use these options if the job does not contain plain text or if you want plain text formatted through the &man.pr.1; utility.</para> - + <indexterm><primary>&tex;</primary></indexterm> <para>For example, the following command prints a DVI file (from the &tex; typesetting system) named <filename>fish-report.dvi</filename> to the printer named <literal>bamboo</literal>:</para> - + <screen>&prompt.user; <userinput>lpr -P bamboo -d fish-report.dvi</userinput></screen> - + <para>These options apply to every file in the job, so you cannot mix (say) DVI and ditroff files together in a job. Instead, submit the files as separate jobs, using a different conversion option for each @@ -4084,34 +4084,34 @@ cfA013rose dequeued <para>Print cifplot files.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-d</option></term> - + <listitem> <para>Print DVI files.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-f</option></term> - + <listitem> <para>Print FORTRAN text files.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-g</option></term> - + <listitem> <para>Print plot data.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-i <replaceable>number</replaceable></option></term> - + <listitem> <para>Indent the output by <replaceable>number</replaceable> columns; if you omit <replaceable>number</replaceable>, indent @@ -4124,36 +4124,36 @@ cfA013rose dequeued </note> </listitem> </varlistentry> - + <varlistentry> <term><option>-l</option></term> - + <listitem> <para>Print literal text data, including control characters.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-n</option></term> - + <listitem> <para>Print ditroff (device independent troff) data.</para> </listitem> </varlistentry> - + <varlistentry> <term>-p</term> - + <listitem> <para>Format plain text with &man.pr.1; before printing. See &man.pr.1; for more information.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-T <replaceable>title</replaceable></option></term> - + <listitem> <para>Use <replaceable>title</replaceable> on the &man.pr.1; header instead of the file name. This option has @@ -4161,47 +4161,47 @@ cfA013rose dequeued option.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-t</option></term> - + <listitem> <para>Print troff data.</para> </listitem> </varlistentry> - + <varlistentry> <term><option>-v</option></term> - + <listitem> <para>Print raster data.</para> </listitem> </varlistentry> </variablelist> - + <para>Here is an example: this command prints a nicely formatted version of the &man.ls.1; manual page on the default printer:</para> - + <screen>&prompt.user; <userinput>zcat /usr/share/man/man1/ls.1.gz | troff -t -man | lpr -t</userinput></screen> - + <para>The &man.zcat.1; command uncompresses the source of the &man.ls.1; manual page and passes it to the &man.troff.1; command, which formats that source and makes GNU troff output and passes it to &man.lpr.1;, which submits the job - to the <application>LPD</application> spooler. Because we + to the <application>LPD</application> spooler. Because we used the <option>-t</option> option to &man.lpr.1;, the spooler will convert the GNU troff output into a format the default printer can understand when it prints the job.</para> </sect3> - + <sect3 id="printing-lpr-options-job-handling"> <title>Job Handling Options</title> - <para>The following options to &man.lpr.1; tell + <para>The following options to &man.lpr.1; tell <application>LPD</application> to handle the job specially:</para> - + <variablelist> <varlistentry> <term>-# <replaceable>copies</replaceable></term> @@ -4218,14 +4218,14 @@ cfA013rose dequeued <para>This example prints three copies of <filename>parser.c</filename> followed by three copies of <filename>parser.h</filename> to the default printer:</para> - + <screen>&prompt.user; <userinput>lpr -#3 parser.c parser.h</userinput></screen> </listitem> </varlistentry> - + <varlistentry> <term>-m</term> - + <listitem> <para>Send mail after completing the print job. With this option, the <application>LPD</application> system will send @@ -4235,29 +4235,29 @@ cfA013rose dequeued and (often) what the error was.</para> </listitem> </varlistentry> - + <varlistentry> <term>-s</term> - + <listitem> <para>Do not copy the files to the spooling directory, but make symbolic links to them instead.</para> - + <para>If you are printing a large job, you probably want to use this option. It saves space in the spooling directory (your job might overflow the free space on the filesystem where the - spooling directory resides). It saves time as well since + spooling directory resides). It saves time as well since <application>LPD</application> will not have to copy each and every byte of your job to the spooling directory.</para> - - <para>There is a drawback, though: since + + <para>There is a drawback, though: since <application>LPD</application> will refer to the original files directly, you cannot modify or remove them until they have been printed.</para> - + <note> - <para>If you are printing to a remote printer, + <para>If you are printing to a remote printer, <application>LPD</application> will eventually have to copy files from the local host to the remote host, so the <option>-s</option> option will save @@ -4266,10 +4266,10 @@ cfA013rose dequeued </note> </listitem> </varlistentry> - + <varlistentry> <term>-r</term> - + <listitem> <para>Remove the files in the job after copying them to the spooling directory, or after printing them with the @@ -4279,7 +4279,7 @@ cfA013rose dequeued </varlistentry> </variablelist> </sect3> - + <sect3 id="printing-lpr-options-misc"> <title>Header Page Options</title> @@ -4288,7 +4288,7 @@ cfA013rose dequeued the destination printer, these options have no effect. See section <link linkend="printing-advanced-header-pages">Header Pages</link> for information about setting up header pages.</para> - + <variablelist> <varlistentry> <term>-C <replaceable>text</replaceable></term> @@ -4299,10 +4299,10 @@ cfA013rose dequeued name of the host from which the job was submitted.</para> </listitem> </varlistentry> - + <varlistentry> <term>-J <replaceable>text</replaceable></term> - + <listitem> <para>Replace the job name on the header page with <replaceable>text</replaceable>. The job name is normally the @@ -4311,13 +4311,13 @@ cfA013rose dequeued input.</para> </listitem> </varlistentry> - + <varlistentry> <term>-h</term> - + <listitem> <para>Do not print any header page.</para> - + <note> <para>At some sites, this option may have no effect due to the way header pages are generated. See <link @@ -4329,15 +4329,15 @@ cfA013rose dequeued </variablelist> </sect3> </sect2> - + <sect2 id="printing-lpc"> <title>Administering Printers</title> - + <para>As an administrator for your printers, you have had to install, set up, and test them. Using the &man.lpc.8; command, you can interact with your printers in yet more ways. With &man.lpc.8;, you can</para> - + <itemizedlist> <listitem> <para>Start and stop the printers</para> @@ -4351,20 +4351,20 @@ cfA013rose dequeued <para>Rearrange the order of the jobs in each queue.</para> </listitem> </itemizedlist> - + <para>First, a note about terminology: if a printer is <emphasis>stopped</emphasis>, it will not print anything in its queue. Users can still submit jobs, which will wait in the queue until the printer is <emphasis>started</emphasis> or the queue is cleared.</para> - + <para>If a queue is <emphasis>disabled</emphasis>, no user (except <username>root</username>) can submit jobs for the printer. An <emphasis>enabled</emphasis> queue allows jobs to be submitted. A printer can be <emphasis>started</emphasis> for a disabled queue, in which case it will continue to print jobs in the queue until the queue is empty.</para> - + <para>In general, you have to have <username>root</username> privileges to use the &man.lpc.8; command. Ordinary users can use the &man.lpc.8; command to get printer status and to restart a hung printer only.</para> @@ -4374,7 +4374,7 @@ cfA013rose dequeued tell on which printer to operate. You can use <literal>all</literal> for the <replaceable>printer-name</replaceable> to mean all printers listed in <filename>/etc/printcap</filename>.</para> - + <variablelist> <varlistentry> <term><command>abort @@ -4389,11 +4389,11 @@ cfA013rose dequeued <varlistentry> <term><command>clean <replaceable>printer-name</replaceable></command></term> - + <listitem> <para>Remove old files from the printer's spooling directory. Occasionally, the files that make up a job are not properly - removed by <application>LPD</application>, particularly if + removed by <application>LPD</application>, particularly if there have been errors during printing or a lot of administrative activity. This command finds files that do not belong in the spooling directory and @@ -4404,13 +4404,13 @@ cfA013rose dequeued <varlistentry> <term><command>disable <replaceable>printer-name</replaceable></command></term> - + <listitem> <para>Disable queuing of new jobs. If the printer is running, it will continue to print any jobs remaining in the queue. The superuser (<username>root</username>) can always submit jobs, even to a disabled queue.</para> - + <para>This command is useful while you are testing a new printer or filter installation: disable the queue and submit jobs as <username>root</username>. Other users will not be able to submit @@ -4422,7 +4422,7 @@ cfA013rose dequeued <varlistentry> <term><command>down <replaceable>printer-name</replaceable> <replaceable>message</replaceable></command></term> - + <listitem> <para>Take a printer down. Equivalent to <command>disable</command> followed by <command>stop</command>. @@ -4436,7 +4436,7 @@ cfA013rose dequeued <varlistentry> <term><command>enable <replaceable>printer-name</replaceable></command></term> - + <listitem> <para>Enable the queue for a printer. Users can submit jobs but the printer will not print anything until it is started.</para> @@ -4446,7 +4446,7 @@ cfA013rose dequeued <varlistentry> <term><command>help <replaceable>command-name</replaceable></command></term> - + <listitem> <para>Print help on the command <replaceable>command-name</replaceable>. With no @@ -4458,10 +4458,10 @@ cfA013rose dequeued <varlistentry> <term><command>restart <replaceable>printer-name</replaceable></command></term> - + <listitem> <para>Start the printer. Ordinary users can use this command if - some extraordinary circumstance hangs + some extraordinary circumstance hangs <application>LPD</application>, but they cannot start a printer stopped with either the <command>stop</command> or <command>down</command> commands. The @@ -4474,7 +4474,7 @@ cfA013rose dequeued <varlistentry> <term><command>start <replaceable>printer-name</replaceable></command></term> - + <listitem> <para>Start the printer. The printer will print jobs in its queue.</para> @@ -4484,7 +4484,7 @@ cfA013rose dequeued <varlistentry> <term><command>stop <replaceable>printer-name</replaceable></command></term> - + <listitem> <para>Stop the printer. The printer will finish the current job and will not print anything else in its queue. Even though the @@ -4496,7 +4496,7 @@ cfA013rose dequeued <varlistentry> <term><command>topq <replaceable>printer-name</replaceable> <replaceable>job-or-username</replaceable></command></term> - + <listitem> <para>Rearrange the queue for <replaceable>printer-name</replaceable> by placing the jobs with @@ -4511,7 +4511,7 @@ cfA013rose dequeued <varlistentry> <term><command>up <replaceable>printer-name</replaceable></command></term> - + <listitem> <para>Bring a printer up; the opposite of the <command>down</command> command. Equivalent to @@ -4520,19 +4520,19 @@ cfA013rose dequeued </listitem> </varlistentry> </variablelist> - + <para>&man.lpc.8; accepts the above commands on the command line. If you do not enter any commands, &man.lpc.8; enters an interactive mode, where you can enter commands until you type <command>exit</command>, <command>quit</command>, or end-of-file.</para> </sect2> </sect1> - + <sect1 id="printing-lpd-alternatives"> <title>Alternatives to the Standard Spooler</title> - + <para>If you have been reading straight through this manual, by now you - have learned just about everything there is to know about the + have learned just about everything there is to know about the <application>LPD</application> spooling system that comes with FreeBSD. You can probably appreciate many of its shortcomings, which naturally leads to the question: @@ -4550,7 +4550,7 @@ cfA013rose dequeued <quote>LPR: the Next Generation</quote> is a complete rewrite of PLP. Patrick Powell and Justin Mason (the principal maintainer of PLP) collaborated to - make <application>LPRng</application>. The main site for + make <application>LPRng</application>. The main site for <application>LPRng</application> is <ulink url="http://www.lprng.org/"></ulink>.</para> </listitem> @@ -4815,7 +4815,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ <listitem> <para>If the printer supports carrier flow control, specify - the <literal>crtscts</literal> mode in the + the <literal>crtscts</literal> mode in the <literal>ms#</literal> capability. Make sure the cable connecting the printer to the computer is correctly wired for carrier flow control.</para> @@ -4865,7 +4865,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ see, try to correct the problem.</para> <para>If you do not specify a <literal>lf</literal> capability, - <application>LPD</application> uses + <application>LPD</application> uses <filename>/dev/console</filename> as a default.</para> </listitem> </varlistentry> diff --git a/pl_PL.ISO8859-2/books/handbook/security/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/security/chapter.sgml index c242bbce7d..2c66ec746f 100644 --- a/pl_PL.ISO8859-2/books/handbook/security/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/security/chapter.sgml @@ -70,7 +70,7 @@ <para>How to configure IPsec and create a <acronym>VPN</acronym> between &os;/&windows; machines.</para> </listitem> - + <listitem> <para>How to configure and use <application>OpenSSH</application>, &os;'s <acronym>SSH</acronym> implementation.</para> @@ -203,7 +203,7 @@ </indexterm> <para>A user account compromise is even more common than a DoS - attack. Many sysadmins still run standard + attack. Many sysadmins still run standard <application>telnetd</application>, <application>rlogind</application>, <application>rshd</application>, and <application>ftpd</application> servers on their machines. @@ -511,7 +511,7 @@ <application>rshd</application> or <application>rlogind</application>, then turn off those services!</para> - + <para>&os; now defaults to running <application>ntalkd</application>, <application>comsat</application>, and @@ -622,7 +622,7 @@ </indexterm> <para>But even if you turn off the <devicename>bpf</devicename> device, you still have - <filename>/dev/mem</filename> and + <filename>/dev/mem</filename> and <filename>/dev/kmem</filename> to worry about. For that matter, the intruder can still write to raw disk devices. Also, there is another kernel feature called @@ -710,7 +710,7 @@ <para>When using ssh rather than NFS, writing the security script is much more difficult. You - essentially have to <command>scp</command> the scripts to the client + essentially have to <command>scp</command> the scripts to the client box in order to run them, making them visible, and for safety you also need to <command>scp</command> the binaries (such as find) that those @@ -802,7 +802,7 @@ page carefully and pay specific attention to the <option>-c</option>, <option>-C</option>, and <option>-R</option> options. Note that spoofed-IP attacks - will circumvent the <option>-C</option> option to + will circumvent the <option>-C</option> option to <application>inetd</application>, so typically a combination of options must be used. Some standalone servers have self-fork-limitation parameters.</para> @@ -888,7 +888,7 @@ Use the <application>sysctl</application> variable <literal>net.inet.icmp.icmplim</literal> to limit these attacks. The last major class of springboard - attacks is related to certain internal + attacks is related to certain internal <application>inetd</application> services such as the udp echo service. An attacker simply spoofs a UDP packet with the source address being server A's echo port, and the destination @@ -896,7 +896,7 @@ on your LAN. The two servers then bounce this one packet back and forth between each other. The attacker can overload both servers and their LANs simply by injecting a few packets in this manner. - Similar problems exist with the internal + Similar problems exist with the internal <application>chargen</application> port. A competent sysadmin will turn off all of these inetd-internal test services.</para> @@ -910,22 +910,22 @@ <command>netstat -rna | fgrep W3</command>. These routes typically timeout in 1600 seconds or so. If the kernel detects that the cached route table has gotten too big it will dynamically - reduce the <varname>rtexpire</varname> but will never decrease it - to less than <varname>rtminexpire</varname>. There are two + reduce the <varname>rtexpire</varname> but will never decrease it + to less than <varname>rtminexpire</varname>. There are two problems:</para> - + <orderedlist> <listitem> <para>The kernel does not react quickly enough when a lightly loaded server is suddenly attacked.</para> </listitem> - + <listitem> <para>The <varname>rtminexpire</varname> is not low enough for the kernel to survive a sustained attack.</para> </listitem> </orderedlist> - + <para>If your servers are connected to the Internet via a T3 or better, it may be prudent to manually override both <varname>rtexpire</varname> and <varname>rtminexpire</varname> @@ -1019,11 +1019,11 @@ &unix; came into being was based on DES, the Data Encryption Standard. This was not such a problem for users resident in the US, but since the source code for DES could not be exported - outside the US, &os; had to find a way to both comply with + outside the US, &os; had to find a way to both comply with US law and retain compatibility with all the other &unix; variants that still used DES.</para> - <para>The solution was to divide up the encryption libraries + <para>The solution was to divide up the encryption libraries so that US users could install the DES libraries and use DES but international users still had an encryption method that could be exported abroad. This is how &os; came to @@ -1038,7 +1038,7 @@ functions. By default &os; uses MD5 to encrypt passwords.</para> - <para>It is pretty easy to identify which encryption method + <para>It is pretty easy to identify which encryption method &os; is set up to use. Examining the encrypted passwords in the <filename>/etc/master.passwd</filename> file is one way. Passwords encrypted with the MD5 hash are longer than those @@ -1181,7 +1181,7 @@ MOS MALL GOAT ARM AVID COED <sect2> <title>Insecure Connection Initialization</title> - + <para>To initialize or change your secret password over an insecure connection, you will need to already have a secure connection to some place where you can run @@ -1226,7 +1226,7 @@ GAME GAG WELT OUT DOWN CHAT <sect2> <title>Generating a Single One-time Password</title> - <para>Once you have initialized OPIE and login, you will be + <para>Once you have initialized OPIE and login, you will be presented with a prompt like this:</para> <screen>&prompt.user; <userinput>telnet example.com</userinput> @@ -1312,7 +1312,7 @@ Enter secret pass phrase: <userinput><secret password></userinput> Please check &man.opieaccess.5; for more information on this file and which security considerations you should be aware of when using it.</para> - + <para>Here is a sample <filename>opieaccess</filename> file:</para> <programlisting>permit 192.168.0.0 255.255.0.0</programlisting> @@ -1320,7 +1320,7 @@ Enter secret pass phrase: <userinput><secret password></userinput> <para>This line allows users whose IP source address (which is vulnerable to spoofing) matches the specified value and mask, to use &unix; passwords at any time.</para> - + <para>If no rules in <filename>opieaccess</filename> are matched, the default is to deny non-OPIE logins.</para> @@ -1341,7 +1341,7 @@ Enter secret pass phrase: <userinput><secret password></userinput> <title>TCP Wrappers</title> <indexterm><primary>TCP Wrappers</primary></indexterm> - + <para>Anyone familiar with &man.inetd.8; has probably heard of <acronym>TCP</acronym> Wrappers at some point. But few individuals seem to fully comprehend its usefulness in a @@ -1453,7 +1453,7 @@ qpopper : ALL : allow</programlisting> configuration options known as <literal>wildcards</literal>, expansion characters and external command execution. The next two sections are written to cover these situations.</para> - + <sect3> <title>External Commands</title> @@ -1614,28 +1614,28 @@ sendmail : PARANOID : deny</programlisting> <sect2> <title>Creating the Initial Database</title> - + <para>This is done on the Kerberos server only. First make sure that you do not have any old Kerberos databases around. You should change to the directory <filename>/etc/kerberosIV</filename> and check that only the following files are present:</para> - + <screen>&prompt.root; <userinput>cd /etc/kerberosIV</userinput> &prompt.root; <userinput>ls</userinput> README krb.conf krb.realms</screen> - + <para>If any additional files (such as <filename>principal.*</filename> or <filename>master_key</filename>) exist, then use the <command>kdb_destroy</command> command to destroy the old Kerberos database, or if Kerberos is not running, simply delete the extra files.</para> - + <para>You should now edit the <filename>krb.conf</filename> and <filename>krb.realms</filename> files to define your Kerberos realm. In this case the realm will be <literal>EXAMPLE.COM</literal> and the server is <hostid role="fqdn">grunt.example.com</hostid>. We edit or create the <filename>krb.conf</filename> file:</para> - + <screen>&prompt.root; <userinput>cat krb.conf</userinput> EXAMPLE.COM EXAMPLE.COM grunt.example.com admin server @@ -1647,11 +1647,11 @@ ATHENA.MIT.EDU kerberos-3.mit.edu LCS.MIT.EDU kerberos.lcs.mit.edu TELECOM.MIT.EDU bitsy.mit.edu ARC.NASA.GOV trident.arc.nasa.gov</screen> - + <para>In this case, the other realms do not need to be there. They are here as an example of how a machine may be made aware of multiple realms. You may wish to not include them for simplicity.</para> - + <para>The first line names the realm in which this system works. The other lines contain realm/host entries. The first item on a line is a realm, and the second is a host in that realm that is acting as a @@ -1659,59 +1659,59 @@ ARC.NASA.GOV trident.arc.nasa.gov</screen> server</literal> following a host's name means that host also provides an administrative database server. For further explanation of these terms, please consult the Kerberos manual pages.</para> - + <para>Now we have to add <hostid role="fqdn">grunt.example.com</hostid> to the <literal>EXAMPLE.COM</literal> realm and also add an entry to put all hosts in the <hostid role="domainname">.example.com</hostid> domain in the <literal>EXAMPLE.COM</literal> realm. The <filename>krb.realms</filename> file would be updated as follows:</para> - + <screen>&prompt.root; <userinput>cat krb.realms</userinput> grunt.example.com EXAMPLE.COM .example.com EXAMPLE.COM .berkeley.edu CS.BERKELEY.EDU .MIT.EDU ATHENA.MIT.EDU .mit.edu ATHENA.MIT.EDU</screen> - + <para>Again, the other realms do not need to be there. They are here as an example of how a machine may be made aware of multiple realms. You may wish to remove them to simplify things.</para> - + <para>The first line puts the <emphasis>specific</emphasis> system into the named realm. The rest of the lines show how to default systems of a particular subdomain to a named realm.</para> - + <para>Now we are ready to create the database. This only needs to run on the Kerberos server (or Key Distribution Center). Issue the <command>kdb_init</command> command to do this:</para> - + <screen>&prompt.root; <userinput>kdb_init</userinput> <prompt>Realm name [default ATHENA.MIT.EDU ]:</prompt> <userinput>EXAMPLE.COM</userinput> You will be prompted for the database Master Password. It is important that you NOT FORGET this password. - + <prompt>Enter Kerberos master key:</prompt> </screen> - + <para>Now we have to save the key so that servers on the local machine can pick it up. Use the <command>kstash</command> command to do this:</para> - + <screen>&prompt.root; <userinput>kstash</userinput> - + <prompt>Enter Kerberos master key:</prompt> Current Kerberos master key version is 1. Master key entered. BEWARE!</screen> - + <para>This saves the encrypted master password in <filename>/etc/kerberosIV/master_key</filename>.</para> </sect2> - + <sect2> <title>Making It All Run</title> - + <indexterm> <primary>KerberosIV</primary> <secondary>initial startup</secondary> @@ -1722,14 +1722,14 @@ Master key entered. BEWARE!</screen> Their names are <literal>kpasswd</literal> and <literal>rcmd</literal>. These two principals are made for each system, with the instance being the name of the individual system.</para> - + <para>These daemons, <application>kpasswd</application> and <application>rcmd</application> allow other systems to change Kerberos passwords and run commands like &man.rcp.1;, &man.rlogin.1; and &man.rsh.1;.</para> - + <para>Now let us add these entries:</para> - + <screen>&prompt.root; <userinput>kdb_edit</userinput> Opening database... @@ -1782,7 +1782,7 @@ Edit O.K. <sect2> <title>Creating the Server File</title> - + <para>We now have to extract all the instances which define the services on each machine. For this we use the <command>ext_srvtab</command> command. This will create a file @@ -1791,23 +1791,23 @@ Edit O.K. <filename>/etc/kerberosIV</filename> directory. This file must be present on each server and client, and is crucial to the operation of Kerberos.</para> - - + + <screen>&prompt.root; <userinput>ext_srvtab grunt</userinput> <prompt>Enter Kerberos master key:</prompt> - + Current Kerberos master key version is 1. Master key entered. BEWARE! Generating 'grunt-new-srvtab'....</screen> - + <para>Now, this command only generates a temporary file which must be renamed to <filename>srvtab</filename> so that all the servers can pick it up. Use the &man.mv.1; command to move it into place on the original system:</para> - + <screen>&prompt.root; <userinput>mv grunt-new-srvtab srvtab</userinput></screen> - + <para>If the file is for a client system, and the network is not deemed safe, then copy the <filename><replaceable>client</replaceable>-new-srvtab</filename> to @@ -1815,18 +1815,18 @@ Generating 'grunt-new-srvtab'....</screen> rename it to <filename>srvtab</filename> in the client's <filename>/etc/kerberosIV</filename> directory, and make sure it is mode 600:</para> - + <screen>&prompt.root; <userinput>mv grumble-new-srvtab srvtab</userinput> &prompt.root; <userinput>chmod 600 srvtab</userinput></screen> </sect2> - + <sect2> <title>Populating the Database</title> - + <para>We now have to add some user entries into the database. First let us create an entry for the user <username>jane</username>. Use the <command>kdb_edit</command> command to do this:</para> - + <screen>&prompt.root; <userinput>kdb_edit</userinput> Opening database... @@ -1858,14 +1858,14 @@ Edit O.K. <sect2> <title>Testing It All Out</title> - + <para>First we have to start the Kerberos daemons. Note that if you have correctly edited your <filename>/etc/rc.conf</filename> then this will happen automatically when you reboot. This is only necessary on the Kerberos server. Kerberos clients will automatically get what they need from the <filename>/etc/kerberosIV</filename> directory.</para> - + <screen>&prompt.root; <userinput>kerberos &</userinput> Kerberos server starting Sleep forever on error @@ -1884,30 +1884,30 @@ regular kill instead Current Kerberos master key version is 1. Master key entered. BEWARE!</screen> - + <para>Now we can try using the <command>kinit</command> command to get a ticket for the ID <username>jane</username> that we created above:</para> - + <screen>&prompt.user; <userinput>kinit jane</userinput> MIT Project Athena (grunt.example.com) Kerberos Initialization for "jane" <prompt>Password:</prompt> </screen> - + <para>Try listing the tokens using <command>klist</command> to see if we really have them:</para> - + <screen>&prompt.user; <userinput>klist</userinput> Ticket file: /tmp/tkt245 Principal: jane@EXAMPLE.COM Issued Expires Principal Apr 30 11:23:22 Apr 30 19:23:22 krbtgt.EXAMPLE.COM@EXAMPLE.COM</screen> - + <para>Now try changing the password using &man.passwd.1; to - check if the <application>kpasswd</application> daemon can get + check if the <application>kpasswd</application> daemon can get authorization to the Kerberos database:</para> - + <screen>&prompt.user; <userinput>passwd</userinput> realm EXAMPLE.COM <prompt>Old password for jane:</prompt> @@ -1919,7 +1919,7 @@ Password changed.</screen> <sect2> <title>Adding <command>su</command> Privileges</title> - + <para>Kerberos allows us to give <emphasis>each</emphasis> user who needs <username>root</username> privileges their own <emphasis>separate</emphasis> &man.su.1; password. @@ -1929,7 +1929,7 @@ Password changed.</screen> associated with a principal. Using <command>kdb_edit</command> we can create the entry <literal>jane.root</literal> in the Kerberos database:</para> - + <screen>&prompt.root; <userinput>kdb_edit</userinput> Opening database... @@ -1958,27 +1958,27 @@ Principal's new key version = 1 <prompt>Attributes [ 0 ] ?</prompt> Edit O.K. <prompt>Principal name:</prompt> <---- null entry here will cause an exit</screen> - + <para>Now try getting tokens for it to make sure it works:</para> - + <screen>&prompt.root; <userinput>kinit jane.root</userinput> MIT Project Athena (grunt.example.com) Kerberos Initialization for "jane.root" <prompt>Password:</prompt></screen> - + <para>Now we need to add the user to <username>root</username>'s <filename>.klogin</filename> file:</para> - + <screen>&prompt.root; <userinput>cat /root/.klogin</userinput> jane.root@EXAMPLE.COM</screen> - + <para>Now try doing the &man.su.1;:</para> - + <screen>&prompt.user; <userinput>su</userinput> <prompt>Password:</prompt></screen> - + <para>and take a look at what tokens we have:</para> - + <screen>&prompt.root; <userinput>klist</userinput> Ticket file: /tmp/tkt_root_245 Principal: jane.root@EXAMPLE.COM @@ -1989,7 +1989,7 @@ May 2 20:43:12 May 3 04:43:12 krbtgt.EXAMPLE.COM@EXAMPLE.COM</screen> <sect2> <title>Using Other Commands</title> - + <para>In an earlier example, we created a principal called <literal>jane</literal> with an instance <literal>root</literal>. This was based on a user with the same name as the principal, and this @@ -2000,17 +2000,17 @@ May 2 20:43:12 May 3 04:43:12 krbtgt.EXAMPLE.COM@EXAMPLE.COM</screen> <username>root</username> if the necessary entries are in the <filename>.klogin</filename> file in <username>root</username>'s home directory:</para> - + <screen>&prompt.root; <userinput>cat /root/.klogin</userinput> jane.root@EXAMPLE.COM</screen> - + <para>Likewise, if a user has in their own home directory lines of the form:</para> - + <screen>&prompt.user; <userinput>cat ~/.klogin</userinput> jane@EXAMPLE.COM jack@EXAMPLE.COM</screen> - + <para>This allows anyone in the <literal>EXAMPLE.COM</literal> realm who has authenticated themselves as <username>jane</username> or <username>jack</username> (via <command>kinit</command>, see above) @@ -2018,10 +2018,10 @@ jack@EXAMPLE.COM</screen> account or files on this system (<hostid>grunt</hostid>) via &man.rlogin.1;, &man.rsh.1; or &man.rcp.1;.</para> - + <para>For example, <username>jane</username> now logs into another system using Kerberos:</para> - + <screen>&prompt.user; <userinput>kinit</userinput> MIT Project Athena (grunt.example.com) <prompt>Password:</prompt> @@ -2031,13 +2031,13 @@ Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen> - + <para>Or <username>jack</username> logs into <username>jane</username>'s account on the same machine (<username>jane</username> having set up the <filename>.klogin</filename> file as above, and the person in charge of Kerberos having set up principal <emphasis>jack</emphasis> with a null instance):</para> - + <screen>&prompt.user; <userinput>kinit</userinput> &prompt.user; <userinput>rlogin grunt -l jane</userinput> MIT Project Athena (grunt.example.com) @@ -2947,7 +2947,7 @@ An optional company name []:<userinput><replaceable>Another Name</replaceable></ generate the <acronym>RSA</acronym> key:</para> <screen>&prompt.root; <userinput>openssl dsaparam -rand -genkey -out <filename>myRSA.key</filename> 1024</userinput></screen> - + <para>Next, generate the <acronym>CA</acronym> key:</para> <screen>&prompt.root; <userinput>openssl gendsa -des3 -out <filename>myca.key</filename> <filename>myRSA.key</filename></userinput></screen> @@ -3060,7 +3060,7 @@ Connection closed by foreign host.</screen> <para>Creating a VPN between two networks, separated by the Internet, using FreeBSD gateways.</para> - + <sect2> <sect2info> <authorgroup> @@ -3084,7 +3084,7 @@ Connection closed by foreign host.</screen> IPsec, it is necessary that you are familiar with the concepts of building a custom kernel (see <xref linkend="kernelconfig"/>).</para> - + <para><emphasis>IPsec</emphasis> is a protocol which sits on top of the Internet Protocol (IP) layer. It allows two or more hosts to communicate in a secure manner (hence the name). The @@ -3130,12 +3130,12 @@ options FAST_IPSEC # new IPsec (cannot define w/ IPSEC) options IPSEC_FILTERGIF #filter ipsec packets from a tunnel </screen> </note> - + <indexterm> <primary>IPsec</primary> <secondary>ESP</secondary> </indexterm> - + <indexterm> <primary>IPsec</primary> <secondary>AH</secondary> @@ -3161,11 +3161,11 @@ options IPSEC_FILTERGIF #filter ipsec packets from a tunnel packet to be authenticated.</para> </listitem> </itemizedlist> - + <para><acronym>ESP</acronym> and <acronym>AH</acronym> can either be used together or separately, depending on the environment.</para> - + <indexterm> <primary>VPN</primary> </indexterm> @@ -3184,7 +3184,7 @@ options IPSEC_FILTERGIF #filter ipsec packets from a tunnel known as a <emphasis>Virtual Private Network (VPN)</emphasis>. The &man.ipsec.4; manual page should be consulted for detailed information on the IPsec subsystem in FreeBSD.</para> - + <para>To add IPsec support to your kernel, add the following options to your kernel configuration file:</para> @@ -3218,25 +3218,25 @@ options IPSEC_DEBUG #debug for IP security <sect2> <title>The Problem</title> - + <para>There is no standard for what constitutes a VPN. VPNs can be implemented using a number of different technologies, each of which have their own strengths and weaknesses. This section presents a scenario, and the strategies used for implementing a VPN for this scenario.</para> </sect2> - - <sect2> + + <sect2> <title>The Scenario: Two networks, connected to the Internet, to behave as one</title> - + <indexterm> <primary>VPN</primary> <secondary>creating</secondary> </indexterm> <para>The premise is as follows:</para> - + <itemizedlist> <listitem> <para>You have at least two sites</para> @@ -3265,15 +3265,15 @@ options IPSEC_DEBUG #debug for IP security configuration nightmare.</para> </listitem> </itemizedlist> - + <para>If you find that you are trying to connect two networks, both of which, internally, use the same private IP address range (e.g. both of them use <hostid role="ipaddr">192.168.1.x</hostid>), then one of the networks will have to be renumbered.</para> - + <para>The network topology might look something like this:</para> - + <mediaobject> <imageobject> <imagedata fileref="security/ipsec-network" align="center"/> @@ -3303,7 +3303,7 @@ Network #2 [ Internal Hosts ] [ UNIX ]</literallayout> </textobject> </mediaobject> - + <para>Notice the two public IP addresses. I will use the letters to refer to them in the rest of this article. Anywhere you see those letters in this article, replace them with your own public IP @@ -3315,35 +3315,35 @@ Network #2 [ Internal Hosts ] machines on the private networks have been configured to use the <hostid role="ipaddr">.1</hostid> machine as their default gateway.</para> - + <para>The intention is that, from a network point of view, each network should view the machines on the other network as though they were directly attached the same router -- albeit a slightly slow router with an occasional tendency to drop packets.</para> - + <para>This means that (for example), machine <hostid role="ipaddr">192.168.1.20</hostid> should be able to run</para> - + <programlisting>ping 192.168.2.34</programlisting> - + <para>and have it work, transparently. &windows; machines should be able to see the machines on the other network, browse file shares, and so on, in exactly the same way that they can browse machines on the local network.</para> - + <para>And the whole thing has to be secure. This means that traffic between the two networks has to be encrypted.</para> - + <para>Creating a VPN between these two networks is a multi-step process. The stages are as follows:</para> - + <orderedlist> <listitem> <para>Create a <quote>virtual</quote> network link between the two networks, across the Internet. Test it, using tools like &man.ping.8;, to make sure it works.</para> </listitem> - + <listitem> <para>Apply security policies to ensure that traffic between the two networks is transparently encrypted and decrypted as @@ -3361,7 +3361,7 @@ Network #2 [ Internal Hosts ] <sect3> <title>Step 1: Creating and testing a <quote>virtual</quote> network link</title> - + <para>Suppose that you were logged in to the gateway machine on network #1 (with public IP address <hostid role="ipaddr">A.B.C.D</hostid>, private IP address <hostid @@ -3395,7 +3395,7 @@ Network #2 [ Internal Hosts ] role="ipaddr">192.168.2.1</hostid>.</para> </listitem> </orderedlist> - + <para>You can think of this as requiring a <quote>tunnel</quote> between the two networks. The two <quote>tunnel mouths</quote> are the IP addresses <hostid role="ipaddr">A.B.C.D</hostid> and <hostid @@ -3403,120 +3403,120 @@ Network #2 [ Internal Hosts ] addresses of the private IP addresses that will be allowed to pass through it. The tunnel is used to transfer traffic with private IP addresses across the public Internet.</para> - + <para>This tunnel is created by using the generic interface, or <devicename>gif</devicename> devices on FreeBSD. As you can imagine, the <devicename>gif</devicename> interface on each gateway host must be configured with four IP addresses; two for the public IP addresses, and two for the private IP addresses.</para> - + <para>Support for the gif device must be compiled in to the &os; kernel on both machines. You can do this by adding the line:</para> - + <programlisting>device gif</programlisting> - + <para>to the kernel configuration files on both machines, and then compile, install, and reboot as normal.</para> - + <para>Configuring the tunnel is a two step process. First the tunnel must be told what the outside (or public) IP addresses are, using &man.ifconfig.8;. Then the private IP addresses must be configured using &man.ifconfig.8;.</para> - + <para>On the gateway machine on network #1 you would run the following two commands to configure the tunnel.</para> - + <programlisting>ifconfig gif0 A.B.C.D W.X.Y.Z ifconfig gif0 inet 192.168.1.1 192.168.2.1 netmask 0xffffffff </programlisting> - + <para>On the other gateway machine you run the same commands, but with the order of the IP addresses reversed.</para> - + <programlisting>ifconfig gif0 W.X.Y.Z A.B.C.D ifconfig gif0 inet 192.168.2.1 192.168.1.1 netmask 0xffffffff </programlisting> - + <para>You can then run:</para> - + <programlisting>ifconfig gif0</programlisting> - + <para>to see the configuration. For example, on the network #1 gateway, you would see this:</para> - + <screen>&prompt.root; <userinput>ifconfig gif0</userinput> gif0: flags=8011<UP,POINTTOPOINT,MULTICAST> mtu 1280 inet 192.168.1.1 --> 192.168.2.1 netmask 0xffffffff physical address inet A.B.C.D --> W.X.Y.Z </screen> - + <para>As you can see, a tunnel has been created between the physical addresses <hostid role="ipaddr">A.B.C.D</hostid> and <hostid role="ipaddr">W.X.Y.Z</hostid>, and the traffic allowed through the tunnel is that between <hostid role="ipaddr">192.168.1.1</hostid> and <hostid role="ipaddr">192.168.2.1</hostid>.</para> - + <para>This will also have added an entry to the routing table on both machines, which you can examine with the command <command>netstat -rn</command>. This output is from the gateway host on network #1.</para> - + <screen>&prompt.root; <userinput>netstat -rn</userinput> Routing tables - + Internet: Destination Gateway Flags Refs Use Netif Expire ... 192.168.2.1 192.168.1.1 UH 0 0 gif0 ... </screen> - + <para>As the <quote>Flags</quote> value indicates, this is a host route, which means that each gateway knows how to reach the other gateway, but they do not know how to reach the rest of their respective networks. That problem will be fixed shortly.</para> - + <para>It is likely that you are running a firewall on both machines. This will need to be circumvented for your VPN traffic. You might want to allow all traffic between both networks, or you might want to include firewall rules that protect both ends of the VPN from one another.</para> - + <para>It greatly simplifies testing if you configure the firewall to allow all traffic through the VPN. You can always tighten things up later. If you are using &man.ipfw.8; on the gateway machines then a command like</para> <programlisting>ipfw add 1 allow ip from any to any via gif0</programlisting> - + <para>will allow all traffic between the two end points of the VPN, without affecting your other firewall rules. Obviously you will need to run this command on both gateway hosts.</para> - + <para>This is sufficient to allow each gateway machine to ping the other. On <hostid role="ipaddr">192.168.1.1</hostid>, you should be able to run</para> - + <programlisting>ping 192.168.2.1</programlisting> - + <para>and get a response, and you should be able to do the same thing on the other gateway machine.</para> - + <para>However, you will not be able to reach internal machines on either network yet. This is because of the routing -- although the gateway machines know how to reach one another, they do not know how to reach the network behind each one.</para> - + <para>To solve this problem you must add a static route on each gateway machine. The command to do this on the first gateway would be:</para> - + <programlisting>route add 192.168.2.0 192.168.2.1 netmask 0xffffff00 </programlisting> - + <para>This says <quote>In order to reach the hosts on the network <hostid role="ipaddr">192.168.2.0</hostid>, send the packets to the host <hostid @@ -3524,24 +3524,24 @@ Destination Gateway Flags Refs Use Netif Expire run a similar command on the other gateway, but with the <hostid role="ipaddr">192.168.1.x</hostid> addresses instead.</para> - + <para>IP traffic from hosts on one network will now be able to reach hosts on the other network.</para> - + <para>That has now created two thirds of a VPN between the two networks, in as much as it is <quote>virtual</quote> and it is a <quote>network</quote>. It is not private yet. You can test this using &man.ping.8; and &man.tcpdump.1;. Log in to the gateway host and run</para> - + <programlisting>tcpdump dst host 192.168.2.1</programlisting> <para>In another log in session on the same host run</para> <programlisting>ping 192.168.2.1</programlisting> - + <para>You will see output that looks something like this:</para> - + <programlisting> 16:10:24.018080 192.168.1.1 > 192.168.2.1: icmp: echo request 16:10:24.018109 192.168.1.1 > 192.168.2.1: icmp: echo reply @@ -3550,16 +3550,16 @@ Destination Gateway Flags Refs Use Netif Expire 16:10:26.028896 192.168.1.1 > 192.168.2.1: icmp: echo request 16:10:26.029112 192.168.1.1 > 192.168.2.1: icmp: echo reply </programlisting> - + <para>As you can see, the ICMP messages are going back and forth unencrypted. If you had used the <option>-s</option> parameter to &man.tcpdump.1; to grab more bytes of data from the packets you would see more information.</para> - + <para>Obviously this is unacceptable. The next section will discuss securing the link between the two networks so that it all traffic is automatically encrypted.</para> - + <itemizedlist> <title>Summary:</title> <listitem> @@ -3593,14 +3593,14 @@ route_vpn="192.168.2.0 192.168.2.1 netmask 0xffffff00" <sect3> <title>Step 2: Securing the link</title> - + <para>To secure the link we will be using IPsec. IPsec provides a mechanism for two hosts to agree on an encryption key, and to then use this key in order to encrypt data between the two hosts.</para> - + <para>The are two areas of configuration to be considered here.</para> - + <orderedlist> <listitem> <para>There must be a mechanism for two hosts to agree on the @@ -3617,13 +3617,13 @@ route_vpn="192.168.2.0 192.168.2.1 netmask 0xffffff00" <quote>security policies</quote>.</para> </listitem> </orderedlist> - + <para>Security associations and security policies are both maintained by the kernel, and can be modified by userland programs. However, before you can do this you must configure the kernel to support IPsec and the Encapsulated Security Payload (ESP) protocol. This is done by configuring a kernel with:</para> - + <indexterm> <primary>kernel options</primary> <secondary>IPSEC</secondary> @@ -3632,11 +3632,11 @@ route_vpn="192.168.2.0 192.168.2.1 netmask 0xffffff00" <programlisting>options IPSEC options IPSEC_ESP </programlisting> - + <para>and recompiling, reinstalling, and rebooting. As before you will need to do this to the kernels on both of the gateway hosts.</para> - + <indexterm> <primary>IKE</primary> </indexterm> @@ -3646,10 +3646,10 @@ options IPSEC_ESP which entails choosing the encryption algorithm, encryption keys, and so forth, or you can use daemons that implement the Internet Key Exchange protocol (IKE) to do this for you.</para> - + <para>I recommend the latter. Apart from anything else, it is easier to set up.</para> - + <indexterm> <primary>IPsec</primary> <secondary>security policies</secondary> @@ -3666,13 +3666,13 @@ options IPSEC_ESP also display the current security associations, and to continue the analogy further, is akin to <command>netstat -r</command> in that respect.</para> - + <para>There are a number of choices for daemons to manage security associations with FreeBSD. This article will describe how to use one of these, racoon — which is available from <filename role="package">security/ipsec-tools</filename> in the &os; Ports collection.</para> - + <indexterm> <primary>racoon</primary> </indexterm> @@ -3681,7 +3681,7 @@ options IPSEC_ESP is configured with the IP address of the other end of the VPN, and a secret key (which you choose, and must be the same on both gateways).</para> - + <para>The two daemons then contact one another, confirm that they are who they say they are (by using the secret key that you configured). The daemons then generate a new secret key, and use @@ -3690,14 +3690,14 @@ options IPSEC_ESP of the keys (which is as theoretically close to unfeasible as it gets) it will not do them much good -- by the time they have cracked the key the two daemons have chosen another one.</para> - + <para>The configuration file for racoon is stored in <filename>${PREFIX}/etc/racoon</filename>. You should find a configuration file there, which should not need to be changed too much. The other component of racoon's configuration, which you will need to change, is the <quote>pre-shared key</quote>.</para> - + <para>The default racoon configuration expects to find this in the file <filename>${PREFIX}/etc/racoon/psk.txt</filename>. It is important to note that the pre-shared key is <emphasis>not</emphasis> the key that will be used to @@ -3708,55 +3708,55 @@ options IPSEC_ESP remote site you are dealing with. In this example, where there are two sites, each <filename>psk.txt</filename> file will contain one line (because each end of the VPN is only dealing with one other end).</para> - + <para>On gateway host #1 this line should look like this:</para> - + <programlisting>W.X.Y.Z secret</programlisting> - + <para>That is, the <emphasis>public</emphasis> IP address of the remote end, whitespace, and a text string that provides the secret. Obviously, you should not use <quote>secret</quote> as your key -- the normal rules for choosing a password apply.</para> - + <para>On gateway host #2 the line would look like this</para> - + <programlisting>A.B.C.D secret</programlisting> - + <para>That is, the public IP address of the remote end, and the same secret key. <filename>psk.txt</filename> must be mode <literal>0600</literal> (i.e., only read/write to <username>root</username>) before racoon will run.</para> - + <para>You must run racoon on both gateway machines. You will also need to add some firewall rules to allow the IKE traffic, which is carried over UDP to the ISAKMP (Internet Security Association Key Management Protocol) port. Again, this should be fairly early in your firewall ruleset.</para> - + <programlisting>ipfw add 1 allow udp from A.B.C.D to W.X.Y.Z isakmp ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp </programlisting> - + <para>Once racoon is running you can try pinging one gateway host from the other. The connection is still not encrypted, but racoon will then set up the security associations between the two hosts -- this might take a moment, and you may see this as a short delay before the ping commands start responding.</para> - + <para>Once the security association has been set up you can view it using &man.setkey.8;. Run</para> - + <programlisting>setkey -D</programlisting> - + <para>on either host to view the security association information.</para> - + <para>That's one half of the problem. They other half is setting your security policies.</para> - + <para>To create a sensible security policy, let's review what's been set up so far. This discussions hold for both ends of the link.</para> - + <para>Each IP packet that you send out has a header that contains data about the packet. The header includes the IP addresses of both the source and destination. As we already know, private IP @@ -3765,9 +3765,9 @@ ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp Instead, they must first be encapsulated inside another packet. This packet must have the public source and destination IP addresses substituted for the private addresses.</para> - + <para>So if your outgoing packet started looking like this:</para> - + <mediaobject> <imageobject> <imagedata fileref="security/ipsec-out-pkt" align="center"/> @@ -3784,10 +3784,10 @@ ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp `----------------------'</literallayout> </textobject> </mediaobject> - + <para>Then it will be encapsulated inside another packet, looking something like this:</para> - + <mediaobject> <imageobject> <imagedata fileref="security/ipsec-encap-pkt" align="center"/> @@ -3810,13 +3810,13 @@ ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp `--------------------------'</literallayout> </textobject> </mediaobject> - + <para>This encapsulation is carried out by the <devicename>gif</devicename> device. As you can see, the packet now has real IP addresses on the outside, and our original packet has been wrapped up as data inside the packet that will be put out on the Internet.</para> - + <para>Obviously, we want all traffic between the VPNs to be encrypted. You might try putting this in to words, as:</para> @@ -3824,51 +3824,51 @@ ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp role="ipaddr">A.B.C.D</hostid>, and it is destined for <hostid role="ipaddr">W.X.Y.Z</hostid>, then encrypt it, using the necessary security associations.</quote></para> - + <para><quote>If a packet arrives from <hostid role="ipaddr">W.X.Y.Z</hostid>, and it is destined for <hostid role="ipaddr">A.B.C.D</hostid>, then decrypt it, using the necessary security associations.</quote></para> - + <para>That's close, but not quite right. If you did this, all traffic to and from <hostid role="ipaddr">W.X.Y.Z</hostid>, even traffic that was not part of the VPN, would be encrypted. That's not quite what you want. The correct policy is as follows</para> - + <para><quote>If a packet leaves from <hostid role="ipaddr">A.B.C.D</hostid>, and that packet is encapsulating another packet, and it is destined for <hostid role="ipaddr">W.X.Y.Z</hostid>, then encrypt it, using the necessary security associations.</quote></para> - + <para><quote>If a packet arrives from <hostid role="ipaddr">W.X.Y.Z</hostid>, and that packet is encapsulating another packet, and it is destined for <hostid role="ipaddr">A.B.C.D</hostid>, then decrypt it, using the necessary security associations.</quote></para> - + <para>A subtle change, but a necessary one.</para> - + <para>Security policies are also set using &man.setkey.8;. &man.setkey.8; features a configuration language for defining the policy. You can either enter configuration instructions via stdin, or you can use the <option>-f</option> option to specify a filename that contains configuration instructions.</para> - + <para>The configuration on gateway host #1 (which has the public IP address <hostid role="ipaddr">A.B.C.D</hostid>) to force all outbound traffic to <hostid role="ipaddr">W.X.Y.Z</hostid> to be encrypted is:</para> - + <programlisting> spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/require; </programlisting> - + <para>Put these commands in a file (e.g. <filename>/etc/ipsec.conf</filename>) and then run</para> <screen>&prompt.root; <userinput>setkey -f /etc/ipsec.conf</userinput></screen> - + <para><option>spdadd</option> tells &man.setkey.8; that we want to add a rule to the secure policy database. The rest of this line specifies which packets will match this policy. <hostid @@ -3881,7 +3881,7 @@ spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/req packets. <option>-P out</option> says that this policy applies to outgoing packets, and <option>ipsec</option> says that the packet will be secured.</para> - + <para>The second line specifies how this packet will be encrypted. <option>esp</option> is the protocol that will be used, while <option>tunnel</option> indicates that the packet @@ -3891,37 +3891,37 @@ spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/req association to use, and the final <option>require</option> mandates that packets must be encrypted if they match this rule.</para> - + <para>This rule only matches outgoing packets. You will need a similar rule to match incoming packets.</para> - + <programlisting>spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P in ipsec esp/tunnel/W.X.Y.Z-A.B.C.D/require;</programlisting> - + <para>Note the <option>in</option> instead of <option>out</option> in this case, and the necessary reversal of the IP addresses.</para> - + <para>The other gateway host (which has the public IP address <hostid role="ipaddr">W.X.Y.Z</hostid>) will need similar rules.</para> - + <programlisting>spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P out ipsec esp/tunnel/W.X.Y.Z-A.B.C.D/require; spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P in ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/require;</programlisting> - + <para>Finally, you need to add firewall rules to allow ESP and IPENCAP packets back and forth. These rules will need to be added to both hosts.</para> - + <programlisting>ipfw add 1 allow esp from A.B.C.D to W.X.Y.Z ipfw add 1 allow esp from W.X.Y.Z to A.B.C.D ipfw add 1 allow ipencap from A.B.C.D to W.X.Y.Z ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D </programlisting> - + <para>Because the rules are symmetric you can use the same rules on each gateway host.</para> - + <para>Outgoing packets will now look something like this:</para> - + <mediaobject> <imageobject> <imagedata fileref="security/ipsec-crypt-pkt" align="center"/> @@ -3958,34 +3958,34 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D <devicename>gif</devicename> interface, which will unwrap the second layer, until you are left with the innermost packet, which can then travel in to the inner network.</para> - + <para>You can check the security using the same &man.ping.8; test from earlier. First, log in to the <hostid role="ipaddr">A.B.C.D</hostid> gateway machine, and run:</para> - + <programlisting>tcpdump dst host 192.168.2.1</programlisting> - + <para>In another log in session on the same host run</para> - + <programlisting>ping 192.168.2.1</programlisting> - + <para>This time you should see output like the following:</para> - + <programlisting>XXX tcpdump output</programlisting> - + <para>Now, as you can see, &man.tcpdump.1; shows the ESP packets. If you try to examine them with the <option>-s</option> option you will see (apparently) gibberish, because of the encryption.</para> - + <para>Congratulations. You have just set up a VPN between two remote sites.</para> - + <itemizedlist> <title>Summary</title> <listitem> <para>Configure both kernels with:</para> - + <programlisting>options IPSEC options IPSEC_ESP </programlisting> @@ -4001,7 +4001,7 @@ options IPSEC_ESP <listitem> <para>Add the following lines to <filename>/etc/rc.conf</filename> on each host:</para> - + <programlisting>ipsec_enable="YES" ipsec_file="/etc/ipsec.conf" </programlisting> @@ -4010,16 +4010,16 @@ ipsec_file="/etc/ipsec.conf" <para>Create an <filename>/etc/ipsec.conf</filename> on each host that contains the necessary spdadd lines. On gateway host #1 this would be:</para> - + <programlisting> spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/require; spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P in ipsec esp/tunnel/W.X.Y.Z-A.B.C.D/require; </programlisting> - + <para>On gateway host #2 this would be:</para> - + <programlisting> spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P out ipsec esp/tunnel/W.X.Y.Z-A.B.C.D/require; @@ -4030,7 +4030,7 @@ spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P in ipsec <listitem> <para>Add firewall rules to allow IKE, ESP, and IPENCAP traffic to both hosts:</para> - + <programlisting> ipfw add 1 allow udp from A.B.C.D to W.X.Y.Z isakmp ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp @@ -4046,8 +4046,8 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D running. Machines on each network will be able to refer to one another using IP addresses, and all traffic across the link will be automatically and securely encrypted.</para> - </sect3> - </sect2> + </sect3> + </sect2> </sect1> <sect1 id="openssh"> @@ -4084,7 +4084,7 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D <sect2> <title>Advantages of Using OpenSSH</title> - + <para>Normally, when using &man.telnet.1; or &man.rlogin.1;, data is sent over the network in an clear, un-encrypted form. Network sniffers anywhere in between the client and server can @@ -4100,7 +4100,7 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D <secondary>enabling</secondary> </indexterm> - <para>The + <para>The <application>sshd</application> is an option presented during a <literal>Standard</literal> install of &os;. To see if <application>sshd</application> is enabled, check the @@ -4121,7 +4121,7 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D <secondary>client</secondary> </indexterm> - <para>The &man.ssh.1; utility works similarly to + <para>The &man.ssh.1; utility works similarly to &man.rlogin.1;.</para> <screen>&prompt.root; <userinput>ssh <replaceable>user@example.com</replaceable></userinput> @@ -4133,7 +4133,7 @@ user@example.com's password: <userinput>*******</userinput></screen> <para>The login will continue just as it would have if a session was created using <command>rlogin</command> or <command>telnet</command>. SSH utilizes a key fingerprint - system for verifying the authenticity of the server when the + system for verifying the authenticity of the server when the client connects. The user is prompted to enter <literal>yes</literal> only when connecting for the first time. Future attempts to login are all @@ -4153,7 +4153,7 @@ user@example.com's password: <userinput>*******</userinput></screen> The version 1 compatibility is maintained in the client for backwards compatibility with older versions.</para> </sect2> - + <sect2> <title>Secure Copy</title> <indexterm> @@ -4168,8 +4168,8 @@ user@example.com's password: <userinput>*******</userinput></screen> <screen>&prompt.root; <userinput> scp <replaceable>user@example.com:/COPYRIGHT COPYRIGHT</replaceable></userinput> user@example.com's password: <userinput>*******</userinput> -COPYRIGHT 100% |*****************************| 4735 -00:00 +COPYRIGHT 100% |*****************************| 4735 +00:00 &prompt.root;</screen> <para>Since the fingerprint was already saved for this host in the previous example, it is verified when using &man.scp.1; @@ -4195,8 +4195,8 @@ COPYRIGHT 100% |*****************************| 4735 <application>OpenSSH</application> daemon and client reside within the <filename>/etc/ssh</filename> directory.</para> - <para><filename>ssh_config</filename> configures the client - settings, while <filename>sshd_config</filename> configures the + <para><filename>ssh_config</filename> configures the client + settings, while <filename>sshd_config</filename> configures the daemon.</para> <para>Additionally, the <option>sshd_program</option> @@ -4304,7 +4304,7 @@ Identity added: /home/user/.ssh/id_dsa (/home/user/.ssh/id_dsa) <para><application>OpenSSH</application> has the ability to create a tunnel to encapsulate another protocol in an encrypted session.</para> - <para>The following command tells &man.ssh.1; to create a tunnel + <para>The following command tells &man.ssh.1; to create a tunnel for <application>telnet</application>:</para> <screen>&prompt.user; <userinput>ssh -2 -N -f -L <replaceable>5023:localhost:23 user@foo.example.com</replaceable></userinput> @@ -4316,7 +4316,7 @@ Identity added: /home/user/.ssh/id_dsa (/home/user/.ssh/id_dsa) <variablelist> <varlistentry> <term><option>-2</option></term> - + <listitem> <para>Forces <command>ssh</command> to use version 2 of the protocol. (Do not use if you are working with older @@ -4387,7 +4387,7 @@ user@mailserver.example.com's password: <userinput>*****</userinput> Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. -220 mailserver.example.com ESMTP</screen> +220 mailserver.example.com ESMTP</screen> <para>This can be used in conjunction with an &man.ssh-keygen.1; and additional user accounts to create a @@ -4486,7 +4486,7 @@ user@unfirewalled-system.example.org's password: <userinput>*******</userinput>< <sect2> <title>Further Reading</title> <para><ulink url="http://www.openssh.com/">OpenSSH</ulink></para> - <para>&man.ssh.1; &man.scp.1; &man.ssh-keygen.1; + <para>&man.ssh.1; &man.scp.1; &man.ssh-keygen.1; &man.ssh-agent.1; &man.ssh-add.1; &man.ssh.config.5;</para> <para>&man.sshd.8; &man.sftp-server.8; &man.sshd.config.5;</para> </sect2> @@ -4575,7 +4575,7 @@ user@unfirewalled-system.example.org's password: <userinput>*******</userinput>< users of the system, and re-enabling <acronym>ACLs</acronym> may re-attach the previous <acronym>ACLs</acronym> to files that have since had their permissions changed, resulting in other unpredictable behavior.</para></note> - + <para>File systems with <acronym>ACLs</acronym> enabled will show a <literal>+</literal> (plus) sign in their permission settings when viewed. For example:</para> @@ -4981,5 +4981,5 @@ VII. References<co id="co-ref"/></programlisting> &man.lastcomm.1;, &man.acct.5; and &man.sa.8; manual pages.</para> </sect2> - </sect1> + </sect1> </chapter> diff --git a/pl_PL.ISO8859-2/books/handbook/txtfiles.ent b/pl_PL.ISO8859-2/books/handbook/txtfiles.ent index 112f7ee320..a6a6a99c26 100644 --- a/pl_PL.ISO8859-2/books/handbook/txtfiles.ent +++ b/pl_PL.ISO8859-2/books/handbook/txtfiles.ent @@ -1,14 +1,14 @@ <?xml version="1.0" encoding="ISO8859-2"?> -<!-- - Creates entities for each .txt screenshot that is included in the +<!-- + Creates entities for each .txt screenshot that is included in the Handbook. Each entity is named txt.dir.foo, where dir is the directory in - which it is stored, and foo is its filename, without the '.txt' + which it is stored, and foo is its filename, without the '.txt' extension. Entities should be listed in alphabetical order. - + $FreeBSD$ Original revision: 1.2 --> diff --git a/pl_PL.ISO8859-2/books/handbook/users/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/users/chapter.sgml index b569af709d..63f6e1e950 100644 --- a/pl_PL.ISO8859-2/books/handbook/users/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/users/chapter.sgml @@ -28,10 +28,10 @@ </chapterinfo> <title>Użytkownicy i podstawy zarządzania kontami</title> - + <sect1 id="users-synopsis"> <title>Streszczenie</title> - + <para>FreeBSD umożliwia pracę z komputerem wielu użytkownikom w tym samym czasie. Oczywiście, tylko jedna osoba może w danej chwili siedzieć przed monitorem i klawiaturą @@ -41,7 +41,7 @@ </footnote>, lecz dowolna liczba użytkowników może być zalogowana przez sieć. By móc korzystać z systemu, każdy użytkownik musi posiadać konto.</para> - + <para>Po przeczytaniu tego rozdziału, będziemy wiedzieć:</para> <itemizedlist> @@ -125,7 +125,7 @@ <listitem> <para>UID jest numerem, tradycyjnie z przedziału od 0 do - 65535<footnote id="users-largeuidgid"> + 65535<footnote id="users-largeuidgid"> <para>Możliwe jest również wykorzystanie identyfikatorów UID/GID do 4294967295, jednakże takie identyfikatory mogą być przyczyną poważnych problemów z oprogramowaniem, które dokonuje pewnych założeń co do wartości @@ -239,10 +239,10 @@ wykorzystywane są przez prawdziwych ludzi, którzy logują się, czytają pocztę itp.</para> </sect1> - + <sect1 id="users-superuser"> <title>Konto superużytkownika</title> - + <indexterm> <primary>konta</primary> <secondary>superużytkownik (root)</secondary> @@ -252,7 +252,7 @@ by ułatwić administrację systemem i jako takie nie powinno być wykorzystywane do codziennych zajęć, jak np. wysyłanie i odbiór poczty, ogólne zgłębianie systemu czy programowanie.</para> - + <para>Powodem tego jest fakt, iż superużytkownik - w przeciwieństwie do zwykłego użytkownika - może działać bez żadnych ograniczeń. Stąd też niewłaściwe użycie tego konta może skończyć się spektakularną @@ -273,7 +273,7 @@ omówiony zostanie proces tworzenia dodatkowego konta oraz zmiany trybu pracy pomiędzy zwykłym użytkownikiem a superużytkownikiem.</para> </sect1> - + <sect1 id="users-system"> <title>Konta systemowe</title> @@ -497,7 +497,7 @@ Goodbye! <step> <para>Ostatecznie, usuwa użytkownika z wszystkich grup w <filename>/etc/group</filename>, do których należy. - + <note> <para>Jeśli po usunięciu użytkownika grupa pozostanie pusta a nazwa tej grupy jest taka sama jak nazwa użytkownika, diff --git a/pl_PL.ISO8859-2/books/handbook/vinum/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/vinum/chapter.sgml index 6c4cf23ced..fb76c4b294 100644 --- a/pl_PL.ISO8859-2/books/handbook/vinum/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/vinum/chapter.sgml @@ -22,7 +22,7 @@ </chapterinfo> <title>The Vinum Volume Manager</title> - + <sect1 id="vinum-synopsis"> <title>Synopsis</title> @@ -80,7 +80,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> <indexterm><primary>Vinum</primary></indexterm> <indexterm><primary>RAID</primary> <secondary>software</secondary></indexterm> - + <para><emphasis>Vinum</emphasis> is a so-called <emphasis>Volume Manager</emphasis>, a virtual disk driver that addresses these three problems. Let us look at them in more detail. Various @@ -239,7 +239,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> <indexterm> <primary>RAID-1</primary> </indexterm> - + <para>The traditional way to approach this problem has been <emphasis>mirroring</emphasis>, keeping two copies of the data on different physical hardware. Since the advent of the @@ -249,9 +249,9 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> both locations; a read can be satisfied from either, so if one drive fails, the data is still available on the other drive.</para> - + <para>Mirroring has two problems:</para> - + <itemizedlist> <listitem> <para>The price. It requires twice as much disk storage as @@ -333,7 +333,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> <emphasis>subdisks</emphasis>, which it uses as building blocks for plexes.</para> </listitem> - + <listitem> <para>Subdisks reside on Vinum <emphasis>drives</emphasis>, currently &unix; partitions. Vinum drives can @@ -355,7 +355,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> an individual drive does not limit the size of a plex, and thus of a volume.</para> </sect2> - + <sect2> <title>Redundant Data Storage</title> <para>Vinum implements mirroring by attaching multiple plexes to @@ -371,7 +371,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> provide the data for the complete address range of the volume, the volume is fully functional.</para> </sect2> - + <sect2> <title>Performance Issues</title> @@ -397,7 +397,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> <title>Which Plex Organization?</title> <para>The version of Vinum supplied with FreeBSD &rel.current; implements two kinds of plex:</para> - + <itemizedlist> <listitem> <para>Concatenated plexes are the most flexible: they can @@ -426,10 +426,10 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> indistinguishable from a concatenated plex.</para> </listitem> </itemizedlist> - + <para><xref linkend="vinum-comparison"/> summarizes the advantages and disadvantages of each plex organization.</para> - + <table id="vinum-comparison" frame="none"> <title>Vinum Plex Organizations</title> <tgroup cols="5"> @@ -452,7 +452,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> <entry>Large data storage with maximum placement flexibility and moderate performance</entry> </row> - + <row> <entry>striped</entry> <entry>2</entry> @@ -466,7 +466,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> </table> </sect2> </sect1> - + <sect1 id="vinum-examples"> <title>Some Examples</title> @@ -479,7 +479,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> Vinum calls a <emphasis>device</emphasis>) under its control. This database is updated on each state change, so that a restart accurately restores the state of each Vinum object.</para> - + <sect2> <title>The Configuration File</title> <para>The configuration file describes individual Vinum objects. The @@ -545,13 +545,13 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 1 (16 configured) - + D a State: up Device /dev/da3h Avail: 2061/2573 MB (80%) - + V myvol State: up Plexes: 1 Size: 512 MB - + P myvol.p0 C State: up Subdisks: 1 Size: 512 MB - + S myvol.p0.s0 State: up PO: 0 B Size: 512 MB</programlisting> <para>This output shows the brief listing format of &man.gvinum.8;. It @@ -607,21 +607,21 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> Volumes: 2 (4 configured) Plexes: 3 (8 configured) Subdisks: 3 (16 configured) - + D a State: up Device /dev/da3h Avail: 1549/2573 MB (60%) D b State: up Device /dev/da4h Avail: 2061/2573 MB (80%) V myvol State: up Plexes: 1 Size: 512 MB V mirror State: up Plexes: 2 Size: 512 MB - + P myvol.p0 C State: up Subdisks: 1 Size: 512 MB P mirror.p0 C State: up Subdisks: 1 Size: 512 MB P mirror.p1 C State: initializing Subdisks: 1 Size: 512 MB - + S myvol.p0.s0 State: up PO: 0 B Size: 512 MB S mirror.p0.s0 State: up PO: 0 B Size: 512 MB S mirror.p1.s0 State: empty PO: 0 B Size: 512 MB</programlisting> - + <para><xref linkend="vinum-mirrored-vol"/> shows the structure graphically.</para> @@ -669,21 +669,21 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> Volumes: 3 (4 configured) Plexes: 4 (8 configured) Subdisks: 7 (16 configured) - + D a State: up Device /dev/da3h Avail: 1421/2573 MB (55%) D b State: up Device /dev/da4h Avail: 1933/2573 MB (75%) D c State: up Device /dev/da5h Avail: 2445/2573 MB (95%) D d State: up Device /dev/da6h Avail: 2445/2573 MB (95%) - + V myvol State: up Plexes: 1 Size: 512 MB V mirror State: up Plexes: 2 Size: 512 MB V striped State: up Plexes: 1 Size: 512 MB - + P myvol.p0 C State: up Subdisks: 1 Size: 512 MB P mirror.p0 C State: up Subdisks: 1 Size: 512 MB P mirror.p1 C State: initializing Subdisks: 1 Size: 512 MB P striped.p1 State: up Subdisks: 1 Size: 512 MB - + S myvol.p0.s0 State: up PO: 0 B Size: 512 MB S mirror.p0.s0 State: up PO: 0 B Size: 512 MB S mirror.p1.s0 State: empty PO: 0 B Size: 512 MB @@ -744,7 +744,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> </para> </sect2> </sect1> - + <sect1 id="vinum-object-naming"> <title>Object Naming</title> @@ -834,7 +834,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> /dev/vinum/plex: total 0 crwxr-xr-- 1 root wheel 25, 0x10000002 Apr 13 16:46 s64.p0 - + /dev/vinum/sd: total 0 crwxr-xr-- 1 root wheel 91, 0x20000002 Apr 13 16:46 s64.p0.s0 @@ -887,7 +887,7 @@ newfs: /dev/gvinum/concat: can't figure out file system partition</screen> </sect2> </sect1> - + <sect1 id="vinum-config"> <title>Configuring Vinum</title> @@ -929,7 +929,7 @@ sd name bigraid.p0.s1 drive b plex bigraid.p0 state initializing len 4194304b dr sd name bigraid.p0.s2 drive c plex bigraid.p0 state initializing len 4194304b driveoff set 1573129b plexoffset 8388608b sd name bigraid.p0.s3 drive d plex bigraid.p0 state initializing len 4194304b driveoff set 1573129b plexoffset 12582912b sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b driveoff set 1573129b plexoffset 16777216b</programlisting> - + <para>The obvious differences here are the presence of explicit location information and naming (both of which are also allowed, but discouraged, for use by the user) and the @@ -940,7 +940,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr label. This enables Vinum to identify drives correctly even if they have been assigned different &unix; drive IDs.</para> - + <sect3 id="vinum-rc-startup"> <title>Automatic Startup</title> diff --git a/pl_PL.ISO8859-2/books/handbook/x11/chapter.sgml b/pl_PL.ISO8859-2/books/handbook/x11/chapter.sgml index d3161bd11c..cf296f26a2 100644 --- a/pl_PL.ISO8859-2/books/handbook/x11/chapter.sgml +++ b/pl_PL.ISO8859-2/books/handbook/x11/chapter.sgml @@ -37,7 +37,7 @@ <para>Środowisko graficzne dostępne we FreeBSD korzysta z zaawansowanego serwera graficznego X11 — implementacji open-source Systemu okien X obejmującej - zarówno <application>&xorg;</application> jak i + zarówno <application>&xorg;</application> jak i <application>&xfree86;</application>. &os; 5.2.1-RELEASE oraz wcześniejsze wydania wykorzystują <application>&xfree86;</application>, serwer X11 opracowany diff --git a/pl_PL.ISO8859-2/share/sgml/entities.ent b/pl_PL.ISO8859-2/share/sgml/entities.ent index dad3d2d561..06a3061827 100644 --- a/pl_PL.ISO8859-2/share/sgml/entities.ent +++ b/pl_PL.ISO8859-2/share/sgml/entities.ent @@ -1,4 +1,4 @@ -<!-- +<!-- The FreeBSD Polish Documentation Project $FreeBSD$ diff --git a/pl_PL.ISO8859-2/share/sgml/freebsd.dsl b/pl_PL.ISO8859-2/share/sgml/freebsd.dsl index 267dad116d..24be6027d0 100644 --- a/pl_PL.ISO8859-2/share/sgml/freebsd.dsl +++ b/pl_PL.ISO8859-2/share/sgml/freebsd.dsl @@ -12,14 +12,14 @@ <!ENTITY % freebsd.l10n PUBLIC "-//FreeBSD//ENTITIES DocBook Language Specific Entities//EN"> %freebsd.l10n; -<!ENTITY % output.html "IGNORE"> +<!ENTITY % output.html "IGNORE"> <!ENTITY % output.print "IGNORE"> ]> <style-sheet> <style-specification use="docbook"> <style-specification-body> - <![ %output.html; [ + <![ %output.html; [ (define ($email-footer$) (make sequence @@ -33,7 +33,7 @@ (literal "."))) (make element gi: "p" attributes: (list (list "align" "center")) - (make element gi: "small" + (make element gi: "small" (literal "W przypadku pytań o FreeBSD prosimy przeczytać dostępną ") (create-link (list (list "HREF" "http://www.FreeBSD.org/docs.html")) @@ -51,6 +51,6 @@ ]]> </style-specification-body> </style-specification> - + <external-specification id="docbook" document="freebsd.dsl"> </style-sheet> diff --git a/pl_PL.ISO8859-2/share/sgml/l10n.ent b/pl_PL.ISO8859-2/share/sgml/l10n.ent index b7aff0afd6..7747ee9a49 100644 --- a/pl_PL.ISO8859-2/share/sgml/l10n.ent +++ b/pl_PL.ISO8859-2/share/sgml/l10n.ent @@ -13,4 +13,4 @@ <!ENTITY doc.langcode "&doc.langcode.pl;"> <!-- charset for HTML output --> -<!ENTITY doc.html.charset "iso-8859-2">
\ No newline at end of file +<!ENTITY doc.html.charset "iso-8859-2"> diff --git a/pl_PL.ISO8859-2/share/sgml/trademarks.ent b/pl_PL.ISO8859-2/share/sgml/trademarks.ent index c8137fa2a7..33fc28f020 100644 --- a/pl_PL.ISO8859-2/share/sgml/trademarks.ent +++ b/pl_PL.ISO8859-2/share/sgml/trademarks.ent @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="ISO8859-2"?> -<!-- +<!-- Trademark Legend, as required by The Open Group, Sun, etc.. $FreeBSD$ @@ -49,7 +49,7 @@ i postaci 'skompilowanej' (SGML, HTML, PDF, PostScript, RTF itd.), wraz z lub bez modyfikacji, są dozwolone przy spełnieniu następujących warunków:</para> - + <orderedlist> <listitem> <para>Redystrybucja kodu źródłowego (DookBook SGML) musi zachować @@ -57,7 +57,7 @@ wyżej zamieszczoną notę o prawach autorskich, obecny wykaz warunków i poniższe oświadczenie.</para> </listitem> - + <listitem> <para>Redystrybucja w formie skompilowanej (przekształconej do innych DTD, skonwertowanej do formatu PDF, PostScript, RTF i innych) musi zawierać @@ -66,7 +66,7 @@ oraz poniższe oświadczenie.</para> </listitem> </orderedlist> - + <important> <para>DOKUMENTACJA TA DOSTARCZANA JEST PRZEZ THE FREEBSD DOCUMENTATION PROJECT "JAK JEST", BEZ JAKIEJKOLWIEK ODPOWIEDZIALNOŚCI LUB GWARANCJI |