clean up whitespace, formatting

This commit is contained in:
lukem 2002-06-29 22:37:39 +00:00
parent 7a3ba9ecb7
commit 7b70a250c5
8 changed files with 76 additions and 60 deletions

View File

@ -1,9 +1,9 @@
.\" $NetBSD: hardware,v 1.14 2002/05/06 11:33:20 takemura Exp $
.\" $NetBSD: hardware,v 1.15 2002/06/29 22:37:39 lukem Exp $
.
A H/PC machine contains a keyboard and a touch screen and
generally has 8 MB or more of RAM. The port supports the HPC
form factor, as well as the H/PC Pro and PsPC (Palmsized PC)
form factors.
generally has 8 MB or more of RAM.
The port supports the HPC form factor,
as well as the H/PC Pro and PsPC (Palmsized PC) form factors.
.
.Ss2 Supported WindowsCE machines
.(bullet -offset indent
@ -128,7 +128,8 @@ Vr4122-based
Vr4131-based
.It
TX3912-based: TX3912 machines are not supported with installation kernel and
GENERIC kernel. Use special kernel for TX3912 (netbsd.TX3912.gz).
GENERIC kernel.
Use special kernel for TX3912 (netbsd.TX3912.gz).
.It
TX3922-based
.bullet)

View File

@ -1,4 +1,4 @@
.\" $NetBSD: install,v 1.9 2002/05/06 11:33:20 takemura Exp $
.\" $NetBSD: install,v 1.10 2002/06/29 22:37:40 lukem Exp $
.
Boot with bootloader and
.Pa netbsd
@ -14,7 +14,8 @@ kernel and system install consume about 7 MB of memory.
Please configure the
.Tn "Windows CE"
memory setting to allow this amount of
memory to be used. If bootloader failed with a
memory to be used.
If bootloader failed with a
.Dq cannot allocate heap
error, configure more RAM for memory and less for disk with the dialog at
[Setting]-\*>[ControlPanel]-\*>[System]-\*>[Memory] under

View File

@ -1,4 +1,4 @@
.\" $NetBSD: whatis,v 1.7 2002/04/07 02:58:16 shin Exp $
.\" $NetBSD: whatis,v 1.8 2002/06/29 22:37:40 lukem Exp $
.
This is the second official release of
.Nx*M .
@ -8,7 +8,8 @@ brings the
NetBSD operating system to
MIPS based
.Tn "Windows CE"
PDA machines. Currently, the
PDA machines.
Currently, the
Vr4102, Vr4111, Vr4121, TX3912, and TX3922 processors are supported.
.Pp
The port name

View File

@ -1,9 +1,9 @@
.\" $NetBSD: hardware,v 1.2 2002/06/16 16:00:31 itojun Exp $
.\" $NetBSD: hardware,v 1.3 2002/06/29 22:41:53 lukem Exp $
.
A H/PC machine contains a keyboard and a touch screen and
generally has 8 MB or more of RAM. The port supports the HPC
form factor, as well as the H/PC Pro and PsPC (Palmsized PC)
form factors.
generally has 8 MB or more of RAM.
The port supports the HPC form factor,
as well as the H/PC Pro and PsPC (Palmsized PC) form factors.
.
.Ss2 Supported WindowsCE machines
.(bullet -offset indent

View File

@ -1,4 +1,4 @@
.\" $NetBSD: whatis,v 1.1 2002/06/15 21:31:38 itojun Exp $
.\" $NetBSD: whatis,v 1.2 2002/06/29 22:41:54 lukem Exp $
.
This is the non-official release of
.Nx*M .
@ -8,7 +8,8 @@ brings the
NetBSD operating system to
Hitachi SH-3/4 based
.Tn "Windows CE"
PDA machines. Currently, the
PDA machines.
Currently, the
SH7709, SH7709R, SH7709A and SH7750V processors are supported.
.Pp
The port name

View File

@ -1,16 +1,18 @@
.\" $NetBSD: hardware,v 1.105 2002/06/01 17:38:53 bouyer Exp $
.\" $NetBSD: hardware,v 1.106 2002/06/29 22:45:29 lukem Exp $
.
.Nx \*V
runs on ISA (AT-Bus), EISA, MCA, PCI, and VL-bus systems
with 386-family processors, with or without math coprocessors. The
minimal configuration is said to require 4 MB of RAM and 50 MB of disk
with 386-family processors, with or without math coprocessors.
The minimal configuration is said to require 4 MB of RAM and 50 MB of disk
space, though we do not know of anyone running with a system quite
this minimal today. To install the entire system requires much more
disk space (the unpacked binary distribution, without sources,
this minimal today.
To install the entire system requires much more disk space
(the unpacked binary distribution, without sources,
requires at least 65 MB without counting space needed for swap space,
etc), and to run X or compile the system, more RAM is recommended.
(4 MB of RAM will actually allow you to run X and/or compile, but it
won't be speedy. Note that until you have around 16 MB of RAM, getting
won't be speedy.
Note that until you have around 16 MB of RAM, getting
more RAM is more important than getting a faster CPU.)
.
.Ss2 Supported devices
@ -276,7 +278,7 @@ Znyx ZX34X
.It
Digital EtherWORKS III ISA adapters (DE203/DE204/DE205) [*]
.It
Digital DEPCM-BA (PCMCIA) and DE305 (ISA) NE2000-compat. cards
Digital DEPCM-BA (PCMCIA) and DE305 (ISA) NE2000-compatible cards
.It
BICC Isolan [* and not recently tested]
.It
@ -394,7 +396,7 @@ Aironet 4500/4800 and Cisco 340 series PCMCIA cards
BayStack 650 802.11FH PCMCIA cards [*] [+]
.It
Corega Wireless LAN PCC-11 cards [*] [+]
.It
.It
DEC/Cabletron RoamAbout 802.11 DS High Rate cards [*] [+]
.It
ELSA AirLancer MC-11 card [*] [+]
@ -522,7 +524,7 @@ Generic support for HID devices [*] [+]
Ethernet adapters [*] [+]
.It
Audio devices [*] [+]
.It
.It
driver for FTDI based serial adapters [*] [+]
.It
Mass storage devices such as disks, ZIP drives and digital cameras [*] [+]
@ -586,7 +588,8 @@ Drivers are
.Em not
present in kernels on the distribution floppies.
Except as noted above, all drivers are present
on all disks. Also, at the present time, the distributed kernels
on all disks.
Also, at the present time, the distributed kernels
support only one SCSI host adapter per machine.
.Nx
normally
@ -697,8 +700,8 @@ SCSI tapes st0, st1, ...
SCSI and ATAPI CD-ROMs cd0, cd1, ...
For each SCSI and IDE controller found, the SCSI or ATA(PI) devices
present on the bus are probed in increasing ID order for SCSI and
master/slave order for ATA(PI). So the first SCSI drive found will
be called sd0, the second sd1, and so on ...
master/slave order for ATA(PI). So the first SCSI drive found will
be called sd0, the second sd1, and so on ...
StarLAN cards
ai0 0x360 7 any iomem 0xd0000

View File

@ -1,17 +1,19 @@
.\" $NetBSD: prep,v 1.12 2001/04/07 18:25:46 jhawk Exp $
.\" $NetBSD: prep,v 1.13 2002/06/29 22:45:30 lukem Exp $
.
First and foremost, before beginning the installation process,
.Em make sure you have a reliable backup
of any data on your hard disk that you
wish to keep. Mistakes in partitioning your hard disk may lead
to data loss.
wish to keep.
Mistakes in partitioning your hard disk may lead to data loss.
.Pp
Before you begin, you should be aware of the geometry issues that may
arise in relation to your hard disk. First of all, you should know
about sector size. You can count on this to be 512 bytes; other sizes
are rare (and currently not supported). Of particular interest are
the number of sectors per track, the number of tracks per cylinder
(also known as the number of heads), and the number of cylinders.
arise in relation to your hard disk.
First of all, you should know about sector size.
You can count on this to be 512 bytes; other sizes are rare
(and currently not supported).
Of particular interest are the number of sectors per track,
the number of tracks per cylinder (also known as the number of heads),
and the number of cylinders.
Together they describe the disk geometry.
.Pp
The
@ -19,40 +21,45 @@ The
has a limit of 1024 cylinders and 63 sectors per track for
doing
.Tn BIOS
I/O. This is because of the old programming interface
I/O.
This is because of the old programming interface
to the
.Tn BIOS
that restricts these values. Most of the big disks
currently being used have more than 1024 real cylinders. Some have
more than 63 sectors per track. Therefore, the
that restricts these values.
Most of the big disks currently being used have more than 1024 real cylinders.
Some have more than 63 sectors per track.
Therefore, the
.Tn BIOS
can be instructed
to use a fake geometry that accesses most of the disk and the fake
geometry has less than or equal to 1024 cylinders and less than or
equal to 63 sectors. This is possible because the disks can be
addressed in a way that is not restricted to these values, and the
equal to 63 sectors.
This is possible because the disks can be addressed in a way that is
not restricted to these values, and the
.Tn BIOS
can internally perform a translation. This can be activated
in most modern BIOSes by using
can internally perform a translation.
This can be activated in most modern BIOSes by using
.Em Large
or
.Em LBA
mode for the disk.
.Pp
.Nx
does not have the mentioned limitations with regard to the
geometry. However, since the
does not have the mentioned limitations with regard to the geometry.
However, since the
.Tn BIOS
has to be used during startup,
it is important to know about the geometry the
.Tn BIOS
uses. The
uses.
The
.Nx
kernel should be on a part of the disk where it can be loaded using the
.Tn BIOS ,
within the limitations of the
.Tn BIOS
geometry. The install program will check this for you, and
geometry.
The install program will check this for you, and
will give you a chance to correct this if this is not the case.
.Pp
If you have not yet installed any other systems on the hard disk
@ -68,12 +75,13 @@ settings for the
or
.Sq LBA
modes, and activate
them for the hard disk in question. While they are not needed
by
them for the hard disk in question.
While they are not needed by
.Nx
as such, doing so will remove the limitations mentioned
above, and will avoid hassle should you wish to share the disk with
other systems. Do
other systems.
Do
.Em not
change these settings if you already have
data on the disk that you want to preserve!
@ -81,10 +89,9 @@ data on the disk that you want to preserve!
In any case, it is wise to check your the
.Tn BIOS
settings for the
hard disk geometry before beginning the installation, and write
them down. While this should usually not be needed, it enables
you to verify that the install program determines these values
correctly.
hard disk geometry before beginning the installation, and write them down.
While this should usually not be needed, it enables you to verify
that the install program determines these values correctly.
.Pp
The geometry that the
.Tn BIOS

View File

@ -1,20 +1,22 @@
.\" $NetBSD: upgrade,v 1.20 2000/11/16 17:12:08 tv Exp $
.\" $NetBSD: upgrade,v 1.21 2002/06/29 22:45:30 lukem Exp $
.
.so ../common/upgrade
.Pp
.Nx*M
has switched its executable format from the old a.out format
to ELF, the now more commonly used and supported format. Your old
binaries will continue to work just fine. The installation procedure
will try to take the necessary steps to accomplish this. The most
important step is to move the old a.out shared libraries in
to ELF, the now more commonly used and supported format.
Your old binaries will continue to work just fine.
The installation procedure will try to take the necessary steps to
accomplish this.
The most important step is to move the old a.out shared libraries in
.Pa /usr/lib
and
.Pa /usr/X11R6/lib
(if X was installed) to
.Pa /emul/aout ,
where they will be automatically found if an older a.out binary
is executed. Sysinst will use an existing
is executed.
Sysinst will use an existing
.Pa /emul
and / or
.Pa /emul/aout