gnu-linux-faq.ko.po

Mismatched links: 44.

Mismatched ids: 0.

#text
8 | <a [-href="#why">Why do you call it GNU/Linux-] {+href="#what">What is
| the real relationship between GNU+} and [-not-] Linux?</a> 
<a href="#what">What is the real relationship between GNU and Linux?</a> 
<a href="#why"> 왜 Linux가 아니라 GNU/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="#whyslash">Why do you write &ldquo;GNU/Linux&rdquo; instead-]
| {+href="#long1">How about calling the system &ldquo;GliNUx&rdquo;
| (instead+} of [-&ldquo;GNU Linux&rdquo;?</a>-]
| {+&ldquo;GNU/Linux&rdquo;)?</a>+} 
<a href="#long1">How about calling the system &ldquo;GliNUx&rdquo; (instead of &ldquo;GNU/Linux&rdquo;)?</a> 
<a href="#whyslash">왜 &ldquo;GNU Linux&rdquo;대신 &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">시스템이 오늘날과 같이 되도록 기여한 회사들이 많습니다. 우리가 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">&ldquo;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">왜 &ldquo;GNU Linux&rdquo;대신 &ldquo;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> 
 
82  
See <a href="/gnu/linux-and-gnu.html">Linux and the GNU System</a> and <a href="/gnu/gnu-users-never-heard-of-gnu.html">GNU Users Who Have Never Heard of GNU</a> for more explanation, and <a href="/gnu/the-gnu-project.html">The GNU Project</a> for the history. 
<a href="/gnu/the-gnu-project.html">GNU프로젝트</a>의 역사와 자세한 설명은 <a href="/gnu/linux-and-gnu.html">Linux와 GNU 시스템</a>과 <a href="/gnu/gnu-users-never-heard-of-gnu.html">GNU에 대해 알지 못하는 GNU 사용자</a>를 읽어보세요. 
86 | [-Why do you call it GNU/Linux-]{+What is the real relationship between
| GNU+} and [-not-] Linux? <span class="anchor-reference-id">(<a
| [-href="#why">#why</a>)</span>-] {+href="#what">#what</a>)</span>+} 
What is the real relationship between GNU and Linux? <span class="anchor-reference-id">(<a href="#what">#what</a>)</span> 
왜 Linux가 아니라 GNU/Linux라고 부르나요? <span class="anchor-reference-id">(<a href="#why">#why</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> 
운영체제를 만들 때 커널 관련 작업이 대부분이지 않나요?<span class="anchor-reference-id">(<a href="#kernelmost">#kernelmost</a>)</span> 
153 | The shortest legitimate name for this system is [-&ldquo;GNU&rdquo;,-]
| {+&ldquo;GNU,&rdquo;+} but we call it &ldquo;GNU/Linux&rdquo; <a
| href="#justgnu"> for the reasons given below</a>. 
The shortest legitimate name for this system is &ldquo;GNU,&rdquo; but we call it &ldquo;GNU/Linux&rdquo; <a href="#justgnu"> for the reasons given below</a>. 
이 시스템을 위한 가장 짧고 합리적인 이름은 &ldquo;GNU&rdquo;이지만, 다음과 같은 이유로 &ldquo;GNU/Linux&rdquo;라 부릅니다. 
154 | [-Why do you write &ldquo;GNU/Linux&rdquo; instead-]{+How about calling
| the system &ldquo;GliNUx&rdquo; (instead+} of [-&ldquo;GNU Linux&rdquo;?-]
| {+&ldquo;GNU/Linux&rdquo;)?+} <span class="anchor-reference-id">(<a
| [-href="#whyslash">#whyslash</a>)</span>-]
| {+href="#long1">#long1</a>)</span>+} 
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> 
왜 &ldquo;GNU Linux&rdquo;대신 &ldquo;GNU/Linux&rdquo;라고 쓰나요?<span class="anchor-reference-id">(<a href="#whyslash">#whyslash</a>)</span> 
161 | [-Why do you write-]{+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; [-instead of &ldquo;GNU Linux&rdquo;?-] {+every
| time?+} <span class="anchor-reference-id">(<a
| [-href="#whyslash">#whyslash</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> 
왜 &ldquo;GNU Linux&rdquo;대신 &ldquo;GNU/Linux&rdquo;라고 쓰나요?<span class="anchor-reference-id">(<a href="#whyslash">#whyslash</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> 
시스템이 오늘날과 같이 되도록 기여한 회사들이 많습니다. 우리가 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. 
우리는 Linux 커널의 구별된 GNU 판에 대해 이야기하는 것이 아닙니다. GNU 프로젝트는 별도의 Linux 판본을 갖고 있지 않습니다. GNU/Linux 시스템은 다른 Linux 판본을 사용하지 않습니다. Linux의 주된 용도는 이런 시스템들에 포함되는 것이고, Linux 표준판이 이런 시스템들을 위해 개발되었습니다. 그래서 &ldquo;Linux의 GNU 판&rdquo; 역시 맞지 않습니다. 
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> 
&ldquo;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> 
왜 &ldquo;GNU Linux&rdquo;대신 &ldquo;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>.) 
이러한 재귀어의 처음은 TINT,&ldquo;TINT Is Not TECO&rdquo;였습니다. TINT라는 이름을 지은 사람은 이미 다양한 시스템에 구현되어 있는 TECO를 달리 구현하고서 &ldquo;<em>무언가 다른</em> TECO&rdquo;라는 시시한 이름으로 부르기 보다는 멋있고 재미있는 이름을 지었습니다. (이것이 바로 해킹이 의미하는 바, <a href="http://stallman.org/articles/on-hacking.html">재치있는 기발함</a>입니다.) 
266 | [-Are there complete Linux systems [sic] without GNU?-]{+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="#linuxsyswithoutgnu">#linuxsyswithoutgnu</a>)</span>-]
| {+href="#usegnulinuxandandroidlinuxsyswithoutgnu">#usegnulinuxandandroidl
| inuxsyswithoutgnu</a>)</span>+} 
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> 
GNU가 없는 완전한 Linux 시스템들이 있나요?<span class="anchor-reference-id">(<a href="#linuxsyswithoutgnu">#linuxsyswithoutgnu</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: 
리누스 토발즈는 처음에는 이를 인식했습니다. 첫 Linux 발표문을 보면 <a href="http://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01"> &ldquo;Linux에 쓰인 대부분의 도구는 GNU 소프트웨어이고 GNU 저작권 아래 있습니다. 이 도구들은 배포판에 들어있지 않습니다. 더 자세한 정보는 저(나 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. 
리누스 토발즈는 처음에는 이를 인식했습니다. 첫 Linux 발표문을 보면 <a href="http://ftp.funet.fi/pub/linux/historical/kernel/old-versions/RELNOTES-0.01"> &ldquo;Linux에 쓰인 대부분의 도구는 GNU 소프트웨어이고 GNU 저작권 아래 있습니다. 이 도구들은 배포판에 들어있지 않습니다. 더 자세한 정보는 저(나 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>. 
Linux와 충분히 경쟁할 만한 GND Hurd를 만드는 작업은 큰 일이 될 것이나 이것이 명확히 필요하지는 않습니다. Linux를 커널로 봤을 때 윤리적으로 옳지 못한 단 한 가지는 펌웨어 &ldquo;blobs&rdquo;의 포함입니다. 이 문제를 해결하는 가장 좋은 방안은 <a href="http://fsf.org/campaigns/priority-projects">무료 대체물인 blobs을 개발하는 것입니다.</a>