View | Details | Raw Unified | Return to bug 70954
Collapse All | Expand All

(-)book.sgml (-9 / +15 lines)
Lines 759-764 Link Here
759
                      <entry>French</entry>
759
                      <entry>French</entry>
760
                    </row>
760
                    </row>
761
761
762
		    <row>
763
		      <entry><literal>it_IT.ISO8859-15</literal></entry>
764
765
		      <entry>Italian</entry>
766
		    </row>
767
762
                    <row>
768
                    <row>
763
                      <entry><literal>ja_JP.eucJP</literal></entry>
769
                      <entry><literal>ja_JP.eucJP</literal></entry>
764
770
Lines 4296-4302 Link Here
4296
4302
4297
	  <para>You must remove all power from the PC card slot to
4303
	  <para>You must remove all power from the PC card slot to
4298
	    fully reset the hardware.  Completely power off the
4304
	    fully reset the hardware.  Completely power off the
4299
	    laptop.  (Don't suspend it, don't let it go into standby;
4305
	    laptop.  (Do not suspend it, do not let it go into standby;
4300
	    the power needs to be completely off.)  Wait a few
4306
	    the power needs to be completely off.)  Wait a few
4301
	    moments, and reboot.  Your PC card should work now.</para>
4307
	    moments, and reboot.  Your PC card should work now.</para>
4302
4308
Lines 4396-4402 Link Here
4396
          <para>The problem can be caused by many factors, although
4402
          <para>The problem can be caused by many factors, although
4397
            perhaps the most common cause is faulty or incorrect
4403
            perhaps the most common cause is faulty or incorrect
4398
            cabling.  Check that the ATA cables are undamaged and rated
4404
            cabling.  Check that the ATA cables are undamaged and rated
4399
            for the Ultra DMA mode in use.  If you're using removable
4405
            for the Ultra DMA mode in use.  If you are using removable
4400
            drive trays, they must also be compatible.  Be sure that
4406
            drive trays, they must also be compatible.  Be sure that
4401
            all connections are making good contact.  Problems have
4407
            all connections are making good contact.  Problems have
4402
            also been noticed when an old drive is installed on the
4408
            also been noticed when an old drive is installed on the
Lines 4438-4447 Link Here
4438
              using a combination of hard coded lock orders, and run-time
4444
              using a combination of hard coded lock orders, and run-time
4439
              detected lock orders, and generates console warnings when lock
4445
              detected lock orders, and generates console warnings when lock
4440
              orders are violated.  The intent of this is to detect the
4446
              orders are violated.  The intent of this is to detect the
4441
              potential for deadlocks due to lock order violations; it's worth
4447
              potential for deadlocks due to lock order violations; it is worth
4442
              observing that Witness is actually slightly conservative, and so
4448
              observing that Witness is actually slightly conservative, and so
4443
              it's possible to get false positives.  In the event that Witness
4449
              it is possible to get false positives.  In the event that Witness
4444
              is accurately reporting a lock order problem, it's basically
4450
              is accurately reporting a lock order problem, it is basically
4445
              saying "If you were unlucky, a deadlock would have happened
4451
              saying "If you were unlucky, a deadlock would have happened
4446
              here".  There are a couple of "well known" false positives,
4452
              here".  There are a couple of "well known" false positives,
4447
              which we need to do a better job of documenting to prevent
4453
              which we need to do a better job of documenting to prevent
Lines 6334-6340 Link Here
6334
	    <username>root</username> user.
6340
	    <username>root</username> user.
6335
	    &man.df.1; does not count that space when
6341
	    &man.df.1; does not count that space when
6336
	    calculating the <literal>Capacity</literal> column, so it can
6342
	    calculating the <literal>Capacity</literal> column, so it can
6337
	    exceed 100%.  Also, you'll notice that the
6343
	    exceed 100%.  Also, you will notice that the
6338
	    <literal>Blocks</literal> column is always greater than the
6344
	    <literal>Blocks</literal> column is always greater than the
6339
	    sum of the <literal>Used</literal> and
6345
	    sum of the <literal>Used</literal> and
6340
	    <literal>Avail</literal> columns, usually by a factor of
6346
	    <literal>Avail</literal> columns, usually by a factor of
Lines 8358-8364 Link Here
8358
            just a special case of the previous question and works
8364
            just a special case of the previous question and works
8359
            perfectly well.</para>
8365
            perfectly well.</para>
8360
8366
8361
	  <para>If you're using dialup to connect to the Internet
8367
	  <para>If you are using dialup to connect to the Internet
8362
            user-mode &man.ppp.8; contains a <option>-nat</option>
8368
            user-mode &man.ppp.8; contains a <option>-nat</option>
8363
            option. If you run &man.ppp.8; with the
8369
            option. If you run &man.ppp.8; with the
8364
            <option>-nat</option> option, set
8370
            <option>-nat</option> option, set
Lines 8439-8445 Link Here
8439
        </question>
8445
        </question>
8440
8446
8441
        <answer>
8447
        <answer>
8442
          <para>Because they aren't necessary. In the Berkeley
8448
          <para>Because they are not necessary. In the Berkeley
8443
            networking framework, network interfaces are only directly
8449
            networking framework, network interfaces are only directly
8444
            accessible by kernel code. Please see the
8450
            accessible by kernel code. Please see the
8445
            <filename>/etc/rc.network</filename> file and the manual
8451
            <filename>/etc/rc.network</filename> file and the manual
Lines 11897-11903 Link Here
11897
	    server hourly, this update might happen at any time during
11903
	    server hourly, this update might happen at any time during
11898
	    the hour.  This means that some servers have newer code
11904
	    the hour.  This means that some servers have newer code
11899
	    than others, even though all servers have code that is
11905
	    than others, even though all servers have code that is
11900
	    less than an hour old.  If cvsup.FreeBSD.org was a round
11906
	    less than an hour old.  If <hostid>cvsup.FreeBSD.org</hostid> was a round
11901
	    robin DNS entry that simply redirected users to a random
11907
	    robin DNS entry that simply redirected users to a random
11902
	    CVSup server, running CVSup twice in a row could download
11908
	    CVSup server, running CVSup twice in a row could download
11903
	    code older than the code already on the system.</para>
11909
	    code older than the code already on the system.</para>

Return to bug 70954