New sentence, new line.
This commit is contained in:
parent
80cb79a916
commit
054f95470c
@ -1,4 +1,4 @@
|
||||
.\" $NetBSD: ccd.4,v 1.31 2014/10/27 16:18:38 wiz Exp $
|
||||
.\" $NetBSD: ccd.4,v 1.32 2014/10/27 16:20:48 wiz Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1996, 1997 The NetBSD Foundation, Inc.
|
||||
.\" All rights reserved.
|
||||
@ -96,7 +96,7 @@ to the following to your kernel configuration file:
|
||||
pseudo-device ccd # concatenated disk devices
|
||||
.Ed
|
||||
.Pp
|
||||
The
|
||||
The
|
||||
.Nm Ns s
|
||||
are allocated dynamically as needed.
|
||||
.Pp
|
||||
|
@ -1,4 +1,4 @@
|
||||
.\" $NetBSD: cgfourteen.4,v 1.7 2014/10/27 16:18:38 wiz Exp $
|
||||
.\" $NetBSD: cgfourteen.4,v 1.8 2014/10/27 16:20:47 wiz Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1996 The President and Fellows of Harvard College.
|
||||
.\" All rights reserved.
|
||||
@ -52,8 +52,8 @@
|
||||
The
|
||||
.Nm cgfourteen
|
||||
is a memory based color frame buffer, with graphics acceleration and
|
||||
overlay capabilities. Its pixel memory can be mapped into a user process
|
||||
address space by using
|
||||
overlay capabilities.
|
||||
Its pixel memory can be mapped into a user process address space by using
|
||||
the
|
||||
.Xr mmap 2
|
||||
system call.
|
||||
|
@ -1,4 +1,4 @@
|
||||
.\" $NetBSD: hp.4,v 1.14 2014/10/27 16:18:38 wiz Exp $
|
||||
.\" $NetBSD: hp.4,v 1.15 2014/10/27 16:20:48 wiz Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1991, 1993, 19801988
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
@ -109,7 +109,8 @@ with the error bits decoded if any error bits other than
|
||||
.Tn MBEXC
|
||||
and
|
||||
.Tn DTABT
|
||||
are set. In any case the contents of the two error registers are also printed
|
||||
are set.
|
||||
In any case the contents of the two error registers are also printed
|
||||
in octal and symbolically with bits decoded.
|
||||
(Note that er2 is what old
|
||||
.Tn RP06
|
||||
@ -133,7 +134,8 @@ The parenthesized fields list the actual disk sector number
|
||||
relative to the beginning of the drive,
|
||||
as well as the cylinder, track and sector number of the block.
|
||||
This happens normally
|
||||
a few times a week. If it happens more frequently than
|
||||
a few times a week.
|
||||
If it happens more frequently than
|
||||
this the sectors where the errors are occurring should be checked to see
|
||||
if certain cylinders on the pack, spots on the carriage of the drive
|
||||
or heads are indicated.
|
||||
|
@ -1,4 +1,4 @@
|
||||
.\" $NetBSD: core.5,v 1.26 2014/10/27 16:18:38 wiz Exp $
|
||||
.\" $NetBSD: core.5,v 1.27 2014/10/27 16:20:48 wiz Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 2002 The NetBSD Foundation, Inc.
|
||||
.\" All rights reserved.
|
||||
@ -128,14 +128,15 @@ The maximum size of a core file is limited by
|
||||
Files which would be larger than the limit are not created.
|
||||
.Ss ELF CORE FORMAT
|
||||
ELF-format core files are described by a standard ELF exec header and
|
||||
a series of ELF program headers. Each program header describes a range
|
||||
a series of ELF program headers.
|
||||
Each program header describes a range
|
||||
of the virtual address space of the process.
|
||||
.Pp
|
||||
In addition,
|
||||
.Nx
|
||||
ELF core files include an ELF note section which provides additional
|
||||
information about the process. The first note in the note section
|
||||
has a note name of
|
||||
information about the process.
|
||||
The first note in the note section has a note name of
|
||||
.Dq NetBSD-CORE
|
||||
and a note type of
|
||||
ELF_NOTE_NETBSD_CORE_PROCINFO (1), and contains the following
|
||||
@ -172,8 +173,10 @@ The fields of
|
||||
are as follows:
|
||||
.Bl -tag -width cpi_sigignoreXX
|
||||
.It cpi_version
|
||||
The version of this structure. The current version is defined by
|
||||
the NETBSD_ELFCORE_PROCINFO_VERSION constant.
|
||||
The version of this structure.
|
||||
The current version is defined by the
|
||||
.Dv NETBSD_ELFCORE_PROCINFO_VERSION
|
||||
constant.
|
||||
.It cpi_cpisize
|
||||
The size of this structure.
|
||||
.It cpi_signo
|
||||
@ -182,20 +185,20 @@ Signal that caused the process to dump core.
|
||||
Signal-specific code, if any, corresponding to
|
||||
.Va cpi_signo .
|
||||
.It cpi_sigpend
|
||||
A mask of signals pending delivery to the process. This may be
|
||||
examined by copying it to a
|
||||
A mask of signals pending delivery to the process.
|
||||
This may be examined by copying it to a
|
||||
.Fa sigset_t .
|
||||
.It cpi_sigmask
|
||||
The set of signals currently blocked by the process. This may be
|
||||
examined by copying it to a
|
||||
The set of signals currently blocked by the process.
|
||||
This may be examined by copying it to a
|
||||
.Fa sigset_t .
|
||||
.It cpi_sigignore
|
||||
The set of signals currently being ignored by the process. This may be
|
||||
examined by copying it to a
|
||||
The set of signals currently being ignored by the process.
|
||||
This may be examined by copying it to a
|
||||
.Fa sigset_t .
|
||||
.It cpi_sigcatch
|
||||
The set of signals with registers signals handlers for the process. This
|
||||
may be examined by copying it to a
|
||||
The set of signals with registers signals handlers for the process.
|
||||
This may be examined by copying it to a
|
||||
.Fa sigset_t .
|
||||
.It cpi_pid
|
||||
Process ID of the process.
|
||||
@ -235,9 +238,11 @@ is the LWP ID of the execution context, for example:
|
||||
These notes contain register and other per-execution context
|
||||
data in the same format as is used by the
|
||||
.Xr ptrace 2
|
||||
system call. The note types correspond to the
|
||||
system call.
|
||||
The note types correspond to the
|
||||
.Xr ptrace 2
|
||||
request numbers that return the same data. For example,
|
||||
request numbers that return the same data.
|
||||
For example,
|
||||
a note with a note type of PT_GETREGS would contain a
|
||||
.Fa struct reg
|
||||
with the register contents of the execution context.
|
||||
@ -249,7 +254,8 @@ header file.
|
||||
.Ss A.OUT CORE FORMAT
|
||||
.Pp
|
||||
The core file consists of a core header followed by a number of
|
||||
segments. Each segment is preceded by a core segment header.
|
||||
segments.
|
||||
Each segment is preceded by a core segment header.
|
||||
Both the core header and core segment header are defined in
|
||||
.In sys/core.h .
|
||||
.Pp
|
||||
@ -285,7 +291,8 @@ These values may be extracted with the
|
||||
.Fn CORE_GETMAGIC ,
|
||||
and
|
||||
.Fn CORE_GETFLAG
|
||||
macros. The machine ID values are listed in
|
||||
macros.
|
||||
The machine ID values are listed in
|
||||
.In sys/exec_aout.h .
|
||||
For a valid core file, the magic value in the header must be
|
||||
.Dv COREMAGIC .
|
||||
|
Loading…
Reference in New Issue
Block a user