This commit is contained in:
gferg 2007-11-28 21:38:15 +00:00
parent 908e643dc3
commit 7de95d089f
1 changed files with 48 additions and 34 deletions

View File

@ -1,6 +1,6 @@
<?xml version="1.0"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://docbook.org/xml/4.1.2/docbookx.dtd" [
"docbook/docbookxx.dtd" [
<!ENTITY howto "http://www.tldp.org/HOWTO/">
<!ENTITY mini-howto "&howto;/mini/">
<!ENTITY howto-host "www.tldp.org">
@ -25,8 +25,8 @@
<revhistory>
<revision>
<revnumber>2.9</revnumber>
<date>2004-03-03</date>
<revnumber>2.10</revnumber>
<date>2007-11-28</date>
<authorinitials>esr</authorinitials>
<revremark>
Minor updates.
@ -34,6 +34,14 @@
</revision>
<!--
<revision>
<revnumber>2.9</revnumber>
<date>2004-03-03</date>
<authorinitials>esr</authorinitials>
<revremark>
Minor updates.
</revremark>
</revision>
<revision>
<revnumber>2.8</revnumber>
<date>2003-10-04</date>
@ -196,12 +204,12 @@ from lack of a good mental model of what is really going on.</para>
<para>I'll try to describe in clear, simple language how it all works. The
presentation will be tuned for people using Unix or Linux on PC-class
hardware. Nevertheless, I'll usually refer simply to &lsquo;Unix&rsquo;
here, as most of what I will describe is constant across platforms and
across Unix variants.</para>
machines. Nevertheless, I'll usually refer simply to &lsquo;Unix&rsquo;
here, as most of what I will describe is constant across different machines
and across Unix variants.</para>
<para>I'm going to assume you're using an Intel PC. The details differ
slightly if you're running an Alpha or PowerPC or some other Unix box, but
slightly if you're running an PowerPC or some other kind of computer, but
the basic concepts are the same.</para>
<para>I won't repeat things, so you'll have to pay attention, but that
@ -220,8 +228,8 @@ periodically.</para>
periodically posted to <ulink url="news:comp.os.linux.help">
comp.os.linux.help</ulink> and <ulink url="news:comp.os.linux.announce">
comp.os.linux.announce</ulink> and <ulink url="news:news.answers">
news.answers</ulink>. They will also be uploaded to various Linux WWW and
FTP sites, including the LDP home page.</para>
news.answers</ulink>. They will also be uploaded to various websites,
including the Linux Documentation Project home page.</para>
<para>You can view the latest version of this on the World Wide Web via the URL
<ulink
@ -229,8 +237,9 @@ url="&howto;Unix-and-Internet-Fundamentals-HOWTO/index.html">
http:&howto;Unix-and-Internet-Fundamentals-HOWTO/index.html</ulink>.
</para>
<para>This document has been translated into <ulink
url="http://theta.uoks.uj.edu.pl/~gszczepa/gszczepa/esr1iso2.htm">Polish</ulink>.</para>
<para>This document has been translated into: <ulink
url="http://theta.uoks.uj.edu.pl/~gszczepa/gszczepa/esr1iso2.htm">Polish</ulink><ulink
url="http://es.tldp.org/Manuales-LuCAS/doc-fundamentos-unix-internet/fundamentos.htm">Spanish</ulink>.</para>
</sect2>
<sect2 id="feedback"><title>Feedback and corrections</title>
@ -348,11 +357,12 @@ that Unix isn't good enough for you.)</para>
<para>Once the kernel starts, it has to look around, find the rest of the
hardware, and get ready to run programs. It does this by poking not at
ordinary memory locations but rather at <firstterm>I/O ports</firstterm> &mdash;
special bus addresses that are likely to have device controller cards
listening at them for commands. The kernel doesn't poke at random; it has
a lot of built-in knowledge about what it's likely to find where, and how
controllers will respond if they're present. This process is called
ordinary memory locations but rather at <firstterm>I/O ports</firstterm>
&mdash; special bus addresses that are likely to have device controller
cards listening at them for commands. The kernel doesn't poke at random;
it has a lot of built-in knowledge about what it's likely to find where,
and how controllers will respond if they're present. This process is
called
<firstterm>autoprobing</firstterm><indexterm><primary>autoprobing</primary></indexterm>.</para>
<para>Most of the messages you see at boot time are the kernel autoprobing
@ -673,8 +683,8 @@ goes on in your machine, you should learn how all of them work.</para>
<para>The five kinds of memory are these: processor registers, internal (or
on-chip) cache, external (or off-chip) cache, main memory, and disk. And
the reason there are so many kinds is simple: speed costs money. I have
listed these kinds of memory in decreasing order of access time and
increasing order of cost. Register memory is the fastest and most
listed these kinds of memory in increasing order of access time and
decreasing order of cost. Register memory is the fastest and most
expensive and can be random-accessed about a billion times a second, while
disk is the slowest and cheapest and can do about 100 random accesses a
second.</para>
@ -920,23 +930,25 @@ accented and other special characters needed by users of other languages.
Even British English has trouble with the lack of a pound-currency
sign.</para>
<para>There have been several attempts to fix this problem. All use the extra
high bit that ASCII doesn't, making it the low half of a 256-character set.
The most widely-used of these is the so-called &lsquo;Latin-1&rsquo; character set
(more formally called ISO 8859-1). This is the default character set for
Linux, HTML, and X. Microsoft Windows uses a mutant version of Latin-1
that adds a bunch of characters such as right and left double quotes in
places proper Latin-1 leaves unassigned for historical reasons (for a
scathing account of the trouble this causes, see the <ulink
<para>There have been several attempts to fix this problem. All use the
extra high bit that ASCII doesn't, making it the low half of a
256-character set. The most widely-used of these is the so-called
&lsquo;Latin-1&rsquo; character set (more formally called ISO 8859-1).
This is the default character set for Linux, older versions of HTML, and X.
Microsoft Windows uses a mutant version of Latin-1 that adds a bunch of
characters such as right and left double quotes in places proper Latin-1
leaves unassigned for historical reasons (for a scathing account of the
trouble this causes, see the <ulink
url="http://www.fourmilab.ch/webtools/demoroniser/">demoroniser</ulink>
page).</para>
<para>Latin-1 handles western European languages, including English,
French, German, Spanish, Italian, Dutch, Norwegian, Swedish, Danish.
However, this isn't good enough either, and as a result there is a whole
series of Latin-2 through -9 character sets to handle things like Greek,
Arabic, Hebrew, Esperanto, and Serbo-Croatian. For details, see the <ulink
url="http://www.utia.cas.cz/user_data/vs/documents/ISO-8859-X-charsets.html">
French, German, Spanish, Italian, Dutch, Norwegian, Swedish, Danish, and
Icelandic. However, this isn't good enough either, and as a result there
is a whole series of Latin-2 through -9 character sets to handle things
like Greek, Arabic, Hebrew, Esperanto, and Serbo-Croatian. For details,
see the <ulink
url="http://czyborra.com/charsets/iso8859.html">
ISO alphabet soup</ulink> page.</para>
<para>The ultimate solution is a huge standard called Unicode (and its
@ -946,7 +958,8 @@ Cyrillic, Armenian, Hebrew, Arabic, Devanagari, Bengali, Gurmukhi,
Gujarati, Oriya, Tamil, Telugu, Kannada, Malayalam, Thai, Lao, Georgian,
Tibetan, Japanese Kana, the complete set of modern Korean Hangul, and a
unified set of Chinese/Japanese/Korean (CJK) ideographs. For details, see
the <ulink url="http://www.unicode.org/">Unicode Home Page</ulink>.</para>
the <ulink url="http://www.unicode.org/">Unicode Home Page</ulink>. XML
and XHTML use this character set.</para>
</sect2>
</sect1>
@ -1265,7 +1278,7 @@ including Linux, the latter behavior can be selected by setting the
set-group-ID on the directory (chmod g+s).</para>
</sect2>
<sect2><title id="fsck">How things can go wrong</title>
<sect2 id="fsck"><title>How things can go wrong</title>
<para>Earlier it was hinted that file systems can be fragile things.
Now we know that to get to a file you have to hopscotch through what may be
@ -1381,7 +1394,7 @@ Today, Unix shells and the Lisp that lives inside the Emacs editor are
probably the most important pure interpreted languages.</para>
</sect2>
<sect2><title>P-code languages</title>
<sect2 id="pcode"><title>P-code languages</title>
<para>Since 1990 a kind of hybrid language that uses both compilation and
interpretation has become increasingly important. P-code languages are
@ -1677,3 +1690,4 @@ fill-column:75
compile-command: "mail -s \"Unix and Internet Fundamentals HOWTO update\" submit@en.tldp.org <Unix-and-Internet-Fundamentals-HOWTO.xml"
End:
-->