gnu-linux-faq.pl.po

Mismatched links: 39.

Mismatched ids: 0.

#text
8  
<a href="#what">What is the real relationship between GNU and Linux?</a> 
 
22  
<a href="#nokernel">An operating system requires a kernel. Since the GNU Project didn't develop a kernel, how can the system be GNU?</a> 
 
27  
<a href="#long1">How about calling the system &ldquo;GliNUx&rdquo; (instead of &ldquo;GNU/Linux&rdquo;)?</a> 
 
30  
<a href="#long4">Stallman doesn't ask us to call him &ldquo;Richard Matthew Stallman&rdquo; every the time. So why ask us to say &ldquo;GNU/Linux&rdquo; every time?</a> 
 
34 | <a [-href="#manycompanies">Many companies contributed to-]
| {+href="#systemd">systemd plays an important role in+} the {+GNU/Linux+}
| system as it is today; [-doesn't that mean-] {+are+} we [-ought-]
| {+obligated+} to call it [-GNU/Red&nbsp;Hat/Novell/Linux?</a>-]
| {+GNU/systemd/Linux?</a>+} 
<a href="#systemd">systemd plays an important role in the GNU/Linux system as it is today; are we obligated to call it GNU/systemd/Linux?</a> 
<a href="#manycompanies">Wiele przedsiębiorstw wniosło swój wkład do&nbsp;systemu, czyniąc go takim, jaki jest dzisiaj; czyżby to znaczyło, że&nbsp;powinniśmy go nazywać GNU/Red&nbsp;hat/Novell/Linux?</a> 
39 | <a [-href="#bsd">Should we say &ldquo;GNU/BSD&rdquo; too?</a>-]
| {+href="#pronounce">How is the name &ldquo;GNU/Linux&rdquo;
| pronounced?</a>+} 
<a href="#pronounce">How is the name &ldquo;GNU/Linux&rdquo; pronounced?</a> 
<a href="#bsd">Czy&nbsp;powinniśmy również mówić &bdquo;GNU/BSD&rdquo;?</a> 
40 | <a [-href="#whyslash">Why-] {+href="#whynoslash">Why+} do you write
| [-&ldquo;GNU/Linux&rdquo; instead of-] &ldquo;GNU [-Linux&rdquo;?</a>-]
| {+Emacs&rdquo; rather than &ldquo;GNU/Emacs&rdquo;?</a>+} 
<a href="#whynoslash">Why do you write &ldquo;GNU Emacs&rdquo; rather than &ldquo;GNU/Emacs&rdquo;?</a> 
<a href="#whyslash">Czemu piszecie &bdquo;GNU/Linux&rdquo; zamiast &bdquo;GNU Linux&rdquo;?</a> 
58  
<a href="#usegnulinuxandandroid">Is it correct to say &ldquo;using Linux&rdquo; if it refers to using GNU/Linux and using Android?</a> 
 
86  
What is the real relationship between GNU and Linux? <span class="anchor-reference-id">(<a href="#what">#what</a>)</span> 
 
87  
The GNU operating system and the Linux kernel are separate software projects that do complementary jobs. Typically they are packaged in a <a href="/distros/distros.html">GNU/Linux distribution</a>, and used together. 
 
136 | [-Isn't writing-]{+An operating system requires a kernel. Since+} the
| [-kernel most of-] {+GNU Project didn't develop a kernel, how can+} the
| [-work in an operating system? <span-] {+system be GNU?<span+}
| class="anchor-reference-id">(<a
| [-href="#kernelmost">#kernelmost</a>)</span>-]
| {+href="#nokernel">#nokernel</a>)</span>+} 
An operating system requires a kernel. Since the GNU Project didn't develop a kernel, how can the system be GNU?<span class="anchor-reference-id">(<a href="#nokernel">#nokernel</a>)</span> 
Czy&nbsp;pisanie jądra nie jest większością pracy w&nbsp;tworzeniu systemu operacyjnego?<span class="anchor-reference-id">(<a href="#kernelmost">#kernelmost</a>)</span> 
154  
How about calling the system &ldquo;GliNUx&rdquo; (instead of &ldquo;GNU/Linux&rdquo;)? <span class="anchor-reference-id">(<a href="#long1">#long1</a>)</span> 
 
157  
The problem with &ldquo;GNU/Linux&rdquo; is that it is too long. Why should I go to the trouble of saying &ldquo;GNU/&rdquo;? <span class="anchor-reference-id">(<a href="#long2">#long2</a>)</span> 
Nazwa &bdquo;GNU/Linux&rdquo; sprawia kłopot, bo&nbsp;jest za&nbsp;długa. Dlaczego mam się wysilać aby&nbsp;mówić &bdquo;GNU/&rdquo;? <span class="anchor-reference-id">(<a href="#long">#long2</a>)</span> 
161 | [-The problem with &ldquo;GNU/Linux&rdquo; is that it is too long. Why
| should I go-]{+Stallman doesn't ask us+} to {+call him &ldquo;Richard
| Matthew Stallman&rdquo; every+} the [-trouble of saying
| &ldquo;GNU/&rdquo;?-] {+time. So why ask us to say
| &ldquo;GNU/Linux&rdquo; every time?+} <span
| class="anchor-reference-id">(<a [-href="#long2">#long2</a>)</span>-]
| {+href="#long4">#long4</a>)</span>+} 
Stallman doesn't ask us to call him &ldquo;Richard Matthew Stallman&rdquo; every the time. So why ask us to say &ldquo;GNU/Linux&rdquo; every time? <span class="anchor-reference-id">(<a href="#long4">#long4</a>)</span> 
Nazwa &bdquo;GNU/Linux&rdquo; sprawia kłopot, bo&nbsp;jest za&nbsp;długa. Dlaczego mam się wysilać aby&nbsp;mówić &bdquo;GNU/&rdquo;? <span class="anchor-reference-id">(<a href="#long">#long2</a>)</span> 
177 | [-Many companies contributed to-]{+systemd plays an important role in+}
| the {+GNU/Linux+} system as it is today; [-doesn't that mean-] {+are+} we
| [-ought-] {+obligated+} to call it [-GNU/Red&nbsp;Hat/Novell/Linux?-]
| {+GNU/systemd/Linux?+} <span class="anchor-reference-id">(<a
| [-href="#manycompanies">#manycompanies</a>)</span>-]
| {+href="#others">#others</a>)</span>+} 
systemd plays an important role in the GNU/Linux system as it is today; are we obligated to call it GNU/systemd/Linux? <span class="anchor-reference-id">(<a href="#others">#others</a>)</span> 
Wiele przedsiębiorstw wniosło swój wkład do&nbsp;systemu, czyniąc go takim, jaki jest dzisiaj; czyżby to znaczyło, że&nbsp;powinniśmy go nazywać GNU/Red&nbsp;hat/Novell/Linux? <span class="anchor-reference-id">(<a href="#manycompanies">#manycompanies</a>)</span> 
191 | We're not talking about a distinct GNU version of Linux, the kernel. The
| free GNU/Linux distros do have a <a
| [-href="http://directory.fsf.org/project/linux">separate-]
| {+href="https://directory.fsf.org/wiki/Linux-libre">separate+} version
| of Linux</a>, since the &ldquo;standard&rdquo; version contains
| non[---]free firmware [-&ldquo;blobs&rdquo;.-] {+&ldquo;blobs.&rdquo;+} If
| this were part of the GNU Project, it could be considered &ldquo;GNU
| Linux&rdquo;; but we would not want to call it that, because it would be
| too confusing. 
We're not talking about a distinct GNU version of Linux, the kernel. The free GNU/Linux distros do have a <a href="https://directory.fsf.org/wiki/Linux-libre">separate version of Linux</a>, since the &ldquo;standard&rdquo; version contains nonfree firmware &ldquo;blobs.&rdquo; If this were part of the GNU Project, it could be considered &ldquo;GNU Linux&rdquo;; but we would not want to call it that, because it would be too confusing. 
Nie mamy na&nbsp;myśli odrębnej wersji GNU jądra Linux. Wolne dystrybucje GNU/Linuksa posiadają <a href="http://directory.fsf.org/project/linux">oddzielną wersję Linuksa</a>, od&nbsp;kiedy &bdquo;standardowa&rdquo; wersja zawiera niewolne części firmware'u. Jeżeli&nbsp;byłyby one częścią projektu GNU, mogłyby wchodzić w&nbsp;skład &bdquo;GNU Linuksa&rdquo;, jednak&nbsp;nie chcemy używać takiej nazwy, ponieważ&nbsp;byłaby ona zbyt myląca. 
194 | [-Should we say &ldquo;GNU/BSD&rdquo; too?-]{+How is the name
| &ldquo;GNU/Linux&rdquo; pronounced?+} <span
| class="anchor-reference-id">(<a [-href="#bsd">#bsd</a>)</span>-]
| {+href="#pronounce">#pronounce</a>)</span>+} 
How is the name &ldquo;GNU/Linux&rdquo; pronounced? <span class="anchor-reference-id">(<a href="#pronounce">#pronounce</a>)</span> 
Czy&nbsp;powinniśmy również mówić &bdquo;GNU/BSD&rdquo;? <span class="anchor-reference-id">(<a href="#bsd">#bsd</a>)</span> 
195  
Please pronounce it as &ldquo;GNU slash Linux.&rdquo; If you don't pronounce the slash, people will think you are saying &ldquo;GNU Linux,&rdquo; which is <a href="#whyslash">not a suitable name for the combination</a>. 
 
196 | Why do you write [-&ldquo;GNU/Linux&rdquo; instead of-] &ldquo;GNU
| [-Linux&rdquo;?-] {+Emacs&rdquo; rather than &ldquo;GNU/Emacs&rdquo;?+}
| <span class="anchor-reference-id">(<a
| [-href="#whyslash">#whyslash</a>)</span>-]
| {+href="#whynoslash">#whynoslash</a>)</span>+} 
Why do you write &ldquo;GNU Emacs&rdquo; rather than &ldquo;GNU/Emacs&rdquo;? <span class="anchor-reference-id">(<a href="#whynoslash">#whynoslash</a>)</span> 
Czemu piszecie &bdquo;GNU/Linux&rdquo; zamiast &bdquo;GNU Linux&rdquo;? <span class="anchor-reference-id">(<a href="#whyslash">#whyslash</a>)</span> 
243 | The first such recursive acronym was TINT, &ldquo;TINT Is Not
| [-TECO&rdquo;.-] {+TECO.&rdquo;+} The author of TINT wrote another
| implementation of TECO (there were already many of them, for various
| systems), but instead of calling it by a dull name like
| &ldquo;<em>somethingorother</em> [-TECO&rdquo;,-] {+TECO,&rdquo;+} he
| thought of a clever amusing name. (That's what hacking means: <a
| href="http{+s+}://stallman.org/articles/on-hacking.html">playful
| cleverness</a>.) 
The first such recursive acronym was TINT, &ldquo;TINT Is Not TECO.&rdquo; The author of TINT wrote another implementation of TECO (there were already many of them, for various systems), but instead of calling it by a dull name like &ldquo;<em>somethingorother</em> TECO,&rdquo; he thought of a clever amusing name. (That's what hacking means: <a href="https://stallman.org/articles/on-hacking.html">playful cleverness</a>.) 
Pierwszym takim rekursywnym akronimem był TINT, &bdquo;TINT Is Not TECO&rdquo; [TINT To Nie TECO]. Autor programu TINT napisał kolejną implementację TECO (było ich już wiele, dostępnych dla różnych systemów), ale&nbsp;zamiast nazywać ją nudną nazwą typu &bdquo;takiczyinny TECO&rdquo;, wymyślił pomysłową, zabawną nazwę. (To właśnie znaczy hacking: <a href="http://stallman.org/articles/on-hacking.html">pomysłowość i&nbsp;dobra zabawa</a>). 
266  
Is it correct to say &ldquo;using Linux&rdquo; if it refers to using GNU/Linux and using Android? <span class="anchor-reference-id">(<a href="#usegnulinuxandandroidlinuxsyswithoutgnu">#usegnulinuxandandroidlinuxsyswithoutgnu</a>)</span> 
 
278 | He recognized this at the beginning. The {+<a
| href="https://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01">+}
| earliest Linux release [-notes said, <a
| href="http://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01">
| &ldquo;Most of the tools used with linux are GNU software and are under
| the GNU copyleft. These tools aren't in the distribution - ask me (or GNU)
| for more info&rdquo;</a>.-] {+notes</a> said:+} 
He recognized this at the beginning. The <a href="https://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01"> earliest Linux release notes</a> said: 
Przyznał się do&nbsp;tego na&nbsp;samym początku. Uwagi do&nbsp;wydania najwcześniejszego Linuksa mówiły, <a href="http://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01"> &bdquo;Większość narzędzi używanym wraz z&nbsp;linuksem są oprogramowaniem GNU i&nbsp;są wydane na&nbsp;licencji GNU copyleft. Te narzędzia nie są w&nbsp;dystrybucji&nbsp;&ndash; aby&nbsp;dowiedzieć się więcej, zapytaj mnie (albo GNU)&rdquo;</a>. 
279 | [-He recognized this at the beginning. The earliest Linux release notes
| said, <a
| href="http://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01">
| &ldquo;Most-]{+Most+} of the tools used with linux are GNU software and
| are under the GNU copyleft. These tools aren't in the distribution - ask
| me (or GNU) for more [-info&rdquo;</a>.-] {+info.+} 
Most of the tools used with linux are GNU software and are under the GNU copyleft. These tools aren't in the distribution - ask me (or GNU) for more info. 
Przyznał się do&nbsp;tego na&nbsp;samym początku. Uwagi do&nbsp;wydania najwcześniejszego Linuksa mówiły, <a href="http://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01"> &bdquo;Większość narzędzi używanym wraz z&nbsp;linuksem są oprogramowaniem GNU i&nbsp;są wydane na&nbsp;licencji GNU copyleft. Te narzędzia nie są w&nbsp;dystrybucji&nbsp;&ndash; aby&nbsp;dowiedzieć się więcej, zapytaj mnie (albo GNU)&rdquo;</a>. 
282 | Making the GNU Hurd work well enough to compete with Linux would be a big
| job, and it's not clearly necessary. The only thing ethically wrong with
| Linux as a kernel is its inclusion of firmware &ldquo;blobs&rdquo;; the
| best fix for that problem is <a
| [-href="http://fsf.org/campaigns/priority-projects">-]
| {+href="https://www.fsf.org/campaigns/priority-projects">+} developing
| free replacement for the blobs</a>. 
Making the GNU Hurd work well enough to compete with Linux would be a big job, and it's not clearly necessary. The only thing ethically wrong with Linux as a kernel is its inclusion of firmware &ldquo;blobs&rdquo;; the best fix for that problem is <a href="https://www.fsf.org/campaigns/priority-projects"> developing free replacement for the blobs</a>. 
Doprowadzenie GNU Hurd do&nbsp;takiego stopnia aby&nbsp;konkurował z&nbsp;Linuksem byłoby sporym przedsięwzięciem i&nbsp;nie jest konieczne. Jedyną nieetyczną sprawą z&nbsp;Linuksem jako jądrem jest załączaniem &bdquo;blobów&rdquo; w&nbsp;postaci firmware; najlepszym rozwiązaniem jest <a href="http://fsf.org/campaigns/priority-projects">rozwijaniem wolnych zamienników tych blobów</a>. 
323  
Please send general FSF &amp; GNU inquiries to <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>. There are also <a href="/contact/">other ways to contact</a> the FSF. Broken links and other corrections or suggestions can be sent to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>. 
Wszelkie pytania dotyczące GNU i&nbsp;FSF prosimy kierować na&nbsp;adres <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>. Inne metody kontaktu z&nbsp;FSF można znaleźć na&nbsp;stronie <a href="/contact/contact.html">kontakt</a> <br /> Informacje o niedziałających odnośnikach oraz&nbsp;inne poprawki (lub propozycje) prosimy wysyłać na&nbsp;adres <a href="mailto:web-translators@gnu.org">&lt;web-translators@gnu.org&gt;</a>. 
324 || No change detected. The change might only be in amounts of spaces. 
Please see the <a href="/server/standards/README.translations.html">Translations README</a> for information on coordinating and contributing translations of this article. 
Staramy się, aby&nbsp;tłumaczenia były wierne i&nbsp;wysokiej jakości, ale&nbsp;nie jesteśmy zwolnieni z&nbsp;niedoskonałości. Komentarze odnośnie tłumaczenia polskiego oraz&nbsp;zgłoszenia dotyczące chęci współpracy w&nbsp;tłumaczeniu prosimy kierować na&nbsp;adres <a href="mailto:www-pl-trans@gnu.org">www-pl-trans@gnu.org</a>. <br /> Więcej informacji na&nbsp;temat koordynacji oraz&nbsp;zgłaszania propozycji tłumaczeń artykułów znajdziecie na&nbsp;<a href="/server/standards/README.translations.html">stronie tłumaczeń</a>.