Typo and punctuation fixes.
This commit is contained in:
parent
9b5776d04c
commit
b2fbb31f74
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=28570
5 changed files with 10 additions and 10 deletions
en_US.ISO8859-1/articles
console-server
cvsup-advanced
hats
laptop
new-users
|
@ -275,7 +275,7 @@
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>If the network is down, then we can use the console on the PC to
|
<para>If the network is down, then we can use the console on the PC to
|
||||||
run the <application>console</application> client locally. For
|
run the <application>console</application> client locally. For
|
||||||
remote sites, we can add a modem for dial-in access to the the
|
remote sites, we can add a modem for dial-in access to the
|
||||||
server command line to run the client.</para>
|
server command line to run the client.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
|
@ -1108,7 +1108,7 @@ exit 0</programlisting>
|
||||||
first serial port known as <devicename>COM1</devicename> in DOS/&windows; or
|
first serial port known as <devicename>COM1</devicename> in DOS/&windows; or
|
||||||
<devicename>ttyd0</devicename> in &unix;).</para>
|
<devicename>ttyd0</devicename> in &unix;).</para>
|
||||||
|
|
||||||
<para>The cabling for these servers depends on the PC harware. If
|
<para>The cabling for these servers depends on the PC hardware. If
|
||||||
the PC has DB-25 female socket on board (as most older PCs do),
|
the PC has DB-25 female socket on board (as most older PCs do),
|
||||||
then the same headshell as works for the Sun server above will
|
then the same headshell as works for the Sun server above will
|
||||||
work fine. If the PC has DB-9 male plug on board (as more
|
work fine. If the PC has DB-9 male plug on board (as more
|
||||||
|
@ -1216,7 +1216,7 @@ exit 0</programlisting>
|
||||||
recognises a serial <literal>BREAK</literal> as a command to halt the
|
recognises a serial <literal>BREAK</literal> as a command to halt the
|
||||||
OS and return to the ROM monitor prompt. A serial <literal>BREAK</literal>
|
OS and return to the ROM monitor prompt. A serial <literal>BREAK</literal>
|
||||||
is an out-of-band signal on an RS-232 serial port that involves making
|
is an out-of-band signal on an RS-232 serial port that involves making
|
||||||
the TX DATA line active (i.e. pulled down to less than -5v) for more than
|
the TX DATA line active (i.e. pulled down to less than -5V) for more than
|
||||||
two whole character times (or about 2ms on a 9600bps line).
|
two whole character times (or about 2ms on a 9600bps line).
|
||||||
Alas, this <literal>BREAK</literal> signal is all to
|
Alas, this <literal>BREAK</literal> signal is all to
|
||||||
easily generated by serial hardware during power-on or power-off. And
|
easily generated by serial hardware during power-on or power-off. And
|
||||||
|
|
|
@ -200,7 +200,7 @@ checkouts.cvs:B</userinput>
|
||||||
<para>For example, <literal>A=RELENG_4</literal>, <literal>B=.</literal>. The period in <literal>B=.</literal> means
|
<para>For example, <literal>A=RELENG_4</literal>, <literal>B=.</literal>. The period in <literal>B=.</literal> means
|
||||||
-CURRENT. This is a rather typical update, from 4-STABLE
|
-CURRENT. This is a rather typical update, from 4-STABLE
|
||||||
to -CURRENT. While it is straightforward to <quote>downgrade</quote> your
|
to -CURRENT. While it is straightforward to <quote>downgrade</quote> your
|
||||||
sources (eg from -CURRENT to -STABLE), downgrading a system
|
sources (e.g., from -CURRENT to -STABLE), downgrading a system
|
||||||
is quite another matter. You are STRONGLY advised not to
|
is quite another matter. You are STRONGLY advised not to
|
||||||
attempt such an operation, unless you know exactly what you
|
attempt such an operation, unless you know exactly what you
|
||||||
are doing.</para>
|
are doing.</para>
|
||||||
|
@ -233,14 +233,14 @@ checkouts.cvs:B</userinput>
|
||||||
<programlisting>src-all tag=RELENG_4 date=2000.08.27.10.00.00</programlisting>
|
<programlisting>src-all tag=RELENG_4 date=2000.08.27.10.00.00</programlisting>
|
||||||
|
|
||||||
<note><para>The format of a date is rigid. You have to specify
|
<note><para>The format of a date is rigid. You have to specify
|
||||||
all the components of the date: century (<quote>20</quote>, ie the 21st
|
all the components of the date: century (<quote>20</quote>, i.e., the 21st
|
||||||
century, must be supplied whereas <quote>19</quote>, the past century, can
|
century, must be supplied whereas <quote>19</quote>, the past century, can
|
||||||
be omitted), year, month, day, hour, minutes, seconds—as
|
be omitted), year, month, day, hour, minutes, seconds—as
|
||||||
shown in the above example. For more information, please
|
shown in the above example. For more information, please
|
||||||
see &man.cvsup.1;.</para></note>
|
see &man.cvsup.1;.</para></note>
|
||||||
|
|
||||||
<para>Whether or not a date is specified, the checkouts file
|
<para>Whether or not a date is specified, the checkouts file
|
||||||
is called <filename>checkouts.cvs:A</filename> (eg
|
is called <filename>checkouts.cvs:A</filename> (e.g.,
|
||||||
<filename>checkouts.cvs:RELENG_4</filename>). As a result,
|
<filename>checkouts.cvs:RELENG_4</filename>). As a result,
|
||||||
no particular action is needed in order to revert to the
|
no particular action is needed in order to revert to the
|
||||||
previous state: you have to modify the date in the <filename>supfile</filename>,
|
previous state: you have to modify the date in the <filename>supfile</filename>,
|
||||||
|
|
|
@ -50,9 +50,9 @@
|
||||||
with the patches. Core expects the hat to offer solutions and
|
with the patches. Core expects the hat to offer solutions and
|
||||||
work with the submitter to reach a compromise. Core expects the
|
work with the submitter to reach a compromise. Core expects the
|
||||||
hat to be courteous. It is reasonable for hats to request that
|
hat to be courteous. It is reasonable for hats to request that
|
||||||
normal project rules be followed when reviewing patches (eg, that
|
normal project rules be followed when reviewing patches (e.g., that
|
||||||
they generally conform to &man.style.9; or the prevailing style of the
|
they generally conform to &man.style.9; or the prevailing style of the
|
||||||
file, that style and content changes be separated, etc).</para>
|
file, that style and content changes be separated.).</para>
|
||||||
|
|
||||||
<para>When a dispute arises, core expects the hat to make his or her
|
<para>When a dispute arises, core expects the hat to make his or her
|
||||||
best efforts to compromise or otherwise resolve the dispute. The
|
best efforts to compromise or otherwise resolve the dispute. The
|
||||||
|
|
|
@ -276,7 +276,7 @@ apm_event NORMRESUME, STANDBYRESUME {
|
||||||
<para>If you want to disable ACPI simply add
|
<para>If you want to disable ACPI simply add
|
||||||
<literal>hint.acpi.0.disabled="1"</literal> to
|
<literal>hint.acpi.0.disabled="1"</literal> to
|
||||||
<filename>/boot/device.hints</filename>. You can disable
|
<filename>/boot/device.hints</filename>. You can disable
|
||||||
ACPI temporarily at the boot loader prompt by issueing
|
ACPI temporarily at the boot loader prompt by issuing
|
||||||
<literal>unset acpi_load</literal> if you are having problems
|
<literal>unset acpi_load</literal> if you are having problems
|
||||||
booting an ACPI enabled machine. &os; 5.1-RELEASE and
|
booting an ACPI enabled machine. &os; 5.1-RELEASE and
|
||||||
later come with a boot-time menu that controls how &os; is
|
later come with a boot-time menu that controls how &os; is
|
||||||
|
|
|
@ -677,7 +677,7 @@
|
||||||
directory, call them up with DOS EDIT, &windows; Notepad or
|
directory, call them up with DOS EDIT, &windows; Notepad or
|
||||||
Wordpad, or a word processor, make a minor change so the file
|
Wordpad, or a word processor, make a minor change so the file
|
||||||
has to be saved, and print as you normally would from DOS or
|
has to be saved, and print as you normally would from DOS or
|
||||||
Windows. Hope it works! manual pages come out best if printed
|
Windows. Hope it works! Manual pages come out best if printed
|
||||||
with the DOS <command>print</command> command. (Copying files
|
with the DOS <command>print</command> command. (Copying files
|
||||||
from FreeBSD to a mounted DOS partition is in some cases still a
|
from FreeBSD to a mounted DOS partition is in some cases still a
|
||||||
little risky.)</para>
|
little risky.)</para>
|
||||||
|
|
Loading…
Reference in a new issue