Various typo and punctuation fixes.
This commit is contained in:
Marc Fonvieille
parent
f2d65c53a5
commit
e13bdf2a4b
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=28566
8 changed files with 14 additions and 14 deletions
en_US.ISO8859-1/books
arch-handbook
developers-handbook
pmake
|
|
@ -356,7 +356,7 @@ if (p2->p_prison) {
|
|||
turn on or off in order to affect the behavior of Jail. One of
|
||||
these sysctls was <literal>jail_sysvipc_allowed</literal>. On
|
||||
most systems, this sysctl is set to 0. If it were set to 1, it
|
||||
would defeat the whole purpose of having a jail; privleged
|
||||
would defeat the whole purpose of having a jail; privileged
|
||||
users from within the jail would be able to affect processes
|
||||
outside of the environment. The difference between a message
|
||||
and a signal is that the message only consists of the signal
|
||||
|
|
@ -518,7 +518,7 @@ static int bpfopen(dev, flags, fmt, p)
|
|||
parameter is set. nam is a pointer to a sockaddr structure,
|
||||
which describes the address on which to bind the service. A
|
||||
more exact definition is that sockaddr "may be used as a
|
||||
template for reffering to the identifying tag and length of
|
||||
template for referring to the identifying tag and length of
|
||||
each address"[2]. In the function in
|
||||
<literal>pcbbind</literal>, <literal>sin</literal> is a
|
||||
pointer to a sockaddr.in structure, which contains the port,
|
||||
|
|
|
|||
|
|
@ -5882,7 +5882,7 @@ Label destruction o</programlisting>
|
|||
information, and passed attribute information. Return
|
||||
<returnvalue>0</returnvalue> for success, or an
|
||||
<varname>errno</varname> value for failure. Suggested
|
||||
failure: <errorcode>EACCES</errorcode>. for label mismatch,
|
||||
failure: <errorcode>EACCES</errorcode> for label mismatch,
|
||||
or <errorcode>EPERM</errorcode> for lack of privilege.
|
||||
This call may be made in a number of situations, including
|
||||
as a result of calls to &man.open.2; with
|
||||
|
|
|
|||
|
|
@ -301,7 +301,7 @@
|
|||
<title>Important locations in the source hierarchy</title>
|
||||
|
||||
<para><filename>src/sys/[arch]/[arch]</filename> - Kernel code for a
|
||||
specific machine architecture resides in this directory. for example,
|
||||
specific machine architecture resides in this directory. For example,
|
||||
the <literal>i386</literal> architecture, or the
|
||||
<literal>SPARC64</literal> architecture.</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -24,11 +24,11 @@
|
|||
<sect1 id="kerneldebug-obtain">
|
||||
<title>Obtaining a Kernel Crash Dump</title>
|
||||
|
||||
<para>When running a development kernel (eg: &os.current;), such as a
|
||||
kernel under extreme conditions (eg: very high load averages,
|
||||
<para>When running a development kernel (e.g., &os.current;), such as a
|
||||
kernel under extreme conditions (e.g., very high load averages,
|
||||
tens of thousands of connections, exceedingly high number of
|
||||
concurrent users, hundreds of &man.jail.8;s, etc.), or using a
|
||||
new feature or device driver on &os.stable; (eg:
|
||||
new feature or device driver on &os.stable; (e.g.,
|
||||
<acronym>PAE</acronym>), sometimes a kernel will panic. In the
|
||||
event that it does, this chapter will demonstrate how to extract
|
||||
useful information out of a crash.</para>
|
||||
|
|
@ -111,7 +111,7 @@
|
|||
<filename>/var/crash</filename> (or whatever
|
||||
<varname>dumpdir</varname> is set to), the kernel will
|
||||
increment the trailing number for every crash to avoid
|
||||
overwriting an existing <filename>vmcore</filename> (eg:
|
||||
overwriting an existing <filename>vmcore</filename> (e.g.,
|
||||
<filename>vmcore.1</filename>). While debugging, it is
|
||||
highly likely that you will want to use the highest version
|
||||
<filename>vmcore</filename> in
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Run in single user mode. E.g. &man.cron.8;, and and
|
||||
<para>Run in single user mode. E.g. &man.cron.8;, and
|
||||
other daemons only add noise. The &man.sshd.8; daemon can
|
||||
also cause problems. If ssh access is required during test
|
||||
either disable the SSHv1 key regeneration, or kill the
|
||||
|
|
|
|||
|
|
@ -231,7 +231,7 @@
|
|||
creation of elaborate geometric shapes an easy task even
|
||||
for very small children.</para>
|
||||
|
||||
<para>The lastest version of Logo for &os; is available from
|
||||
<para>The latest version of Logo for &os; is available from
|
||||
the Ports Collection in
|
||||
<filename role="package">lang/logo</filename>.</para>
|
||||
</listitem>
|
||||
|
|
|
|||
|
|
@ -358,7 +358,7 @@ Linking index</screen>
|
|||
<para>A target's shell script is fed to the shell on its (the
|
||||
shell's) input stream. This means that any commands, such as
|
||||
<application>ci</application> that need to get input from the
|
||||
terminal will not work right – they willl get the shell's
|
||||
terminal will not work right – they will get the shell's
|
||||
input, something they probably will not find to their liking.
|
||||
A simple way around this is to give a command like this:</para>
|
||||
|
||||
|
|
@ -1282,7 +1282,7 @@ d : a</programlisting>
|
|||
<term><option>-x</option></term>
|
||||
|
||||
<listitem>
|
||||
<para>This tells <application>PMake</application> it is ok to export
|
||||
<para>This tells <application>PMake</application> it is OK to export
|
||||
jobs to other machines, if they are available. It is used when
|
||||
running in Make mode, as exporting in this mode tends to make
|
||||
things run slower than if the commands were just executed
|
||||
|
|
|
|||
|
|
@ -240,7 +240,7 @@ cc a.o b.o</screen>
|
|||
|
||||
<para>and this is why: <application>PMake</application> starts with the
|
||||
target <filename>jive.out</filename>, figures out its suffix
|
||||
(<filename>.out</filename>) and looks for things i t can
|
||||
(<filename>.out</filename>) and looks for things it can
|
||||
transform to a <filename>.out</filename> file. In this case, it
|
||||
only finds <filename>.o</filename>, so it looks for the file
|
||||
<filename>jive.o</filename>. It fails to find it, so it
|
||||
|
|
@ -934,7 +934,7 @@ MAKELIB : .USE
|
|||
find in the current directory. If you give no
|
||||
sources, it will clear out any directories added to
|
||||
the search path before. Since the effects of this
|
||||
all get very complex, I will leave it til <xref
|
||||
all get very complex, we will leave it till <xref
|
||||
linkend="gods"> to give you a complete
|
||||
explanation.</entry>
|
||||
</row>
|
||||
|
|
|
|||
Loading…
Reference in a new issue