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

(-)kerneldebug/chapter.sgml (-3 / +3 lines)
Lines 131-139 Link Here
131
131
132
    <para>This instructs &man.savecore.8; to extract a kernel dump
132
    <para>This instructs &man.savecore.8; to extract a kernel dump
133
      from <filename>/dev/ad0s1b</filename> and place the contents in
133
      from <filename>/dev/ad0s1b</filename> and place the contents in
134
      <filename>/var/crash</filename>.  Don't forget to make sure the
134
      <filename>/var/crash</filename>.  Do not forget to make sure the
135
      destination directory <filename>/var/crash</filename> has enough
135
      destination directory <filename>/var/crash</filename> has enough
136
      space for the dump.  Also, don't forget to specify the correct path to your swap
136
      space for the dump.  Also, do not forget to specify the correct path to your swap
137
      device as it is likely different than
137
      device as it is likely different than
138
      <filename>/dev/ad0s1b</filename>!</para></tip>
138
      <filename>/dev/ad0s1b</filename>!</para></tip>
139
139
Lines 414-420 Link Here
414
      </varlistentry>
414
      </varlistentry>
415
    </variablelist>
415
    </variablelist>
416
416
417
    <tip><para>If your system is crashing regularly and you're running
417
    <tip><para>If your system is crashing regularly and you are running
418
      out of disk space, deleting old <filename>vmcore</filename>
418
      out of disk space, deleting old <filename>vmcore</filename>
419
      files in <filename>/var/crash</filename> could save a
419
      files in <filename>/var/crash</filename> could save a
420
      considerable amount of disk space!</para></tip>
420
      considerable amount of disk space!</para></tip>
(-)tools/chapter.sgml (-1 / +1 lines)
Lines 794-800 Link Here
794
	  <question>
794
	  <question>
795
	    <para>I compiled a file called
795
	    <para>I compiled a file called
796
	      <filename>foobar.c</filename> and I cannot find an
796
	      <filename>foobar.c</filename> and I cannot find an
797
	      executable called <filename>foobar</filename>.  Where's
797
	      executable called <filename>foobar</filename>.  Where has
798
	      it gone?</para>
798
	      it gone?</para>
799
	  </question>
799
	  </question>

Return to bug 77778