Add an initial set of install notes for the prep port.

This commit is contained in:
garbled 2006-04-05 18:37:00 +00:00
parent f5ffa47293
commit 338eb2ab90
9 changed files with 173 additions and 1 deletions

View File

@ -1,4 +1,4 @@
# $NetBSD: Makefile,v 1.35 2005/08/21 18:35:26 riz Exp $
# $NetBSD: Makefile,v 1.36 2006/04/05 18:37:00 garbled Exp $
#
.include <bsd.own.mk>
@ -36,6 +36,7 @@ SUBDIR+= next68k
SUBDIR+= pc532
SUBDIR+= pmax
SUBDIR+= pmppc
SUBDIR+= prep
SUBDIR+= sandpoint
SUBDIR+= sgimips
SUBDIR+= shark

View File

@ -0,0 +1,5 @@
# $NetBSD: Makefile,v 1.1 2006/04/05 18:37:00 garbled Exp $
MERGED_SRCS+= ${COMMON}/sysinst ${COMMON}/upgrade ${COMMON}/xfer
.include <bsd.man.mk>

View File

@ -0,0 +1,86 @@
.\" $NetBSD: hardware,v 1.1 2006/04/05 18:37:00 garbled Exp $
.
.Pp
The minimum configuration requires 16 MB of RAM and 60 MB of disk space.
To install the entire system requires about 250 MB (not including swap).
.Nx
works best with about 32 MB or RAM, but at least 64 MB is advised, especially
on the slower processors.
.
.Ss2 Supported machines
.Pp
In general NetBSD/\*M should run on any PowerPC machine with fully
PReP-compliant firmware. This includes most Motorola machines with
PPCBUG firmware.
.
.(bullet -offset indent
IBM
.(bullet -compact
Model 6015 or 7020 (40P)
.It
Model 6040 (Thinkpad 820)
.It
Model 6050 or 6070 (Power Series 830)
.It
Model 7248 (43P/100, 43P/120 and 43P/133)
.It
Model 7043 (43P-140)
.It
Model 7024 (E20 and E30)
.It
Model 7025 (F30. Others maybe, but F50 is known not to work)
.bullet)
.It
Motorola
.(bullet -compact
Motorola Ultra 603
.It
Motorola Ultra Plus
.bullet)
.bullet)
.
.Ss2 Machines not supported by NetBSD/\*M
.(bullet -offset indent
IBM
.(bullet -compact
Model 7043 (43P-150)
.It
Model 7025 (F50)
.It
Model 7026 (All)
.It
Any POWER or POWER2 RS/6000 machines
.It
Any of the newer p-Series or 64bit PPC machines
.bullet)
Motorola
.(bullet -compact
MPC750 (In-progress)
.It
Powerstack E1 (In-progress, probably works without IDE)
.It
MVMEPPC boards (Possibly works, untested yet)
.bullet)
.bullet)
.
.Ss2 Supported devices
.Pp
.Nx
supports most of the hardware that shipped on these systems through the
machine-independent device drivers. There are a few notable exceptions, listed
below:
.
.Ss2 Unsupported devices
.(bullet -offset indent
Floppy disk controller
.It
IBM SSA controllers
.It
IBM Escon adapters
.It
X server
.It
Front panel LED and LCD devices
.It
Keyswitch devices
.bullet)

View File

@ -0,0 +1,3 @@
.\" $NetBSD: install,v 1.1 2006/04/05 18:37:00 garbled Exp $
.
.so ../common/sysinst

4
distrib/notes/prep/legal Normal file
View File

@ -0,0 +1,4 @@
.\" $NetBSD: legal,v 1.1 2006/04/05 18:37:00 garbled Exp $
.
.It
This product includes software developed by TooLs GmbH.

24
distrib/notes/prep/prep Normal file
View File

@ -0,0 +1,24 @@
.\" $NetBSD: prep,v 1.1 2006/04/05 18:37:00 garbled Exp $
.
When installing
.Nx
for your
.Nx \*V
system, you will have to create a PReP boot partition on your primary boot
drive.
Sysinst will handle this automatically for you if you tell it to use the
whole disk for NetBSD.
Doing so will delete any partitions and information on that disk.
It may be possible to manually partition a disk such that you could dual-boot
AIX, but it would likely be very difficult.
If you wish to retain AIX, you will likely have to install
.Nx
onto a separate drive.
.Nx
requires a PReP boot partition of at least 2 MB in size.
It is recommended that the partition be at least 5 MB in size to allow for
future growth.
The PReP boot partition must be marked as the active partition.
Do not mark the
.Nx
partition as active.

View File

@ -0,0 +1,39 @@
.\" $NetBSD: upgrade,v 1.1 2006/04/05 18:37:00 garbled Exp $
.
When upgrading from a version of
.Nx*M
prior to 4.0, you will need to prepare the system manually before starting
sysinst.
The old boot partition code for
.Nx*M
required the boot image to be dd'd to the head of the root disk.
This created a floppy-sized partition entry of type PReP.
The
.Nx
partition was usually manually offset into the disk to avoid overwriting this
boot partition.
You will need to extend the size of the PReP boot partition out to the
beginning of the
.Nx
partition, and most likely offset it from the head of the disk by a few sectors.
Doing this will render your current version of
.Nx*M
unbootable.
Once this is accomplished, you will need to create a disklabel partition of
type boot that matches the location and size of the PReP MBR partition.
You could instead backup your current data, create proper PReP and
.Nx
partitions, and then restore your current data to those.
.
.Pp
Because of the difficulty in performing all these steps, it is recommended that
rather than attempt upgrade of
.Nx*M
you instead reinstall from scratch. Future versions of
.Nx*M
will allow simple upgrade without these additional steps.
Sysinst can upgrade any machine which has a PReP boot partition of at least
2 MB in size, offset by at least 2 sectors from the beginning of the disk, and
has a matching disklabel partition of type boot.
.
.so ../common/upgrade

View File

@ -0,0 +1,7 @@
.\" $NetBSD: whatis,v 1.1 2006/04/05 18:37:00 garbled Exp $
.
This is the fifth major release of
.Nx*M .
This is the first release which brings a fully functional installation
system to the prep platform, as well as support for fully automatic root-device
detection at boot for most machines.

3
distrib/notes/prep/xfer Normal file
View File

@ -0,0 +1,3 @@
.\" $NetBSD: xfer,v 1.1 2006/04/05 18:37:00 garbled Exp $
.
.so ../common/xfer