- Whitespac changes; translators may ignore
This commit is contained in:
parent
736c0caff1
commit
adbdb3187f
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=42403
10 changed files with 135 additions and 69 deletions
en_US.ISO8859-1
articles/contributing
books
arch-handbook
developers-handbook/policies
handbook
boot
cutting-edge
install
introduction
l10n
network-servers
|
@ -412,7 +412,8 @@
|
|||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>The BSD copyright<indexterm><primary>BSD copyright</primary></indexterm>. This copyright is most preferred
|
||||
<para>The BSD copyright<indexterm><primary>BSD copyright</primary>
|
||||
</indexterm>. This copyright is most preferred
|
||||
due to its <quote>no strings attached</quote> nature and
|
||||
general attractiveness to commercial enterprises. Far
|
||||
from discouraging such commercial use, the FreeBSD Project
|
||||
|
|
|
@ -155,8 +155,9 @@
|
|||
free the <structname>devq</structname> also because we can do
|
||||
nothing else with it and we want to conserve memory.</para>
|
||||
|
||||
<para>If a SCSI card has multiple SCSI buses<indexterm><primary>SCSI</primary><secondary>bus</secondary></indexterm> on it then each bus
|
||||
requires its own <structname>cam_sim</structname>
|
||||
<para>If a SCSI card has multiple SCSI buses<indexterm>
|
||||
<primary>SCSI</primary><secondary>bus</secondary></indexterm>
|
||||
on it then each bus requires its own <structname>cam_sim</structname>
|
||||
structure.</para>
|
||||
|
||||
<para>An interesting question is what to do if a SCSI card has
|
||||
|
@ -227,7 +228,8 @@
|
|||
</itemizedlist>
|
||||
|
||||
<para>Finally we register the SCSI buses associated with our SCSI
|
||||
adapter<indexterm><primary>SCSI</primary><secondary>adapter</secondary></indexterm>:</para>
|
||||
adapter<indexterm><primary>SCSI</primary><secondary>adapter</secondary>
|
||||
</indexterm>:</para>
|
||||
|
||||
<programlisting> if(xpt_bus_register(sim, bus_number) != CAM_SUCCESS) {
|
||||
cam_sim_free(sim, /*free_devq*/ TRUE);
|
||||
|
@ -605,9 +607,10 @@
|
|||
}</programlisting>
|
||||
|
||||
<para>Then allocate whatever data structures (such as
|
||||
card-dependent hardware control block<indexterm><primary>hardware control block</primary></indexterm>) we need to process this
|
||||
request. If we can not then freeze the SIM queue and remember
|
||||
that we have a pending operation, return the CCB back and ask
|
||||
card-dependent hardware control block<indexterm>
|
||||
<primary>hardware control block</primary></indexterm>) we need
|
||||
to process this request. If we can not then freeze the SIM queue and
|
||||
remember that we have a pending operation, return the CCB back and ask
|
||||
CAM to re-queue it. Later when the resources become available
|
||||
the SIM queue must be unfrozen by returning a ccb with the
|
||||
<literal>CAM_SIMQ_RELEASE</literal> bit set in its status. Otherwise, if all went
|
||||
|
@ -1258,9 +1261,10 @@ of the union ccb:</para>
|
|||
</itemizedlist>
|
||||
|
||||
<para>If the returned geometry differs much enough from what the
|
||||
SCSI controller BIOS<indexterm><primary>SCSI</primary><secondary>BIOS</secondary></indexterm> thinks and a disk on this SCSI controller
|
||||
is used as bootable the system may not be able to boot. The
|
||||
typical calculation example taken from the aic7xxx driver
|
||||
SCSI controller BIOS<indexterm><primary>SCSI</primary>
|
||||
<secondary>BIOS</secondary></indexterm> thinks and a disk
|
||||
on this SCSI controller is used as bootable the system may not be able
|
||||
to boot. The typical calculation example taken from the aic7xxx driver
|
||||
is:</para>
|
||||
|
||||
<programlisting> struct ccb_calc_geometry *ccg;
|
||||
|
|
|
@ -122,7 +122,8 @@
|
|||
DRIVER_MODULE(snd_xxxpci, pci, xxx_driver, pcm_devclass, 0, 0);
|
||||
MODULE_DEPEND(snd_xxxpci, snd_pcm, PCM_MINVER, PCM_PREFVER,PCM_MAXVER);</programlisting>
|
||||
|
||||
<para>Most sound drivers<indexterm><primary>device drivers</primary><secondary>sound</secondary></indexterm> need to store additional private
|
||||
<para>Most sound drivers<indexterm><primary>device drivers</primary>
|
||||
<secondary>sound</secondary></indexterm> need to store additional private
|
||||
information about their device. A private data structure is
|
||||
usually allocated in the attach routine. Its address is
|
||||
passed to <devicename>pcm</devicename> by the calls to
|
||||
|
|
|
@ -454,12 +454,14 @@
|
|||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>The <ulink url="&url.base;/administration.html#t-core">Core team</ulink><indexterm><primary>core team</primary></indexterm> decides if
|
||||
<para>The <ulink url="&url.base;/administration.html#t-core">Core team</ulink><indexterm>
|
||||
<primary>core team</primary></indexterm> decides if
|
||||
the code should be part of <command>make world</command>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>The <ulink url="&url.base;/administration.html#t-re">Release Engineering</ulink><indexterm><primary>release engineering</primary></indexterm>
|
||||
<para>The <ulink url="&url.base;/administration.html#t-re">Release Engineering</ulink><indexterm>
|
||||
<primary>release engineering</primary></indexterm>
|
||||
decides if it goes into the release.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
|
|
@ -519,9 +519,10 @@ boot:</screen>
|
|||
|
||||
<para>Use <filename>kernel.GENERIC</filename> to refer to
|
||||
the default kernel that comes with an installation, or
|
||||
<filename>kernel.old</filename><indexterm><primary><filename>kernel.old</filename></primary></indexterm> to refer to the
|
||||
previously installed kernel before a system upgrade or
|
||||
before configuring a custom kernel.</para>
|
||||
<filename>kernel.old</filename><indexterm>
|
||||
<primary><filename>kernel.old</filename></primary></indexterm>
|
||||
to refer to the previously installed kernel before a system
|
||||
upgrade or before configuring a custom kernel.</para>
|
||||
|
||||
<note>
|
||||
<para>Use the following to load the usual modules with
|
||||
|
|
|
@ -1334,7 +1334,10 @@ Fetching 133 new ports or files... done.</screen>
|
|||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Use <link linkend="svn">svn</link><indexterm><primary>Subversion</primary></indexterm><indexterm><primary>-CURRENT</primary><secondary>Syncing with <application>Subversion</application></secondary></indexterm> to check out
|
||||
<para>Use <link linkend="svn">svn</link><indexterm><primary>Subversion</primary>
|
||||
</indexterm><indexterm><primary>-CURRENT</primary>
|
||||
<secondary>Syncing with <application>Subversion</application></secondary>
|
||||
</indexterm> to check out
|
||||
the desired development or release branch. This is
|
||||
the recommended method, providing access to &os;
|
||||
development as it occurs. Checkout the -CURRENT
|
||||
|
@ -1347,7 +1350,9 @@ Fetching 133 new ports or files... done.</screen>
|
|||
|
||||
<listitem>
|
||||
<para>Use the <application><link
|
||||
linkend="ctm">CTM</link></application><indexterm><primary>-CURRENT</primary><secondary>Syncing with CTM</secondary></indexterm> facility.
|
||||
linkend="ctm">CTM</link></application><indexterm>
|
||||
<primary>-CURRENT</primary><secondary>Syncing with CTM</secondary>
|
||||
</indexterm> facility.
|
||||
If you have bad connectivity such as high price
|
||||
connections or only email access,
|
||||
<application>CTM</application> is an option, but it
|
||||
|
@ -1369,7 +1374,8 @@ Fetching 133 new ports or files... done.</screen>
|
|||
compile just a subset is almost guaranteed to cause
|
||||
problems.</para>
|
||||
|
||||
<para>Before compiling &os.current;<indexterm><primary>-CURRENT</primary><secondary>compiling</secondary></indexterm>, read
|
||||
<para>Before compiling &os.current;<indexterm><primary>-CURRENT</primary>
|
||||
<secondary>compiling</secondary></indexterm>, read
|
||||
<filename>/usr/src/Makefile</filename> very carefully.
|
||||
<link linkend="makeworld">Install a new kernel and
|
||||
rebuild the world</link> the first time through as part
|
||||
|
@ -1497,14 +1503,17 @@ Fetching 133 new ports or files... done.</screen>
|
|||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Use <link linkend="svn">svn</link><indexterm><primary>Subversion</primary></indexterm> to check out
|
||||
<para>Use <link linkend="svn">svn</link><indexterm>
|
||||
<primary>Subversion</primary></indexterm> to check out
|
||||
the desired development or release branch. This is
|
||||
the recommended method, providing access to &os;
|
||||
development as it occurs. Branch names include
|
||||
<literal>head</literal> for the current development
|
||||
head, and branches identified in <ulink
|
||||
url="&url.base;/releng/">the release engineering
|
||||
page</ulink>, such as <literal>stable/9</literal><indexterm><primary>-STABLE</primary><secondary>syncing with <application>Subversion</application></secondary></indexterm>
|
||||
page</ulink>, such as <literal>stable/9</literal><indexterm>
|
||||
<primary>-STABLE</primary>
|
||||
<secondary>syncing with <application>Subversion</application></secondary></indexterm>
|
||||
or <literal>releng/9.0</literal>. URL prefixes for
|
||||
<application>Subversion</application> checkout of
|
||||
the base system are shown in <link
|
||||
|
@ -1517,14 +1526,17 @@ Fetching 133 new ports or files... done.</screen>
|
|||
|
||||
<listitem>
|
||||
<para>Consider using <application><link
|
||||
linkend="ctm">CTM</link></application><indexterm><primary>-STABLE</primary><secondary>syncing with CTM</secondary></indexterm> if you do
|
||||
linkend="ctm">CTM</link></application><indexterm>
|
||||
<primary>-STABLE</primary><secondary>syncing with CTM</secondary>
|
||||
</indexterm> if you do
|
||||
not have a fast connection to the Internet.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Before compiling &os.stable;<indexterm><primary>-STABLE</primary><secondary>compiling</secondary></indexterm>, read
|
||||
<para>Before compiling &os.stable;<indexterm><primary>-STABLE</primary>
|
||||
<secondary>compiling</secondary></indexterm>, read
|
||||
<filename>/usr/src/Makefile</filename> carefully. <link
|
||||
linkend="makeworld">Install a new kernel and rebuild
|
||||
the world</link> the first time through as part of the
|
||||
|
|
|
@ -2293,8 +2293,9 @@ Mounting root from ufs:/dev/md0c
|
|||
|
||||
<listitem>
|
||||
<para>This option instructs &man.sysinstall.8;
|
||||
to use passive mode<indexterm><primary>FTP</primary><secondary>passive mode</secondary></indexterm> for all FTP
|
||||
operations.
|
||||
to use passive mode<indexterm>
|
||||
<primary>FTP</primary><secondary>passive mode</secondary>
|
||||
</indexterm> for all FTP operations.
|
||||
This allows the user to pass through firewalls
|
||||
that do not allow incoming connections on random TCP ports.
|
||||
</para>
|
||||
|
@ -2313,7 +2314,8 @@ Mounting root from ufs:/dev/md0c
|
|||
the requests and send them to the FTP server.
|
||||
This allows the user to pass through firewalls
|
||||
that do not allow FTP, but offer a HTTP
|
||||
proxy<indexterm><primary>FTP</primary><secondary>via a HTTP proxy</secondary></indexterm>.
|
||||
proxy<indexterm><primary>FTP</primary>
|
||||
<secondary>via a HTTP proxy</secondary></indexterm>.
|
||||
In this case, specify the proxy in
|
||||
addition to the FTP server.</para>
|
||||
</listitem>
|
||||
|
|
|
@ -78,14 +78,16 @@
|
|||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><emphasis>Preemptive multitasking</emphasis><indexterm><primary>preemptive multitasking</primary></indexterm> with
|
||||
<para><emphasis>Preemptive multitasking</emphasis><indexterm>
|
||||
<primary>preemptive multitasking</primary></indexterm> with
|
||||
dynamic priority adjustment to ensure smooth and fair
|
||||
sharing of the computer between applications and users,
|
||||
even under the heaviest of loads.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><emphasis>Multi-user facilities</emphasis><indexterm><primary>multi-user facilities</primary></indexterm> which allow
|
||||
<para><emphasis>Multi-user facilities</emphasis><indexterm>
|
||||
<primary>multi-user facilities</primary></indexterm> which allow
|
||||
many people to use a &os; system simultaneously for a
|
||||
variety of things. This means, for example, that system
|
||||
peripherals such as printers and tape drives are properly
|
||||
|
@ -95,7 +97,8 @@
|
|||
over-use.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Strong <emphasis>TCP/IP networking</emphasis><indexterm><primary>TCP/IP networking</primary></indexterm> with
|
||||
<para>Strong <emphasis>TCP/IP networking</emphasis><indexterm>
|
||||
<primary>TCP/IP networking</primary></indexterm> with
|
||||
support for industry standards such as SCTP, DHCP, NFS,
|
||||
NIS, PPP, SLIP, IPsec, and IPv6. This means that your
|
||||
&os; machine can interoperate easily with other systems as
|
||||
|
@ -106,7 +109,8 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><emphasis>Memory protection</emphasis><indexterm><primary>memory protection</primary></indexterm> ensures that
|
||||
<para><emphasis>Memory protection</emphasis><indexterm>
|
||||
<primary>memory protection</primary></indexterm> ensures that
|
||||
applications (or users) cannot interfere with each other.
|
||||
One application crashing will not affect others in any
|
||||
way.</para>
|
||||
|
@ -114,7 +118,9 @@
|
|||
|
||||
<listitem>
|
||||
<para>The industry standard <emphasis>X Window
|
||||
System</emphasis><indexterm><primary>X Window System</primary></indexterm> (X11R7) provides a graphical user
|
||||
System</emphasis><indexterm>
|
||||
<primary>X Window System</primary></indexterm>
|
||||
(X11R7) provides a graphical user
|
||||
interface (GUI) for the cost of a common VGA card and
|
||||
monitor and comes with full sources.</para>
|
||||
</listitem>
|
||||
|
@ -163,7 +169,8 @@
|
|||
compile.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Demand paged <emphasis>virtual memory</emphasis><indexterm><primary>virtual memory</primary></indexterm> and
|
||||
<para>Demand paged <emphasis>virtual memory</emphasis><indexterm>
|
||||
<primary>virtual memory</primary></indexterm> and
|
||||
<quote>merged VM/buffer cache</quote> design efficiently
|
||||
satisfies applications with large appetites for memory
|
||||
while still maintaining interactive response to other
|
||||
|
@ -171,8 +178,9 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><emphasis>SMP</emphasis><indexterm><primary>Symmetric Multi-Processing (SMP)</primary></indexterm> support for machines with
|
||||
multiple CPUs.</para>
|
||||
<para><emphasis>SMP</emphasis><indexterm>
|
||||
<primary>Symmetric Multi-Processing (SMP)</primary></indexterm>
|
||||
support for machines with multiple CPUs.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -194,7 +202,8 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><emphasis>Source code</emphasis><indexterm><primary>source code</primary></indexterm> for the entire system
|
||||
<para><emphasis>Source code</emphasis><indexterm>
|
||||
<primary>source code</primary></indexterm> for the entire system
|
||||
means you have the greatest degree of control over your
|
||||
environment. Why be locked into a proprietary solution
|
||||
at the mercy of your vendor when you can have a truly open
|
||||
|
@ -211,8 +220,11 @@
|
|||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>&os; is based on the 4.4BSD-Lite<indexterm><primary>4.4BSD-Lite</primary></indexterm> release from Computer
|
||||
Systems Research Group (CSRG)<indexterm><primary>Computer Systems Research Group (CSRG)</primary></indexterm> at the University of California
|
||||
<para>&os; is based on the 4.4BSD-Lite<indexterm>
|
||||
<primary>4.4BSD-Lite</primary></indexterm> release from Computer
|
||||
Systems Research Group (CSRG)<indexterm>
|
||||
<primary>Computer Systems Research Group (CSRG)</primary></indexterm>
|
||||
at the University of California
|
||||
at Berkeley, and carries on the distinguished tradition of BSD
|
||||
systems development. In addition to the fine work provided by
|
||||
CSRG, the &os; Project has put in many thousands of hours
|
||||
|
@ -251,11 +263,13 @@
|
|||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>FTP servers<indexterm><primary>FTP servers</primary></indexterm></para>
|
||||
<para>FTP servers<indexterm>
|
||||
<primary>FTP servers</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>World Wide Web servers<indexterm><primary>web servers</primary></indexterm> (standard or secure
|
||||
<para>World Wide Web servers<indexterm>
|
||||
<primary>web servers</primary></indexterm> (standard or secure
|
||||
[SSL])</para>
|
||||
</listitem>
|
||||
|
||||
|
@ -264,8 +278,9 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Firewalls<indexterm><primary>firewall</primary></indexterm> and NAT<indexterm><primary>NAT</primary></indexterm> (<quote>IP masquerading</quote>)
|
||||
gateways</para>
|
||||
<para>Firewalls<indexterm><primary>firewall</primary></indexterm>
|
||||
and NAT<indexterm><primary>NAT</primary></indexterm>
|
||||
(<quote>IP masquerading</quote>) gateways</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -281,7 +296,8 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>USENET<indexterm><primary>USENET</primary></indexterm> News or Bulletin Board Systems</para>
|
||||
<para>USENET<indexterm><primary>USENET</primary></indexterm>
|
||||
News or Bulletin Board Systems</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -319,8 +335,11 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><emphasis>Networking:</emphasis> Need a new router?<indexterm><primary>router</primary></indexterm>
|
||||
A name server (DNS)?<indexterm><primary>DNS Server</primary></indexterm> A firewall to keep people out of your
|
||||
<para><emphasis>Networking:</emphasis> Need a new router?<indexterm>
|
||||
<primary>router</primary></indexterm>
|
||||
A name server (DNS)?<indexterm>
|
||||
<primary>DNS Server</primary></indexterm> A firewall to
|
||||
keep people out of your
|
||||
internal network? &os; can easily turn that unused 386 or
|
||||
486 PC sitting in the corner into an advanced router with
|
||||
sophisticated packet-filtering capabilities.</para>
|
||||
|
@ -348,8 +367,9 @@
|
|||
<listitem>
|
||||
<para><emphasis>Software Development:</emphasis> The basic
|
||||
&os; system comes with a full complement of development
|
||||
tools including the renowned GNU C/C++<indexterm><primary>GNU Compiler Collection</primary></indexterm> compiler and
|
||||
debugger.</para>
|
||||
tools including the renowned GNU
|
||||
C/C++<indexterm><primary>GNU Compiler Collection</primary></indexterm>
|
||||
compiler and debugger.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
@ -373,12 +393,14 @@
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.apple.com/">Apple</ulink><indexterm><primary>Apple</primary></indexterm></para>
|
||||
url="http://www.apple.com/">Apple</ulink><indexterm>
|
||||
<primary>Apple</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.cisco.com/">Cisco</ulink><indexterm><primary>Cisco</primary></indexterm></para>
|
||||
url="http://www.cisco.com/">Cisco</ulink><indexterm>
|
||||
<primary>Cisco</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -388,7 +410,8 @@
|
|||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.netapp.com/">NetApp</ulink><indexterm><primary>NetApp</primary></indexterm></para>
|
||||
url="http://www.netapp.com/">NetApp</ulink><indexterm>
|
||||
<primary>NetApp</primary></indexterm></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
@ -398,61 +421,73 @@
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.yahoo.com/">Yahoo!</ulink><indexterm><primary>Yahoo!</primary></indexterm></para>
|
||||
url="http://www.yahoo.com/">Yahoo!</ulink><indexterm>
|
||||
<primary>Yahoo!</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.yandex.ru/">Yandex</ulink><indexterm><primary>Yandex</primary></indexterm></para>
|
||||
url="http://www.yandex.ru/">Yandex</ulink><indexterm>
|
||||
<primary>Yandex</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.apache.org/">Apache</ulink><indexterm><primary>Apache</primary></indexterm></para>
|
||||
url="http://www.apache.org/">Apache</ulink><indexterm>
|
||||
<primary>Apache</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.rambler.ru/">Rambler</ulink><indexterm><primary>Rambler</primary></indexterm></para>
|
||||
url="http://www.rambler.ru/">Rambler</ulink><indexterm>
|
||||
<primary>Rambler</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink url="http://www.sina.com/">Sina</ulink><indexterm><primary>Sina</primary></indexterm></para>
|
||||
<para><ulink url="http://www.sina.com/">Sina</ulink><indexterm>
|
||||
<primary>Sina</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.pair.com/">Pair Networks</ulink><indexterm><primary>Pair Networks</primary></indexterm></para>
|
||||
url="http://www.pair.com/">Pair Networks</ulink><indexterm>
|
||||
<primary>Pair Networks</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.sony.co.jp/">Sony Japan</ulink><indexterm><primary>Sony Japan</primary></indexterm></para>
|
||||
url="http://www.sony.co.jp/">Sony Japan</ulink><indexterm>
|
||||
<primary>Sony Japan</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.netcraft.com/">Netcraft</ulink><indexterm><primary>Netcraft</primary></indexterm></para>
|
||||
url="http://www.netcraft.com/">Netcraft</ulink><indexterm>
|
||||
<primary>Netcraft</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.163.com/">NetEase</ulink><indexterm><primary>NetEase</primary></indexterm></para>
|
||||
url="http://www.163.com/">NetEase</ulink><indexterm>
|
||||
<primary>NetEase</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.weathernews.com/">Weathernews</ulink><indexterm><primary>Weathernews</primary></indexterm></para>
|
||||
url="http://www.weathernews.com/">Weathernews</ulink><indexterm>
|
||||
<primary>Weathernews</primary></indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink url="http://www.telehouse.com/">TELEHOUSE
|
||||
America</ulink><indexterm><primary>TELEHOUSE America</primary></indexterm></para>
|
||||
America</ulink><indexterm><primary>TELEHOUSE America</primary>
|
||||
</indexterm></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink url="http://www.experts-exchange.com/">Experts
|
||||
Exchange</ulink><indexterm><primary>Experts Exchange</primary></indexterm></para>
|
||||
Exchange</ulink><indexterm><primary>Experts Exchange</primary>
|
||||
</indexterm></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
@ -724,7 +759,8 @@
|
|||
id="development-committers"/></term>
|
||||
|
||||
<listitem>
|
||||
<para>The <firstterm>committers</firstterm><indexterm><primary>committers</primary></indexterm>
|
||||
<para>The <firstterm>committers</firstterm><indexterm>
|
||||
<primary>committers</primary></indexterm>
|
||||
are the people who have <emphasis>write</emphasis>
|
||||
access to the Subversion tree, and are authorized to
|
||||
make modifications to the &os; source (the term
|
||||
|
@ -743,7 +779,8 @@
|
|||
id="development-core"/></term>
|
||||
|
||||
<listitem>
|
||||
<para>The <firstterm>&os; core team</firstterm><indexterm><primary>core team</primary></indexterm>
|
||||
<para>The <firstterm>&os; core team</firstterm><indexterm>
|
||||
<primary>core team</primary></indexterm>
|
||||
would be equivalent to the board of directors if the
|
||||
&os; Project were a company. The primary task of
|
||||
the core team is to make sure the project, as a whole,
|
||||
|
@ -792,7 +829,8 @@
|
|||
|
||||
<para><citetitle><ulink
|
||||
url="&url.articles.contributors;/article.html">The
|
||||
&os; Contributors List</ulink></citetitle><indexterm><primary>contributors</primary></indexterm> is a long
|
||||
&os; Contributors List</ulink></citetitle><indexterm>
|
||||
<primary>contributors</primary></indexterm> is a long
|
||||
and growing one, so why not join it by contributing
|
||||
something back to &os; today?</para>
|
||||
|
||||
|
|
|
@ -254,7 +254,8 @@
|
|||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><envar>LANG</envar> for &posix;<indexterm><primary>POSIX</primary></indexterm> &man.setlocale.3;
|
||||
<para><envar>LANG</envar> for &posix;<indexterm>
|
||||
<primary>POSIX</primary></indexterm> &man.setlocale.3;
|
||||
family functions</para>
|
||||
</listitem>
|
||||
|
||||
|
|
|
@ -1333,7 +1333,8 @@ Exports list on foobar:
|
|||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>A <emphasis>NIS master server</emphasis><indexterm><primary>NIS</primary><secondary>master server</secondary></indexterm>. This
|
||||
<para>A <emphasis>NIS master server</emphasis><indexterm>
|
||||
<primary>NIS</primary><secondary>master server</secondary></indexterm>. This
|
||||
server, analogous to a &windowsnt; primary domain
|
||||
controller, maintains the files used by all of the NIS
|
||||
clients. The <filename>passwd</filename>,
|
||||
|
@ -1348,8 +1349,9 @@ Exports list on foobar:
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><emphasis>NIS slave servers</emphasis><indexterm><primary>NIS</primary><secondary>slave server</secondary></indexterm>. Similar to
|
||||
the &windowsnt; backup domain controllers, NIS slave
|
||||
<para><emphasis>NIS slave servers</emphasis><indexterm>
|
||||
<primary>NIS</primary><secondary>slave server</secondary></indexterm>.
|
||||
Similar to the &windowsnt; backup domain controllers, NIS slave
|
||||
servers maintain copies of the NIS master's data files.
|
||||
NIS slave servers provide the redundancy, which is
|
||||
needed in important environments. They also help to
|
||||
|
@ -1359,7 +1361,9 @@ Exports list on foobar:
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><emphasis>NIS clients</emphasis><indexterm><primary>NIS</primary><secondary>client</secondary></indexterm>. NIS clients, like
|
||||
<para><emphasis>NIS clients</emphasis><indexterm>
|
||||
<primary>NIS</primary><secondary>client</secondary></indexterm>.
|
||||
NIS clients, like
|
||||
most &windowsnt; workstations, authenticate against the
|
||||
NIS server (or the &windowsnt; domain controller in the
|
||||
&windowsnt; workstations case) to log on.</para>
|
||||
|
|
Loading…
Reference in a new issue