Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Oct 2012 22:02:56 +0000 (UTC)
From:      Rene Ladan <rene@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org
Subject:   svn commit: r39869 - translations/nl_NL.ISO8859-1/books/faq
Message-ID:  <201210302202.q9UM2uag085243@svn.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: rene
Date: Tue Oct 30 22:02:55 2012
New Revision: 39869
URL: http://svn.freebsd.org/changeset/doc/39869

Log:
  Merge up to revision 39865

Modified:
  translations/nl_NL.ISO8859-1/books/faq/book.xml

Modified: translations/nl_NL.ISO8859-1/books/faq/book.xml
==============================================================================
--- translations/nl_NL.ISO8859-1/books/faq/book.xml	Tue Oct 30 20:53:16 2012	(r39868)
+++ translations/nl_NL.ISO8859-1/books/faq/book.xml	Tue Oct 30 22:02:55 2012	(r39869)
@@ -6,7 +6,7 @@
 	$FreeBSD$
 
 	%SOURCE%  en_US.ISO8859-1/books/faq/book.xml
-	%SRCID%	  39853
+	%SRCID%	  39865
 -->
 
 <!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
@@ -71,7 +71,6 @@
 
     <legalnotice id="trademarks" role="trademarks">
       &tm-attrib.freebsd;
-      &tm-attrib.3com;
       &tm-attrib.adobe;
       &tm-attrib.creative;
       &tm-attrib.ibm;
@@ -2668,48 +2667,6 @@ bindkey ^[[3~ delete-char # for xterm</p
 	      needs.</para>
 	  </answer>
 	</qandaentry>
-
-	<qandaentry>
-	  <question id="micron-hang-boot">
-	    <para>Why does my Micron system hang at boot time?</para>
-	  </question>
-
-	  <answer>
-	    <para>Certain Micron motherboards have a non-conforming PCI
-	      BIOS implementation that causes grief when &os; boots
-	      because PCI devices do not get configured at their
-	      reported addresses.</para>
-
-	    <para>Disable the <quote>Plug and Play Operating
-	      System</quote> flag in the BIOS to work around this
-	      problem.</para>
-	  </answer>
-	</qandaentry>
-
-	<qandaentry>
-	  <question id="asusk7v-boot-failure">
-	    <para>The boot floppy hangs on a system with an ASUS K7V
-	      motherboard.  How do I fix this?</para>
-	  </question>
-
-	  <answer>
-	    <para>Go into the BIOS setup and disable the <quote>boot
-	      virus protection</quote>.</para>
-	  </answer>
-	</qandaentry>
-
-	<qandaentry>
-	  <question id="micron-3comnic-failure">
-	    <para>Why does my &tm.3com; PCI network card not work with my
-	      Micron computer?</para>
-	  </question>
-
-	  <answer>
-	    <para>See <link
-		linkend="micron-hang-boot">the previous answer</link>.
-	      </para>
-	  </answer>
-	</qandaentry>
       </qandaset>
     </sect1>
   </chapter>
@@ -2870,19 +2827,6 @@ quit</programlisting>
       </qandaentry>
 
       <qandaentry>
-	<question id="bad-3c509">
-	  <para>Why did my &tm.3com; 3C509 card stop working for no
-	    apparent reason?</para>
-	</question>
-
-	<answer>
-	  <para>This card has a bad habit of losing its configuration
-	    information.  Refresh your card's settings with the DOS
-	    utility <command>3c5x9.exe</command>.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
 	<question id="signal11">
 	  <para>Why do my programs occasionally die with
 	    <errorname>Signal 11</errorname> errors?</para>
@@ -2954,8 +2898,8 @@ quit</programlisting>
 		on the processor might have died.  In either case you
 		need to ensure that you have hardware running at what it
 		is specified to run at, at least while trying to solve
-		this problem.  i.e.  Clock it back to the default
-		settings.</para>
+		this problem (in other words, clock it back to the default
+		settings.)</para>
 
 	      <para>If you are overclocking then note that it is far
 		cheaper to have a slow system than a fried system that
@@ -3554,7 +3498,7 @@ chip1@pci0:31:5:        class=0x040100 c
 	      <para>Break the warnings by changing the value of
 		<varname>MAX_STRAY_LOG</varname> from
 		<literal>5</literal> to <literal>0</literal> in your
-		platform's (e.g.  &i386;)
+		platform's (e.g., &i386;)
 		<filename>intr_machdep.c</filename> file and rebuild the
 		new kernel and all the warnings will be
 		suppressed.</para>
@@ -3897,11 +3841,7 @@ kern.timecounter.hardware: TSC -&gt; i82
 	      url="http://www.openoffice.org">OpenOffice.org</ulink></application>;
 	    and <application><ulink
 	      url="http://www.libreoffice.org">LibreOffice</ulink></application>;
-	    office suites work natively on &os;.  The &linux; version of
-	    <application><ulink
-	      url="http://www.oracle.com/us/products/applications/open-office/index.html/">Oralce Open Office</ulink></application>,
-	    the value-added closed-source version of OpenOffice.org,
-	    also works on &os;.</para>
+	    office suites work natively on &os;.</para>
 
 	  <para>&os; also includes a variety of text editors,
 	    spreadsheets, and drawing programs in the Ports
@@ -4234,38 +4174,12 @@ kern.timecounter.hardware: TSC -&gt; i82
 	</question>
 
 	<answer>
-	  <para>First, always make sure that you have a completely
+	  <para>First, always make sure that you have a complete
 	    up-to-date Ports Collection.  Errors that affect building
 	    <filename>INDEX</filename> from an up-to-date copy of the
 	    Ports Collection are high-visibility and are thus almost
 	    always fixed immediately.</para>
 
-	  <para>However, if you are up-to-date, perhaps you are seeing
-	    another problem.  <command>make <maketarget>index</maketarget></command>
-	    has a known bug in dealing with incomplete copies of the
-	    Ports Collection.  It assumes that you have a local copy of
-	    every single port that every other port that you have a
-	    local copy of depends on.  To explain, if you have a copy of
-	    <filename>foo/bar</filename> on your disk, and
-	    <filename>foo/bar</filename> depends on
-	    <filename>baz/quux</filename>, then you must also have a
-	    copy of <filename>baz/quux</filename> on your disk, and the
-	    ports <filename>baz/quux</filename> depends on, and so on.
-	    Otherwise, <command>make <maketarget>index</maketarget></command>
-	    has insufficient information to create its dependency
-	    tree.</para>
-
-	  <para>This is particularly a problem for &os; users who
-	    utilize &man.csup.1; to track the Ports
-	    Collection but choose not to install certain categories by
-	    specifying them in <filename>refuse</filename>.  In theory,
-	    one should be able to refuse categories, but in practice
-	    there are too many ports that depend on ports in other
-	    categories.  Until someone comes up with a solution for this
-	    problem, the general rule is that if you want to build
-	    <filename>INDEX</filename>, you must have a complete copy of
-	    the Ports Collection.</para>
-
 	  <para>There are rare cases where <filename>INDEX</filename>
 	    will not build due to odd cases involving
 	    <makevar>WITH_<replaceable>*</replaceable></makevar> or
@@ -4764,11 +4678,8 @@ kern.sched.name: ULE</screen>
 	    they are getting in contact with such a disk, or even worse,
 	    they might damage the BSD bootstrap without even asking or
 	    notifying you.  In addition, the <quote>dangerously
-	    dedicated</quote> disk's layout is known to confuse many
-	    BIOSes, including those from AWARD (e.g. as found in HP
-	    Netserver and Micronics systems as well as many others) and
-	    Symbios/NCR (for the popular 53C8xx range of SCSI
-	    controllers).  This is not a complete list, there are more.
+	    dedicated</quote> disk's layout is known to confuse some
+	    BIOSes.
 	    Symptoms of this confusion include the <errorname>read
 	    error</errorname> message printed by the &os; bootstrap when
 	    it cannot find itself, as well as system lockups when
@@ -4809,7 +4720,7 @@ kern.sched.name: ULE</screen>
 	    &os; lists your disks, first IDE, then SCSI.</para>
 
 	  <para>When you are slicing up your disk, check that the disk
-	    geometry displayed in the FDISK screen is correct (ie.  it
+	    geometry displayed in the FDISK screen is correct (i.e., it
 	    matches the BIOS numbers); if it is wrong, use the
 	    <keycap>G</keycap> key to fix it.  You may have to do this
 	    if there is absolutely nothing on the disk, or if the disk
@@ -4999,11 +4910,11 @@ use "disklabel -r" to install initial la
 	      <term>NTFS</term>
 
 	      <listitem>
-		<para>&os; includes a read-only NTFS driver.  For more
-		  information, see &man.mount.ntfs.8;.  A port of <ulink
-		    url="http://www.tuxera.com/community/"><application>ntfs-3g</application></ulink>;
-		  supports write operations on NTFS (see <filename
-		    role="package">sysutils/fusefs-ntfs</filename>).</para>
+		<para>Ondersteuning voor NTFS gebaseerd op FUSE is beschikbaar
+		  als een poort (<filename
+		    role="package">sysutils/fusefs-ntfs</filename>).  Zie voor
+		  meer informatie <ulink
+		    url="http://www.tuxera.com/community/ntfs-3g-manual/"><application>ntfs-3g</application></ulink>.</para>;
 	      </listitem>
 	    </varlistentry>
 
@@ -5184,7 +5095,7 @@ C:\="DOS"</programlisting>
 	    following to your configuration file
 	    <filename>/boot/grub/menu.lst</filename> (or
 	    <filename>/boot/grub/grub.conf</filename> in some systems,
-	    e.g. Red Hat Linux and its derivatives).</para>
+	    e.g., Red Hat Linux and its derivatives).</para>
 
 	  <programlisting>title &os; 6.1
 	root <replaceable>(hd0,a)</replaceable>
@@ -7734,7 +7645,7 @@ Key F15        A        A        Menu Wo
 
 	      <para>The most common way to accomplish this is to build a
 		simulated environment in a subdirectory and then run the
-		processes in that directory chroot'd (i.e. <filename
+		processes in that directory chroot'd (i.e., <filename
 		  role="directory">/</filename> for that process is this
 		directory, not the real <filename
 		  role="directory">/</filename> of the system).</para>
@@ -9147,150 +9058,6 @@ hint.sio.7.irq="12"</programlisting>
 &prompt.root; <userinput>chmod 4511 /usr/bin/tip</userinput></screen>
 	</answer>
       </qandaentry>
-
-      <qandaentry>
-	<question id="hayes-unsupported">
-	  <para>My stock Hayes modem is not supported &mdash; what can I
-	    do?</para>
-	</question>
-
-	<answer>
-	  <para>See <ulink
-	      url="&url.books.handbook;/dialout.html#AEN30993">this answer</ulink>
-	    in the &os; Handbook.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question id="direct-at">
-	  <para>How am I expected to enter these AT commands?</para>
-	</question>
-
-	<answer>
-	  <para>See <ulink
-	      url="&url.books.handbook;/dialout.html#DIRECT-AT">this answer</ulink>
-	    in the &os; Handbook.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question id="gt-failure">
-	  <para>Why does the <literal>@</literal> sign for the
-	    <literal>pn</literal> capability not
-	    work?</para>
-	</question>
-
-	<answer>
-	  <para>See <ulink
-	      url="&url.books.handbook;/dialout.html#AEN31034">this answer</ulink>
-	    in the &os; Handbook.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question id="dial-command-line">
-	  <para>How can I dial a phone number on the command
-	    line?</para>
-	</question>
-
-	<answer>
-	  <para>See <ulink
-	      url="&url.books.handbook;/dialout.html#AEN31043">this answer</ulink>
-	    in the &os; Handbook.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question id="set-bps">
-	  <para>Do I have to type in the bps rate every time I do
-	    that?</para>
-	</question>
-
-	<answer>
-	  <para>See <ulink
-	      url="&url.books.handbook;/dialout.html#AEN31062">this answer</ulink>
-	    in the &os; Handbook.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question id="terminal-server">
-	  <para>How can I more easily access a number of hosts through a
-	    terminal server?</para>
-	</question>
-
-	<answer>
-	  <para>See <ulink
-	      url="&url.books.handbook;/dialout.html#AEN31069">this answer</ulink>
-	    in the &os; Handbook.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question id="tip-multiline">
-	  <para>Can tip try more than one line for each site?</para>
-	</question>
-
-	<answer>
-	  <para>See <ulink
-	      url="&url.books.handbook;/dialout.html#AEN31083">this answer</ulink>
-	    in the &os; Handbook.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question id="multi-controlp">
-	  <para>Why do I have to hit <keycombo
-	      action="simul"><keycap>Ctrl</keycap><keycap>P</keycap></keycombo>
-	    twice to send <keycombo
-	      action="simul"><keycap>Ctrl</keycap><keycap>P</keycap></keycombo>
-	    once?</para>
-	</question>
-
-	<answer>
-	  <para>See <ulink
-	      url="&url.books.handbook;/dialout.html#AEN31097">this answer</ulink>
-	    in the &os; Handbook.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question id="uppercase">
-	  <para>Why is everything I type suddenly in UPPER CASE?</para>
-	</question>
-
-	<answer>
-	  <para>See <ulink
-	      url="&url.books.handbook;/dialout.html#AEN31133">this answer</ulink>
-	    in the &os; Handbook.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question id="tip-filetransfer">
-	  <para>How can I do file transfers with
-	    <command>tip</command>?</para>
-	</question>
-
-	<answer>
-	  <para>See <ulink
-	      url="&url.books.handbook;/dialout.html#AEN31159">this answer</ulink>
-	    in the &os; Handbook.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question id="zmodem-tip">
-	  <para>How can I run zmodem with
-	    <application>tip</application>?</para>
-	</question>
-
-	<answer>
-	  <para>See <ulink
-	      url="&url.books.handbook;/dialout.html#AEN31177">this answer</ulink>
-	    in the &os; Handbook.</para>
-	</answer>
-      </qandaentry>
     </qandaset>
   </chapter>
 
@@ -10422,7 +10189,7 @@ panic: page fault</programlisting>
 	<answer>
 	  <para>By default, the kernel address space is 1&nbsp;GB
 	    (2&nbsp;GB for PAE) for i386.  If you run a
-	    network-intensive server (e.g. a large FTP or HTTP server),
+	    network-intensive server (e.g., a large FTP or HTTP server),
 	    or you want to use ZFS, you might find that is not
 	    enough.</para>
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201210302202.q9UM2uag085243>