Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

major terraform (this is MUCH more than a rototill :-), including: 

- update for 1.5 (still more MD stuff to check)
- use new macros in ../common/macros as appropriate
- introduce some CONSISTENCY between the various ports' install docs
- use various mdoc macros as appropriate, including .Li, .Pa, .Sy, and .Ic.
- migrate more stuff into ../common/*
- whitespace cleanup
- lots of other little things i'm sure...
This commit is contained in:
lukem 2000-10-10 12:55:15 +00:00
parent 6a50c6b116
commit b4d52d9d24
141 changed files with 3757 additions and 3863 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

289
distrib/notes/alpha/hardware
View File

@ -1,6 +1,7 @@
.\" $NetBSD: hardware,v 1.9 2000/03/21 10:50:03 soda Exp $
.Pp
NetBSD/alpha \*V runs on most of the
.\" $NetBSD: hardware,v 1.10 2000/10/10 12:55:15 lukem Exp $
.
.Nx*M
\*V runs on most of the
.Tn DEC
Alpha PCI platforms, on all
of the TURBOChannel models, on the high end 8200 and 8400 systems,
@ -10,7 +11,8 @@ The SRM console is required.
This
console can be distinguished from the ARC console (which is used to
boot Windows NT) by the fact that it has a command line interface,
rather than a menu-driven interface. The SRM prompt is ``\*>\*>\*>''.
rather than a menu-driven interface. The SRM prompt is
.Dq Li \*>\*>\*> .
.Pp
Some platforms have both the SRM console and
the ARC console, and can switch between them, and other platforms have
@ -23,171 +25,199 @@ You may want to buy a firmware update CD from Compaq Computer Corporation.
.Pp
More information on supported platforms and devices can be found on the
alpha port web pages at
.Lk http://www.netbsd.org/ "" .
.Lk http://www.netbsd.org/ .
.Pp
A basic system will fit on a 200 MB disk (including swap) without too
much difficulty, but you will probably want at least 500 MB of disk
to have any level of comfort.
.Pp
Although
it is actually possible to boot and install NetBSD/alpha in only
it is actually possible to boot and install
.Nx*M
in only
16 MB of RAM, you will want to have at least 32 MB.
.
.
We support add-in devices on the PCI, ISA, EISA and TurboChannel buses.
Because NetBSD has an extremely machine-independent device driver
Because
.Nx
has an extremely machine-independent device driver
system, many device drivers are the same as used in other ports that
use the same bus. For example, the `de' network card driver is shared
use the same bus. For example, the
.Em de
network card driver is shared
by the i386 and Alpha ports. Some drivers on inspection appear as if
they will work on the alpha but have not been tested because that
hardware was not available to NetBSD testers; these are marked as
.Em untested
hardware was not available to
.Nx
testers; these are marked as
.Em UNTESTED
below. If you have one of these devices, and it does work,
please get in touch with
.Mt port-alpha-maintainer@netbsd.org
and let us know that it works. If it doesn't work, do the same thing and we
can probably fix it pretty easily.
.Pp
Supported devices by bus type are:
.Bl -bullet -compact
.It
PCI Bus
.Bl -bullet -compact
.It
.
.Ss2 Supported PCI bus devices
.(bullet -offset indent
Graphics Adapters
.Bl -hyphen -compact
.It
VGA-compatible video (pcivga)
.(bullet -compact
VGA-compatible video
.Em ( pcivga )
.It
ZLXp-E1
DECchip 21030-based video,
.Em tga
.(Note
ZLXp-E2 and ZLXp-E3 boards are not supported in
.Nx \*V .
.Note)
.El
DECchip 21030-based video
.Em ( tga )
.It
ZLXp-E2 and ZLXp-E3 video
.Em ( tga )
.bullet)
.It
Network Cards
.Bl -hyphen -compact
.(bullet -compact
DECchip 21x40-family 10 and 100 Mbps Ethernet
.Em ( de , tlp )
.It
DECchip 21x40-family 10 and 100 Mbps Ethernet (de)
DEC DEFPA FDDI
.Em ( fpa )
.It
DEC DEFPA FDDI (fpa)
PCI LANCE Ethernet
.Em ( le ; UNTESTED )
.It
PCI LANCE Ethernet (le, UNTESTED)
Efficient Networks ENI-155p ATM
.Em ( en ; UNTESTED )
.It
Efficient Networks ENI-155p ATM (en, UNTESTED)
3Com 3c59x and 3c90x (except 3c906) 10 and 100 Mbps Ethernet
.Em ( ep )
.It
3Com 3c59x and 3c90x (except 3c906) 10 and 100 Mbps Ethernet (ep)
Intel EtherExpress Pro 10/100B PCI Ethernet
.Em ( fxp )
.It
Intel EtherExpress Pro 10/100B PCI Ethernet (fxp, UNTESTED)
.El
SMC EPIC/100 Fast Ethernet boards
.Em ( epic )
.bullet)
.It
SCSI Controllers
.Bl -hyphen -compact
.(bullet -compact
Adaptec 291x, 2920, 2930C, 294x, 295x, 39xx, 19160, 29160 and
AIC-78xx SCSI
.Em ( ahc )
.It
Adaptec 291x, 2920, 2930C, 294x, 295x, 39xx, 19160, 29160 and AIC-78xx SCSI (ahc)
BusLogic 9xx SCSI
.Em ( bha ,
Works on Alpha PC164)
.It
BusLogic 9xx SCSI (bha, Works on Alpha PC164)
Qlogic ISP 10x0-family SCSI
.Em ( isp )
.It
Qlogic ISP 10x0-family SCSI (isp)
.It
NCR/Symbios 53c8xx-family SCSI (ncr, NCR825 Doesn't always work)
.El
NCR/Symbios 53c8xx-family SCSI
.Em ( ncr , siop ;
The latter is preferred. NCR825 Doesn't always work)
.bullet)
.It
Miscellaneous Devices
.Bl -hyphen -compact
Cyclades Cyclom-Y serial boards (cy, UNTESTED)
.It
PCI-PCI bridges (ppb, tested with the DECchip 21050, but should
work with all bridges and system firmware revisions that
comply with the PCI-PCI bridge specification)
.El
.El
.It
ISA Bus
.Bl -bullet -compact
.It
Network Cards
.Bl -hyphen -compact
.It
3Com 3c509 Ethernet (ep)
.It
DEC DE200,DE201,DE202 (le)
.It
DEC DE203,DE204,DE205 (lc)
.El
.It
Miscellaneous Devices
.Bl -hyphen -compact
.It
PC-style parallel ports (lpt)
.It
NS16450 and NS16550 UARTs (com)
.It
ISA multi-port 16x50 boards (such as ast, boca--only boca has
been tested)
.El
.El
.It
EISA Bus
.Bl -bullet -compact
.It
Network Cards
.Bl -hyphen -compact
.It
DEC DEFEA FDDI (fea)
.It
3Com 3c5xx series (ed, UNTESTED)
.El
.It
SCSI Controllers
.Bl -hyphen -compact
.It
Adaptec 274x and aic7770 SCSI (ahc, UNTESTED)
.It
BusLogic 7xx SCSI (bha, UNTESTED)
.El
.El
.It
Turbochannel Bus
.Bl -bullet -compact
.(bullet -compact
Cyclades Cyclom-Y serial boards
.Em ( cy ; UNTESTED )
.It
PCI-PCI bridges
.Em ( ppb ;
Tested with the DECchip 21050, but should work with all bridges and system
firmware revisions that comply with the PCI-PCI bridge specification)
.bullet)
.bullet)
.
.Ss2 Supported ISA bus devices
.(bullet -offset indent
Graphics Adapters
.Bl -hyphen -compact
.(bullet -compact
VGA-compatible video
.Em ( vga ;
Text console only)
.bullet)
.It
CFB video (PMAG-BA, cfb)
Network Cards
.(bullet -compact
3Com 3c509 Ethernet
.Em ( ep )
.It
SFB video (PMAGB-BA, sfb)
.El
DEC DE200,DE201,DE202
.Em ( le )
.It
DEC DE203,DE204,DE205
.Em ( lc )
.bullet)
.It
Miscellaneous Devices
.(bullet -compact
PC-style parallel ports
.Em ( lpt )
.It
NS16450 and NS16550 UARTs
.Em ( com )
.It
ISA multi-port 16x50 boards
.Em ( ast , boca ;
Only the latter has been tested )
.bullet)
.bullet)
.
.Ss2 Supported EISA bus devices
.(bullet -offset indent
Network Cards
.(bullet -compact
DEC DEFEA FDDI
.Em ( fea )
.It
3Com 3c5xx series
.Em ( ed ; UNTESTED )
.bullet)
.It
SCSI Controllers
.(bullet -compact
Adaptec 274x and aic7770 SCSI
.Em ( ahc ; UNTESTED )
.It
BusLogic 7xx SCSI
.Em ( bha ; UNTESTED )
.bullet)
.bullet)
.
.Ss2 Supported Turbochannel bus devices
.(bullet -offset indent
Graphics Adapters
.(bullet -compact
CFB video (PMAG-BA,
.Em cfb )
.It
SFB video (PMAGB-BA,
.Em sfb )
.bullet)
.(Note
Although these boards are supported by NetBSD/alpha,
Although these boards are supported by
.Nx*M
since there is no keyboard or mouse support available for the
TurboChannel systems, they aren't very useful.
XXX: is this still true now that the MI sfb.c is used???
.Note)
.It
Network Cards
.Bl -hyphen -compact
.(bullet -compact
DEC LANCE Ethernet (PMAD-AA,
.Em le ; UNTESTED )
.It
DEC LANCE Ethernet (PMAD-AA, le, UNTESTED)
.It
DEC DEFTA FDDI (PMAF-F, fta)
.El
.El
.El
.(Note
Note that PC-style floppy disk drives are not supported in 1.3
(except to boot from), but are supported to some degree in
NetBSD-current.
.Note)
.(Note
DEC DEFTA FDDI (PMAF-F,
.Em fta )
.bullet)
.bullet)
.Pp
Note that some devices, especially ISA-based devices, have to have
certain settings set properly for the install and GENERIC kernels to
detect them. (Once installed, you can always rebuild your own kernel
to detect them anywhere you wish, of course.) Here is a list of such
devices and the necessary settings:
.Note)
certain settings set properly for the install and
.Li GENERIC
kernels to detect them.
(Once installed, you can always rebuild your own kernel
to detect them anywhere you wish, of course.)
Here is a list of such devices and the necessary settings:
.\"(disp
.Bd -literal
Device Name Port IRQ DRQ Misc
------ ---- ---- --- --- ----
@ -234,15 +264,16 @@ DEC DE200,201,202 EtherWORKS II/Turbo ISA Ethernet boards
le? 0x300 5 memory at D0000-DFFFF
le? 0x200 10 memory at D8000-DFFFF
You should enter the following SRM console command to enable the le device:
\*>\*>\*> isacfg -mk -slot ? -dev 0 -handle DE200-LE -irq0 5
-membase0 d0000 -memlen0 10000 -iobase0 300 -etyp 1 -enadev 1
You should enter the following SRM console command to enable the
le device:
\*>\*>\*> isacfg -mk -slot ? -dev 0 -handle DE200-LE -irq0 5
-membase0 d0000 -memlen0 10000 -iobase0 300 -etyp 1 -enadev 1
DEC DE203,204,205 EtherWORKS III ISA Ethernet boards
lc0 0x300 any
lc1 0x320 any
You should enter the following SRM console command to enable the device:
\*>\*>\*> add_de205
.Ed
You should enter the following SRM console command to enable
the device:
\*>\*>\*> add_de205
.disp)

162
distrib/notes/alpha/install
View File

@ -1,4 +1,4 @@
.\" $NetBSD: install,v 1.18 2000/10/03 22:46:20 lukem Exp $
.\" $NetBSD: install,v 1.19 2000/10/10 12:55:15 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -31,8 +31,9 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.Pp
Installation of NetBSD/alpha is now easier than ever!
Installation of
.Nx*M
is now easier than ever!
For the latest news, problem reports, and discussion, join
the port-alpha mainlist by mailing a line saying
.Dl subscribe port-alpha
@ -46,21 +47,25 @@ If you encounter any problems, please report them via the mailing list or the
.Xr send-pr 1
program so that they can be fixed for the next release.
.Pp
To install or upgrade NetBSD, you need to first boot an installation
To install or upgrade
.Nx ,
you need to first boot an installation
program and then interact with the screen-menu program
.Ic sysinst .
The installation program actually consists of the NetBSD kernel plus
an in-memory file system of utility programs.
The installation program actually consists of the
.Nx
kernel plus an in-memory file system of utility programs.
.Pp
The usual procedure is to write the installation system to a floppy
disk set and then boot from the floppies, however, there
are now six ways to boot the NetBSD/alpha installation system! Each approach
are now six ways to boot the
.Nx*M
installation system! Each approach
loads the exact same installation bits.
The six paths are:
.Pp
.
.Bl -enum -compact -offset indent
.It
.(bullet -offset indent
Floppy disk boot
.It
CD boot
@ -72,31 +77,41 @@ Magnetic Tape Boot
Existing Root FS Boot
.It
Network boot
.El
.bullet)
.
.Pp
In all cases, you need to transfer a
bootable image of the installation system
from the NetBSD CD or from an ftp site to the chosen media type.
from the
.Nx
CD or from an ftp site to the chosen media type.
Although booting from floppy is the usual path, the
hard drive boot is useful if you have another operating system (and a spare
drive) already installed, or if you don't mind swapping hard drives from
box to box. CD and tape boots are nice and fast if you have a CD writer
or a tape format in common with another previously installed Unix-like
system. Finally, most versions of SRM can locate the NetBSD boot program
system. Finally, most versions of SRM can locate the
.Nx
boot program
.Ic netboot
via bootp and download it via tftp,
.Ic netboot
then mounts the root file system via NFS and loads the kernel.
.
.
.Bl -enum -compact
.Pp
.It
Note that if you are installing or upgrading from a writable media,
the media can be write-protected if you wish.
These systems mount a root image from inside the kernel, and will not
need to write to the media.
If you booted from a floppy, the floppy disk may be removed from
the drive after the system has booted.
.Pp
.
.(bullet
Floppy disk boot
.Pp
The 3.5", 1.44 MB boot floppy set is found under the
NetBSD/alpha \*V distribution directory in
.Nx*M
\*V distribution directory in
.Pa alpha/installation/floppy/
as two files called
.Pa disk1of2
@ -106,13 +121,14 @@ You need to put these two disk images on two floppy disks.
.Pp
If you have a Unix system handy, you can do this with commands
like the following:
.Bd -literal -offset indent
.(disp -offset indent
dd if=disk1of2 of=/dev/rfd0a bs=18k
dd if=disk2of2 of=/dev/rfd0a bs=18k
.Ed
.disp)
.Pp
If the Unix system you are using is not a NetBSD system, you will
probably need to replace
If the Unix system you are using is not a
.Nx
system, you will probably need to replace
.Li /dev/rfd0a
with the name of the floppy device on your particular system.
.Pp
@ -150,8 +166,10 @@ or
it is important
to create the tape image with 512-byte records. Use a command like:
.Dl "dd if=cdhdtape bs=512 of=/dev/rst0"
If the host system is not NetBSD, the names of the destination devices
are likely to be different. Be sure to use a
If the host system is not
.Nx ,
the names of the destination devices are likely to be different.
Be sure to use a
.Dq "raw partition"
device that doesn't skip over labels!
.Pp
@ -176,15 +194,16 @@ uncompress it first.
.It
Network Boot
.Pp
Booting NetBSD/alpha \*V over a network requires a BOOTP or
Booting
.Nx*M
\*V over a network requires a BOOTP or
DHCP server, a TFTP server and an NFS server. (These are usually
all run on the same machine.) There are three basic stages to
the boot:
.Pp
.
.
.Bl -bullet
.It
.(bullet
Alpha console software sends a BOOTP request to get its
own address, the address of the TFTP server and the file to
download. It downloads this file, which is the second stage
@ -198,14 +217,16 @@ root path via NFS and reads in and transfers to the kernel:
The kernel probes and configures the devices, and then sends
out another BOOTP request so it can find out its address, the NFS
server, and path. It then mounts its root via NFS and continues.
.El
.bullet)
.
.
.Pp
You will need to set up servers for BOOTP, TFTP and NFS.
.Pp
If you want to run a full system
from the network, untar the NetBSD snapshot or distribution
from the network, untar the
.Nx
snapshot or distribution
into a directory on your server and NFS export that directory
to the client. Make sure you put a kernel there as well, and
create the device nodes in
@ -215,14 +236,10 @@ with
Detailed instructions on netbooting can be found by visiting the
.Nx
Alpha platform page:
.Pp
\~\~\~\~\~
.Lk http://www.NetBSD.org/Ports/alpha
.Pp
At the time of this
release, the URL for the netbooting instructions is:
.Pp
\~\~\~\~\~
.Lk http://www.netbsd.org/Documentation/network/netboot/
.Pp
You'll want to map root to
@ -231,7 +248,9 @@ You'll want to map root to
.Li nobody )
when you export your root filesystem. A typical
.Pa /etc/exports
line on a NetBSD system would be:
line on a
.Nx
system would be:
.Dl /usr/export/alpha -maproot=0 myclient.mydom.com
.Pp
One option is to load just the install kernel over the network but then
@ -248,7 +267,9 @@ image from the distribution.
The gzipped image can be booted directly; it is not necessary to
uncompress it first.
.Pp
The console will be using TFTP to load the NetBSD boot program,
The console will be using TFTP to load the
.Nx
boot program,
so for the TFTP setup, you need to copy the second stage bootstrap,
.Ic netboot ,
into an appropriately named file such as
@ -261,10 +282,8 @@ if not, you can get this from the
directory where you found the alpha distribution.
.Pp
For the BOOTP server you need to specify the:
.Pp
.
.Bl -bullet -compact
.It
.(bullet -compact -offset indent
hardware type (Ethernet)
.It
hardware address (Ethernet MAC address)
@ -278,18 +297,19 @@ address of of the TFTP/NFS server
name of the second stage bootstrap loaded via TFTP
.It
path to the root for the client (mounted via NFS)
.El
.bullet)
.
.Pp
Here's an example for a Unix system running bootpd:
.Bd -literal -offset indent
.(disp
myhost.mydom.com:\
:ht=ethernet:ha=0000c0391ae4:\e
:ip=192.168.1.2:sm=255.255.255.0:\e
:sa=192.168.1.1:bf=boot.netbsd.alpha:rp=/usr/export/alpha:
.Ed
.disp)
.Pp
And here's an example for a Unix system running the ISC dhcpd:
.Bd -literal -offset indent
.(disp
host axp {
hardware ethernet 0:0:c0:39:1a:e4;
fixed-address 192.168.1.2;
@ -300,7 +320,7 @@ host axp {
option broadcast-address 255.255.255.0;
option domain-name "my.domain";
}
.Ed
.disp)
.Pp
The only Ethernet device the console on most Alpha systems
knows how to boot from is the onboard Ethernet interface or a
@ -332,8 +352,7 @@ do not have a
option and use different device names. They also tend to not netboot very
well so you probably don't need to worry about this section. However, if you
want to give it a try, note the following differences:
.Bl -bullet -offset indent
.It
.(bullet -offset indent
There is no
.Fl Ar proto
argument, or
@ -349,14 +368,14 @@ boot program.
.It
Example:
.Dl \*>\*>\*>\ boot\ ez0
.El
.El
.bullet)
.bullet)
.
.
.Pp
.so ../common/sysinst
.
.Ss2 "Manual and Script-Assisted Installation"
.Ss2 Manual and script-assisted installation
.
All of the installation procedures consist of
putting a label on the disk to provide information on
@ -366,13 +385,12 @@ filesystems on the partitions, and unpacking the distribution
tar archives.
.
.
.Bl -enum
.It
.(enum
Disk prep: label, boot block, and file system setup
.
.
.Bl -tag -width 3n
.It A.
.(tag "AA."
.It "A."
Manual Install from the Shell Prompt
.Pp
The normal installation involves running the install shell script
@ -385,8 +403,7 @@ what the install script does. The procedure is:
.Pp
.
.
.Bl -bullet -compact
.It
.(bullet -compact
create
.Pa /etc/disktab ,
see
@ -406,12 +423,13 @@ cd to
.Pa /usr/mdec
and run
.Xr installboot 8
.El
.bullet)
.
.
.Pp
If you are reviewing man pages on NetBSD platforms other than
alpha, be sure that when reading
If you are reviewing man pages on
.Nx
platforms other than alpha, be sure that when reading
.Xr installboot 8
you read the alpha
version by typing: "man 8 alpha/installboot".
@ -489,8 +507,7 @@ bootable, initialise the filesystems, and mount them all under
.Pa /mnt .
You are now ready to go on to the next step.
.
.
.El
.tag)
.
.
.It
@ -509,8 +526,7 @@ via a CD-ROM archive, a tape archive, or by preloading an accessible hard
drive with the necesary tar files.
.
.
.Bl -bullet
.It
.(bullet
Preparing to Install from a CD-ROM
.Pp
All you need to do is mount the CD-ROM, which will generally
@ -582,25 +598,25 @@ which to put them and then use the ftp client to download them.
Mirror sites are listed at:
.Lk http://www.netbsd.org/Sites/net.html
A typical session might be:
.Bd -literal -offset indent
.(disp
mkdir /mnt/usr/release
cd /mnt/usr/release
ftp ftp.netbsd.org
.Ed
[the following commmands are given to the ftp program
after logging in]
.Bd -literal offset indent
.disp)
.Pp
[the following commmands are given to the ftp program after logging in]
.(disp
prompt
cd /pub/NetBSD/NetBSD-\*V/alpha/binary/sets
mget *
bye
.Ed
.disp)
.Pp
Feel free, of course, to leave off the sets that you don't need
if you don't plan to install everything.
.
.
.El
.bullet)
.
.
.It
@ -618,7 +634,7 @@ For this and the following commands, replace
with the path to your NFS volume or CD-ROM if that's how you
chose to access your install files instead.
.Pp
The sets and kernel are extracted with
The sets and kernel are extracted with:
.
.(disp
cd /mnt
@ -626,8 +642,9 @@ for i in base kern comp etc games man misc text; do
tar xpzf /mnt/usr/release/$i.tgz;
done
.disp)
.
.Pp
or perhaps:
.Pp
.
.(disp
cd /mnt
@ -636,14 +653,13 @@ for i in /mnt/usr/release/*.tgz; do
tar xpzf $i
done
.disp)
.
.Pp
Now make the device nodes:
.(disp
cd /mnt/dev
sh ./MAKEDEV all
.disp)
.
.
.It
Restart your system
.Pp
@ -671,12 +687,12 @@ to see a full list of bootable
devices in your system. Your system will come up in single-user
mode, ready for you to configure it.
.
.El
.enum)
.
.
.Pp
You can create the floppy needed for installation
under DOS or Windows. Supposing your 1.44M floppy
under DOS or Windows. Supposing your 1.44 MB floppy
drive is drive A:, and your CD is drive
.Ic E: ,
do the following from an MS-DOS command prompt:

26
distrib/notes/alpha/legal
View File

@ -1,25 +1,9 @@
.\" $NetBSD: legal,v 1.5 2000/10/05 08:37:55 lukem Exp $
.Pp
This product includes software developed by Charles Hannum.
.Pp
This product includes software developed by Charles Hannum, by
the University of Vermont and State Agricultural College and
Garrett A. Wollman, by William F. Jolitz, and by the
University of California, Berkeley, Lawrence Berkeley
Laboratory, and its contributors.
.Pp
This product includes software developed by the University of
Vermont and State Agricultural College and Garrett A. Wollman.
.Pp
This product includes software developed by Dean Huxley.
.Pp
This product includes software developed by Herb Peyerl.
.Pp
.\" $NetBSD: legal,v 1.6 2000/10/10 12:55:16 lukem Exp $
.
In the following statement, "This software" refers to the parallel
port driver:
.Pp
.Bl -item -offset indent
.It
This software is a component of "386BSD" developed by
.(item -offset indent
This software is a component of "386BSD" developed by
William F. Jolitz, TeleMuse.
.El
.item)

14
distrib/notes/alpha/prep
View File

@ -1,8 +1,12 @@
.\" $NetBSD: prep,v 1.4 1999/01/13 07:30:02 ross Exp $
If you have any data on
your disks that you want to keep,
.\" $NetBSD: prep,v 1.5 2000/10/10 12:55:16 lukem Exp $
.
If you have any data on your disks that you want to keep,
.Em back it up
before starting. Note that NetBSD/alpha does not support booting more than
before starting. Note that
.Nx*M
does not support booting more than
one operating system from a single disk, although it's fine to have
multiple operating systems on your machine if you have a separate
disk for NetBSD, or if one of them uses a network boot.
disk for
.Nx ,
or if one of them uses a network boot.

2
distrib/notes/alpha/upgrade
View File

@ -1,3 +1,3 @@
.\" $NetBSD: upgrade,v 1.8 1999/01/13 09:59:22 ross Exp $
.\" $NetBSD: upgrade,v 1.9 2000/10/10 12:55:16 lukem Exp $
.
.so ../common/upgrade

70
distrib/notes/alpha/whatis
View File

@ -1,53 +1,35 @@
.\" $NetBSD: whatis,v 1.5 1999/04/23 00:04:07 ross Exp $
There have been many, many Alpha-specific enchancements since the
1.3 release. These include:
.Bl -bullet
.\" $NetBSD: whatis,v 1.6 2000/10/10 12:55:16 lukem Exp $
.
There have been many \*M-specific enhancements since the
1.4 release.
These include:
.(bullet
The following new system types are supported:
.(bullet -compact
API UP1000 (AMD 751-based) EV6 systems
.It
Many new system types are supported:
.Bl -hyphen -compact
264DP, XP1000, DS10, DS20, API UP2000 and other Tsunami-based EV6 systems
.It
EB66 Evaluation Board
DECpc AXP 150 (Jensen)
.bullet)
.It
ALPHABook 1
Ability to boot off RAIDframe RAID-1 (mirrored) FFS partitions.
.It
Digital AlphaServer 4100 systems
Ability to boot off LFS partitions.
.It
Digital AlphaServer 1000 systems
.Ic ddb
traceback code added.
.It
Digital AlphaServer 1000A systems
Emulate user program use of BWX instructions on CPUs which don't
support them. Handle unaligned accesses caused by BWX instructions.
.It
Digital AlphaServer 800 systems
.It
Digital Server 330x systems
.El
.It
Jason Thorpe's new virtual memory code provides
full support for the alpha's large address space with context switching
and translation buffer state optimizations.
.It
Extensive scheduler work enables process nice levels to work as expected,
fixing ancient BSD scheduler bugs that affected NetBSD/alpha more than
other ports with slower clock Hz defaults. Nice +19 and +20 processes
now take no time away from nice +0 programs regardless of load average.
.It
Many new device drivers and sound cards are supported. Floppy
disk drives are now supported.
.It
IDE peripheral devices are now supported on Multia and AXPPCI33 systems.
.It
A new multi-volume boot loader allows all supported system types
and device drivers to be present on floppy disk media, and enables the
.Em sysinst
screen-menu installation program to be included on
floppy disks as well. Although two floppies are now used, they load
much faster than the single floppy did in 1.3.
.It
Installation from CD and magnetic tape media is now supported.
.It
A new set of boot programs provides considerable operational and
performance enhancement.
.El
Improved TGA graphics support, accelerating the text mode and adding
support for the: 8bpp TGA2, and 32bpp ZLXp-E2 and -E3.
.bullet)
.Pp
NetBSD \*V on alpha is, as usual, also fully backward compatible
with old NetBSD/alpha binaries, so you don't need to recompile all
.Nx
\*V on alpha is, as usual, also fully backward compatible
with old
.Nx*M
binaries, so you don't need to recompile all
your local programs.

94
distrib/notes/alpha/xfer
View File

@ -1,91 +1,3 @@
.\" $NetBSD: xfer,v 1.6 2000/03/13 22:37:10 soren Exp $
.Pp
A large number of different media types can be used to hold the
binary distribution sets, but they must originally be obtained
from the
.Nx
project via a mechanism from the list below.
.Bl -bullet -compact
.It
FTP
.It
Remote NFS partition
.It
CD-ROM
.El
.Pp
The steps necessary to prepare the distribution sets
for installation depend on which installation medium you choose.
The steps for the various media are outlined below.
.Pp
.Bl -tag -width NFS\ Installation
.It Em NFS\ Installation
Place the NetBSD distribution sets you wish to install into a
directory on an NFS server, and make that directory mountable
by the machine on which you are installing or upgrading NetBSD.
This will probably require modifying the
.Pa /etc/exports
file on of the NFS server and resetting its mount daemon (mountd).
(Both of these actions will probably require superuser
privileges on the server.)
.Pp
You need to know the numeric IP address of the NFS server,
and, if the server is not on a network directly connected to
the machine on which you're installing or upgrading NetBSD,
you need to know the numeric IP address of the closest router .
Finally, you need to know the numeric
IP address of the NetBSD machine itself. The install
program will ask you to provide this information to be able
to access the sets.
.Pp
Once the NFS server is set up properly and you have the
information mentioned above, you can start the actual
installation process.
.It Em FTP\ Installation
Determine an FTP site from which
you can retrieve the NetBSD distribution when you're about
to install. You will need to know the IP address of your
nameserver or of your ftp site,
and, if it's not on a network directly connected to
the machine on which you're installing or upgrading NetBSD,
you need to know the IP address of the router
closest to the NetBSD machine. Finally, you need to know
the numeric IP address of the NetBSD machine itself. The
install program will ask you to provide this information
to be able to access the sets via ftp.
.Pp
Once you have this information, you can proceed to the actual
installation.
.It Upgrade
If you are upgrading NetBSD, you also have the option of installing
NetBSD by putting the new distribution sets somewhere in your existing
file system, and using them from there. To do that, you must do the
following:
.Pp
Place the distribution sets you wish to upgrade somewhere in
your current file system tree. Please note that the
.Pa /dev
on the floppy used for upgrades only knows about wd0, wd1, sd0,
sd1 and sd2. If you have more than two IDE drives or more than
three SCSI drives, you should take care not to place the sets
on the high numbered drives.
.Pp
At a bare minimum, you must upgrade the
.Sy base
and
.Sy kern
binary distribution, and so must put the
.Sy base
and
.Sy kern
sets somewhere in your file system. If you wish,
you can do the other sets, as well, but you should
.Em not
upgrade the
.Sy etc
distribution; it contains system
configuration files that you should review and update by hand.
.Pp
Once you have done this, you can proceed to the next step in
the upgrade process, actually upgrading your system.
.El
.\" $NetBSD: xfer,v 1.7 2000/10/10 12:55:16 lukem Exp $
.
.so ../common/xfer

273
distrib/notes/amiga/hardware
View File

@ -1,4 +1,4 @@
.\" $NetBSD: hardware,v 1.36 2000/09/14 19:57:01 is Exp $
.\" $NetBSD: hardware,v 1.37 2000/10/10 12:55:16 lukem Exp $
.
.Nx \*V
runs on any Amiga that has a 68020 or better CPU with
@ -8,130 +8,173 @@ For 68020 and 68030 systems, a FPU is recommended but not required for the
system utilities.
68LC040, 68040V and 68LC060 systems don't work correctly at the moment.
.Pp
The minimal configuration requires 6M of RAM (not including CHIPMEM!)
and about 75M of disk space. To install the entire system requires
The minimal configuration requires 6 MB of RAM (not including CHIPMEM!)
and about 75 MB of disk space. To install the entire system requires
much more disk space, and to run X or compile the system, more RAM
is recommended. (6M of RAM will actually allow you to compile,
however it won't be speedy. X really isn't usable on a 6M system.)
is recommended. (6 MB of RAM will actually allow you to compile,
however it won't be speedy. X really isn't usable on a 6 MB system.)
.Pp
Here is a table of recommended HD partition sizes for a full install:
.Bl -column -offset indent Partition Suggested 100xMBxx Needed 100xMB
.It Partition Ta Suggested Ta +\ X Ta Needed Ta +\ X
.It root\ (/) Ta "25 MB" Ta "25 MB" Ta "20 MB" Ta "20 MB"
.It /usr Ta "245 MB" Ta "270 MB" Ta "120 MB" Ta "145 MB"
.It /var Ta "20 MB" Ta "20 MB" Ta "5 MB" Ta "5 MB"
.It swap Ta Em "2*RAM below 32 MB, then up to you"
.El
.(item -offset indent
Anything else is up to you!
.item)
.Pp
As you may note the recommended size of
.Pa /usr
is 125 MB greater than needed.
This is to leave room for a kernel source and compile tree as
you will probably want to compile your own kernel.
.Li GENERIC
is large and bulky to accommodate all people.
For example, most people's machines have an FPU, so you do not need the
bulky FPU_EMULATE option.
.Pp
Preconfigured or precompiled packages are installed below
.Pa /usr/pkg
by default.
You should either make
.Pa /usr
larger (if you intend to install a lot of them), make
.Pa /usr/pkg
an additional partition, use the
.Fl p
option to
.Ic pkg_add
to install them in a different place, or link
.Pa /usr/pkg
to a different place.
.Pp
If you only have less than 8 MB of fast memory, you should make your swap
partition larger, as your system will be doing much more swapping.
Especially: do
.Em not
place it onto a old small (and normally slow) disk!
.
.Bd -literal -offset indent
partition: advise, with X, needed, with X
root (/) 25M 25M 20M 20M
user (/usr) 245M 270M 120M 145M
swap 2 times RAM size below 32 MB, then up to you
local (/usr/local) up to you
.Ed
.
.Pp
As you may note the recommended size of /usr is 125M greater than
needed. This is to leave room for a kernel source and compile tree as
you will probably want to compile your own kernel. GENERIC is large
and bulky to accommodate all people. For example, most peoples machines
have an FPU, so you do not need the bulky FPU_EMULATE option.
.Pp
Preconfigured or precompiled packages are installed below /usr/pkg per
default. You should either make /usr larger (if you intend to install
a lot of them), make /usr/pkg an additional partiton, use the -p option
to pkg_add to install them in a different place or link /usr/pkg to
some different place.
.Pp
If you only have less than 8M of fast memory, you should make your swap
partition larger, as your system will be doing much more swapping. Especially:
do NOT place it onto a old small (and normally slow) disk!
.Pp
Supported devices include:
.Bd -literal -offset indent
A4000/A1200 IDE controller, including ATAPI devices.
SCSI host adapters:
33c93 based boards: A2091, A3000 builtin, A3000 builtin
modified for Apollo accellerator board, and GVP series II.
53c80 based boards: 12 Gauge, IVS, Wordsync/Bytesync and
Emplant.*)
53c710 based boards: A4091, Magnum, Warp Engine, Zeus
and DraCo builtin.
FAS216 based SCSI boards: FastLane Z3, Blizzard I and II,
Blizzard IV, Blizzard 2060, CyberSCSI Mk I and II.
53c770 based SCSI baords: Cyberstorm Mk III SCSI, Cyberstorm
PPC SCSI.
Video controllers:
ECS, AGA and A2024 built in on various Amigas.
Retina Z2*****, Retina Z3 and Altais.
Cirrus CL GD 54xx based boards:
GVP Spectrum,
Picasso II, II+ and IV,
Piccolo and Piccolo SD64.
Tseng ET4000 based boards:
Domino and Domino16M proto,
oMniBus,
Merlin.
A2410*****.
Cybervision 64.
Cybervision 64/3D.
Audio I/O:
Amiga builtin
Melody Mpeg-audio layer 2 board
Ethernet controllers:
A2065 Ethernet
Hydra Ethernet
ASDG Ethernet
A4066 Ethernet
Ariadne Ethernet
Ariadne II Ethernet
Quicknet Ethernet
X-surf Ethernet port
ARCnet controllers:
A2060 ARCnet
Tape drives:
Most SCSI tape drives, including
Archive Viper, Cipher SCSI-2 ST150.
Scanners:
SCSI-2 scanners behaving as SCSI-2 scanner devices,
HP Scanjet II, Mustek SCSI scanner.***)
CD-ROM drives:
Most SCSI CD-ROM drives
Serial cards:
HyperCom 3Z, HyperCom 4, HyperCom 3+ and 4+
MultiFaceCard II and III
A2232 (normal and clockdoubled)
Amiga floppy drives with Amiga (880/1760kB) and
IBM (720/1440kB) encoding. ****)
Amiga parallel port.
Amiga serial port.
Amiga mouse.
DraCo serial port, including serial mouse.
DraCo parallel printer port.
Real-time clocks:
A2000, A3000, A4000 builtin (r/w),
DraCo builtin (r/o).
.Ed
.Pp
If its not on the above lists, there is no support for it in this
release. Especially (but this is an incomplete list), there are no
drivers for: Blizzard III SCSI option,
Ferret SCSI, Oktagon SCSI.
.Pp
Footnotes: Known problems with some hardware:
.Bl -tag -width *****
.It *
the Emplant SCSI adapter has been reported by a party to
hang after doing part of the installation without problems.
.It **
.Ss2 Supported devices
.(bullet -offset indent
A4000/A1200 IDE controller, including ATAPI devices
.It
SCSI host adapters
.(bullet -compact
33c93 based boards: A2091, A3000 builtin, A3000 builtin modified for Apollo
accellerator board, and GVP series II.
.It
53c80 based boards: 12 Gauge, IVS, Wordsync/Bytesync and Emplant
The Emplant SCSI adapter has been reported by a party to
hang after doing part of the installation without problems
.It
53c710 based boards: A4091, Magnum, Warp Engine, Zeus and DraCo builtin
.It
FAS216 based SCSI boards: FastLane Z3, Blizzard I and II, Blizzard IV,
Blizzard 2060, CyberSCSI Mk I and II
.It
53c770 based SCSI boards: Cyberstorm Mk III SCSI, Cyberstorm PPC SCSI
.bullet)
.It
Video controllers
.(bullet -compact
ECS, AGA and A2024 built in on various Amigas
.It
Retina Z2 (no X server available), Retina Z3 and Altais
.It
Cirrus CL GD 54xx based boards: GVP Spectrum, Picasso II, II+ and IV,
Piccolo and Piccolo SD64
.It
Tseng ET4000 based boards: Domino and Domino16M proto, oMniBus, Merlin
.It
A2410 (no X server available)
.It
Cybervision 64
.It
Cybervision 64/3D
.bullet)
.It
Audio I/O
.(bullet -compact
Amiga builtin
.It
Melody Mpeg-audio layer 2 board
.bullet)
.It
Ethernet controllers
.(bullet -compact
A2065 Ethernet
.It
Hydra Ethernet
.It
ASDG Ethernet
.It
A4066 Ethernet
.It
Ariadne Ethernet
.It
Ariadne II Ethernet
.It
Quicknet Ethernet
.It
X-surf Ethernet port
.bullet)
.It
ARCnet controllers
.(bullet -compact
A2060 ARCnet
.bullet)
.It
Most SCSI tape drives, including Archive Viper, Cipher SCSI-2 ST150
.It
SCSI-2 scanners behaving as SCSI-2 scanner devices, HP Scanjet II,
Mustek SCSI scanner.
SCSI scanner support is machine independent, so it should
work, but hasn't been tested yet on most Amiga configurations.
There are reports that the Mustek and HP Scanjet hang if
There are reports that the Mustek and HP ScanJet hang if
accessed from the A3000. This might apply to other
33C93-Adapters, too.
.It ****
Our floppy driver doesn't notice when mounted floppies are
.It
Most SCSI CD-ROM drives
.It
Serial cards
.(bullet -compact
HyperCom 3Z, HyperCom 4, HyperCom 3+ and 4+
.It
MultiFaceCard II and III
.It
A2232 (normal and clockdoubled)
.bullet)
.It
Amiga floppy drives with Amiga (880/1760kB) and IBM (720/1440kB) encoding.
Our floppy driver doesn't notice when mounted floppies are
write-protected at the moment. Your floppy will stay
unchanged, but you might not notice that you didn't write
anything due to the buffer cache. Also note that HD floppy
drives only get detected as such if a HD floppy is inserted at
boot time.
.It *****
No X11 server available.
.El
.It
Amiga parallel port
.It
Amiga serial port
.It
Amiga mouse
.It
DraCo serial port, including serial mouse
.It
DraCo parallel printer port
.It
Real-time clocks
.(bullet -compact
A2000, A3000, A4000 builtin (r/w)
.It
DraCo builtin (r/o)
.bullet)
.bullet)
.Pp
If its not on the above lists, there is no support for it in this
release. Especially (but this is an incomplete list), there are no
drivers for: Blizzard III SCSI option,
Ferret SCSI, Oktagon SCSI.

67
distrib/notes/amiga/install
View File

@ -1,4 +1,4 @@
.\" $NetBSD: install,v 1.24 2000/10/03 23:05:30 lukem Exp $
.\" $NetBSD: install,v 1.25 2000/10/10 12:55:16 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -31,7 +31,6 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.Pp
Installing
.Nx
is a relatively complex process, but, if you have
@ -54,7 +53,7 @@ for swapping, as described in the "Preparing
your System for
.Nx
Installation" section above.
.Ss2 Booting\ from\ AmigaOS,\ using\ loadbsd:
.Ss2 Booting from AmigaOS, using loadbsd
You then need to have
.Pa ixemul.library
in your
@ -78,14 +77,16 @@ the dblNTSC mode, you may also include the
.Fl A No option to
enable the dblNTSC display mode.
.Pp
If your machine has a fragmented physical memory space, as,
If your machine has a fragmented physical memory space, as,
e.g., DraCo machines, you should add the
.Fl n2 No option to
.Fl n2 No option to
enable the use of all memory segments.
.Pp
If you have a M680x0 + PPC board, make sure the PPC cpu is inactive
before using loadbsd, else the kernel will hang!
.Ss2 Directly\ booting\ NetBSD,\ with\ boot\ blocks\ installed:
.Ss2 Directly booting
.Nx ,
with boot blocks installed
.Pp
[This description is for V40 (OS 3.1) ROMs. For older ROMs,
there might be small differences. Check your AmigaOS documentation
@ -93,7 +94,7 @@ to learn about the exact procedure.]
Using bootblocks may not work on some
systems, and may require a mountable filesystem on others.
.Pp
Reboot your machine, holding down both mouse buttons if you
Reboot your machine, holding down both mouse buttons if you
have a 2-button mouse, the outer mouse buttons if you have
a 3-button mouse. On the DraCo, press the left mouse button
instead, when the boot screen prompts you for it.
@ -121,7 +122,7 @@ E.g., instead of
.Dl loadbsd -bsSn2 netbsd
use
.Dl netbsd -bsSn2
.Ss2 Once\ your\ kernel\ boots:
.Ss2 Once your kernel boots
You should see the screen clear and some information about
your system as the kernel configures the hardware. Note which
hard disk device(s) are configured (sd0, sd1, etc). Then
@ -131,10 +132,10 @@ where
.Ic sd0
is the device which contains the swap
partition you created during the hard disk preparation.
When prompted for a dump device, answer 'none' for the install
(normally, you would tell it one of the swap devices). When
prompted for the root filesystem type, confirm 'generic', which
will auto-detect it.
When prompted for a dump device, answer 'none' for the install
(normally, you would tell it one of the swap devices). When
prompted for the root filesystem type, confirm 'generic', which
will auto-detect it.
.Pp
If the system should hang after entering the root device, try
again with
@ -153,8 +154,9 @@ response here...
.Pp
The installer starts with a nice welcome messages. Read this
message carefully, it also informs you of the risks involved
in continuing! If you still want to go on, type 'y'. The
installer now continues by trying to figure out your disk
in continuing! If you still want to go on, type
.Sq y .
The installer now continues by trying to figure out your disk
configuration. When it is done, you will be prompted to
select a root device from the list of disks it has found.
.Pp
@ -168,7 +170,7 @@ the next one sd1, etc. Also, any Amiga internal IDE disk drives
will be configured as "SCSI" drives, and will be configured
before any 'real' SCSI drives (if any are present).
.Pp
The installer will offer you to look at the
The installer will offer you to look at the
.Nx
disk label of the disks at this point. You should do this, to find out
what partition letters the
@ -178,14 +180,17 @@ disk number you are going to use is right.
.Pp
.Em you are now at the point of no return.
If you confirm that
you want to install NetBSD, your hard drive will be modified,
you want to install
.Nx ,
your hard drive will be modified,
and perhaps its contents scrambled at the whim of the install
program. Type Control-C NOW if you don't want this.
.Pp
At this time, you will need to tell the installer which partition
will be associated with the different filesystems. Normally, you'll
want to add a partition for /usr, at least.
.(tag Em Caveat:
.(tag Caveat:
.It Em Caveat:
Do not use the (r)sdNc partitions for anything! They are for access to
the whole disk only and do
.Em not
@ -195,10 +200,10 @@ correspond to any Amiga partition!
The install program will now make the file systems you
specified. There should be only one error per file system in
this section of the installation. It will look like this:
.Bd -literal -offset indent
.(disp
newfs: ioctl (WDINFO): Invalid argument
newfs: /dev/rsd0a: can't rewrite disk label
.Ed
.disp)
.Pp
If there are any others, restart from the beginning of
the installation process. This error is ok as the Amiga
@ -217,8 +222,7 @@ your freshly made filesystems. Select the device type you wish
to install from and off you go....
.Pp
Some notes:
.Bl -hyphen
.It
.(bullet -offset indent
If you want to install from tape, please read the section
about how to create such a tape.
.It
@ -226,11 +230,16 @@ Some tapes (e.g. Archive Viper 150) refuse to operate with
the default tape density ("nrst0"). Try "nrst0h",
"nrst0m", or "nrst0l" instead.
.It
Install at least the base and etc sets.
Install at least the
.Sy base
and
.Sy etc
sets.
.It
If you have to specify a path relative to the mount-point and
you need the mount-point itself, enter '.'.
.El
you need the mount-point itself, use
.Sq \&. .
.bullet)
.Pp
Next you will be asked to specify the timezone. Just select the
timezone you are in. The installer will make the correct setup
@ -249,7 +258,7 @@ manual page about how to do this.
.Pp
Once the installer is done, halt the system with the
.Ic halt No command
(wait for
(wait for
.Li halted
to be displayed) and reboot. Then again boot
.Nx
@ -274,15 +283,15 @@ or
to edit the files. If you installed the man pages
you can type
.Ic man vi No or Ic man ed
for instructions on how to use these somewhat non-intuitive editors.
for instructions on how to use these somewhat non-intuitive editors.
.Pp
Once you are done with the rest of configuration unmount your file
systems and halt your system, then reboot:
.Bd -literal -offset indent
.(disp
cd /
umount -av
halt
.Ed
.disp)
.Pp
Finally you can now boot your system and it will be completely
functional:
@ -290,5 +299,5 @@ functional:
.Pp
When it boots off of the hard drive, you will have a complete
.Nx
system!
system!
.Em Congratulations! No (You really deserve them!!!)

37
distrib/notes/amiga/legal
View File

@ -1,36 +1,27 @@
.\"$NetBSD: legal,v 1.6 1999/01/13 07:30:02 ross Exp $
.\" $NetBSD: legal,v 1.7 2000/10/10 12:55:16 lukem Exp $
.
This product includes software developed by Tobias Abt.
.Pp
This product includes software developed by Klaus Burkert.
.Pp
This product includes software developed by Michael van Elst.
.Pp
This product includes software developed by Bernd Ernesti.
This product includes software developed by Michael L. Hitch.
This product includes software developed by Christian E. Hopps.
.Pp
This product includes software developed by Markus Illenseer.
.Pp
This product includes software developed by Mika Kortelainen.
.Pp
This product includes software developed by Jukka Marin.
.Pp
This product includes software developed by Kari Mettinen.
.Pp
This product includes software developed by Brad Pepers.
.Pp
This product includes software developed by Ignatios Souvatzis.
This product includes software developed by Ezra Story.
.Pp
This product includes software developed by Michael Teske.
.Pp
This product includes software developed by Lutz Vieweg.
.Pp
This product includes software developed by Daniel Widenfalk.
This product includes software developed by Markus Wild.

112
distrib/notes/amiga/prep
View File

@ -1,15 +1,19 @@
.\" $NetBSD: prep,v 1.21 2000/10/03 23:05:30 lukem Exp $
.Pp
.\" $NetBSD: prep,v 1.22 2000/10/10 12:55:16 lukem Exp $
.
You will need an AmigaDOS hard drive prep tool to prepare your hard
drives for use with NetBSD/Amiga. HDToolBox is provided with the
drives for use with
.Nx*M .
HDToolBox is provided with the
system software and on floppy installation disks since Release 2.0
of AmigaDOS, so we will provide instructions for its use.
.Pp
Note that NetBSD can't currently be installed on disks with a sector
Note that
.Nx
can't currently be installed on disks with a sector
size other than 512 bytes (e.g., "640 MB" 90mm MO media). You can, however,
mount ADOSFS partitions on such MOs.
.
.Ss2 "Preparing your hard disk with HDToolBox"
.Ss2 Preparing your hard disk with HDToolBox
.
.Pp
A full explanation of HDToolBox can be found with your
@ -20,17 +24,17 @@ type so that you have working geometry parameters. To do this
you enter the "Change drive type" menu, and either use "read
parameters from drive" or set them manually.
.Pp
Note you will be modifying your HD's. If you mess something
up here you could lose everything on all the drives that
Note you will be modifying your HD's. If you mess something
up here you could lose everything on all the drives that
you configure. It is therefore advised that you:
.Bl -enum
.It
.(enum -offset indent
Write down your current configurations. Do this
by examining each partition on the drive and the
drives parameters (from Change drive type.)
.It
Back up the partitions you are keeping.
.El
.enum)
.Pp
What you need to do is partition your drives; creating at least
root, swap and /usr partitions and possibly at least one more for
/usr/local if you have the space.
@ -39,32 +43,35 @@ This should be done as the HDToolBox manual describes. One thing
to note is that if you are not using a Commodore controller you
will need to specify the device your SCSI controller uses, e.g.
if you have a Warp Engine you would:
.Pp
from cli,
.(tag From\ cli -offset indent
.It From cli
.Dl "hdtoolbox warpdrive.device"
.Pp
from wb set the tooltype,
.It From wb
Set the tooltype
.Dl "SCSI_DEVICE_NAME=warpdrive.device"
.tag)
.Pp
The important things you need to do above and beyond normal
partitioning includes (from Partition Drive section):
.Bl -enum
.It
Marking all NetBSD partitions as non-bootable, with
.(enum
Marking all
.Nx
partitions as non-bootable, with
two exceptions: the root partition, if you want to boot
NetBSD directly, or the swap partition, if you want
.Nx
directly, or the swap partition, if you want
to boot the installation miniroot directly.
.It
Changing the file system parameters of the partitions
to NetBSD ones. This must be done from the
Changing the file system parameters of the partitions to
.Nx
ones. This must be done from the
partitioning section and `Advanced options' must
be enabled.
.El
.enum)
.Pp
To Make the needed changes:
To make the needed changes:
.Pp
.Bl -bullet -compact
.It
.(enum -compact -offset indent
Click the `Adv. Options' button
.It
Click the `Change file system' button
@ -74,15 +81,17 @@ Choose `Custom File System'
Turn off `Automount' if on.
.It
Set the dostype to one of these three choices:
.Bd -literal -offset indent
.(disp
root partition : 0x4e425207
swap partition : 0x4e425301
other partitions: 0x4e425507
.Ed
.disp)
.Pp
Here `other' refers to other partitions you will
format for reading and writing under NetBSD (e.g.
/usr)
format for reading and writing under
.Nx
(e.g.
.Pa /usr )
.Pp
Make sure you press the return key to enter this value
as some versions of HDToolBox will forget your entry
@ -93,13 +102,12 @@ Turn custom boot code off
Set Reserved Blocks start and end to 0.
.It
Click Ok.
.El
.enum)
.Pp
On the root (and, for installation, swap) partition,
set instead this:
.Pp
.Bl -bullet -compact
.It
.(enum -compact -offset indent
Turn custom boot code on
.It
Set Reserved Blocks start and end to 0.
@ -110,37 +118,46 @@ Set Automount This Partition on
.It
Click Ok.
.Pp
Mask and maxtransfer are not used with NetBSD.
.El
.(tag Em Caveat:
Mask and maxtransfer are not used with
.Nx .
.enum)
.(tag Caveat:
.It Em Caveat:
The swap (for installation) and the root partition (if you plan to
use the bootblocks) MUST BE WITHIN THE FIRST 4 gigabytes of the disk!
The reason for the former is that xstreamtodev uses trackdisk.device
compatible I/O-calls, the reason for the latter is that the bootblock
compatible I/O-calls, the reason for the latter is that the bootblock
gets a 32bit partition offset from the operating system.
.tag)
.Pp
Once this is done NetBSD/Amiga will be able to recognize your
Once this is done
.Nx*M
will be able to recognize your
disks and which partitions it should use.
.
.Ss2 "Transferring the miniroot file system"
.Ss2 Transferring the miniroot file system
.
The NetBSD/Amiga installation or upgrade now uses a "miniroot"
The
.Nx*M
installation or upgrade now uses a "miniroot"
file system which is installed on the partition used by NetBSD
for swapping. This removes the requirement of using a floppy
disk for the file system used by the installation or upgrade
process. It also allows more utilities to be present on the
file system than would be available when using an 880K floppy
file system than would be available when using an 880 KB floppy
disk.
.Pp
Once the hard disk has been prepared for NetBSD, the miniroot
file system (miniroot.fs) is transferred to the swap
Once the hard disk has been prepared for
.Nx ,
the miniroot file system (miniroot.fs) is transferred to the swap
partition configured during the hard disk prep (or the existing
swap partition in the case of an upgrade). The xstreamtodev
utility provided in the "amiga/installation/misc" directory can
be used on AmigaDOS to transfer the file system for either a new
installation or an upgrade. The file system can also be
transferred on an existing NetBSD system for an update by
transferred on an existing
.Nx
system for an update by
using dd. This should only be done after booting NetBSD
into single-user state. It may also be possible to shutdown
to single-user, providing that the single-user state processes
@ -157,8 +174,12 @@ option
and/or
.Dl --unit=\*<SCSI unit number\*>
.Pp
To transfer the miniroot using NetBSD, you should be booted up
in single user state on the current NetBSD system, or use the
To transfer the miniroot using
.Nx ,
you should be booted up
in single user state on the current
.Nx
system, or use the
"shutdown now" command to shutdown to single-user state. Then
copy the miniroot using dd:
.Dl dd if=miniroot.fs of=/dev/rsd0b
@ -167,7 +188,8 @@ where
should be the device path of the swap partition
your system is configured to use. Once the file is copied,
reboot back to AmigaDOS to boot the upgrade kernel.
.(tag Em Caveat:
.(tag Caveat:
.It Em Caveat:
Once you have started installation, if you abort it
and want to retry you must reinstall the miniroot.fs on the swap
partition.

39
distrib/notes/amiga/upgrade
View File

@ -1,4 +1,4 @@
.\" $NetBSD: upgrade,v 1.20 2000/10/03 23:05:30 lukem Exp $
.\" $NetBSD: upgrade,v 1.21 2000/10/10 12:55:16 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -44,18 +44,23 @@ you must transfer the miniroot file system miniroot.fs onto the swap
partition of the
.Nx
hard disk. You must also have at least the
"base" binary distribution set available, so that you can upgrade
.Sy base
binary distribution set available, so that you can upgrade
with it, using one of the upgrade methods described above. Finally,
you must have sufficient disk space available to install the new
binaries. Since the old binaries are being overwritten in place,
you only need space for the new binaries, which weren't previously
on the system. If you have a few megabytes free on each of your
root and /usr partitions, you should have enough space.
.Pa /
(root) and
.Pa /usr
partitions, you should have enough space.
.Pp
Since upgrading involves replacing the kernel, and most of the system
binaries, it has the potential to cause data loss. You are strongly
advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the
NetBSD partition or on another operating system's partition, before
.Nx
partition or on another operating system's partition, before
beginning the upgrade process.
.Pp
To upgrade your system, follow the following instructions:
@ -79,14 +84,16 @@ machines, use this instead:
.Pp
If you have a M680x0 + PPC board, make sure the PPC cpu is inactive
before using loadbsd, else the kernel will hang!
.Ss2 Directly\ booting\ NetBSD,\ with\ boot\ blocks\ installed:
.(tag Note:
.Ss2 Directly booting
.Nx ,
with boot blocks installed
.(Note
This description is for V40 (OS 3.1) ROMs. For older ROMs,
there might be small differences. Check your AmigaOS documentation
to learn about the exact procedure.
Booting using bootblocks doesn't work at all on some systems, and may
require a mountable filesystem on others.
.tag)
.Note)
.Pp
Reboot your machine, holding down both mouse buttons if you
have a 2-button mouse, the outer mouse buttons if you have
@ -116,7 +123,7 @@ E.g., instead of
use
.Dl "netbsd -bsSn2
.
.Ss2 Once\ your\ kernel\ boots:
.Ss2 Once your kernel boots
.
You should see the screen clear and some information about
your system as the kernel configures the hardware. Note which
@ -145,7 +152,8 @@ may be left in an inconsistent (and possibly unusable) state.
.Pp
You will now be greeted and reminded of the fact that this is a
potential dangerous procedure and that you should not upgrade the
etc-set.
.Sy etc
set.
.Pp
When you decide to proceed, you will be prompted to enter
your root disk. After you've done this, it will be checked
@ -155,7 +163,9 @@ you will be asked if you want to configure your network.
.Pp
You are now allowed to edit your fstab. Normally you don't have
to. Note that the upgrade-kit uses it's own copy of the fstab.
Whatever you do here *won't* affect your actual fstab.
Whatever you do here
.Em won't
affect your actual fstab.
After you are satisfied with your fstab, the upgrade-kit will check
all filesystems mentioned in it. When they're ok, they will be
mounted.
@ -164,7 +174,7 @@ You will now be asked if your sets are stored on a normally
mounted filesystem. You should answer 'y' to this question if
you have the sets stored on a filesystem that was present in
the fstab. The actions you should take for the set extraction
are pretty logical (I think).
are pretty logical (we think).
.Pp
After you have extracted the sets, the upgrade kit will proceed
with setting the timezone and installing the kernel and bootcode.
@ -182,8 +192,11 @@ doesn't mean that you're finished with the upgrade process.
There are several things that you should do, or might have to
do, to insure that the system works properly.
.Pp
You will probably want to get the etc distribution,
extract it, and compare its contents with those in your /etc
You will probably want to get the
.Sy etc
distribution,
extract it, and compare its contents with those in your
.Pa /etc
directory. You will probably want to replace some of your
system configuration files, or incorporate some of the changes
in the new versions into yours.

21
distrib/notes/amiga/whatis
View File

@ -1,8 +1,15 @@
$NetBSD: whatis,v 1.12 2000/09/11 06:26:01 is Exp $
This is the sixth public release of NetBSD for the Amiga and DraCo
.\" $NetBSD: whatis,v 1.13 2000/10/10 12:55:16 lukem Exp $
.
This is the seventh public release of NetBSD for the Amiga and DraCo
line of computers.
New port-specific features include: an optional experimental new
driver for the internal IDE port, which links to the machine
independent wdc code.
.Pp
New port-specific features include:
.(bullet
Support Amiga partition tables that fake more than one sector per
filesystem block (for Adosfs), and partition tables on media with more
than 512 bytes per sector.
.It
PCMCIA support.
.It
Recognize Linux ext2fs partitions.
.bullet)

156
distrib/notes/amiga/xfer
View File

@ -1,153 +1,3 @@
.\" $NetBSD: xfer,v 1.16 2000/03/13 22:37:12 soren Exp $
.Pp
Installation is supported from several media types, including:
.Bl -bullet
.It
AmigaDOS HD partitions
.It
Tape
.It
NFS partitions
.It
FTP
.It
NetBSD partitions, if doing an upgrade.
.It
CD-ROM (SCSI or ATAPI)
.El
.Pp
The miniroot file system needs to be transferred to the NetBSD swap
partition. This can be done from AmigaDOS in the case of a new
install or upgrade, or from NetBSD when doing an upgrade. See the
"Preparing your System for NetBSD Installation" section for details.
.Pp
The steps necessary to prepare the distribution sets
for installation depend on which method of installation
you choose. The various methods are explained below.
.Bl -bullet
.It
To prepare for installing via an AmigaDOS partition:
.Pp
To install NetBSD from an AmigaDOS partition, you need to
get the NetBSD distribution sets you wish to install
on your system on to an AmigaDOS partition. All of the
set_name.xx pieces can be placed in a single directory
instead of separate ones for each distribution set. This
will also simplify the installation work later on.
.Pp
Note where you place the files you will need this later.
.Pp
Once you have done this, you can proceed to the next
step in the installation process, preparing your hard disk.
.It
To prepare for installing from CD-ROM:
.Pp
To install NetBSD from a CD-ROM drive, make sure it is a SCSI
CD-ROM on a SCSI bus currently supported by NetBSD (refer to the
supported hardware list) or an ATAPI cd-rom connected to the A1200
or A4000 internal IDE connector. If it is a
SCSI CD-ROM on a non-supported SCSI bus like
Blizzard-3 SCSI, Apollo SCSI) you must first copy the distribution
sets to an AmigaDOS partition like described above.
.Pp
If your SCSI CD-ROM is connected to a supported SCSI host adapter,
or it is an ATAPI cd-rom connected to the A1200/A4000 internal IDE connector,
simply put the CD into the drive before installation.
.Pp
Once you have done this, you can proceed to the next
step in the installation process, preparing your hard disk.
.It
To prepare for installing via a tape:
.Pp
To install NetBSD from a tape, you need to somehow
get the NetBSD file sets you wish to install on
your system on to the appropriate kind of tape.
.Pp
If you're making the tape on a UN*X system, the easiest
way to do so is:
.Bd -literal -offset indent
dd if=\*<first file\*> of=\*<tape device\*>
dd if=\*<2nd file\*> of=\*<tape device\*>
\&...
.Ed
.Pp
where "\*<tape_device\*>" is the name of the non-rewinding tape
device that describes the tape drive you're using (possibly
something like /dev/nrst0, but we make no guarantees 8-).
If you can't figure it out, ask your system administrator.
"\*<files\*>" are the names of the "set_name.tgz" files
which you want to be placed on the tape.
.Pp
If you have a slow cpu (e.g. 68030 @ 25 MHz) on the target
machine, but big tapes, you might want to store the
uncompressed installation sets instead. This will help tape
streaming when doing the actual installation. E.g, do:
.Bd -literal -offset indent
gzip -d -c \*<first file\*> | dd of=\*<tape device\*>
gzip -d -c \*<2nd file\*> | dd of=\*<tape device\*>
\&...
.Ed
Once you have done this, you can proceed to the next
step in the installation process, preparing your hard disk.
.It
To prepare for installing via an NFS partition:
.(tag Em Note:
this method of installation is recommended
only for those already familiar with using
the BSD network-manipulation commands and
interfaces. If you aren't, this documentation
should help, but is not intended to be
all-encompassing.
.tag)
.Pp
Place the NetBSD software you wish to install into
a directory on an NFS server, and make that directory
mountable by the machine which you will be installing
NetBSD on. This will probably require modifying the
/etc/exports file of the NFS server and resetting
mountd, acts which will require superuser privileges.
Note the numeric IP address of the NFS server and of
the router closest to the new NetBSD machine,
if the NFS server is not on a network which is
directly attached to the NetBSD machine.
.Pp
Once you have done this, you can proceed to the next
step in the installation process, preparing your hard disk.
.It
To prepare for installing via FTP:
.(tag Em Note:
this method of installation is recommended
only for those already familiar with using
the BSD network-manipulation commands and
interfaces. If you aren't, this documentation
should help, but is not intended to be
all-encompassing.
.tag)
.Pp
The preparations for this method of installation
are easy: all you have to do is make sure that
there's some FTP site from which you can retrieve
the NetBSD installation when it's time to do
the install. You should know the numeric IP
address of that site, the numeric IP address of
your nearest router if one is necessary
.Pp
Once you have done this, you can proceed to the next
step in the installation process, preparing your hard disk.
.It
If you are upgrading NetBSD, you also have the option of installing
NetBSD by putting the new distribution sets somewhere in your existing
file system, and using them from there. To do that, you must do the
following:
.Pp
Place the distribution sets you wish to upgrade somewhere in
your current file system tree. At a bare minimum, you must
upgrade the "base" binary distribution, and so must put the
"base" set somewhere in your file system. If you wish,
you can do the other sets, as well, but you should NOT upgrade
the "etc" distribution; the "etc" distribution contains system
configuration files that you should review and update by hand.
.Pp
Once you have done this, you can proceed to the next step in
the upgrade process, actually upgrading your system.
.El
.\" $NetBSD: xfer,v 1.17 2000/10/10 12:55:16 lukem Exp $
.
.so ../common/xfer

11
distrib/notes/arc/legal
View File

@ -1,5 +1,5 @@
.\" $NetBSD: legal,v 1.3 2000/10/05 08:39:10 lukem Exp $
.Pp
.\" $NetBSD: legal,v 1.4 2000/10/10 12:55:16 lukem Exp $
.
This product includes software developed by Per Fogelstrom.
.Pp
This product includes software developed under OpenBSD by Per Fogelstrom.
@ -10,8 +10,7 @@ Opsycon AB.
In the following statement, "This software" refers to the parallel
port driver:
.Pp
.Bl -item -offset indent
.It
This software is a component of "386BSD" developed by
.(item -offset indent
This software is a component of "386BSD" developed by
William F. Jolitz, TeleMuse.
.El
.item)

75
distrib/notes/arm26/hardware
View File

@ -1,34 +1,49 @@
.\" $NetBSD: hardware,v 1.1 2000/08/22 21:46:48 bjh21 Exp $
.Pp
NetBSD/arm26 \*V should support all common Acorn machines fitted with
ARM2, ARM3 and ARM250 CPUs. This includes all Archimedes systems except
for the A500 and A680 prototypes, all R-series workstations, the BBC A3000,
.\" $NetBSD: hardware,v 1.2 2000/10/10 12:55:16 lukem Exp $
.
.Nx*M
\*V should support all common Acorn machines fitted with
ARM2, ARM3 and ARM250 CPUs. This includes all Archimedes systems
(except for the A500 and A680 prototypes),
all R-series workstations, the BBC A3000,
the A5000, A4, A3010, A3020 and A4000.
.Pp
NetBSD/arm26 currently requires exactly eight megabytes of RAM to work.
Four-megabyte systems should work, but tend to run out of memory very easily.
.Pp
NetBSD/arm26 supports a subset of the on-board I/O systems on these machines.
The on-board video system is supported, as are the standard keyboard and
mouse. Other on-board device support differs between two classes of machine:
.Bl -tag -width 5em
.It "Old machines (Archimedes, R-series and BBC A3000)"
None of the other on-board devices are supported.
.It "New machines (A5000, A4, A3010, A3020 and A4000)"
The on-board IDE controller, serial port and parallel port are believed to
be supported, but this support is mostly untested.
.El
.Pp
NetBSD/arm26 supports a few Expansion Cards (otherwise known as "podules").
At present, the following are known to work:
.Bl -bullet
.
.Ss2 Supported devices
.(bullet -offset indent
Memory
.(bullet -compact
8 MB of RAM.
4 MB systems should work, but tend to run out of memory very easily.
.bullet)
.It
Acorn AKA25 Ethernet (Ether1) (ei)
On-board video
.It
Atomwide Ethernet III (Ether3) (ea)
.El
Standard keyboard
.It
Standard mouse
.It
Expansion Cards (aka
.Dq podules ) .
.(bullet -compact
Acorn AKA25 Ethernet (Ether1,
.Em ei )
.It
Atomwide Ethernet III (Ether3,
.Em ea )
.bullet)
.Pp
NetBSD/arm26 uses the machine's ROM OS to boot, and hence depends slightly on
it. It's been tested with RISC OS 3.10 and RISC OS 3.11, and should work
with other versions of RISC OS as well. It hasn't been tested with Arthur at
all.
.Em "New machines (A5000, A4, A3010, A3020 and A4000)"
.Em "may support the following, but this is mostly untested"
.It
On-board IDE controller
.It
Serial port
.It
Parallel port
.bullet)
.
.Pp
.Nx*M
uses the machine's ROM OS to boot, and hence depends slightly on it.
It's been tested with RISC OS 3.10 and RISC OS 3.11, and should work
with other versions of RISC OS as well.
It hasn't been tested with Arthur at all.

8
distrib/notes/arm26/install
View File

@ -1,3 +1,5 @@
.\" $NetBSD: install,v 1.1 2000/08/22 21:46:48 bjh21 Exp $
.Nx Ns /arm26
doesn't currently have a nice GUI installer. This is a problem.
.\" $NetBSD: install,v 1.2 2000/10/10 12:55:16 lukem Exp $
.
.Nx*M
doesn't currently have a nice GUI installer.
This is a problem.

7
distrib/notes/arm26/legal
View File

@ -1,10 +1,13 @@
.\" $NetBSD: legal,v 1.2 2000/10/10 12:55:16 lukem Exp $
.
.\" db_disasm.c locore.S disklabel.h disklabel_acorn.h fp.h frame.h signal.h
.\" undefined.h iocreg.h iic.h rtc.c podulebus.h
.
This product includes software developed by Brini.
.Pp
.\"softintr.c vm_machdep.c ascvar.h
This product includes software developed by Mark Brinicombe for the
NetBSD Project.
.Pp
.\" param.h
This product includes software developed by the RiscBSD team.

9
distrib/notes/arm26/prep
View File

@ -1,4 +1,5 @@
.\" $NetBSD: prep,v 1.1 2000/08/22 21:46:48 bjh21 Exp $
.Nx Ns /arm26
cannot currently be installed to a local disc, so there's not a lot to do to
prepare a machine to run it.
.\" $NetBSD: prep,v 1.2 2000/10/10 12:55:17 lukem Exp $
.
.Nx*M
cannot currently be installed to a local disk,
so there's not a lot to do to prepare a machine to run it.

7
distrib/notes/arm26/upgrade
View File

@ -1,2 +1,7 @@
.\" $NetBSD: upgrade,v 1.1 2000/08/22 21:46:49 bjh21 Exp $
.\" $NetBSD: upgrade,v 1.2 2000/10/10 12:55:17 lukem Exp $
.
.\" No machine-dependent upgrade problems yet.
.
This is the first release of
.Nx*M ,
and as such, there is no ability to upgrade from a prior release.

7
distrib/notes/arm26/whatis
View File

@ -1,2 +1,5 @@
.\" $NetBSD: whatis,v 1.1 2000/08/22 21:46:49 bjh21 Exp $
NetBSD/arm26 \*V is the first formal release of NetBSD/arm26.
.\" $NetBSD: whatis,v 1.2 2000/10/10 12:55:17 lukem Exp $
.
.Nx*M
\*V is the first formal release of
.Nx*M .

10
distrib/notes/arm26/xfer
View File

@ -1,5 +1,7 @@
.\" $NetBSD: xfer,v 1.1 2000/08/22 21:46:49 bjh21 Exp $
.\" $NetBSD: xfer,v 1.2 2000/10/10 12:55:17 lukem Exp $
.
Currently,
.Nx Ns /arm26
can only sensibly be run discless. This requires an unpacked copy of the
binary distribution to be available by NFS to the target system.
.Nx*M
can only sensibly be run diskless.
This requires an unpacked copy of the binary distribution to be
available by NFS to the target system.

425
distrib/notes/arm32/hardware
View File

@ -1,174 +1,289 @@
.\" $NetBSD: hardware,v 1.5 2000/03/21 10:50:04 soda Exp $
NetBSD/arm32 \*V runs on a number of systems with
.\" $NetBSD: hardware,v 1.6 2000/10/10 12:55:17 lukem Exp $
.
.Nx*M
\*V runs on a number of systems with
.Tn ARM6
or later processors,
with or without FPU coprocessor. The minimal configuration is said to
require 8M of RAM and 50M of disk space, though we do not know of anyone
require 8 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, requires at least 65M without counting space needed for
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. (8M of RAM will actually allow you to run X and/or compile,
but it won't be speedy. Note that until you have around 16M of RAM,
recommended. (8 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 more RAM is more important than getting a faster CPU.)
.Pp
Supported devices include (but is not limited to):
.Pp
.Bd -literal -offset indent
RiscPC/A7000(+) floppy controller.
IDE controllers:
Acorn motherboard IDE.
Simtec IDE controller.
RapIDE Issue 2 IDE controller.
ICS V5 & V6 IDE controller.
SCSI host adapters:
Cumana SCSI 2.
PowerTec SCSI 2.
MCS Connect32 SCSI 2.
Acorn SCSI.
Oak SCSI I.
Morley SCSI I (uncached only).
VIDC20 video.
RiscPC Motherboard serial port.
RiscPC Motherboard parallel port.
Ethernet adapters:
Acorn Ether1.
Atomwide Ether3.
ANT Ether3.
ANT Ether5.
Atomwide EtherA.
ANT EtherB.
Acorn EtherH.
I-cubed EtherH.
ANT EtherM.
Most SCSI disk drives.
Most SCSI tape drives.
CD-ROM drives:
Most SCSI CD-ROM drives.
Most ATAPI CD-ROM drives.
[ Note: Some low-priced IDE CDROM drives are known
for being not or not fully ATAPI compliant, and thus
requires some hack (generally an entry to a quirk
table) to work with NetBSD.]
Mice:
RiscPC quadrature mouse.
A7000 PS/2 mouse.
Processors:
ARM 610.
ARM 700.
ARM 700 + FPA11.
ARM 710.
ARM 7500.
ARM 7500FE.
ARM 810. [*]
SA110.
Motherboards:
Acorn RiscPC.
Acorn A7000.
Acorn A7000+.
VLSI RC7500.
Digital DNARD.
Intel EBSA285.
Chalice CATS.
Other devices:
RiscPC keyboard.
A7000 keyboard.
RiscPC realtime clock.
VLSI RC7500 motherboard devices.
Digital DNARD devices
IDE
keyboard
mouse
ethernet
smartcard
audio
joystick
Chalice CATS devices
ALI M1543 southbridge inc PS/2 keyboard & mouse, ide, serial
parallel, USB and ISA bus
RTC
Intel EBSA285 & Chalice CATS PCI devices
PCI - PCI bridges
DC21150
DC21152
DC21153
DC21154
Hint HB1
Digital DC21x4x-based PCI Ethernet adapters, including:
Cogent EM1X0, EM960 (a.k.a. Adaptec ANA-69XX)
Cogent EM964 [b]
Cogent EM4XX [b]
Compex Readylink PCI
DANPEX EN-9400P3
Digital Celebris GL, GLST on-board ethernet
Digital (DEC) PCI Ethernet/Fast Ethernet adapters (all)
JCIS Condor JC1260
Linksys PCI Fast Ethernet
SMC EtherPower 10, 10/100 (PCI only!)
SMC EtherPower
SVEC PN0455
SVEC FD1000-TP
Znyx ZX34X
Qlogic ISP [12]0x0 SCSI/FibreChannel boards
Adaptec AHA-2910, 2915, 2920, and 2930C adapters.
Adaptec AHA-2x4x[U][2][W] cards and onboard PCI designs
using the AIC-7770, AIC-7850, AIC-7860, AIC-7870,
AIC-7880 and AIC-789x chipsets.
Adaptec AHA-394x[U][W] cards [b]
Adaptec AHA-3950U2 cards
Adaptec AHA-3960, 19160 and 29160 Ultra-160 adapters
NE2000 PCI ethernet adapters
Universal Serial Bus:
UHCI host controllers
OHCI host controllers
Hubs
Keyboards using the boot protocol
Mice
Printers
Generic support for HID devices
Video cards
Diamond Stealth 3D 2000 Pro
ATI Charger 4MB
STB Velocity 128
Cirrus Logic 5446
IGS 2010
IGS 5000
S3 based interfaces
.Ed
.
.Ss2 Supported devices
.(bullet -offset indent
RiscPC/A7000(+) floppy controller
.It
IDE controllers
.(bullet -compact
Acorn motherboard IDE
.It
Simtec IDE controller
.It
RapIDE Issue 2 IDE controller
.It
ICS V5 & V6 IDE controller
.bullet)
.It
SCSI host adapters
.(bullet -compact
Cumana SCSI 2
.It
PowerTec SCSI 2
.It
MCS Connect32 SCSI 2
.It
Acorn SCSI
.It
Oak SCSI I
.It
Morley SCSI I (uncached only)
.bullet)
.It
VIDC20 video
.It
RiscPC Motherboard serial port
.It
RiscPC Motherboard parallel port
.It
Ethernet adapters
.(bullet -compact
Acorn Ether1
.It
Atomwide Ether3
.It
ANT Ether3
.It
ANT Ether5
.It
Atomwide EtherA
.It
ANT EtherB
.It
Acorn EtherH
.It
I-cubed EtherH
.It
ANT EtherM
.bullet)
.It
Most SCSI disk drives
.It
Most SCSI tape drives
.It
CD-ROM drives
.(bullet -compact
Most SCSI CD-ROM drives
.It
Most ATAPI CD-ROM drives
.(Note
Some low-priced IDE CD-ROM drives are known for being not or not fully
ATAPI compliant, and thus requires some hack (generally an entry to a
quirk table) to work with NetBSD.
.Note)
.bullet)
.It
Mice
.(bullet -compact
RiscPC quadrature mouse
.It
A7000 PS/2 mouse
.bullet)
.It
Processors
.(bullet -compact
ARM 610
.It
ARM 700
.It
ARM 700 + FPA11
.It
ARM 710
.It
ARM 7500
.It
ARM 7500FE
.It
ARM 810. [*]
.It
SA110
.bullet)
.It
Motherboards
.(bullet -compact
Acorn RiscPC
.It
Acorn A7000
.It
Acorn A7000+
.It
VLSI RC7500
.It
Digital DNARD
.It
Intel EBSA285
.It
Chalice CATS
.bullet)
.It
Other devices
.(bullet -compact
RiscPC keyboard
.It
A7000 keyboard
.It
RiscPC realtime clock
.It
VLSI RC7500 motherboard devices
.bullet)
.bullet)
.
.Ss2 Supported Digital DNARD devices
.(bullet -offset indent -compact
IDE
.It
Keyboard
.It
Mouse
.It
Ethernet
.It
Smartcard
.It
Audio
.It
Joystick
.bullet)
.
.Ss2 Supported Chalice CATS devices
.(bullet -offset indent -compact
ALI M1543 southbridge inc PS/2 keyboard & mouse, ide, serial
.It
Parallel, USB and ISA bus
.It
RTC
.bullet)
.
.Ss2 Supported Intel EBSA285 & Chalice CATS PCI devices
.(bullet -offset indent
PCI - PCI bridges
.(bullet -compact
DC21150
.It
DC21152
.It
DC21153
.It
DC21154
.It
Hint HB1
.bullet)
.It
Digital DC21x4x-based PCI Ethernet adapters
.(bullet -compact
Cogent EM1X0, EM960 (a.k.a. Adaptec ANA-69XX)
.It
Cogent EM964 [b]
.It
Cogent EM4XX [b]
.It
Compex Readylink PCI
.It
DANPEX EN-9400P3
.It
Digital Celebris GL, GLST on-board ethernet
.It
Digital (DEC) PCI Ethernet/Fast Ethernet adapters (all)
.It
JCIS Condor JC1260
.It
Linksys PCI Fast Ethernet
.It
SMC EtherPower 10, 10/100 (PCI only!)
.It
SMC EtherPower
.It
SVEC
.It
PN0455
.It
SVEC FD1000-TP
.It
Znyx ZX34X
.bullet)
.It
Qlogic ISP [12]0x0 SCSI/FibreChannel boards
.It
Adaptec AHA-2910, 2915, 2920, and 2930C adapters
.It
Adaptec AHA-2x4x[U][2][W] cards and onboard PCI designs using the AIC-7770,
AIC-7850, AIC-7860, AIC-7870, AIC-7880 and AIC-789x chipsets
.It
Adaptec AHA-394x[U][W] cards [b]
.It
Adaptec AHA-3950U2 cards
.It
Adaptec AHA-3960, 19160 and 29160 Ultra-160 adapters
.It
NE2000 PCI ethernet adapters
.It
Universal Serial Bus
.(bullet -compact
UHCI host controllers
.It
OHCI host controllers
.It
Hubs
.It
Keyboards using the boot protocol
.It
Mice
.It
Printers
.It
Generic support for HID devices
.bullet)
.It
Video cards
.(bullet -compact
Diamond Stealth 3D 2000 Pro
.It
ATI Charger 4MB
.It
STB Velocity 128
.It
Cirrus Logic 5446
.It
IGS 2010
.It
IGS 5000
.It
S3 based interfaces
.bullet)
.bullet)
.Pp
Drivers for hardware marked with "[*]" are NOT present in installation
kernels.
kernels.
.Pp
Other PCI device may be supported by Intel EBSA285 & Chalice CATS but
Other PCI devices may be supported by Intel EBSA285 & Chalice CATS but
have not been tested.
.Pp
Support for some devices is limited to particular kernels. eg there is no
SA110 support in A7000 kernels.
.Pp
Hardware the we do NOT currently support, but get many questions
about:
.Pp
.Bl -bullet -compact
.
.Ss2 Unsupported devices
.(bullet -offset indent -compact
Acorn/Aleph1 PC cards
.It
Acorn/Aleph1 PC cards.
Any SCSI card using a PowerROM
.It
Any SCSI card using a PowerROM.
Podule based serial ports
.It
Podule based serial ports.
.It
Castle SCSI/Ethernet cards.
.El
Castle SCSI/Ethernet cards
.bullet)
.Pp
Drivers are planned for some of the above devices.

153
distrib/notes/arm32/install
View File

@ -1,4 +1,4 @@
.\" $NetBSD: install,v 1.5 2000/10/03 23:19:11 lukem Exp $
.\" $NetBSD: install,v 1.6 2000/10/10 12:55:17 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -75,17 +75,17 @@ default answer, it will be displayed in brackets ("[]") after the
question. If you wish to stop the installation, you may press Control-C
at any time, but if you do, you'll have to begin the installation
process again from scratch.
.Pp
Boot your machine using the installation kernel for your
platform. (Instructions for doing this on your platform can be
found in the preparation section of this document.)
.Pp
If this doesn't work, ensure that you're using the correct
kernel for your hardware.
.Pp
Depending upon your platform and the method of loading the,
it may take a while to load the kernel.
.Pp
You will then be presented with the
.Nx
kernel boot
@ -96,7 +96,7 @@ begins with its name. As mentioned above, you will need your
disk's geometry when creating NetBSD's partitions. You will
also need to know the name, to tell the install tools what
disk to install on.
.Pp
While booting, you will probably see several warnings. You
should be warned that no swap space is present, and that
init(8) cannot find
@ -104,34 +104,34 @@ init(8) cannot find
Do not be alarmed, these are
completely normal. When you reach the prompt asking you for a
shell name, just press return.
.Pp
You will be asked if you wish to install or upgrade your
system or go to a shell prompt. Enter
.Ic install .
.Pp
You will be presented with a welcome message and a prompt,
asking if you wish to proceed with the installation process.
If you wish to proceed, enter
.Ic y
and press return.
.Pp
You will be asked what type of disk driver you have. The
valid options are listed by the install program, to make sure
you get it right.
.Pp
The install program will then tell you which disks of that
type it can install on, and ask you which it should use.
Reply with the name of your disk. (The first disk of the type
you selected, either "wd0" for IDE disks, or "sd0" for SCSI
disks, is the default.)
.Pp
You will then be asked to name your disk's disklabel. The
default response is "mywd" or "mysd" depending on the type of
your disk, and for most purposes it will be OK. If you choose
to name it something different, make sure the name is a single
word and contains no special characters. You don't need to
remember this name.
.Pp
You will be prompted for your disk's geometry information,
i.e. the number of bytes per sector, cylinders on the disk,
tracks per cylinder (heads), and sectors per track. Enter
@ -144,7 +144,7 @@ have entered this data, the install program will tell you the
total size of your disk, in both sectors, and cylinders.
Remember this number; if you're installing on the whole disk,
you'll need it again soon.
.Pp
When describing your partitions, you will have the option of
entering data about them in units of disk sectors or
cylinders. If you choose to enter the information in units of
@ -152,7 +152,7 @@ sectors, remember that, for optimal performance, partitions
should begin and end on cylinder boundaries. You will be
asked about which units you wish to use, and you should reply
with "c" for cylinders, or "s" for sectors.
.Pp
You will be asked for the size of the
.Nx
portion of the
@ -161,7 +161,7 @@ size of the disk, as printed earlier by the install program.
If you're using only part of the disk, reply with the size
that you specified in the partition editor. (Don't forget to
enter the size in the units you specified in the last step!)
.Pp
If you are not installing on the whole disk, you will be asked
for the offset of the
.Nx
@ -169,15 +169,15 @@ partition from the beginning of
the disk. Reply with the appropriate offset (again, in
whichever units you specified), as determined by how you
set up your disk using the partition editor.
.Pp
You will be asked to enter the size of your
.Nx
root
partition. It should be at least 13M, but if you are going to
be doing development, 14-16M is a more desirable size. This
partition. It should be at least 13 MB, but if you are going to
be doing development, 14-16 MB is a more desirable size. This
size should be expressed in units of sectors or cylinders,
depending on which you said you wanted to use.
.Pp
Next, you will be asked for the size of your swap partition.
You should probably allocate twice as much swap space as you
have real memory. Systems that will be heavily used should
@ -187,7 +187,7 @@ be able to save crash dumps when it panics, you will need at
least as much swap space as you have RAM. Again, this number
should be expressed in units of sectors or cylinders, as
appropriate.
.Pp
The install program will then ask you for information about
the rest of the partitions you want on your disk. For most
purposes, you will want only one more partition,
@ -198,14 +198,14 @@ as a separate partition. That can be done with these installation
tools, but is not covered here.) The install program will
tell you how much space there is left to be allocated in the
NetBSD area of the disk, and, if you only want one more
partition
partition
.Pq Pa /usr ,
you should enter it at the prompt when the
installer asks you how large the next partition should be.
It will then ask you for the name of the mount point for that
partition. If you're doing a basic installation, that is
.Pa /usr .
.Pp
.Em You are now at the point of no return.
Nothing has been
written to your disk yet, but if you confirm that you want to
@ -216,7 +216,7 @@ program incorrect information. If you are sure you want to
proceed, enter
.Ic yes
at the prompt.
.Pp
The install program will now label your disk and make the file
systems you specified. The filesystems will be initialized to
contain
@ -233,13 +233,13 @@ partition on
and so on.) There should be no errors in this
section of the installation. If there are, restart from the
beginning of the installation process.
.Pp
You will be placed at a shell prompt ("#"). The task is to
install the distribution sets. The flow of installation
differs depending on your hardware resources, and on what
media the distribution sets reside.
.Ss2 To\ install\ from\ floppy
.
.Ss2 To install from floppy
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, enter the command "Set_tmp_dir", and enter
@ -248,15 +248,15 @@ that if your disk is still mounted under
.Pa /mnt ; No you
should probably pick a directory under
.Pa /mnt/usr . )
.Pp
After you have picked a temporary directory, enter the
"Load_fd" command, to load the distribution sets from
your floppies.
.Pp
You will be asked which floppy drive to use. Enter
"0" (zero) if you're using the first floppy drive, or
enter "1" if you're using the second.
.Pp
You will be prompted to insert a floppy into the drive,
to have its contents copied to your hard disk. Do so,
and press return to begin copying. When that is done,
@ -264,7 +264,7 @@ read the remainder of the floppies that contain the
distribution sets that you want to install, one by
one. When the last is read, and you are being
prompted for another, press Control-C.
.Pp
Run the
.Ic Extract
command once for each distribution
@ -272,33 +272,34 @@ set you wish to install. For instance, if you wish to
install the "base13" distribution set, followed by the
"text13" distribution set, and finally the "etc13"
distribution set, use the commands:
.Bd -literal
Extract base13
Extract text13
Extract etc13
.Ed
.(disp
Extract base13
Extract text13
Extract etc13
.disp)
.Pp
For each extraction, it will ask you if the extraction
should be verbose. If you reply affirmatively, it
will print out the name of each file that's being
extracted.
.(tag Note:
.(Note
If you know that you will be running low on
disk space when installing NetBSD, you can load and
extract one distribution set at a time. To do this,
load only the floppies which contain the files for the
first distribution set, extract them, and then change
to the temporary directory and remove them with the
command
command
.Ic rm set_name.??
.tag)
.Note)
.Pp
Once you are finished extracting all of the sets that
you wish to install, you should proceed to the
instructions below (after the last install medium
type-specific instructions), that explain how you
should configure your system.
.Ss2 To\ install\ from\ tape
.
.Ss2 To install from tape
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, enter the command "Set_tmp_dir", and enter
@ -309,23 +310,23 @@ you should
probably pick a directory under
.Pa /mnt/usr . )
.No The default is Pa /mnt/usr/distrib .
.Pp
After you have picked a temporary directory, enter the
"Load_tape" command, to load the distribution sets from
tape.
.Pp
You will be asked which tape drive to use. The
default is "rst0", which is correct if you're using
the SCSI tape drive with the lowest SCSI ID number.
(For the SCSI tape drive with the next lowest SCSI ID
number, you should use "rst1", and so on.)
.Pp
You will be prompted to press return when you have
inserted the tape into the tape drive. When you do,
the contents of the tape will be extracted into the
temporary directory, and the names of the files being
extracted will be printed.
.Pp
After the tape has been extracted, to go the directory
containing the first distribution set you wish to
install. (Depending on how you made the tape, it's
@ -333,7 +334,7 @@ probably a subdirectory of the temporary directory you
specified above.) Once there, run the "Set_tmp_dir"
command again, and accept its default answer by
pressing return at the prompt.
.Pp
Use the "Extract" command to extract the distribution
set. For instance, if you're extracting the "base13"
set, use the command:
@ -341,7 +342,7 @@ set, use the command:
You will be asked if you wish the extraction to be
verbose. If you reply affirmatively, the name of each
file being extracted will be printed.
.Pp
Repeat the previous two steps for each distribution
set you wish to install. Change to the set's
directory, run
@ -349,14 +350,14 @@ directory, run
and then run
.Ic Extract Ar set_name
to extract the set.
.Pp
Once you are finished extracting all of the sets that
you wish to install, you should proceed to the
instructions below (after the last install medium
type-specific instructions), that explain how you
should configure your system.
.Ss2 To\ install\ via\ FTP\ or\ NFS
.Pp
.Ss2 To install via FTP or NFS
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, enter the command "Set_tmp_dir", and enter
@ -366,13 +367,13 @@ that your disk is mounted under
probably pick a directory under
.Pa /mnt/usr . )
The default is /mnt/usr/distrib.
.Pp
Configure the appropriate ethernet interface (e.g.
ea0, eb0, etc.) up, with a command like:
.Pp
.Ic ifconfig Ar ifname ipaddr
.Op Ic netmask Ar netmask
.Pp
where
.Ar ifname No is the interface name, like those
listed above, and
@ -384,15 +385,15 @@ at the end of the command line. (The brackets
indicate that those arguments are optional.) For
instance, to configure interface ea0 with IP address
129.133.10.10, use the command:
.Pp
.Dl ifconfig ea0 129.133.10.10
.Pp
and to configure interface eb0 with IP address
128.32.240.167 and a special netmask, 0xffffff00, use
the command:
.Pp
.Dl ifconfig eb0 128.32.240.167 netmask 0xffffff00
.Pp
If the NFS server or FTP server is not on a directly-
connected network, you need to set up a route to it
using a command like:
@ -401,12 +402,12 @@ using a command like:
.sp
.No where Ar gate_ipaddr
is your gateway's numeric IP address.
.Pp
If you are NFS-mounting the distribution sets, mount
them on the temporary directory with a command like:
.sp
.Ic mount -t nfs Ar serv_ipaddr:dist_dir\ tmp_dir
.Pp
where
.Ar serv_ipaddr
is the server's numeric IP address,
@ -414,24 +415,24 @@ is the server's numeric IP address,
is the path to the distribution files on the server, and
.Ar tmp_dir
is the name of the local temporary directory.
.Pp
Once this is done, proceed as if you had loaded the
files from tape, changing to the appropriate
directories, running "Set_tmp_dir", and running
"Extract" as appropriate.
.Pp
If you are retrieving the distribution sets using ftp,
change into the temporary directory, and execute the
command:
.Pp
.Ic ftp Ar serv_ipaddr
.Pp
where
.Ar serv_ipaddr
is once again the server's numeric
IP address. Get the files with FTP, taking care to
use binary mode when transferring the files.
.Pp
Once you have all of the files for the distribution
sets that you wish to install, you can proceed using
the instructions above, as if you had installed from a
@ -439,29 +440,29 @@ floppy. (Note that as with the floppy install, if
you're short on disk space, you can transfer only one
set at a time, extract it, then delete it, to save
space.)
.Ss2 To install from CDROM:
.Pp
.Ss2 To install from CD-ROM
First create a mount point so that you can mount the
CDROM:
CD-ROM:
.Dl mkdir /mnt/cdrom
If you get an error here of "mkdir: /mnt/cdrom", don't
worry it just means that you didn't need to create the
directory.
Then all you need to do is mount the CDROM.
For the first CDROM drive use:
.Pp
Then all you need to do is mount the CD-ROM.
For the first CD-ROM drive use:
.Dl mount -rt cd9660 /dev/cd0a /mnt/cdrom
Or, for the second use:
.Dl mount -rt cd9660 /dev/cd1a /mnt/cdrom
.Pp
Once this is done, extract the required sets as
described in the "To install from floppy" section, but
ensure that you set the temporary directory to the
location of the sets on the CDROM (usually
.Pa /cdrom/distrib ,
location of the sets on the CD-ROM (usually
.Pa /cdrom/distrib ,
but check the release notes that came with the CD).
.Ss2 Completing\ your\ installation
.Pp
.Ss2 Completing your installation
Once you have finished extracting all of the distribution sets
that you wish to install, and are back at the "#" prompt, you
are ready to configure your system. The configuration utility
@ -475,6 +476,6 @@ run the command "Configure". It will ask you for the system's
host name, domain name, and other network configuration
information. It will set up your configuration files and make
the device nodes for the newly-installed system.
.Pp
.Em Congratulations, you have successfully installed
.Nx \*V .

9
distrib/notes/arm32/legal
View File

@ -1,7 +1,6 @@
.\" $NetBSD: legal,v 1.4 1999/03/26 09:10:48 mark Exp $
This product includes software developed by Mark Brinicombe.
.\" $NetBSD: legal,v 1.5 2000/10/10 12:55:17 lukem Exp $
.
.Pp
This product includes software developed by Neil Carson.
.Pp
This product includes software developed by Scott Stevens.

10
distrib/notes/arm32/prep
View File

@ -1,16 +1,16 @@
.\" $NetBSD: prep,v 1.3 1999/01/13 07:30:03 ross Exp $
.\" $NetBSD: prep,v 1.4 2000/10/10 12:55:17 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. Repartitioning your hard disk is an excellent way to
destroy important data.
.Pp
Second, read and perform the instructions in
.Pa arm32/ Ns Ar platform Ns Pa /prep
that are specific to your platform for partitioning and booting (even if you're
dedicating a device to NetBSD).
.Pp
Finally, when you are happy with your
.Nx
installation, do whatever
@ -18,7 +18,7 @@ is necessary to restore order to the partition you took space away from.
This will most likely involve restoring files, but might involve some
other
.Dq house-work .
.Pp
Your hard disk is now prepared to have
.Nx
installed on it, and you should proceed with the installation instructions.

10
distrib/notes/arm32/prep.RISCOS
View File

@ -1,4 +1,4 @@
$NetBSD: prep.RISCOS,v 1.3 2000/10/03 23:19:11 lukem Exp $
$NetBSD: prep.RISCOS,v 1.4 2000/10/10 12:55:17 lukem Exp $
These instructions are specific to NetBSD/arm32 on Acorn RISCOS platforms
(RiscPC/A7000/A7000+) running RiscOS, but may be relevant to futures
@ -70,9 +70,9 @@ Additionally you will require the following:
A7000(+): UNKNOWN
The Bootloader and RiscOS tools: bootloader.arc (This should
be pre-extracted if you're installing from CDROM).
be pre-extracted if you're installing from CD-ROM).
The NetBSD/arm32 distribution sets (Will be on the CDROM, or
The NetBSD/arm32 distribution sets (Will be on the CD-ROM, or
available from your nearest NetBSD ftp site).
A hardcopy of this document, along with a hardcopy of the
@ -322,7 +322,7 @@ can be non-trivial to put it back.
Now that your device is ready for the installation you need to
unpack the bootloader archive (bootloader.arc, if you're installing
from CDROM then this should be unpacked already), copy it to your
from CD-ROM then this should be unpacked already), copy it to your
harddisk and run the bootloader (!BtRiscBSD).
4.1 Configuring !BtRiscBSD before installation
@ -373,7 +373,7 @@ a certain setup.
device configured (eg *con. IDEdiscs 2) even if it has no RiscOS
section.
2) If you have RISC OS 3.5 without the new FileCore, then you must
also have the NetBSD filesystem *completely* below the 511MB
also have the NetBSD filesystem *completely* below the 511 MB
boundary of the device.
3) You must know the SWI base of the <filesys>_DiscOp SWI. Here
<filesys> is SCSIFS, SCSI or ADFS depending upon which controller

2
distrib/notes/arm32/upgrade
View File

@ -1,3 +1,3 @@
.\" $NetBSD: upgrade,v 1.4 1999/03/26 09:22:52 mark Exp $
.\" $NetBSD: upgrade,v 1.5 2000/10/10 12:55:17 lukem Exp $
.
.so ../common/upgrade

31
distrib/notes/arm32/whatis
View File

@ -1,32 +1,5 @@
.\" $NetBSD: whatis,v 1.4 1999/03/26 09:10:48 mark Exp $
NetBSD/arm32 \*V has a number of improvements over the last release.
.Pp
Support has been added for the following hardware platforms:
.Pp
.Bl -bullet
.It
Digital DNARD (DIGITAL Network Appliance Reference Design) also know
as SHARK.
.It
Intel EBSA285 (SA110/DC21825 evaluation boards)
.It
Chalice CATS (SA110/DC21825 PC style motherboard)
.El
.Pp
Additionally there has also been:
.Pp
.Bl -bullet
.It
Various code optimizations, in particular improvements in interrupt
latencies and improved cache cleaning.
.It
New drivers.
.It
Bug fixes.
.It
full integration of the toolchain.
.El
.Pp
.\" $NetBSD: whatis,v 1.5 2000/10/10 12:55:17 lukem Exp $
.
.Nx \*V
on arm32 is, as usual, also fully backward compatible with old
.Nx

4
distrib/notes/arm32/xfer
View File

@ -1,3 +1,3 @@
.\" $NetBSD: xfer,v 1.3 1999/01/13 07:30:03 ross Exp $
.\" $NetBSD: xfer,v 1.4 2000/10/10 12:55:17 lukem Exp $
.
.so ../common/xfer

128
distrib/notes/atari/hardware
View File

@ -1,89 +1,99 @@
.\" $NetBSD: hardware,v 1.15 2000/09/27 10:54:53 leo Exp $
NetBSD/atari \*V runs on a TT030, Falcon and Hades. An FPU is not required.
The minimum amount of RAM required is 4Mb. On the Hades, only the Tseng PCI
.\" $NetBSD: hardware,v 1.16 2000/10/10 12:55:17 lukem Exp $
.
.Nx*M
\*V runs on a TT030, Falcon and Hades. An FPU is not required.
The minimum amount of RAM required is 4 MB. On the Hades, only the Tseng PCI
VGA cards (et4000/et6000/et6100) are supported in the \*V release. When
an unsupported video card is present, you can use NetBSD with a serial console
only.
.Pp
Here is a table of recommended HD partition sizes for a full install:
.Bd -literal -offset indent
partition: advise, with X, needed, with X
root (/) 25M 25M 20M 20M
user (/usr) 245M 270M 120M 145M
swap 2 times RAM size below 32 MB, then up to you
local (/local) up to you
.Ed
.Bl -column -offset indent Partition Suggested 100xMBxx Needed 100xMB
.It Partition Ta Suggested Ta +\ X Ta Needed Ta +\ X
.It root\ (/) Ta "25 MB" Ta "25 MB" Ta "20 MB" Ta "20 MB"
.It /usr Ta "245 MB" Ta "270 MB" Ta "120 MB" Ta "145 MB"
.It /var Ta "20 MB" Ta "20 MB" Ta "5 MB" Ta "5 MB"
.It swap Ta Em "2*RAM below 32 MB, then up to you"
.El
.(item -offset indent
Anything else is up to you!
.item)
.Pp
In addition of the rule of thumb for the swap size mentioned below, you
probably want to make sure that the size of the swap partition does not
drop below 20Mb (30Mb for systems with X).
Another item are the add-on packages. You might want 20-30M (or more) in
/local (or added to /usr) to store packages from the NetBSD package system.
As you may note the recommended size of /usr is 125M greater than
needed. This is to leave room for a kernel source and compile tree
as you will probably want to compile your own kernel. (GENERIC is
large and bulky to accommodate all people, BOOT is small and might
not have all the features you want).
.Pp
Supported devices include:
.Bl -bullet
. It
drop below 20 MB (30 MB for systems with X).
Another item is the add-on packages. You might want 20-30M (or more) in
.Pa /usr/local
(or added to
.Pa /usr )
to store packages from the NetBSD package system.
As you may note the recommended size of
.Pa /usr
is 125 MB greater than needed.
This is to leave room for a kernel source and compile tree
as you will probably want to compile your own kernel.
.Li ( GENERIC
is large and bulky to accommodate all people,
.Li BOOT
is small and might not have all the features you want).
.
.Ss2 Supported devices
.(bullet -offset indent
The builtin SCSI host adapter
. Bl -hyphen
. It
.(bullet -compact
Should support most SCSI-drives.
. It
.It
Should support most tape drives.
. It
.It
Should support most CD-ROM drives.
. It
.It
Should support most ZIP/MO drives.
. El
. It
.bullet)
.It
The builtin video controller
. It
The builtin (720Kb/1.44Mb) floppydrive
. It
.It
The builtin (720 KB / 1.44 MB) floppy drive
.It
The serial2/modem2 ports
. It
.It
The Falcon FX memory expansion
. It
The atari mouse
. It
.It
The Atari mouse
.It
A 3-button mouse (see build description in the FAQ!)
. It
.It
The parallel printer
. It
.It
IDE interface on both Falcon and Hades (includes ATAPI support)
. It
.It
The serial interface on the first 68901 UART (modem1)
. It
.It
VME-bus devices (TT030/Hades)
. Bl -hyphen
. It
.(bullet -compact
BVME410 ethernet
. It
.It
Circad Leonardo 24-bit VME graphics adapter
. It
.It
Crazy Dots VME et4000 graphics adapter
. It
.It
Riebl (and possibly PAM) ethernet cards on the VME bus.
. El
. It
.bullet)
.It
PCI-bus devices (Hades only)
. Bl -hyphen
. It
.(bullet -compact
ET4000/ET6000/ET6100-PCI (VGA console)
. It
.It
Adaptec 2940U
. El
. It
.bullet)
.It
ISA-bus devices (Hades only)
. Bl -hyphen
. It
.(bullet -compact
Teles S0/16.3-ISA ISDN adapter (with I4B)
. El
.El
.bullet)
.bullet)
.Pp
This list is incomplete by definition. I can not test all SCSI peripherals,
ISA cards or PCI cards... If you have problems with such a peripheral, please
contact the port-atari mailing list.
This list is incomplete by definition. We can not test all SCSI peripherals,
ISA cards or PCI cards. If you have problems with such a peripheral, please
contact the
.Mt port-atari@netbsd.org
mailing list.

53
distrib/notes/atari/install
View File

@ -1,4 +1,4 @@
.\" $NetBSD: install,v 1.13 2000/10/03 23:21:26 lukem Exp $
.\" $NetBSD: install,v 1.14 2000/10/10 12:55:17 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -43,14 +43,13 @@ The following is a walk-through of the steps necessary to get NetBSD
installed on your hard disk. If you wish to stop the installation,
you may press Control-C at any prompt, but if you do, you'll have to
begin again from scratch.
.Bl -enum
.It
.(enum
Booting the miniroot
First you need to get yourself into NetBSD. This can be
done in a couple ways, both of which currently require
GEMDOS. You need either the bootfloppy provided in the
distribution or you can copy the loadbsd.ttp program and
kernel to a boot floppy disk (1.4M needed) or put them on a TOS
kernel to a boot floppy disk (1.44 MB needed) or put them on a TOS
partition. Select the loadbsd program and it will
ask for parameters, supply: '-b netbsd' (or whatever name
you copied the kernel to). You can, of course, also run it
@ -68,10 +67,10 @@ track loaded. After loading 80 tracks, it will ask you
to insert the next floppy. At this time, insert the BSD
install floppy 2 and press any key. The kernel continous
loading another 40 tracks before it continues to boot.
.(tag Note:
If you are using 1.44Mb floppies, you should select 'md1a'
.(Note
If you are using 1.44 MB floppies, you should select 'md1a'
instead of 'md0a'.
.tag)
.Note)
The system should continue to boot. For now ignore WARNING:
messages about bad dates in clocks. Eventually you will be
be asked to enter the pathname of the shell, just press
@ -102,7 +101,7 @@ but is blank or used by another non-AHDI system, start at item 4b.
.Pp
.Em You are now at the point of no return!
The programs in section
4 will modify your harddisk. Type Control-C
4 will modify your harddisk. Type Control-C
.Em now
if you don't
want this.
@ -121,14 +120,14 @@ that AHDI created them. When you leave this editor and continue
at item 4b, your changes to the id's do have consequences to the
partition order! They will show up as follows:
.Pp
. Bl -tag -width d\ (and\ up)
. It a
.(tag d\ (and\ up)
.It a
\- the first NBD partition
. It b
.It b
\- the first NBS partition
. It d\ (and\ up)
.It d (and up)
\- the rest of the partitions in AHDI order
. El
.tag)
.It
Labeling your root disk (using edlabel)
You are now allowed to change the partitioning of your disk. If
@ -139,20 +138,20 @@ yourself by selecting 'standarize geometry'. This allows you to
select a 'sectors per track' and 'tracks/cylinder' value and have
the (fictious) SCSI geometry changed accordingly. So if you select
64 sect/track and 32 tracks/cylinder, each cylinder is exactly
1Mb in size. Well, go ahead and don't forget to save your work
1 MB in size. Well, go ahead and don't forget to save your work
before you quit!
.(tag Note:
.(Note
to make sure that NetBSD can create/mount filesystems on
the partitions you defined, make sure the 'type' is entered
correctly:
.Pp
.Bl -tag -width 4.2BSD -compact
.(tag 4.2BSD -compact
.It Tn 4.2BSD
\- filesystems created by NetBSD
.It Tn MSDOS
\- filesystems shared with GEM
.El
.tag)
.Note)
.It
Label additional disks
Now that your root-disk is labeled, you are given the opportunity
@ -184,8 +183,7 @@ You are finally at the point where some real data will be put on
your freshly-made filesystems. Select the device type you whish
to install from and off you go....
Some notes:
.Bl -bullet
.It
.(bullet
If you want to install from tape, please read the section
about how to create such a tape.
The tape device name will be "nrst0" for the first tape
@ -199,7 +197,7 @@ you need the mount-point itself, enter '.'.
For previous NetBSD users: If you want to install from a
GEMDOS filesystem, you don't need to rename the distribution
sets as you may have done in previous versions of NetBSD.
.El
.bullet)
.It
Timezone selection and device-node building
The isn't much to say about this. Just select the timezone you
@ -211,8 +209,8 @@ Be patient, this will take a while...
Installing the kernel
Because the kernel didn't fit on the install-disks, the installer
asks you about the disk your kernel is on. You can specify the
floppy with disk 'fd0' and partition 'b' for 720K disks and
partition 'c' for 1.4M disks, or one of the hard disk partitions.
floppy with disk 'fd0' and partition 'b' for 720 KB disks and
partition 'c' for 1.44 MB disks, or one of the hard disk partitions.
.It
Installing the bootstrap
Finally, the installer ask you if you want to install the bootblock
@ -226,13 +224,12 @@ also installed a bootblock, you only have to reboot your atari to
enter your freshly build system. If you didn't, get back to section
1 (How to boot the miniroot). Just substitute 'md0a' by your NetBSD
root disk.
.El
.Ss2 Some\ Extra\ Remarks
.enum)
.Ss2 Some extra remarks
If you don't want to use the bootloader. You could use the following
setup:
.Bl -bullet
.It
Reserve a small GEMDOS partition of about 4Mb. This is
.(bullet
Reserve a small GEMDOS partition of about 4 MB. This is
enough to put in a few kernels. Put the netbsd kernel
into this partition. Also, edit your /etc/fstab to always
mount this partition, say as /kernels. Now make a symlink
@ -242,4 +239,4 @@ own kernel. When compilation is finished, you just copy
your kernel to /kernels/netbsd and reboot. It's wise to
make sure there is _always_ a 'known to work' kernel image
present.
.El
.bullet)

14
distrib/notes/atari/legal
View File

@ -1,12 +1,6 @@
.\" $NetBSD: legal,v 1.4 1999/01/13 07:30:03 ross Exp $
This product includes software developed by Gordon Ross
This product includes software developed by Leo Weppelman.
This product includes software developed by Markus Wild.
.\" $NetBSD: legal,v 1.5 2000/10/10 12:55:17 lukem Exp $
.
.Pp
This product includes software developed by Thomas Gerner
.Pp
This product includes software developed by Waldi Ravens.

20
distrib/notes/atari/prep
View File

@ -1,14 +1,14 @@
.\" $NetBSD: prep,v 1.5 1999/01/13 07:30:03 ross Exp $
.\" $NetBSD: prep,v 1.6 2000/10/10 12:55:17 lukem Exp $
.
Note you will be modifying your HD's if you mess something up here you
could lose everything on all the drives that you work with. It is
therefore advised that you:
.Bl -bullet
.It
.(bullet
Write down your current configurations. Do this
by writing down all partition info (especially their sizes).
.It
.Em Back up the partitions you are keeping.
.El
.bullet)
.Pp
If NetBSD has a disk of it's own, you can delay the partitioning until
the installer requests you to do it. This means that you can safely skip
@ -18,11 +18,12 @@ If NetBSD has to share the disk with another operating system, you must
take care of partitioning your harddisk before installing NetBSD; creating
space for at least root, swap and /usr partitions and possibly at
least one more for /local if you have the space.
.(note Em Warning:
.(tag Warning:
.It Em Warning:
The AHDI partioning function erases all partions on your harddisk
even if they are not changed!
I know this is rather stupid, but don't say I didn't warn you.
.note)
.tag)
If you want to use an AHDI partitioning sceme and you want to be able to boot
directly into NetBSD, there are some constraints on the partition layout.
.Pp
@ -32,7 +33,7 @@ disk. The root sector can only contain the neccessary data for four
partitions. Nobody thought that this limitation would cause any problems.
After all, 640 KByte should be enough. As hard disk grew, it was neccessary
to define more than four partitions. In order to be more or less compatible
with the old format, a new type of partition entry was defined: XGM partions.
with the old format, a new type of partition entry was defined: XGM partions.
.Pp
An XGM partition is a "look over there" sign: Another root sector can be
found at the start of the XGM partition. This root sector contains the
@ -70,8 +71,7 @@ while partitions #1, #6 and #7 will be primary partitions.
You can move the extended partition range by clicking on one of the buttons
on the right side of the dalog box. Try to find one where your first NetBSD
partition is a primary partition. Golden rules:
.Bl -bullet
.It
.(bullet
If the disk contains no GEMDOS partitions, don't use AHDI. Let NetBSD
handle it alone.
.It
@ -88,6 +88,6 @@ trouble. Try using partitions #1 and #2 as the first two GEMDOS
partitions. Use partition #3 as the first NetBSD partition. Start the
extended partition range with partition #4. Put the other NetBSD
extended partition range.
.El
.bullet)
.Pp
Good luck, you'll need it...

13
distrib/notes/atari/upgrade
View File

@ -1,6 +1,6 @@
.\" $NetBSD: upgrade,v 1.5 1999/01/13 07:30:04 ross Exp $
.\" $NetBSD: upgrade,v 1.6 2000/10/10 12:55:17 lukem Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -40,8 +40,7 @@ distribution, you have to replace them again after you did the update.
The etc-set needs special caution. You generally don't want to install
this one when upgrading. It is recommended that you get a copy of this
set and _carefully_ upgrade your configuration files by hand.
.Bl -enum
.It
.(enum
Starting the upgrade
.Pp
Ok, let's go. Insert the bootfloppy and follow the 'normal'
@ -58,7 +57,9 @@ your root disk. After you've done this, it will be checked
automatically to make sure that the filesystem is in a sane
state before making any modifications. After this is done,
you will be asked if you want to configure your network. You
can skip this section on NetBSD/Atari for now.
can skip this section on
.Nx*M
for now.
.It
Editing the fstab
.Pp
@ -85,4 +86,4 @@ After you have extracted the sets, the upgrade kit will proceed
with setting the timezone and installing the kernel and bootcode.
This is all exactly the same as described in the installation
section.
.El
.enum)

41
distrib/notes/atari/whatis
View File

@ -1,7 +1,11 @@
.\" $NetBSD: whatis,v 1.9 2000/10/02 11:42:20 lukem Exp $
The Atari release stepped in in March 1995. The first official release was
.\" $NetBSD: whatis,v 1.10 2000/10/10 12:55:17 lukem Exp $
.
The Atari release was imported into
.Nx
in in March 1995.
The first official release was
.Nx 1.1 .
About a year later,
About a year later,
.Nx 1.2
was released for the Atari. This
release fixed a large number of bugs and made the Atari-port a stable member
@ -10,30 +14,9 @@ The saga continued with the
.Nx 1.3
release. In this release, support was added for the Medusa Hades, Riebl
ethernet and Falcon IDE support.
And now, yet another release is emerging!
.Pp
New on the
.Nx 1.4
was released a couple of years later, and added support for various
devices.
And now,
.Nx \*V
release (atari specific):
.Bl -bullet
.It
Crazy Dots VME et4000 graphics adapter
.It
Circad Leonardo 24-bit VME graphics adapter
.It
VME BVME410 ethernet
.It
ATAPI support on IDE
.It
Hades PCI-devices
.Bl -hyphen
. It
Adaptec 2940U
.El
.It
Hades ISA-devices
.Bl -hyphen
. It
Teles 16.3 card (Requires isdn4bsd package).
.El
.El
is emerging!

67
distrib/notes/atari/xfer
View File

@ -1,23 +1,28 @@
.\" $NetBSD: xfer,v 1.11 1999/04/06 12:33:38 leo Exp $
.\" $NetBSD: xfer,v 1.12 2000/10/10 12:55:17 lukem Exp $
.
Installation is supported from several media types, including:
.Pp
.Bl -bullet -compact
.It
TOS HD partitions
.(bullet -compact -offset indent
GEMDOS/TOS HD partitions
.It
Tape
.El
.bullet)
.Pp
No matter what you do, however, you'll need to have three disks handy,
on which you will put the install and boot floppy images.
.Pp
All the images are available from the directory "installation/floppies"
under the root of the NetBSD/atari tree at your favorite archive site.
All the images are available from the directory
.Pa installation/floppies
under the root of the
.Nx*M
tree at your favorite archive site.
.Pp
If you are using NetBSD/atari to make the floppies, you should use
If you are using
.Nx*M
to make the floppies, you should use
the command dd(1) to write the raw floppy images (.fs files) to
the disk. As an example, to write the first part of the miniroot filesystem
onto a 720KB floppy in fd0 use:
onto a 720 KB floppy in fd0 use:
.Dl dd\ if=miniroot.fs.1\ of=/dev/rfd0b\ bs=9b
.Pp
If you are using TOS to make the floppies, grab the 'rawwrite' utility
@ -25,9 +30,13 @@ from the "atari/utils" directory and issue the command:
.Dl rawwrite\ boot.fs
.Pp
This will create the boot-floppy on the floppy in drive a. The floppies
should be pre-formatted on 720Kb/1.44Mb for both the 'dd' and 'rawwrite'
commands to work. Pre-formatting can be best done using the desktop format
command. Some other utilities seem to be giving problems.
should be pre-formatted on 720 KB / 1.44 MB for both the
.Ic dd
and
.Ic rawwrite
commands to work.
Pre-formatting can be best done using the desktop format command.
Some other utilities seem to be giving problems.
.Pp
Since the 1.3 release, it is also possible to use HD-floppies. You should
than use the floppy device '/dev/rfd0c' or add the '-H' flag to 'rawwrite'.
@ -35,34 +44,38 @@ than use the floppy device '/dev/rfd0c' or add the '-H' flag to 'rawwrite'.
The steps necessary to prepare the distribution sets
for installation depend on which method of installation
you choose. The various methods are explained below.
.Bl -bullet
.It
To prepare for installing via an GEMDOS partition:
.Pp
To install NetBSD from an GEMDOS partition, you need to
get the NetBSD distribution sets you wish to install
.(tag GEMDOSxx
.It Em GEMDOS
To install
.Nx
from an GEMDOS partition, you need to get the
.Nx
distribution sets you wish to install
on your system on to an GEMDOS partition.
.Pp
Note where you placed the files, you will need this later.
.Pp
Once you have done this, you can proceed to the next
step in the installation process, preparing your hard disk.
.It
To prepare for installing via a tape:
.Pp
To install NetBSD from a tape, you need to somehow
get the NetBSD filesets you wish to install on
.It Em Tape
To install
.Nx
from a tape, you need to somehow
get the
.Nx
filesets you wish to install on
your system on to the appropriate kind of tape. If you make
the tape on a UN*X-like system, you can create it as follows:
.Bd -literal
cd .../NetBSD-1.3/atari/binary/sets
.(disp
cd .../NetBSD-\*V/atari/binary/sets
T=\*<tape_device\*>
mt -f $T rewind
for f in base etc comp games man misc text
dd if=$f.tgz of=$T conv=sync bs=5k
done
mt -f $T rewind
.Ed
.disp)
.Pp
where "\*<tape_device\*>" is the name of the (non-rewinding!) tape
device that you're using (probably something like /dev/nrst0,
but we make no guarantees 8-).
@ -70,4 +83,4 @@ If you can't figure it out, ask your system administrator.
.Pp
Once you have done this, you can proceed to the next
step in the installation process, preparing your hard disk.
.El
.tag)

181
distrib/notes/hp300/hardware
View File

@ -1,92 +1,121 @@
.\" $NetBSD: hardware,v 1.7 1999/01/13 07:30:04 ross Exp $
NetBSD/hp300 \*V will run on most HP 9000/300- and 400-series machines.
The smallest amount of RAM that has been tested is 4M. If you wish to
.\" $NetBSD: hardware,v 1.8 2000/10/10 12:55:18 lukem Exp $
.
.Nx*M
\*V will run on most HP 9000/300- and 400-series machines.
The smallest amount of RAM that has been tested is 4 MB. If you wish to
run X, more RAM is recommended.
.Pp
Here is a table of recommended HD partition sizes for a full install:
.Bd -literal -offset indent
partition: advise needed
root (/) 25M 15M
user (/usr) 150M 100M
swap (2 or 3 * RAM) 6M (see note below)
.Bl -column -offset indent Partition Suggested Needed
.It Partition Ta Suggested Ta Needed
.It root\ (/) Ta "25 MB" Ta "15 MB"
.It /usr Ta "150 MB" Ta "100 MB"
.It /var Ta "20 MB" Ta "5 MB"
.It swap Ta Em "2-3 *RAM" Ta 6 MB
.El
.(item -offset indent
Anything else is up to you!
.Ed
.(tag Note:
.item)
.Pp
.(Note
The hp300 installation procedure uses a `miniroot' filesystem
which is placed into the swap area of the disk. The swap partition
must be large enough to hold this miniroot image.
.tag)
.Pp
The following HP hardware is supported:
.de section
. El
. Pp
. It Em \\$*
. br
. Bl -bullet -compact
..
.de item
. It
\\$*
..
.Bl -tag -width Disks
. It Em CPUs:
. br
. Bl -bullet -compact
. item 68020-based: 318, 319, 320, 330, and 350.
. item 68030-based: 340, 345, 360, 370, 375, and 400(*).
. item 68040-based: 380, 425(*), and 433(*).
. section Disks:
. item HP-IB/CS80: 7912, 7914, 7933, 7936, 7937, 7945, 7957,
.Note)
.
.Ss2 Supported hardware
.(bullet -offset indent
CPUs
.(bullet -compact
68020-based: 318, 319, 320, 330, and 350.
.It
68030-based: 340, 345, 360, 370, 375, and 400 [1].
.It
68040-based: 380, 425 [1], and 433 [1].
.bullet)
.It
Disks
.(bullet -compact
HP-IB/CS80: 7912, 7914, 7933, 7936, 7937, 7945, 7957,
7958, 7959, 2200, and 2203.
. item SCSI-I(**), including magneto-optical and CD-ROM.
. section Tape drives:
. item Low-density HP-IB/CS80 cartridge: 7914, 7946, and 9144.
. item High-density HP-IB/CS80 cartridge: 9145.
. item HP-IB/CS80 1/2": 7974A, 7978A/B, 7979A, 7980A, and 7980XC.
. item SCSI: HP DAT, Exabyte, and SCSI QIC drives such as
the Archive Viper.
. section RS232 interfaces:
. item 98644 built-in single port (dca).
. item 98642 4-port (dcm).
. item 98638 8-port (dcm).
. section Network interfaces:
. item 98643 built-in and add-on LAN cards.
. section Displays:
. item 98544, 98545, and 98547 color and monochrome Topcat.
. item 98548, 98549, and 98550 color and monochrome Catseye.
. item 98700 and 98710 Gatorbox.
. item 98720 and 98721 Renaissance.
. item 98730 and 98731 DaVinci.
. item A1096A monochrome Hyperion.
. section Input devices:
. item General interface supporting all HIL devices: keyboard,
2 and 3 button mice(***), and ID module.
. section Miscellaneous:
. item Battery-backed real-time clock.
. item 98624 built-in HP-IB interface.
. item 98625A and 98625B `fast' HP-IB interface.
. item 98658A built-in and add-on SCSI interface.
. item Printers and plotters on RS232 and HP-IB.
. item SCSI autochanger.
. El
.El
.It
SCSI-I [2], including magneto-optical and CD-ROM.
.bullet)
.It
Tape drives
.(bullet -compact
Low-density HP-IB/CS80 cartridge: 7914, 7946, and 9144.
.It
High-density HP-IB/CS80 cartridge: 9145.
.It
HP-IB/CS80 1/2": 7974A, 7978A/B, 7979A, 7980A, and 7980XC.
.It
SCSI: HP DAT, Exabyte, and SCSI QIC drives such as the Archive Viper.
.bullet)
.It
RS232 interfaces
.(bullet -compact
98644 built-in single port (dca).
.It
98642 4-port (dcm).
.It
98638 8-port (dcm).
.bullet)
.It
Network interfaces
.(bullet -compact
98643 built-in and add-on LAN cards.
.bullet)
.It
Displays
.(bullet -compact
98544, 98545, and 98547 color and monochrome Topcat.
.It
98548, 98549, and 98550 color and monochrome Catseye.
.It
98700 and 98710 Gatorbox.
.It
98720 and 98721 Renaissance.
.It
98730 and 98731 DaVinci.
.It
A1096A monochrome Hyperion.
.bullet)
.It
Input devices
.(bullet -compact
General interface supporting all HIL devices: keyboard,
2 and 3 button mice [3], and ID module.
.bullet)
.It
Miscellaneous
.(bullet -compact
Battery-backed real-time clock.
.It
98624 built-in HP-IB interface.
.It
98625A and 98625B `fast' HP-IB interface.
.It
98658A built-in and add-on SCSI interface.
.It
Printers and plotters on RS232 and HP-IB.
.It
SCSI autochanger.
.bullet)
.bullet)
.Pp
.Bl -tag -width (***)
. It (*)
.(tag [1] -offset indent
.It [1]
400-series machines configured for Domain/OS
are not fully supported,
notably, the keyboard doesn't work and the ROMs must be in `HP-UX mode'.
. It (**)
are not fully supported.
Notably, the keyboard doesn't work and the ROMs must be in `HP-UX mode'.
.It [2]
SCSI-II drives are known to work,
though this may require changing a
jumper on some drives. See your disk's documentation for details.
. It (***)
.It [3]
Serial mice connected to a `HIL to quad'
converter are also known to work.
.El
.tag)
.Pp
If it's not on this list, there is no official support for it in this release.

24
distrib/notes/hp300/install
View File

@ -1,6 +1,6 @@
.\" $NetBSD: install,v 1.5 2000/03/13 22:37:12 soren Exp $
.\" $NetBSD: install,v 1.6 2000/10/10 12:55:18 lukem Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -36,27 +36,27 @@ you through the entire process, and is well automated. Additional
improvements are planned for future releases.
.Pp
The miniroot's install program will:
.Bl -bullet
.It
.(enum
Allow you to place disklabels on additional disks.
Note that partition sizes and offsets are expressed
in sectors. When you fill out the disklabel, you will
need to specify partition types and filesystem parameters.
If you're unsure what these values should be, use the
following:
.Bd -ragged
.(disp
fstype: 4.2BSD
fsize: 1024
bsize: 4096
cpg: 16
.Ed
.disp)
.Pp
If the partition will be a swap partition, use the following:
.Bd -ragged
.(disp
fstype: swap
fsize: 0 (or blank)
bsize: 0 (or blank)
cpg: 0 (or blank)
.Ed
.disp)
.Pp
You will also need to specify the number of partitions.
The number of partitions is determined by the `index' of
@ -73,16 +73,16 @@ the `c' partition must be fstype `boot'.
Anything after a `#' is a comment.
.Pp
The following is an example disklabel partition map:
.Bd -literal
.(disp
7 partitions:
# size offset fstype [fsize bsize cpg]
# size offset fstype [fsize bsize cpg]
a: 30912 448 4.2BSD 1024 8192 16 # (Cyl. 1 - 69)
b: 130816 31360 swap # (Cyl. 70 - 361)
c: 1296512 0 boot # (Cyl. 0 - 2893)
e: 81984 162176 4.2BSD 1024 8192 16 # (Cyl. 362 - 544)
f: 102592 244160 4.2BSD 1024 4096 16 # (Cyl. 545 - 773)
g: 949760 346752 4.2BSD 1024 8192 16 # (Cyl. 774 - 2893)
.Ed
.disp)
.It
Create filesystems on target partitions.
.It
@ -110,7 +110,7 @@ Copy a new kernel onto your root partition.
Install a new boot block.
.It
Check your filesystems for integrity.
.El
.enum)
.Pp
First-time installation on a system through a method other than the
installation program is possible, but strongly discouraged.

9
distrib/notes/hp300/legal
View File

@ -1,9 +1,4 @@
.\"$NetBSD: legal,v 1.4 1999/01/13 07:30:04 ross Exp $
This product includes software developed by the Computer
Systems Laboratory at the University of Utah.
.\" $NetBSD: legal,v 1.5 2000/10/10 12:55:18 lukem Exp $
.
This product includes software developed at Ludd, University of
Lule}, Sweden and its contributors.
This product includes software developed by Gordon W. Ross.

60
distrib/notes/hp300/prep
View File

@ -1,4 +1,5 @@
.\" $NetBSD: prep,v 1.7 1999/01/13 07:30:04 ross Exp $
.\" $NetBSD: prep,v 1.8 2000/10/10 12:55:18 lukem Exp $
.
Currently, only installing the miniroot from the network is supported.
This may change in a future release.
.Pp
@ -11,9 +12,12 @@ on 1024 byte sectors, while NetBSD's is based on 512 byte sectors.
.Pp
.Em A quick note about partitions:
Since the target disk will become the boot
disk for your new NetBSD/hp300 installation, you will need to treat the
disk for your new
.Nx*M
installation, you will need to treat the
`a' and `c' partitions in a special manner. Due to the size of the
NetBSD/hp300 boot program (it spills into the area after the disklabel),
.Nx*M
boot program (it spills into the area after the disklabel),
it is necessary to offset the `a' partition one cylinder from the beginning
of the disk. Later, the `c' partition will be marked with the type
`FS_BOOT' and may not be used for a filesystem. (For those unfamiliar
@ -37,22 +41,24 @@ code 16, unit numers might be something like the following:
.It HP-IB\ at\ 14,\ slave\ 5 Ta 13 Ta (disk:\ rd13)
.It SCSI\ at\ 16,\ slave\ 0 Ta 0 Ta (disk:\ sd0)
.El
.
.Ss2 Miniroot installation via network
.(tag Em Note:
.(Note
Booting sys_inst via the network
on early hp300 models
.Em is only
.Em possible if your bootrom
.Em is No rev. c Em or later.
.Em is only possible if your bootrom is
rev. c
.Em or later.
When checking the
revision of your BOOTROM, use what it printed on the console during
the self-test, not what may be printed on a sticker on the chip itself.
.tag)
.Note)
.Pp
In order to complete this process, you will need the following from the
.Pa \&.../installation/misc
directory of the distribution:
.(tag SYS_INST.gz
.It Pa SYS_INST.gz
The standalone disklabel and miniroot
installation tool. This file must be un-gzipped before using.
.tag)
@ -62,6 +68,7 @@ the following from the
.Pa \&.../installation/miniroot
directory of of the distribution:
.(tag miniroot.fs.gz
.It Pa miniroot.fs.gz
A miniroot filesystem image.
.tag)
.Pp
@ -72,13 +79,13 @@ special note below.
To boot SYS_INST from tape, you need only place SYS_INST on the tape as
the first file.
.
.
.(tag Em Loading\ SYS_INST\ via\ the\ network xxxxxxx
.Ss2 Loading SYS_INST via the network
.Pp
If you wish to load the SYS_INST program via the network, you may need
the following from the `.../installation/misc' directory in addition to the
items listed above:
.(tag Pa rbootd.tgz
.(tag rbootd.tgz
.It Pa rbootd.tgz
Source code for the rbootd program included with
NetBSD. It requires that the server has a
Berkeley Packet Filter (bpf). You will need to
@ -87,8 +94,15 @@ system does not have this utility already.
.tag)
.Pp
First of all, configure your rbootd to handle boot requests from the
client. NOTE: NetBSD's `rbootd' is slightly different from HP-UX's.
To configure NetBSD's `rbootd', create a file called `/etc/rbootd.conf'
client.
.(Note
NetBSD's
.Cm rbootd
is slightly different from HP-UX's.
To configure NetBSD's
.Cm rbootd ,
create a file called
.Pa /etc/rbootd.conf
and place in it an entry like the following:
.
.Dl 08:00:09:04:AA:33 SYS_INST # thunder-egg
@ -96,15 +110,17 @@ and place in it an entry like the following:
The first column is the ethernet address of the client's network interface.
The second column is the program to send to the client, and anything after
the `#' is a comment. Once you have rbootd running, copy the SYS_INST
program to the /usr/mdec/rbootd directory on your server. If this
program to the
.Pa /usr/mdec/rbootd
directory on your server. If this
directory doesn't exist already, you will need to create it.
.Note)
.Pp
For information on configuring rbootd under HP-UX, see the rbootd(1M)
For information on configuring rbootd under HP-UX, see the
.Xr rbootd 1M
manual page on your server system.
.Pp
Once `rbootd' is configured and running, you will be ready to continue.
.tag)
.
.
.Pp
Make sure that the miniroot filesystem image has been un-gzipped, and
@ -120,11 +136,11 @@ load and prompt you for a command.
If this is a new NetBSD installation, you will need to place a disklabel
on the disk.
.Dl sys_inst\*> disklabel
.(tag Em Note:
.(Note
It may be worth selecting the `zap' option initially to ensure that
the disklabel area is clear. This may be especially important if an
HP-UX boot block had been previously installed on the disk.
.tag)
.Note)
.Pp
Select the `edit' option, and answer the questions about your disk.
There may be several questions which you may not be sure of the answers
@ -142,7 +158,7 @@ to. Listed below are guidelines for SCSI and HP-IB disks:
.El
.Pp
Next, you will be asked to fill out the partition map. You must provide
responses for all 8 partitions. Remember, you must allocate at least 6M
responses for all 8 partitions. Remember, you must allocate at least 6 MB
for the `b' partition, or else the miniroot will not fit. Set the size and
offset of any unused partition to 0. Note that sizes and offsets are
expressed in `n sectors', assuming 512 byte sectors. Care should be taken
@ -150,12 +166,12 @@ to ensure that partitions begin and end on cylinder boundaries (i.e. size
and offset is an even multiple of the number of sectors per cylinder).
While this is not technically necessary, it is generally encouraged.
.Pp
.(tag Em Note:
.(Note
When setting the partition type of the `b' partition, make sure to
specify it as an `ffs' partition so that the miniroot can be mounted (even
if this will be a swap partition). You will be given a chance to clean
this up later in the installation process.
.tag)
.Note)
.Pp
Once you have edited the label, select the `show' option to verify that
it is correct. If so, select `write' and `done'. Otherwise, you may

30
distrib/notes/hp300/upgrade
View File

@ -1,6 +1,6 @@
.\" $NetBSD: upgrade,v 1.9 2000/05/13 08:13:55 lukem Exp $
.\" $NetBSD: upgrade,v 1.10 2000/10/10 12:55:18 lukem Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -31,13 +31,14 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
It is possible to easily upgrade your existing NetBSD/\*m system
It is possible to easily upgrade your existing
.Nx*M
system
using the upgrade program in the miniroot. If you wish to upgrade
your system by this method, simply select the `upgrade' option once
the miniroot has booted. The upgrade program with then guide you
through the procedure. The upgrade program will:
.Bl -bullet
.It
.(enum
Enable the network based on your system's current
network configuration.
.It
@ -52,20 +53,21 @@ resulting file.
Make new device nodes in your root filesystem.
.It
Don't forget to extract the `kern' set from the distribution.
NOTE: the existing kernel WILL NOT be backed up; doing
.(Note
The existing kernel WILL NOT be backed up; doing
so would be pointless, since older kernels may not be
capable of running NetBSD _VER executables.
.Note)
.It
Install a new boot block.
.It
Check your filesystems for integrity.
.El
.enum)
.Pp
While using the miniroot's upgrade program is the preferred method
of upgrading your system, it is possible to upgrade your system
manually. To do this, follow the following procedure:
.Bl -bullet
.It
.(enum
Place _at least_ the `base' binary set in a filesystem
accessible to the target machine. A local filesystem
is preferred, since the NFS subsystem in the NetBSD _VER
@ -93,10 +95,10 @@ are actually stored on disk.
.It
Make sure you are in the root filesystem and extract
the `base' binary set:
.Bd -literal -offset indent
.(disp
cd /
pax -zrvpe -f /path/to/base.tgz
.Ed
.disp)
.It
Install a new boot block:
.D1 Ic cd /usr/mdec
@ -111,8 +113,10 @@ wish to extract additional sets at a later time.
To extract these sets, use the following commands:
.D1 cd /
.D1 pax -zrvpe -f Ar path_to_set
.El
NOTE: you SHOULD NOT extract the
.enum)
.(Note
You SHOULD NOT extract the
.Sy etc
set if upgrading. Instead, you should extract that set into another
area and carefully merge the changes by hand.
.Note)

3
distrib/notes/hp300/whatis
View File

@ -1,3 +1,4 @@
.\" $NetBSD: whatis,v 1.5 1999/01/13 07:30:05 ross Exp $
.\" $NetBSD: whatis,v 1.6 2000/10/10 12:55:18 lukem Exp $
.
This is the third public release of NetBSD for the HP 9000/300 series of
computers.

114
distrib/notes/hp300/xfer
View File

@ -1,21 +1,68 @@
.\" $NetBSD: xfer,v 1.8 1999/01/13 07:30:05 ross Exp $
.\" $NetBSD: xfer,v 1.9 2000/10/10 12:55:18 lukem Exp $
.
Installation is supported from several media types, including:
.Pp
.Bl -bullet -compact
.It
Tape
.It
CD-ROM
.(bullet -compact
FTP
.It
NFS
.It
FTP
.El
Tape
.bullet)
.Pp
The steps necessary to prepare the distribution sets
for installation depend on which method of installation
you choose. The various methods are explained below.
.Ss2 To prepare for installing via a tape:
.
.(tag Tape
.
.It Em FTP
It is possible, using the `install' and `upgrade'
programs in the miniroot, to extract the binary sets
directly onto disk from an FTP server. This is by far
the easiest installation method, as you may specify to
have all sets extracted at once, providing that they
are located in the same directory on the server.
.Pp
All that is required in this case is that you have
network access to an FTP server. This may be your
account on another system, or may even be ftp.netbsd.org
itself. If you wish to use ftp.netbsd.org as your FTP
file server, you may want to keep the following information
handy:
.(disp
IP Address: ftp.netbsd.org
Login: anonymous
Password: \*<your e-mail address\*>
Server path: /pub/NetBSD/NetBSD-_VER/hp300/binary/sets
.disp)
.(Note
If you're not using a nameserver during installation,
you might find 204.152.184.75 handy; it's the IP address of
ftp.netbsd.org as of October, 5, 2000.
.Note)
.
.It Em NFS
SYS_INST currently requires an NFS server from which to
copy the miniroot.
.(bullet
This filesystem must be exported with root permissions,
but may be exported read-only.
.It
The miniroot image _must_ reside in the `root' of the
mounted filesystem. For example, if the client system
mounts `server:/u', then the miniroot image must reside
in /u on the server. This is due to limitations in the
file lookup code used in SYS_INST, and may be fixed in
a future release.
.It
If you also wish to install the binary sets from the
NFS server, place them in a properly exported filesystem
on the server. Note that these files do not suffer from
the same placement restrictions as the miniroot.
.bullet)
.
.It Em Tape
If you wish to load SYS_INST from tape, it must
appear on the tape before any other files. To copy
this onto tape, use a command like the following:
@ -31,11 +78,12 @@ If you wish to extract binary sets onto your disk from
tape, you must first place them on the tape. The easiest
way to do this is with the dd(1) command. Make sure you
use a `no-rewind-on-close' tape device. For example:
.Bd -literal -offset indent
.(disp
for file in base.tgz etc.tgz; do
dd if=${file} of=/dev/nrst0
done
.Ed
.disp)
.Pp
Note that depending on your tape drive, you may need to
explicitly set the EOF marker at the end of each file.
It may also be necessary to use the `conv=osync' argument
@ -44,46 +92,4 @@ to
Note that this argument is incompatible with the
`bs=' argument. Consult the tape-related manual pages on the
system where the tapes are created for more details.
.Ss2 To prepare for installing via NFS:
SYS_INST currently requires an NFS server from which to
copy the miniroot.
.Bl -bullet
.It
This filesystem must be exported with root permissions,
but may be exported read-only.
.It
The miniroot image _must_ reside in the `root' of the
mounted filesystem. For example, if the client system
mounts `server:/u', then the miniroot image must reside
in /u on the server. This is due to limitations in the
file lookup code used in SYS_INST, and may be fixed in
a future release.
.It
If you also wish to install the binary sets from the
NFS server, place them in a properly exported filesystem
on the server. Note that these files do not suffer from
the same placement restrictions as the miniroot.
.El
.Ss2 To prepare for installing via FTP:
It is possible, using the `install' and `upgrade'
programs in the miniroot, to extract the binary sets
directly onto disk from an FTP server. This is by far
the easiest installation method, as you may specify to
have all sets extracted at once, providing that they
are located in the same directory on the server.
.Pp
All that is required in this case is that you have
network access to an FTP server. This may be your
account on another system, or may even be ftp.NetBSD.ORG
itself. If you wish to use ftp.NetBSD.ORG as your FTP
file server, you may want to keep the following information
handy:
.Bd -ragged
IP Address: ftp.NetBSD.ORG
Login: anonymous
Password: \*<your e-mail address\*>
Server path: /pub/NetBSD/NetBSD-_VER/hp300/binary/sets
.Ed
Note: if you're not using a nameserver during installation,
you might find 204.152.184.75 handy; it's the IP address of
ftp.NetBSD.ORG as of December, 29, 1997.
.tag)

260
distrib/notes/hpcmips/hardware
View File

@ -1,101 +1,165 @@
.\" $NetBSD: hardware,v 1.8 2000/07/07 01:39:26 imp Exp $
.\" $NetBSD: hardware,v 1.9 2000/10/10 12:55:18 lukem Exp $
.
A H/PC machine contains a keyboard and a touch screen and
generally has 8MB or more of RAM. The port supports the HPC
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.
The following WindowsCE hardware is supported:
.de section
. El
. Pp
. It Em \\$*
. br
. Bl -bullet -compact
..
.de item
. It
\\$*
..
.Bl -tag -width Disks
. It Em supported machines:
. br
. Bl -bullet -compact
. section CASIO
. item CASSIOPEIA for DoCoMo
. item CASSIOPEIA E-55
. section Compaq
. item C Series 2010c
. item C Series 810
. section Everex
. item FreeStyle A-10 (optional memory card recommended)
. item FreeStyle A-15
. item FreeStyle A-20
. section Fujitsu
. item INTERTOP CX300
. section NEC
. item MobileGear MC-CS12
. item MobileGear MC-CS13
. item MobileGearII MC-R300
. item MobileGearII MC-R320
. item MobileGearII MC-R330
. item MobileGearII for DoCoMo (TypeI/II)
. item MobileGearII MC/R430
. item MobileGearII MC-R500
. item MobileGearII MC-R510
. item MobileGearII MC-R520
. item MobileGearII MC/R530
. item MobileGearII MC-R700
. item MobileGearII MC/R730
. item MobilePro 750C
. item MobilePro 770
. item MobilePro 780
. item MobilePro 800
. item MobilePro 880
. section IBM
. item WorkPad z50
. section Sharp
. item mobilon TRIPAD PV-6000
. item mobilon HC-4100
. item Telios HC-AJ1
. item Telios HC-AJ2
. section Vadem
. item Clio C-1000
. item Clio C-1050
. El
. It Em CPUs:
. br
. Bl -bullet -compact
. item Vr4102-based:
. item Vr4111-based:
. item Vr4121-based:
. item Vr4181-based:
. item TX3912-based: TX3912 machines are not supported with installation kernel. use special kernel for TX3912.
. item TX3922-based: TX3922 machines are not supported with installation kernel. use special kernel for TX3922
. section RAM requirements
. item 8MB of RAM is required to run NetBSD/hpcmips. 4MB is insufficient for most purposes.
. section console device
. item built-in LCD screen
. item built-in keyboard
. item serial port (with kernel option 'h')
. section storage device
. item Flash ATA card, CF card (wd)
. item SCSI disk (sd)
. item Adaptec APA-1460[Slim SCSI](aic)
. section Network interfaces:
. item 3Com 3c589 and 3c562 Ethernet (ep)
. item MB8696x based Ethernet (mbe)
. item NE2000-compatible Ethernet (ne)
. item Megahertz Ethernet (sm)
. section Displays:
. item LCD Display
. section Input devices:
. item Keyboard.
. item TouchPad.
. section Miscellaneous:
. item Battery-backed real-time clock.
. El
.El
.Pp
.Bl -tag -width (***)
.El
.
.Ss2 Supported WindowsCE machines
.(bullet -offset indent
CASIO
.(bullet -compact
CASSIOPEIA for DoCoMo
.It
CASSIOPEIA E-55
.bullet)
.It
Compaq
.(bullet -compact
C Series 2010c
.It
C Series 810
.bullet)
.It
Everex
.(bullet -compact
FreeStyle A-10 (optional memory card recommended)
.It
FreeStyle A-15
.It
FreeStyle A-20
.bullet)
.It
Fujitsu
.(bullet -compact
INTERTOP CX300
.bullet)
.It
NEC
.(bullet -compact
MobileGear MC-CS12
.It
MobileGear MC-CS13
.It
MobileGearII MC-R300
.It
MobileGearII MC-R320
.It
MobileGearII MC-R330
.It
MobileGearII for DoCoMo (TypeI/II)
.It
MobileGearII MC/R430
.It
MobileGearII MC-R500
.It
MobileGearII MC-R510
.It
MobileGearII MC-R520
.It
MobileGearII MC/R530
.It
MobileGearII MC-R700
.It
MobileGearII MC/R730
.It
MobilePro 750C
.It
MobilePro 770
.It
MobilePro 780
.It
MobilePro 800
.It
MobilePro 880
.bullet)
.It
IBM
.(bullet -compact
WorkPad z50
.bullet)
.It
Sharp
.(bullet -compact
mobilon TRIPAD PV-6000
.It
mobilon HC-4100
.It
Telios HC-AJ1
.It
Telios HC-AJ2
.bullet)
.It
Vadem
.(bullet -compact
Clio C-1000
.It
C-1050
.bullet)
.bullet)
.
.Ss2 Supported WindowsCE devices
.(bullet -offset indent
CPUs
.(bullet -compact
Vr4102-based
.It
Vr4111-based
.It
Vr4121-based
.It
Vr4181-based
.It
TX3912-based: TX3912 machines are not supported with installation kernel. use special kernel for TX3912.
.It
TX3922-based: TX3922 machines are not supported with installation kernel. use special kernel for TX3922
.bullet)
.It
RAM requirements
.(bullet -compact
8 MB of RAM is required to run
.Nx*M .
4 MB is insufficient for most purposes.
.bullet)
.It
Console devices
.(bullet -compact
built-in LCD screen
.It
built-in keyboard
.It
serial port (with kernel option 'h')
.bullet)
.It
Storage devices
.(bullet -compact
Flash ATA card, CF card (wd)
.It
SCSI disk (sd)
.It
Adaptec APA-1460[Slim SCSI](aic)
.bullet)
.It
Network interfaces
.(bullet -compact
3Com 3c589 and 3c562 Ethernet (ep)
.It
MB8696x based Ethernet (mbe)
.It
NE2000-compatible Ethernet (ne)
.It
Megahertz Ethernet (sm)
.bullet)
.It
Input devices
.(bullet -compact
Keyboard.
.It
TouchPad.
.bullet)
.It
Miscellaneous
.(bullet -compact
Battery-backed real-time clock.
.bullet)
.bullet)

16
distrib/notes/hpcmips/install
View File

@ -1,12 +1,16 @@
.\" $NetBSD: install,v 1.5 2000/07/07 01:39:27 imp Exp $
.\" $NetBSD: install,v 1.6 2000/10/10 12:55:18 lukem Exp $
.
boot with `pbsdboot.exe' and `netbsd' in `installation' directory.
`sysinst' will automatically start.
The NetBSD/hpcmips kernel and system install consume about 6MB of memory.
Boot with `pbsdboot.exe' and `netbsd' in `installation' directory.
.Ic sysinst
will automatically start.
.Pp
The
.Nx*M
kernel and system install consume about 6 MB of memory.
Please configure the Windows CE memory setting to allow this amount of
memory to be used. If you failed pbsdboot.exe with "cannot allocate heap"
error, configure more RAM for memory and less for disk with the dialog at
[Setting]->[ControlPanel]->[System]->[Memory] under Windows CE.
.Pp
.
.so ../common/sysinst

13
distrib/notes/hpcmips/legal
View File

@ -1,11 +1,7 @@
.\" $NetBSD: legal,v 1.1 2000/02/20 15:45:34 jun Exp $
.Pp
This product includes software developed by The NetBSD Foundation, Inc.
.Pp
.\" $NetBSD: legal,v 1.2 2000/10/10 12:55:18 lukem Exp $
.
This product includes software developed by Frank van der Linden.
.Pp
This product includes software developed by Luke Mewburn.
.Pp
This product includes software developed by Darrin Jewell.
.Pp
This product includes software developed by Anders Magnusson.
@ -16,10 +12,6 @@ This product includes software developed by Jason Thorpe.
.Pp
This product includes software developed by Izumi Tsutsui.
.Pp
This product includes software developed by Frank van der Linden.
.Pp
This product includes software developed by Chris G. Demetriou.
.Pp
This product includes software developed by Andy Doran.
.Pp
This product includes software developed by Matthias Drochner.
@ -37,4 +29,3 @@ This product includes software developed by Takao Shinohara.
This product includes software developed by UCHIYAMA Yasushi.
.Pp
This product includes software developed by Shuiciro URATA.
.Pp

7
distrib/notes/hpcmips/prep
View File

@ -1,9 +1,10 @@
.\" $NetBSD: prep,v 1.2 2000/07/07 01:39:27 imp Exp $
.\" $NetBSD: prep,v 1.3 2000/10/10 12:55:18 lukem Exp $
.
First and foremost, before beginning the installation process,
.Em make sure you have a reliable backup
of any data on your Windows CE memory and settings that you
wish to keep.
Sadly, there is no freely available program to accomplish this task,
so you must use ActiveSync or another commercially available program to
backup your Windows CE machine before installing NetBSD/hpcmips.
backup your Windows CE machine before installing
.Nx*M .

2
distrib/notes/hpcmips/upgrade
View File

@ -1,3 +1,3 @@
.\" $NetBSD: upgrade,v 1.1 2000/02/20 15:45:35 jun Exp $
.\" $NetBSD: upgrade,v 1.2 2000/10/10 12:55:18 lukem Exp $
.
.so ../common/upgrade

16
distrib/notes/hpcmips/whatis
View File

@ -1,13 +1,17 @@
.\" $NetBSD: whatis,v 1.2 2000/07/07 01:39:27 imp Exp $
.\" This is the first public release of NetBSD/hpcmips.
This is the snapshot release of NetBSD/hpcmips.
.\" $NetBSD: whatis,v 1.3 2000/10/10 12:55:18 lukem Exp $
.
This is the first public release of
.Nx*M .
.Pp
NetBSD/hpcmips brings the
.Nx*M
brings the
NetBSD operating system to
MIPS based Windows CE PDA machines. Currently, the
MIPS based Windows CE PDA machines. Currently, the
Vr4102, Vr4111, Vr4121, Vr4181, TX3912, and TX3922 processors are supported.
.Pp
The port name "hpcmips" comes from the name for some of the hardware
that NetBSD/hpcmips runs on: MIPS based systems in Microsoft's
that
.Nx*M
runs on: MIPS based systems in Microsoft's
H/PC (Handheld PC) form factor.
The palm sized units are also supported, but lack an input method.

2
distrib/notes/hpcmips/xfer
View File

@ -1,3 +1,3 @@
.\" $NetBSD: xfer,v 1.1 2000/02/20 15:45:36 jun Exp $
.\" $NetBSD: xfer,v 1.2 2000/10/10 12:55:18 lukem Exp $
.
.so ../common/xfer

771
distrib/notes/i386/hardware
View File

@ -1,270 +1,500 @@
.\" $NetBSD: hardware,v 1.77 2000/10/04 00:31:49 lukem Exp $
.\"
.\" $NetBSD: hardware,v 1.78 2000/10/10 12:55:18 lukem Exp $
.
.Nx \*V
runs on ISA (AT-Bus), EISA, PCI, and VL-bus systems
with 386-family processors, with or without math coprocessors. Support
for MCA systems (such as some IBM PS/2 systems) is present, but
still very experimental and needs special setup. The
minimal configuration is said to require 4M of RAM and 50M of disk
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,
requires at least 65M without counting space needed for swap space,
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.
(4M of RAM will actually allow you to run X and/or compile, but it
won't be speedy. Note that until you have around 16M of RAM, getting
(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
more RAM is more important than getting a faster CPU.)
Supported devices include:
.Bd -literal
Floppy controllers.
MFM, ESDI, IDE, and RLL hard disk controllers.
There is complete support (including IDE DMA or Ultra-
DMA) for the following PCI controllers:
- Acer labs M5229 IDE Controller
- CMD Tech PCI0643, 0646, 0648 and 0649 IDE Controllers
- Contaq Microsystems/Cypress CY82C693 IDE Controller
- HighPoint HPT366 and HPT370 (in Ultra/66 mode only)
- Intel PIIX, PIIX3 and PIIX4 IDE Controllers
- Intel 82801 (ICH/ICH0) IDE Controllers
- Promise PDC20246 (Ultra/33), PDC20262 (Ultra/66) and
Ultra/100 (in Ultra/66 mode only)
- Silicon Integrated System 5597/5598 IDE controller
- VIA Technologies VT82C586 and VT82C586A IDE Controllers
Most of these controllers are only available in
multifunction PCI chips.
Other PCI IDE controllers are supported, but
performances may not be optimal.
ISA, ISA plug and play and PCMCIA IDE controllers
are supported as well.
SCSI host adapters
Adaptec AHA-154xA, -B, -C, and -CF
Adaptec AHA-1640 cards (MCA variant of AHA-1540) [m]
Adaptec AHA-174x
Adaptec AIC-6260 and AIC-6360 based boards, including
the Adaptec AHA-152x, Adaptec APA-1460 (PCMCIA),
and the SoundBlaster SCSI host adapter. (Note
that you cannot boot from these boards if they
do not have a boot ROM; only the AHA-152x and
motherboards using this chip are likely to be
bootable, consequently.)
Adaptec AHA-2910, 2915, 2920, and 2930C adapters.
Adaptec AHA-2x4x[U][2][W] cards and onboard PCI designs
using the AIC-7770, AIC-7850, AIC-7860, AIC-7870,
AIC-7880 and AIC-789x chipsets.
Adaptec AHA-394x[U][W] cards [b]
Adaptec AHA-3950U2 cards
Adaptec AHA-3960, 19160 and 29160 Ultra-160 adapters
AdvanSys ABP-9x0[U][A] cards
AdvanSys ABP-940UW[68], ABP-970UW[68], ASB3940UW-00 cards
AMD PCscsi-PCI (Am53c974) based SCSI adapters, including
Tekram DC-390
BusLogic 54x (Adaptec AHA-154x clones)
BusLogic 445, 74x, 9xx (But not the new "FlashPoint" series
of BusLogic SCSI adapters)
DPT SCSI RAID boards (ISA [*], EISA and PCI):
SmartCache III
SmartCache IV
SmartRAID III
SmartRAID IV
Qlogic ISP [12]0x0 SCSI/FibreChannel boards
Seagate/Future Domain ISA SCSI adapter cards, including
ST01/02
Future Domain TMC-885
Future Domain TMC-950
Symbios Logic (NCR) 53C8xx-based PCI SCSI host adapters:
Acculogic PCIpport
ASUS SC-200 (requires NCR BIOS on motherboard to
boot from disks)
ASUS SC-875
ASUS SP3[G] motherboard onboard SCSI
DEC Celebris XL/590 onboard SCSI
Diamond FirePort 40
Lomas Data SCSI adapters
NCR/SYM 8125 (and its many clones; be careful, some
of these cards have a jumper to set
the PCI interrupt; leave it on INT A!)
Promise DC540 (a particularly common OEM model of
the SYM 8125)
Tekram DC-390U/F
Tyan Yorktown
Symbios Logic (NCR) 5380/53C400-based ISA SCSI host adapters [*]
Ultrastor 14f, 34f, and (possibly) 24f
Western Digital WD7000 SCSI and TMC-7000 host adapters
(ISA cards only)
MDA, CGA, VGA, SVGA, and HGC Display Adapters. (Note that not
all of the display adapters NetBSD/i386 can work with
are supported by X. See the XFree86 FAQ for more
information.) [m]
Serial ports:
8250/16450-based ports [m]
16550/16650/16750-based ports [m]
AST-style 4-port serial cards [*]
BOCA 8-port serial cards [*]
BOCA 6-port (ioat) serial cards [*]
IBM PC-RT 4-port serial cards [*]
Single-port Hayes ESP serial cards [*]
Cyclades Cyclom-Y serial cards [*] [+]
Addonics FlexPort 8S 8-port serial cards [*]
PCI universal communication cards
Parallel ports. [*] [+] [m]
Ethernet adapters:
AMD LANCE and PCnet-based ISA Ethernet adapters [*], including:
Novell NE1500T
Novell NE2100
Kingston 21xx
Digital EtherWORKS II ISA adapters (DE200/DE201/DE202)
AMD PCnet-based PCI Ethernet adapters, including:
Addtron AE-350
BOCALANcard/PCI
SVEC FD0455
X/Lan Add-On Adapter
IBM #13H9237 PCI Ethernet Adapter
AT\*&T StarLAN 10, EN100, and StarLAN Fiber
3COM 3c501
3COM 3c503
3COM 3c505 [*]
3COM 3c507
3COM 3c509, 3c579, 3c589, and 3c59X
3COM 3c90X (including 3c905B)
Digital DC21x4x-based PCI Ethernet adapters, including:
ASUS PCI-DEC100TX+
Cogent EM1X0, EM960 (a.k.a. Adaptec ANA-69XX)
Cogent EM964 [b]
Cogent EM4XX [b]
Compex Readylink PCI
DANPEX EN-9400P3
Digital Celebris GL, GLST on-board ethernet
Digital (DEC) PCI Ethernet/Fast Ethernet adapters (all)
DLINK DFE500-TX
JCIS Condor JC1260
Linksys PCI Fast Ethernet
SMC EtherPower 10, 10/100 (PCI only!)
SMC EtherPower^2 [b]
SVEC PN0455
SVEC FD1000-TP
Znyx ZX34X
Digital EtherWORKS III ISA adapters (DE203/DE204/DE205) [*]
Digital DEPCM-BA (PCMCIA) and DE305 (ISA) NE2000-compat. cards
BICC Isolan [* and not recently tested]
Efficient Networks EN-155 and Adaptec AIC-590x ATM interfaces
Essential Communications Hippi (800Mbit/s)
Fujitsu MB86960A/MB86965A based cards:
Fujitsu FMV-180 series
Allied-Telesis AT1700 series
Allied-Telesis RE2000 series
Intel EtherExpress 16
Intel EtherExpress PRO/10
Intel EtherExpress 100 Fast Ethernet adapters
Novell NE1000, NE2000 (ISA, PCI, PCMCIA, ISA PnP)
RealTek 8129/8139 based boards
SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards
SMC/WD 8216 (the SMC "Elite16 Ultra" ISA boards)
SMC 91C9x-based boards (ISA and PCMCIA)
SMC EPIC/100 Fast Ethernet boards:
SMC Etherpower-II
Texas Instruments ThunderLAN based ethernet boards:
Compaq Netelligent 10/100 TX
Compaq ProLiant Integrated Netelligent 10/100 TX
Compaq Netelligent 10 T (untested)
Compaq Integrated NetFlex 3/P
Compaq NetFlex 3/P in baseboard variant (the PCI
(variant doesn't use the same chip !).
Compaq Dual Port Netelligent 10/100 TX
Compaq Deskpro 4000 5233MMX (untested)
Texas Instruments TravelMate 5000 series laptop
docking station Ethernet board
VIA VT3043(Rhine) and VT86C100A(Rhine-II) based ethernet boards:
D-Link DFE530TX
FDDI adapters:
Digital DEFPA PCI FDDI adapters [*] [+]
Digital DEFEA EISA FDDI adapters [*] [+]
Token-Ring adapters:
IBM Token-Ring Network PC Adapter [+]
IBM Token-Ring Network PC Adapter II [+]
IBM Token-Ring Network Adapter/A [+]
IBM Token-Ring Network 16/4 Adapter [+]
IBM Token-Ring Network 16/4 Adapter/A [+] [m]
IBM 16/4 ISA Adapter [+]
IBM Auto 16/4 Token-Ring ISA Adapter [+]
3COM 3C619 TokenLink [+]
3COM 3C319 TokenLink Velocity [+]
Wireless network adapters:
AT\*&T/Lucent WaveLan IEEE (802.11) PCMCIA cards
BayStack 650 802.11FH PCMIA cards [*] [+]
NetWave AirSurfer PCMCIA cards [*] [+]
High Speed Serial:
LAN Media Corporation SSI/LMC10000 (up to 10Mbps) [*] [+]
LAN Media Corporation HSSI/LMC5200 [*] [+]
LAN Media Corporation DS3/LMC5245 [*] [+]
Tape drives:
Most SCSI tape drives
QIC-02 and QIC-36 format (Archive- and Wangtek-
compatible) tape drives [*] [+]
CD-ROM drives:
Non-IDE Mitsumi CD-ROM drives [*] [+]
[Note: The Mitsumi driver device probe is known
to cause trouble with several devices!]
Most SCSI CD-ROM drives
Most ATAPI CD-ROM drives.
[ Note: Some low-priced IDE CDROM drives are known
for being not or not fully ATAPI compliant, and thus
requires some hack (generally an entry to a quirk
table) to work with NetBSD.]
Mice:
"Logitech"-style bus mice [*] [+]
"Microsoft"-style bus mice [*] [+]
"PS/2"-style mice [*] [+] [m]
Serial mice (no kernel support necessary)
Sound Cards:
SoundBlaster, SoundBlaster Pro, SoundBlaster 16 [*] [+]
Gravis Ultrasound and Ultrasound Max [*] [+]
Windows Sound System [*] [+]
[The following drivers are not extensively tested]
Personal Sound System [*] [+]
ProAudio Spectrum [*] [+]
Gravis Ultrasound Plug\*&Play [*] [+]
Ensoniq AudioPCI [*] [+]
Yamaha OPL3-SA3 [*] [+]
Aria based sound cards [*]
S3 SonicVibes [*] [+]
ESS Technology ES1777/1868/1869/1887/1888/888 and
Solo-1 ES1938/1946 audio [*] [+]
Game Ports (Joysticks). [*] [+]
Miscellaneous:
Advanced power management (APM) [*]
Universal Serial Bus (USB):
UHCI host controllers [*] [+]
OHCI host controllers [*] [+]
Hubs [*] [+]
Keyboards using the boot protocol [*] [+]
Mice [*] [+]
Printers [*] [+]
Modems using Abstract Control Model [*] [+]
Generic support for HID devices [*] [+]
Ethernet adapters [*] [+]
PCMCIA Controllers:
ISA, PCI, and ISA Plug\*&Play attachments for:
Intel 82365 PCIC, rev 0 and rev 1
Cirrus PD6710
Cirrus PD672X
[ Note: will work with most laptops as well as
with ISA cards which provide PCMCIA
slots for desktops ]
RAID Controllers:
Compaq Integrated Array (PCI) [b]
Compaq IAES (EISA)
Compaq IDA, IDA-2 (EISA)
Compaq Smart Array 221, 3100ES, 3200, 4200, 4250ES (PCI) [b]
Compaq Smart Array 431, RAID LC2 [b]
Compaq SMART 2, 2/E (EISA)
Compaq SMART 2/E, 2/P, 2DH, 2SL (PCI) [b]
.Ed
.
.Ss2 Supported devices
.(bullet -offset indent
Floppy controllers.
.It
MFM, ESDI, IDE, and RLL hard disk controllers.
.br
There is complete support (including IDE DMA or Ultra-DMA) for the following
PCI controllers
.(bullet -compact
Acer labs M5229 IDE Controller
.It
CMD Tech PCI0643, 0646, 0648 and 0649 IDE Controllers
.It
Contaq Microsystems/Cypress CY82C693 IDE Controller
.It
HighPoint HPT366 and HPT370 (in Ultra/66 mode only)
.It
Intel PIIX, PIIX3 and PIIX4 IDE Controllers
.It
Intel 82801 (ICH/ICH0) IDE Controllers
.It
Promise PDC20246 (Ultra/33), PDC20262 (Ultra/66) and Ultra/100
(in Ultra/66 mode only)
.It
Silicon Integrated System 5597/5598 IDE controller
.It
VIA Technologies VT82C586 and VT82C586A IDE Controllers
.bullet)
.br
Most of these controllers are only available in multifunction PCI chips.
Other PCI IDE controllers are supported, but performance may not be optimal.
ISA, ISA plug and play and PCMCIA IDE controllers are supported as well.
.It
SCSI host adapters
.(bullet -compact
Adaptec AHA-154xA, -B, -C, and -CF
.It
Adaptec AHA-1640 cards (MCA variant of AHA-1540) [m]
.It
Adaptec AHA-174x
.It
Adaptec AIC-6260 and AIC-6360 based boards, including the Adaptec AHA-152x,
Adaptec APA-1460 (PCMCIA), and the SoundBlaster SCSI host adapter.
.(Note
You cannot boot from these boards if they do not have a boot ROM;
consequently only the AHA-152x and motherboards using this chip are
likely to be bootable.
.Note)
.Pp
.It
Adaptec AHA-2910, 2915, 2920, and 2930C adapters.
.It
Adaptec AHA-2x4x[U][2][W] cards and onboard PCI designs using the AIC-7770,
AIC-7850, AIC-7860, AIC-7870, AIC-7880 and AIC-789x chipsets.
.It
Adaptec AHA-394x[U][W] cards [b]
.It
Adaptec AHA-3950U2 cards
.It
Adaptec AHA-3960, 19160 and 29160 Ultra-160 adapters
.It
AdvanSys ABP-9x0[U][A] cards
.It
AdvanSys ABP-940UW[68], ABP-970UW[68], ASB3940UW-00 cards
.It
AMD PCscsi-PCI (Am53c974) based SCSI adapters, including Tekram DC-390
.It
BusLogic 54x (Adaptec AHA-154x clones)
.It
BusLogic 445, 74x, 9xx (But not the new "FlashPoint" series of BusLogic SCSI
adapters)
.It
DPT SCSI RAID boards (ISA [*], EISA and PCI)
.(bullet -compact
SmartCache III
.It
SmartCache IV
.It
SmartRAID III
.It
SmartRAID IV
.bullet)
.It
Qlogic ISP [12]0x0 SCSI/FibreChannel boards
.It
Seagate/Future Domain ISA SCSI adapter cards
.(bullet -compact
ST01/02
.It
Future Domain TMC-885
.It
Future Domain TMC-950
.bullet)
.It
Symbios Logic (NCR) 53C8xx-based PCI SCSI host adapters
.(bullet -compact
Acculogic PCIpport
.It
ASUS SC-200 (requires NCR BIOS on motherboard to boot from disks)
.It
ASUS SC-875
.It
ASUS SP3[G] motherboard onboard SCSI
.It
DEC Celebris XL/590 onboard SCSI
.It
Diamond FirePort 40
.It
Lomas Data SCSI adapters
.It
NCR/SYM 8125 (and its many clones; be careful, some of these cards have a
jumper to set the PCI interrupt; leave it on INT A!)
.It
Promise DC540 (a particularly common OEM model of the SYM 8125)
.It
Tekram DC-390U/F
.It
Tyan Yorktown
.bullet)
.It
Symbios Logic (NCR) 5380/53C400-based ISA SCSI host adapters [*]
.It
Ultrastor 14f, 34f, and (possibly) 24f
.It
Western Digital WD7000 SCSI and TMC-7000 host adapters (ISA cards only)
.bullet)
.It
MDA, CGA, VGA, SVGA, and HGC Display Adapters.
.(Note
Not all of the display adapters
.Nx*M
can work with are supported by X.
See the XFree86 FAQ for more information. [m]
.Note)
.Pp
.It
Serial ports
.(bullet -compact
8250/16450-based ports [m]
.It
16550/16650/16750-based ports [m]
.It
AST-style 4-port serial cards [*]
.It
BOCA 8-port serial cards [*]
.It
BOCA 6-port (ioat) serial cards [*]
.It
IBM PC-RT 4-port serial cards [*]
.It
Single-port Hayes ESP serial cards [*]
.It
Cyclades Cyclom-Y serial cards [*] [+]
.It
Addonics FlexPort 8S 8-port serial cards [*]
.It
PCI universal communication cards
.bullet)
.It
Parallel ports. [*] [+] [m]
.It
Ethernet adapters
.(bullet -compact
AMD LANCE and PCnet-based ISA Ethernet adapters [*]
.(bullet -compact
Novell NE1500T
.It
Novell NE2100
.It
Kingston 21xx
.It
Digital EtherWORKS II ISA adapters (DE200/DE201/DE202)
.bullet)
.It
AMD PCnet-based PCI Ethernet adapters
.(bullet -compact
Addtron AE-350
.It
BOCALANcard/PCI
.It
SVEC FD0455
.It
X/Lan Add-On Adapter
.It
IBM #13H9237 PCI Ethernet Adapter
.bullet)
.It
AT\*&T StarLAN 10, EN100, and StarLAN Fiber
.It
3COM 3c501
.It
3COM 3c503
.It
3COM 3c505 [*]
.It
3COM 3c507
.It
3COM 3c509, 3c579, 3c589, and 3c59X
.It
3COM 3c90X (including 3c905B)
.It
Digital DC21x4x-based PCI Ethernet adapters
.(bullet -compact
ASUS PCI-DEC100TX+
.It
Cogent EM1X0, EM960 (a.k.a. Adaptec ANA-69XX)
.It
Cogent EM964 [b]
.It
Cogent EM4XX [b]
.It
Compex Readylink PCI
.It
DANPEX EN-9400P3
.It
Digital Celebris GL, GLST on-board ethernet
.It
Digital (DEC) PCI Ethernet/Fast Ethernet adapters (all)
.It
DLINK DFE500-TX
.It
JCIS Condor JC1260
.It
Linksys PCI Fast Ethernet
.It
SMC EtherPower 10, 10/100 (PCI only!)
.It
SMC EtherPower^2 [b]
.It
SVEC PN0455
.It
SVEC FD1000-TP
.It
Znyx ZX34X
.bullet)
.It
Digital EtherWORKS III ISA adapters (DE203/DE204/DE205) [*]
.It
Digital DEPCM-BA (PCMCIA) and DE305 (ISA) NE2000-compat. cards
.It
BICC Isolan [* and not recently tested]
.It
Efficient Networks EN-155 and Adaptec AIC-590x ATM interfaces
.It
Essential Communications Hippi (800 Mbit/s)
.It
Fujitsu MB86960A/MB86965A based cards
.(bullet -compact
Fujitsu FMV-180 series
.It
Allied-Telesis AT1700 series
.It
Allied-Telesis RE2000 series
.bullet)
.It
Intel EtherExpress 16
.It
Intel EtherExpress PRO/10
.It
Intel EtherExpress 100 Fast Ethernet adapters
.It
Novell NE1000, NE2000 (ISA, PCI, PCMCIA, ISA PnP)
.It
RealTek 8129/8139 based boards
.It
SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards
.It
SMC/WD 8216 (the SMC "Elite16 Ultra" ISA boards)
.It
SMC 91C9x-based boards (ISA and PCMCIA)
.It
SMC EPIC/100 Fast Ethernet boards
.(bullet -compact
SMC Etherpower-II
.bullet)
.It
Texas Instruments ThunderLAN based ethernet boards
.(bullet -compact
Compaq Netelligent 10/100 TX
.It
Compaq ProLiant Integrated Netelligent 10/100 TX
.It
Compaq Netelligent 10 T (untested)
.It
Compaq Integrated NetFlex 3/P
.It
Compaq NetFlex 3/P in baseboard variant (the PCI
variant doesn't use the same chip !)
.It
Compaq Dual Port Netelligent 10/100 TX
.It
Compaq Deskpro 4000 5233MMX (untested)
.It
Texas Instruments TravelMate 5000 series laptop docking station Ethernet board
.bullet)
.It
VIA VT3043(Rhine) and VT86C100A(Rhine-II) based ethernet boards
.(bullet -compact
D-Link DFE530TX
.bullet)
.bullet)
.It
FDDI adapters
.(bullet -compact
Digital DEFPA PCI FDDI adapters [*] [+]
.It
Digital DEFEA EISA FDDI adapters [*] [+]
.bullet)
.It
Token-Ring adapters
.(bullet -compact
IBM Token-Ring Network PC Adapter [+]
.It
IBM Token-Ring Network PC Adapter II [+]
.It
IBM Token-Ring Network Adapter/A [+]
.It
IBM Token-Ring Network 16/4 Adapter [+]
.It
IBM Token-Ring Network 16/4 Adapter/A [+] [m]
.It
IBM 16/4 ISA Adapter [+]
.It
IBM Auto 16/4 Token-Ring ISA Adapter [+]
.It
3COM 3C619 TokenLink [+]
.It
3COM 3C319 TokenLink Velocity [+]
.bullet)
.It
Wireless network adapters
.(bullet -compact
AT\*&T/Lucent WaveLan IEEE (802.11) PCMCIA cards
.It
BayStack 650 802.11FH PCMIA cards [*] [+]
.It
NetWave AirSurfer PCMCIA cards [*] [+]
.bullet)
.It
High Speed Serial
.(bullet -compact
LAN Media Corporation SSI/LMC10000 (up to 10 Mbps) [*] [+]
.It
LAN Media Corporation HSSI/LMC5200 [*] [+]
.It
LAN Media Corporation DS3/LMC5245 [*] [+]
.bullet)
.It
Tape drives
.(bullet -compact
Most SCSI tape drives
.It
QIC-02 and QIC-36 format (Archive- and Wangtek- compatible) tape drives [*] [+]
.bullet)
.It
CD-ROM drives
.(bullet -compact
Non-IDE Mitsumi CD-ROM drives [*] [+]
.(Note
The Mitsumi driver device probe is known to cause trouble with several
devices!
.Note)
.Pp
.It
Most SCSI CD-ROM drives
.It
Most ATAPI CD-ROM drives.
.(Note
Some low-priced IDE CD-ROM drives are known for being not or not fully ATAPI
compliant, and thus require some hack (generally an entry to a
quirk table) to work with
.Nx .
.Note)
.bullet)
.It
Mice
.(bullet -compact
"Logitech"-style bus mice [*] [+]
.It
"Microsoft"-style bus mice [*] [+]
.It
"PS/2"-style mice [*] [+] [m]
.It
Serial mice (no kernel support necessary)
.bullet)
.It
Sound Cards
.(bullet -compact
SoundBlaster, SoundBlaster Pro, SoundBlaster 16 [*] [+]
.It
Gravis Ultrasound and Ultrasound Max [*] [+]
.It
Windows Sound System [*] [+]
.Pp
.Em The following drivers have not been extensively tested
.It
Personal Sound System [*] [+]
.It
ProAudio Spectrum [*] [+]
.It
Gravis Ultrasound Plug\*&Play [*] [+]
.It
Ensoniq AudioPCI [*] [+]
.It
Yamaha OPL3-SA3 [*] [+]
.It
Aria based sound cards [*]
.It
S3 SonicVibes [*] [+]
.It
ESS Technology ES1777/1868/1869/1887/1888/888 and Solo-1 ES1938/1946
audio [*] [+]
.bullet)
.It
Game Ports (Joysticks) [*] [+]
.It
Miscellaneous
.(bullet -compact
Advanced power management (APM) [*]
.bullet)
.It
Universal Serial Bus (USB)
.(bullet -compact
UHCI host controllers [*] [+]
.It
OHCI host controllers [*] [+]
.It
Hubs [*] [+]
.It
Keyboards using the boot protocol [*] [+]
.It
Mice [*] [+]
.It
Printers [*] [+]
.It
Modems using Abstract Control Model [*] [+]
.It
Generic support for HID devices [*] [+]
.It
Ethernet adapters [*] [+]
.bullet)
.It
PCMCIA Controllers.
.br
ISA, PCI, and ISA Plug\*&Play attachments
.(bullet -compact
Intel 82365 PCIC, rev 0 and rev 1
.It
Cirrus PD6710
.It
Cirrus PD672X
.bullet)
.(Note
This will work with most laptops as well as with ISA cards which provide
PCMCIA slots for desktops.
.Note)
.Pp
.It
RAID Controllers
.(bullet -compact
Compaq Integrated Array (PCI) [b]
.It
Compaq IAES (EISA)
.It
Compaq IDA, IDA-2 (EISA)
.It
Compaq Smart Array 221, 3100ES, 3200, 4200, 4250ES (PCI) [b]
.It
Compaq Smart Array 431, RAID LC2 [b]
.It
Compaq SMART 2, 2/E (EISA)
.It
Compaq SMART 2/E, 2/P, 2DH, 2SL (PCI) [b]
.bullet)
.bullet)
.Pp
Drivers for hardware marked with "[*]" are 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
support only one SCSI host adapter per machine.
support only one SCSI host adapter per machine.
.Nx
normally
allows more, though, so if you have more than one, you can use all of
@ -272,7 +502,9 @@ them by compiling a custom kernel once
.Nx
is installed.
.Pp
Support for devices marked with "[+]" IS included in the `GENERIC' kernels,
Support for devices marked with "[+]" IS included in the
.Li GENERIC
kernels,
although it is not in the kernels which are on the distribution floppies.
.Pp
Support for devices marked with "[b]" requires BIOS support for PCI-PCI
@ -280,26 +512,27 @@ bridging on your motherboard. Most reasonably modern Pentium motherboards
have this support, or can acquire it via a BIOS upgrade.
.Pp
Devices marked with [m] are supported also by MCA-enabled kernels, such as
one compiled from PS2 configuration file. Support for MCA is NOT in
the `GENERIC' or installation kernels at this moment.
one compiled from PS2 configuration file. Support for MCA is NOT in the
.Li GENERIC
or installation kernels at this moment.
.Pp
Hardware the we do NOT currently support, but get many questions
about:
.Bl -bullet
.It
Multiprocessor systems. (NetBSD will run, but only use one processor.)
Hardware the we do NOT currently support, but get many questions about:
.(bullet -offset indent
Multiprocessor systems.
.Nx
will run, but only use one processor.
.It
PCI WD-7000 SCSI host adapters.
.It
QIC-40 and QIC-80 tape drives.
(Drives that connect to the floppy disk controller.)
.El
.bullet)
.Pp
We are planning future support for many of these devices.
.Pp
To be detected by the distributed kernels, the devices must
be configured as follows:
.Bd -literal
.(disp
Device Name Port IRQ DRQ Misc
------ ---- ---- --- --- ----
Serial ports com0 0x3f8 4 [8250/16450/16550/clones]
@ -408,7 +641,7 @@ Novell NE2100 Ethernet boards
ne2 0x320 9 7
BICC IsoLan cards
ne3 0x320 10 7
ne3 0x320 10 7
SMC/WD 8003, 8013, Elite16, and Elite16 Ultra Ethernet boards
we0 0x280 9 iomem 0xd0000
@ -443,7 +676,7 @@ DC21x4x based Ethernet boards; see above for partial list
de0 any any [you must assign an interrupt in your
PCI BIOS, or let it do so for you]
Digital EtherWORKS III (DE203/DE204/DE205) LEMAC
Digital EtherWORKS III (DE203/DE204/DE205) LEMAC
lc0 0x320 any
Qlogic ISP [12]0x0 SCSI/FibreChannel boards
@ -452,18 +685,18 @@ Qlogic ISP [12]0x0 SCSI/FibreChannel boards
Efficient Networks EN-155 and Adaptec AIC-590x ATM interfaces
en0 any any
SMC EPIC/100 Fast Ethernet boards:
SMC EPIC/100 Fast Ethernet boards
epic0 any any
Texas Instruments ThunderLAN based ethernet boards:
Texas Instruments ThunderLAN based ethernet boards
tl0 any any
VIA VT3043(Rhine) and VT86C100A(Rhine-II) based ethernet boards
vr0 any any
IBM TROPIC based Token-Ring cards:
IBM TROPIC based Token-Ring cards
tr0 0xa20 any iomem 0xd8000
tr1 0xa24 any iomem 0xd0000
tr2 any any
.Ed
.disp)

4
distrib/notes/i386/install
View File

@ -1,3 +1,3 @@
.\" $NetBSD: install,v 1.23 2000/10/04 00:33:50 lukem Exp $
.\"
.\" $NetBSD: install,v 1.24 2000/10/10 12:55:18 lukem Exp $
.
.so ../common/sysinst

32
distrib/notes/i386/legal
View File

@ -1,5 +1,5 @@
.\" $NetBSD: legal,v 1.9 2000/10/04 00:28:36 lukem Exp $
.\"
.\" $NetBSD: legal,v 1.10 2000/10/10 12:55:18 lukem Exp $
.
.ig
WARNING: Don't insert markup into this file without making AT LEAST one of
@ -12,37 +12,19 @@ the following checks:
..
.
.
.Pp
This product includes software developed by Charles Hannum.
.Pp
This product includes software developed by Charles Hannum, by
the University of Vermont and State Agricultural College and
Garrett A. Wollman, by William F. Jolitz, and by the
University of California, Berkeley, Lawrence Berkeley
Laboratory, and its contributors.
.Pp
This product includes software developed by the University of
Vermont and State Agricultural College and Garrett A. Wollman.
.Pp
This product includes software developed by Dean Huxley.
.Pp
This product includes software developed by Herb Peyerl.
.Pp
In the following statement, "This software" refers to the Mitsumi
CD-ROM driver:
.Bl -item -offset indent
.It
.(item -offset indent
This software was developed by Holger Veit and Brian Moore for
use with "386BSD" and similar operating systems. "Similar
operating systems" includes mainly non-profit oriented systems
for research and education, including but not restricted to
"NetBSD", "FreeBSD", "Mach" (by CMU).
.El
.item)
.Pp
In the following statement, "This software" refers to the parallel
port driver:
.Bl -item -offset indent
.It
This software is a component of "386BSD" developed by
.(item -offset indent
This software is a component of "386BSD" developed by
William F. Jolitz, TeleMuse.
.El
.item)

4
distrib/notes/i386/prep
View File

@ -1,5 +1,5 @@
.\" $NetBSD: prep,v 1.9 2000/10/04 00:34:35 lukem Exp $
.\"
.\" $NetBSD: prep,v 1.10 2000/10/10 12:55:18 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

3
distrib/notes/i386/upgrade
View File

@ -1,4 +1,3 @@
.\" $NetBSD: upgrade,v 1.17 2000/10/04 00:33:50 lukem Exp $
.\"
.\" $NetBSD: upgrade,v 1.18 2000/10/10 12:55:19 lukem Exp $
.
.so ../common/upgrade

12
distrib/notes/i386/whatis
View File

@ -1,6 +1,5 @@
.\" $NetBSD: whatis,v 1.11 2000/10/04 00:35:13 lukem Exp $
.\"
.Pp
.\" $NetBSD: whatis,v 1.12 2000/10/10 12:55:19 lukem Exp $
.
As is usual between releases, the i386 port has had many improvements
made to it - too many to detail all of them here.
.Pp
@ -8,14 +7,11 @@ Numerous new drivers have been added. See the supported hardware list
for details.
.Pp
Some (but not all!) notable i386-specific improvements include:
.Pp
.Bl -bullet
.It
.(bullet
Migration to the ELF binary format from a.out.
.It
Preliminary support for MCA (MicroChannel Architecture)
.El
.Pp
.bullet)
.Nx \*V
on i386 is, as usual, also fully backward compatible with old
.Nx

238
distrib/notes/i386/xfer
View File

@ -1,237 +1,3 @@
.\" $NetBSD: xfer,v 1.18 2000/10/04 00:29:28 lukem Exp $
.\"
.\"(
.Pp
Installation is supported from several media types, including:
.Pp
.\"(
.Bl -bullet -compact
.It
FTP
.It
.No Remote Tn NFS No partition
.It
DOS floppies
.El
.\")
.Pp
No matter which installation medium you choose, you'll need to have a
floppy disk (either 1.2M or 1.44M will work). You'll put the boot
floppy image ("boot1.fs" and "boot2.fs" for 1.44M floppies,
"boot-tiny.fs" for 1.2M floppies) onto this disk, which contains
software to install or upgrade your
.Nx
system. Note that the "boot-tiny.fs" image is tailored for "small"
machines, this install image does not have drivers for PCI, PCMCIA,
EISA or SCSI (i.e. ISA-only), but can be used on machines with only
4MB of RAM.
.Pp
If you are using a UN*X-like system to write the floppy images to
disks, you should use the
.Xr dd
command to copy the file system image(s)
(.fs file) directly to the raw floppy disk. It is suggested that you
read the
.Xr dd 1
manual page or ask your system administrator to determine the correct
set of arguments to use; it will be slightly different from system to
system, and a comprehensive list of the possibilities is beyond the
scope of this document.
.Pp
If you are using
.Tn DOS
to write the floppy image(s) to floppy disk, you should use the
.Li rawrite
utility, provided in the
.Pa i386/utilities
directory of the
.Nx
distribution. It will write a file system image (.fs file) to a floppy
disk.
.Pp
Note that, when installing or upgrading, the floppy can be
write-protected if you wish. These systems mount ramdisks as their
root file systems once booted, and will not need to write to the
floppy itself at any time - indeed, once booted, the floppy may be
removed from the disk drive.
.Pp
Obviously, the steps necessary to prepare the distribution sets for
installation or upgrade depend on which installation medium you
choose. The steps for the various media are outlined below.
.Pp
To install or upgrade
.Nx
using
.Tn DOS
floppies, you need to do the following:
.\" $NetBSD: xfer,v 1.19 2000/10/10 12:55:19 lukem Exp $
.
.\"(
.Bl -bullet
.It
Count the number of
.Ar set_name.xx
files that make up the
distribution sets you want to install or upgrade. You will
need one fifth that number of 1.2M floppies, or one sixth that
number of 1.44M floppies. You should only use one size of
floppy for the install or upgrade procedure; you can't use
some 1.2M floppies and some 1.44M floppies.
.It
Format all of the floppies with
.Tn DOS .
.Em \&Do not
make any of them bootable
.Tn DOS
floppies, i.e. don't use
.Li format /s
to format them. (If the floppies are bootable, then the
.Tn DOS
system
files that make them bootable will take up some space, and you
won't be able to fit as many distribution set parts per disk.)
If you're using floppies that are formatted for
.Tn DOS
by their
manufacturers, they probably aren't bootable, and you can use
them out of the box.
.It
Place all of the
.Ar set_name.xx No files on the
.Tn DOS
disks, five per disk if you're using 1.2M disks, six per disk if you're
using 1.44M disks. How you do this is up to you; there are
many possibilities. You could, for instance, use a DOS
terminal program to download them on to the floppies, or use
a UN*X-like system capable of reading and writing
.Tn DOS
file systems (either with "mtools" or a real
.Tn DOS
file system) to place them on the disk.
.Pp
Once you have the files on
.Tn DOS
disks, you can start the actual installation or upgrade process.
.El
.\")
.
.Pp
To install or upgrade
.Nx
using NFS, you must do the following:
.
.\"(
.Bl -bullet
.It
Place the
.Nx
distribution sets you wish to install into a
directory on an
.Tn NFS
server, and make that directory mountable
by the machine on which you are installing or upgrading
.Nx .
This will probably require modifying the
.Pa /etc/exports
file on the
.Tn NFS
server and resetting its mount daemon (mountd).
(Both of these actions will probably require superuser
privileges on the server.)
.It
You need to know the numeric IP address of the
.Tn NFS
server,
and, if the server is not on a network directly connected to
the machine on which you're installing or upgrading
.Nx ,
you need to know the numeric IP address of the router closest
to the
.Nx
machine. Finally, you need to know the numeric
IP address of the
.Nx
machine itself. The install
program will ask you to provide this information to be able
to access the sets.
.Pp
Once the
.Tn NFS
server is set up properly and you have the
information mentioned above, you can start the actual
installation or upgrade process.
.El
.\")
.
.Pp
To install or upgrade
.Nx
by using FTP to get the installation
sets, you must do the following:
.
.\"(
.Bl -bullet
.It
The preparations for this installation/upgrade method are
easy; all you make sure that there's some FTP site from which
you can retrieve the
.Nx
distribution when you're about to
install or upgrade. You need to know the numeric IP address
of that site, and, if it's not on a network directly connected
to the machine on which you're installing or upgrading
.Nx ,
you need to know the numeric IP address of the router closest
to the
.Nx
machine. Finally, you need to know the numeric
IP address of the
.Nx
machine itself. The install program
will ask you to provide this information to be able to access
the sets via ftp.
.Pp
Once you have this information, you can proceed to the actual
installation or upgrade.
.El
.\")
.
.Pp
If you are upgrading
.Nx ,
you also have the option of installing
.Nx
by putting the new distribution sets somewhere in your existing
file system, and using them from there. To do that, you must do the
following:
.
.\"(
.Bl -bullet
.It
Place the distribution sets you wish to upgrade somewhere in
your current file system tree. Please note that the
.Pa /dev
on the floppy used for upgrades only knows about wd0, wd1, sd0, sd1
and sd2. If you have more than two IDE drives or more than
three SCSI drives, you should take care not to place the sets
on the high numbered drives.
.It
At a bare minimum, you must upgrade the
.Sy base
and
.Sy kern
binary distribution, and so must put the
.Sy base
and
.Sy kern
sets somewhere in your file system. If you wish,
you can do the other sets, as well, but you should NOT upgrade
the
.Sy etc
distribution; it contains systems
configuration files that you should review and update by hand.
.Pp
Once you have done this, you can proceed to the next step in
the upgrade process, actually upgrading your system.
.El
.\")
.\")
.so ../common/xfer

16
distrib/notes/mac68k/contrib
View File

@ -1,9 +1,10 @@
.\" $NetBSD: contrib,v 1.2 2000/10/10 12:55:19 lukem Exp $
.
.Ss Contributions
.Pp
The following people have made contributions of various sorts specifically
for the Macintosh port (in alphabetical order):
.Bl -bullet
.It
.(bullet
All of the users who have supplied us with good bug reports and
moral support.
.It
@ -25,7 +26,7 @@ Takashi Hamada and John Wittkoski beating the direct ADB hardware
driver into submission.
.It
David Huang for getting MACE Ethernet and basic DMA working on the
AV Macs.
AV Macs.
.It
Scott Jann for acquiring a IIx and a IIci, used for building and
testing release sets.
@ -77,8 +78,11 @@ Tenon Intersystems for monetary donations, MachTen, and Brad's
access to several machines and documentation after hours.
.It
Virginia Tech English Department for loan of a IIci w/ NuBus
video and 32MB of RAM--the first IIci to run NetBSD/Mac68k.
video and 32 MB of RAM - the first IIci to run
.Nx*M .
.It
Colin Wood for maintaining a host of NetBSD/mac68k documentation,
Colin Wood for maintaining a host of
.Nx*M
documentation,
including the FAQ, Meta-FAQ, and OS Info documents.
.El
.bullet)

131
distrib/notes/mac68k/hardware
View File

@ -1,39 +1,40 @@
.\" $NetBSD: hardware,v 1.16 2000/07/31 00:10:03 briggs Exp $
NetBSD/mac68k \*V runs on several of the older Macintosh computers.
About 4MB of RAM might be sufficient to boot, and the system can probably
be squeezed onto a 40MB hard disk by leaving off an unnecessary set or two.
.\" $NetBSD: hardware,v 1.17 2000/10/10 12:55:19 lukem Exp $
.
.Nx*M
\*V runs on several of the older Macintosh computers.
About 4 MB of RAM might be sufficient to boot, and the system can probably
be squeezed onto a 40 MB hard disk by leaving off an unnecessary set or two.
To actually do much compiling or anything more interesting than booting, at
least 8MB of RAM and more disk space is recommended. About 95MB will be
least 8 MB of RAM and more disk space is recommended. About 95 MB will be
necessary to install all of the
.Nx \*V
binary system distribution
sets (note that this does not count swap space!). An additional 30MB or so
sets (note that this does not count swap space!). An additional 30 MB or so
is needed for the binary X11 distribution sets. Much more disk space is
required to install the source and objects as well (at least another 300MB).
.Ss2 Supported models:
.Pp
.Bl -bullet -compact
required to install the source and objects as well (at least another 300
MB).
.
.Ss2 Supported models
.(bullet -compact -offset indent
Mac II, IIx, IIcx, SE/30, IIci, IIsi, IIvx, IIvi
.It
Mac II, IIx, IIcx, SE/30, IIci, IIsi, IIvx, IIvi,
Performa 400/405/410/430, Performa 450, Performa 460/466/467
.It
Performa 400/405/410/430, Performa 450, Performa 460/466/467,
Performa 520, Performa 550/560, Performa 600
.It
Performa 520, Performa 550/560, Performa 600,
LC II, LC III, LC III+, LC 520, LC 550
.It
LC II, LC III, LC III+, LC 520, LC 550,
MacTV
.It
MacTV,
Centris 650
.It
Centris 650,
.It
Quadra 610, Quadra 630, Quadra 650, Quadra 700, Quadra 800,
Quadra 610, Quadra 630, Quadra 650, Quadra 700, Quadra 800
.It
Quadra/Centris 660AV, Quadra 840AV
.El
.Ss2 Supported\ devices\ on\ all\ of\ the\ above\ systems\ include:
.Pp
.Bl -bullet -compact
.It
.bullet)
.
.Ss2 Supported devices
.(bullet -compact -offset indent
Onboard SCSI bus and most SCSI tapes, hard drives, and CD-ROMs
.It
Internal sound--enough to beep on some machines, anyway
@ -61,61 +62,65 @@ Onboard Ethernet based on the MACE (Am79C940) chip for the Quadra
AV-series Macs
.It
Comm-slot Ethernet should be working for most machines/cards
.El
.bullet)
.Pp
If your 68030 system is not listed above, it may be because of a problem
with accessing onboard video, and it may still work with a serial console.
Some of the known ones in this category:
.Pp
.Bl -bullet -compact
.It
Classic-series Macs
.(bullet -compact -offset indent
Classic-series Macs
.It
PowerBook 100-series and Duo-series Macs
.El
.bullet)
.Pp
If your 68LC040 system is not listed above, it is due to a problem with
floating point emulation (FPE) for this type of processor. Machines in
this category include:
.Pp
.Bl -bullet -compact
.It
.(bullet -compact -offset indent
Newer LC-series machines
.It
Newer Performa-series machines
.It
Some PowerBook 500-series Macs
.El
.Ss2 What\ isn't\ supported,\ but\ often\ asked\ about:
.Bl -hang
.It Em Macintosh IIfx:
This machine has unusual custom chips for the
ADB and serial interfaces which make support for it
difficult. Work is in progress on this, though.
.It Em Quadra 900/950:
These machines have I/O processor chips for their
ADB interfaces similar to those used in the IIfx and thus
face similar support problems.
.It Em PowerPC-based Macs:
This is a separate effort from the mac68k port. PowerMacs
use hardware that is often fairly different from that of
the mac68k port. If you are interested in this, you might
want to take a look at the new NetBSD/macppc port:
http://www.netbsd.org/Ports/macppc/index.html
.El
.bullet)
.
.Ss2 Unsupported models
.(bullet -offset indent
Macintosh IIfx
.Pp
Known hardware issues with this release:
.Bl -hang
.It Em Real Time Clock:
Due to oddities of the Macintosh hardware
interrupt priority scheme, NetBSD/mac68k keeps very poor
time. Under a high interrupt load (e.g. SCSI or serial
port activity) , a machine can lose several minutes per
hour. A consequence of this problem is that attempting to
run xntpd is rather pointless unless you periodically call
ntpdate.
.It Em SCSI difficulties:
The NetBSD/mac68k SCSI drivers are not quite as
This machine has unusual custom chips for the ADB and serial interfaces
which make support for it difficult. Work is in progress on this, though.
.It
Quadra 900/950
.Pp
These machines have I/O processor chips for their ADB interfaces similar to
those used in the IIfx and thus face similar support problems.
.It
PowerPC-based Macs
.Pp
This is a separate effort from the \*M port. PowerMacs use hardware that
is often fairly different from that of the \*M port. If you are
interested in this, you might want to take a look at the new NetBSD/macppc
port:
.Lk http://www.netbsd.org/Ports/macppc/index.html
.bullet)
.
.Ss2 Known hardware issues with this release
.(bullet -offset indent
Real Time Clock
.Pp
Due to oddities of the Macintosh hardware interrupt priority scheme,
.Nx*M
keeps very poor time. Under a high interrupt load (e.g.
SCSI or serial port activity) , a machine can lose several minutes
per hour. A consequence of this problem is that attempting to run xntpd
is rather pointless unless you periodically call ntpdate.
.It
SCSI difficulties
.Pp
The
.Nx*M
SCSI drivers are not quite as
robust as their MacOS counterparts. Symptoms of these
problems are that some SCSI disks will not work under
NetBSD that work fine under MacOS. Other problems include
@ -124,4 +129,4 @@ and the general unreliability of removable SCSI media.
Keep in mind that there are no clear patterns with these
problems, and they do not appear to affect the majority of
users.
.El
.bullet)

79
distrib/notes/mac68k/install
View File

@ -1,6 +1,6 @@
.\" $NetBSD: install,v 1.21 1999/05/31 06:38:16 ender Exp $
.\" $NetBSD: install,v 1.22 2000/10/10 12:55:19 lukem Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -33,14 +33,13 @@
.\"
The installation can be broken down into three basic steps:
.Pp
.Bl -bullet -compact
.It
.(bullet -compact
Run Mkfs to build a filesystem or filesystems.
.It
Run the Installer to load the files onto your filesystems.
.It
Run the Booter to boot the system.
.El
.bullet)
.
.Ss2 Preparing the filesystem(s)
.
@ -96,12 +95,11 @@ you did for Mkfs--i.e., the one you are installing onto.
If you are installing onto a single root partition, proceed to the
.Sx Installation\ of\ base\ files
section, below.
.Bl -item
.It
.Pp
If you have not created filesystems for the root, usr, and
any other filesystems, go back to "Preparing the filesystem(s),"
above.
.It
.Pp
When you started the Installer, it mounted your root partition.
Just before it printed, "Mounting partition 'A' as /," it printed
lines like:
@ -110,53 +108,45 @@ This means that the device for scsi ID 5 is sd1. The partitions
are signified by a trailing letter. For instance, sd1a would be
the root partition of the second scsi disk in the chain, and sd0g
would be the first Usr partition on the first scsi disk.
.It
.Pp
You will need to know the proper device to mount the remaining
partition(s) by hand:
.Bl -bullet
.It
.(bullet
Select "Build Devices" from the "File" menu.
.It
.Pp
Select "Mini Shell" from the "File" menu.
.It
.Pp
You can use the 'disklabel' command to get a listing of
the available partitions and their types and sizes.
.It
.Pp
Create the directory mount point(s) with the command:
.Dl mkdir path
(e.g. for the
.Pa /usr
partition type:
.Ic mkdir /usr )
.It
.Pp
Mount the filesystems you wish with the command:
.Dl mount device path
For example, if you wish to mount a usr partition from
the first scsi disk, sd0, on
.Pa /usr , No you would type:
.Dl mount /dev/sd0g /usr
.It
.Pp
.No Type Ic fstab force
.No to create a proper Pa /etc/fstab
file.
.It
.Pp
Type
.Ic quit
after you have mounted all the filesystems.
.El
.El
.bullet)
.
.Ss2 Installation of base files:
.Ss2 Installation of base files
.
.Bl -item
.It
Select the
.Ic Install
menu item from the
menu item from the
.Ic File
menu and install
.Pa base.tgz , etc.tgz , netbsd.tgz ,
@ -166,14 +156,14 @@ about what's in each set.) The Installer will print out the
filename of each file as it is installed, and will take quite some
time to install everything (the base package alone can take over an
hour on a slow hard drive).
.It
.Pp
As is the case with Mkfs, this is not a particularly well-behaved
Macintosh application and the machine will be completely tied up
while the installation takes place.
.It
.Pp
At some point after installing the base set, select the
.Ic Build Devices
option from the
option from the
.Ic File
menu if you have not already done
so. This will create a bunch of device nodes for you and will
@ -182,20 +172,20 @@ create your initial
The Installer program also has an
option to give you a mini-shell. Do not use this unless you are
sure know what you are doing.
.It
.Pp
When you are finished installing all of the sets you wish to
install, exit the Installer by choosing
.Ic Quit No from the Ic File
.No menu.
.El
.
.Ss2 Booting the system
.
Prior to attempting to boot NetBSD/mac68k, please verify that all of
Prior to attempting to boot
.Nx*M ,
please verify that all of
the following are true:
.Bl -enum
.It
32-bit addressing is enabled[*] in the Memory control panel;
.(enum
32-bit addressing is enabled [1] in the Memory control panel;
.It
All forms of virtual memory are disabled (the Memory control
panel, RAM Doubler, or other software-based memory enhancement
@ -205,16 +195,17 @@ Your system is in B\*&W mode (1-bit color or grayscale) as shown
by the Monitors control panel. You may choose to have the
Booter do this for you automatically by selecting the appropriate
check box and radio button in the
.Ic Monitors No dialog on the
.Ic Monitors No dialog on the
.Ic Options No menu .
.El
.enum)
.Pp
It is probably best to boot your machine with all extensions turned
off[*]. You can do this by booting into MacOS with the
off [1]. You can do this by booting into MacOS with the
.Tn SHIFT No key held
down. You may have to restart your Macintosh for changes to take effect
before proceeding.
.(tag Em [*]Note:
.(tag [1]
.It [1]
If your version of the Memory control panel does not have a 32-bit
addressing mode radio button, this means that your system is already
32-bit clean and is running in 32-bit addressing mode by default. If the
@ -230,10 +221,12 @@ ROM issues which prevent you from enabling 32-bit addressing. Please see
for more information.
.tag)
.Pp
Double-click on the NetBSD/mac68k Booter icon to start the application.
Select
Double-click on the
.Nx*M
Booter icon to start the application.
Select
.Ic Booting
from the
from the
.Ic Options
menu. Check that all of the items in
the resulting dialog look sane--especially the SCSI ID. If not, correct

20
distrib/notes/mac68k/legal
View File

@ -1,19 +1,15 @@
.\" $NetBSD: legal,v 1.9 1999/05/07 03:30:44 ender Exp $
.\" $NetBSD: legal,v 1.10 2000/10/10 12:55:19 lukem Exp $
.
This product includes software developed by the Alice Group.
.Pp
This product includes software developed by Allen Briggs.
This product includes software developed by Christopher G. Demetriou.
.Pp
This product includes software developed by Bradley A. Grantham.
.Pp
This product includes software developed by Takashi Hamada.
This product includes software developed by Christian E. Hopps.
.Pp
This product includes software developed by Scott Reynolds.
.Pp
This product includes software developed by John P. Wittkoski.
.Pp
This product includes software developed by Colin Wood.

27
distrib/notes/mac68k/prep
View File

@ -1,10 +1,10 @@
.\" $NetBSD: prep,v 1.9 1999/05/31 06:54:31 ender Exp $
.\" $NetBSD: prep,v 1.10 2000/10/10 12:55:19 lukem Exp $
.
Find your favorite disk partitioning utility. Any formatter capable of
partitioning a SCSI disk should work. Some of the ones that have been
tried and seem to work are:
.Pp
.Bl -bullet -compact
.It
.(bullet -compact -offset indent
Apple HD SC Setup
.It
Hard Disk ToolKit from FWB
@ -16,7 +16,7 @@ Disk Manager Mac from OnTrack
Silverlining from LaCie
.It
APS Disk Tools
.El
.bullet)
.Pp
Apple's HD SC Setup is probably the easiest to use and the most commonly
available. Instructions for patching HD SC Setup so that it will recognize
@ -29,13 +29,10 @@ First, you need to choose a drive on which to install
Try to pick a
drive with a low SCSI ID number, especially if you are likely to add or
remove drives to your SCSI chain in the future.
.(tag Note:
.Em Be sure you have a reliable backup
.Em of any data which you may want to
.Em keep. Repartitioning your hard drive is an
.Em excellent way to destroy important data.
.tag)
.(Note
Be sure you have a reliable backup of any data which you may want to keep.
Repartitioning your hard drive is an excellent way to destroy important data.
.Note)
.Pp
Second, decide how you want to set up your partitions. At minimum, you
need a partition to hold the
@ -52,7 +49,7 @@ root partition can be fairly small while the
.Pa /usr No partition should be
fairly large. If you plan to use this machine as a server, you may also
want a separate
.Pa /var No partition.
.Pa /var No partition.
.Pp
Once you have decided how to lay out your partitions, you need to calculate
how much space to allocate to each partition. A minimal install of
@ -60,11 +57,11 @@ how much space to allocate to each partition. A minimal install of
(i.e.
.Pa netbsd.tgz , base.tgz , No and
.Pa etc.tgz )
should just fit in a 32M partition.
For a full installation, you should allocate at least 95M (150M if you
should just fit in a 32 MB partition.
For a full installation, you should allocate at least 95 MB (150 MB if you
wish to install the X sets as well). A general rule of thumb for sizing
the swap partition is to allocate twice as much swap space as you have
real memory. Having your swap + real memory total at least 20M is also
real memory. Having your swap + real memory total at least 20 MB is also
a good idea. Systems that will be heavily used or that are low on real
memory should have more swap space allocated. Systems that will be only
lightly used or have a very large amount of real memory can get away

59
distrib/notes/mac68k/upgrade
View File

@ -1,6 +1,6 @@
.\" $NetBSD: upgrade,v 1.15 1999/05/07 03:30:44 ender Exp $
.\" $NetBSD: upgrade,v 1.16 2000/10/10 12:55:19 lukem Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -38,7 +38,8 @@ to advance to a later version by recompiling from source due primarily
to interdependencies in the various components.
.Pp
No automated upgrade procedure exists for upgrading to release \*V for the
NetBSD/mac68k architecture. The current procedure is essentially to perform
.Nx*M
architecture. The current procedure is essentially to perform
a new install from scratch. It is hoped that there will be a good upgrade
procedure for future releases. Please feel free to volunteer to help
replace these installation tools.
@ -46,8 +47,7 @@ replace these installation tools.
The following steps outline the current upgrade procedure. These steps
should help ease the upgrade process. Please read these instructions
carefully and completely before proceeding.
.Bl -enum
.It
.(enum
Since upgrading involves replacing the kernel and most of the system
binaries, it has the potential to cause data loss. You are strongly
advised to
@ -70,7 +70,7 @@ that you place the distribution sets on a filesystem you will be able to
reach from single-user mode.
.It
Install the \*V kernel. You may either use the Installer utility
(included in the
(included in the
.Pa installation/misc
subdirectory) or install from within
.Nx
@ -78,17 +78,18 @@ subdirectory) or install from within
choose the former, proceed as you normally would. If you choose to
install from within NetBSD, then boot (or shutdown) into single-user
mode and do the following:
.Bd -literal -offset indent
.(disp
cd /
pax -zrvpe -f /path/to/kern.tgz
.Ed
.disp)
.Pp
There is no need to backup your old kernel explicitly since it will be
incapable of running many of the newer binaries you are about to
install. (Unless, of course, you have a backup copy of your older
binaries and want to revert to them for some reason.) However, you
might want to keep a backup if you are upgrading from within
.Nx
just in case the newer kernel has trouble booting your machine.
just in case the newer kernel has trouble booting your machine.
.It
If you are installing using the Installer, skip to step 5. Otherwise,
reboot into
@ -115,19 +116,19 @@ or
.Cm sd Ns Ar X Ns Cm e
slots, slots that often were not available under
previous releases of NetBSD. If this is the case, you will need to
manually mount your root partition
manually mount your root partition
.Pq via Sy mount Fl w Cm /
and edit your
.Pa /etc/fstab
file to reflect the new partition layout. Unless you are
familiar with
familiar with
.Xr ex 1
or
.Xr ed 1 .
the easiest way to fix your
.Pa /etc/fstab
file
is probably to simply do a
is probably to simply do a
.Ic cat \*> /etc/fstab
and type in the corrected file in its entirety.
.It
@ -138,10 +139,10 @@ did the 1.3 family of distributions. If you are using the Installer,
proceed normally (remember that you will need to mount non-root
partitions by hand using the MiniShell before installing). If you are
installing from within NetBSD, do the following:
.Bd -literal -offset indent
.(disp
cd /
pax -zrvpe -f /path/to/base.tgz
.Ed
.disp)
.Pp
Keep in mind that there is
no going back once you have installed the base set short of a complete
@ -149,21 +150,22 @@ re-install of an earlier distribution. Continue with the appropriate
command line for each of the other sets you wish to install except for
the etc set. If you are in the Installer, open up the Minishell and do
the following:
.Bd -literal -offset indent
.(disp
cd /tmp
exit
.Ed
.disp)
.Pp
Ignore the warning message this will cause. Now, use the Installer to
install the
.Sy etc No set (it will install into
.Pa /tmp No instead of the
.Pa /etc No directory).
.Pa /etc No directory).
.Pp
If you are in NetBSD, do the following instead:
.Bd -literal -offset indent
.(disp
cd /tmp
pax -zrvpe -f /path/to/etc.tgz
.Ed
.disp)
.It
If you are in the Installer, quit it and boot into
.Nx
@ -179,8 +181,7 @@ changes in the new versions into yours. You should take note of the
following when upgrading to the
.Nx \*V
etc.tgz set:
.Bl -bullet
.It
.(bullet
Several of the options given to many of the file systems have changed,
and some of the file systems have changed names.
.Em \&It is imperative that
@ -205,27 +206,27 @@ as well. Make sure you have installed the latest MAKEDEV script (it
should be included in the etc set) and perform the following commands:
.Dl cd /dev
.Dl sh MAKEDEV all
.El
.bullet)
.It
Run
.Ic fsck Fl f
to make sure that your filesystem is still consistent. If
fsck reports any errors, fix them by answering
fsck reports any errors, fix them by answering
.Ic y
to its suggested
solutions
.(tag Em Note:
if there are a large number of errors, you may wish
to stop and run
solutions
.(Note
If there are a large number of errors, you may wish
to stop and run
.Ic fsck Fl fy
to automatically answer
.Ic yes
instead.
.tag)
.Note)
.It
Exit from single-user mode and it should continue to boot into
multi-user mode.
.El
.enum)
.Pp
At this point you have successfully upgraded to
.Nx \*V .

12
distrib/notes/mac68k/whatis
View File

@ -1,6 +1,7 @@
.\" $NetBSD: whatis,v 1.13 1999/05/07 03:30:44 ender Exp $
.\" $NetBSD: whatis,v 1.14 2000/10/10 12:55:19 lukem Exp $
.
.Nx \*V
is the fifth
is the fifth
.Dq real
release of
.Nx
@ -9,13 +10,12 @@ for the 68k-based Macintosh.
For the mac68k port,
.Nx \*V
brings a number of improvements:
.Bl -bullet
.It
.(bullet
A number of kernel changes enable support for several previously
unsupported systems (such as the LC and Performa 470-series,
570/580-series, and 630-series Macs).
.It
Support for 800KB floppy drives has been added (i.e. machines that
Support for 800 KB floppy drives has been added (i.e. machines that
include the IWM or SWIM, but not the SWIM II or SWIM III)
.It
IBM-compatible MBR handling has been integrated to enable MS-DOS
@ -26,7 +26,7 @@ The
driver has undergone a major revamp.
.It
A number of bugs affecting II-series systems have been fixed.
.El
.bullet)
There is still a lot of work to be done and help is welcomed. Please jump in!
.Nx \*V
on mac68k is, as usual, also fully backward compatible with old

17
distrib/notes/mac68k/xfer
View File

@ -1,4 +1,4 @@
.\" $NetBSD: xfer,v 1.15 1999/05/07 03:30:44 ender Exp $
.\" $NetBSD: xfer,v 1.16 2000/10/10 12:55:19 lukem Exp $
.
Installation is currently only supported from the local Macintosh hard
drive, from a CD-ROM, or from an AppleShare volume (however, you may upgrade
@ -7,7 +7,9 @@ a system from within
; see the section on upgrading for more details).
If you are installing from a local hard drive, this means that you'll need
at least enough room for the largest file that you will have to install.
This is the 10.2M base.tgz file. There has been talk of allowing an install
This is the 15.2 MB
.Pa base.tgz
file. There has been talk of allowing an install
from split files. If you have the time, desire, and knowledge, please feel
free to add that functionality.
.Pp
@ -16,8 +18,7 @@ utility must be in the same folder as the binary distribution sets.
.Pp
Each distribution file is in
.Em raw No archive format.
.Bl -bullet
.It
.(bullet
Distribution files must be downloaded in binary mode. Common web
browsers may not be suitable for this task; FTP clients such as
Fetch and Anarchie work fine, but be sure to specify a binary file
@ -31,13 +32,17 @@ documentation.
.It
If you are installing from a CD-ROM, the distribution sets are
already in the proper format and no special handling is required.
.El
.bullet)
.Pp
You will also need to collect the MacOS installation tools from the
.Pa mac68k/installation/misc No subdirectory of the
.Nx \*V
distribution:
Mkfs, NetBSD/Mac68k Installer, and NetBSD/Mac68k Booter. These three are
Mkfs,
.Nx*M
Installer, and
.Nx*M
Booter. These three are
in binhexed, self-extracting archives as Mkfs.sea.hqx, Installer.sea.hqx,
and Booter.sea.hqx, respectively. Extract them as you would any other
Macintosh application.

174
distrib/notes/macppc/hardware
View File

@ -1,92 +1,116 @@
.\" $NetBSD: hardware,v 1.3 2000/03/21 10:50:04 soda Exp $
.\" $NetBSD: hardware,v 1.4 2000/10/10 12:55:19 lukem Exp $
.
NetBSD/macppc \*V runs on PCI-based Power Macs and several compatibles.
The minimal configuration requires 4M of RAM and ~80M of disk space.
.Nx*M
\*V runs on PCI-based Power Macs and several compatibles.
The minimal configuration requires 4 MB of RAM and ~80 MB of disk space.
To install the entire system requires much more disk space, and to run
X or compile the system, more RAM is recommended. (NetBSD with 4M of
RAM feels like Solaris with 4M of RAM.) Note that until you have
around 16M of RAM, getting more RAM is more important than getting a
faster CPU.)
.Ss2 Supported models:
.Pp
.Bl -bullet -compact -offset indent
. It
X or compile the system, more RAM is recommended, as
.Nx with 4 MB of RAM is very slow. Note that until you have
around 16 MB of RAM, getting more RAM is more important than getting a
faster CPU.
.
.Ss2 Supported models
.(bullet -compact -offset indent
Apple Power Macintosh 7300/7600/8500/8600/9500/9600
. It
.It
Apple Power Macintosh G3 MT266/DT233
. It
.It
Apple PowerBook 2400c/180
. It
.It
Apple iMac (netboot only)
. It
.It
UMAX Apus2000
. It
.It
PowerComputing PowerWave 604/120
. It
.It
Motorola StarMax 3000/240
. It
.It
PowerCity 4000/200 (StarMax 4000/200 OEM)
. It
.It
APS M*Power 604e/200
.El
.Pp
NetBSD/macppc \*V does
.Em not
run on these machines (yet):
.Bl -bullet -compact -offset indent
. It
.bullet)
.
.Ss2 Unsupported models
.(bullet -compact -offset indent
Systems without Open Firmware. (e.g. PowerBook 5xxx)
. It
NuBus-based systems.
. It
PowerPC601-based systems.
. It
m68k-based systems with a PowerPC upgrade card.
.El
.Pp
Supported devices include:
.Pp
.Bl -tag -width indent
. It Em Ethernet:
on-board 79C950-based Ethernet interface. ("mace")
. br
on-board bmac Ethernet interface. (10Base-T only)
. br
.It
NuBus-based systems
.It
PowerPC601-based systems
.It
m68k-based systems with a PowerPC upgrade card
.bullet)
.
.Ss2 Supported devices
.(bullet -offset indent
Ethernet
.(bullet -compact
On-board 79C950-based Ethernet interface. ("mace")
.It
On-board bmac Ethernet interface. (10Base-T only)
.It
PCI NE2000 compatible Ethernet adapters. ("ne")
. It Em SCSI:
on-board 53c94 SCSI controler.
. br
on-board MESH SCSI controler. ("mesh")
. br
.bullet)
.It
SCSI
.(bullet -compact
On-board 53c94 SCSI controller
.It
On-board MESH SCSI controller ("mesh")
.It
Adaptec 291x, 2920, 2930C, 294x, 295x, 39xx, 19160, 29160
and AIC-78xx SCSI controller. ("ahc")
. br
AdvanSys 1200[A,B], 9xx[U,UA] SCSI controler. (Since it has no OpenFirmware
and AIC-78xx SCSI controller ("ahc")
.It
AdvanSys 1200[A,B], 9xx[U,UA] SCSI controller. (Since it has no OpenFirmware
support, you cannot boot from drive connected to this card)
. br
Most of SCSI disk/tape/CD-ROM devices should work.
. It Em PCI controler:
bandit/MPC106
. It Em IDE:
on-board IDE controler which is found in several models. (e.g. iMac)
. br
Most of hard drive and CD-ROM should work.
. It Em ADB devices:
Most ADB keyboards and mice.
. br
. It Em PS/2 devices: (PowerMac 4400 and several compatibles have them)
.It
Most of SCSI disk/tape/CD-ROM devices should work
.bullet)
.It
PCI controller
.(bullet -compact
Bandit/MPC106
.bullet)
.It
IDE
.(bullet -compact
On-board IDE controler which is found in several models. (e.g. iMac)
Most hard drives and CD-ROMs should work
.bullet)
.It
ADB devices
.(bullet -compact
Most ADB keyboards and mice
.bullet)
.It
PS/2 devices
.br
(PowerMac 4400 and several compatibles have PS/2 devices)
.(bullet -compact
PS/2 Keyboards
. br
.It
PS/2 Mice (middle button of 3-button one does not work)
. It Em Video (video card/on-board video):
PCI frame buffers which have Open Firmware support.
. It Em Serial ports:
ttya and ttyb can be used as console if needed. AKA serial/printer port.
.El
.Pp
Hardware the we do NOT currently support yet:
.Bl -tag -width indent
. It Em Floppy disk:
Though NetBSD/macppc can boot from it, no kernel support yet.
. It Em AWACS internal audio:
.El
.bullet)
.It
Video (video card/on-board video)
.(bullet -compact
PCI frame buffers which have Open Firmware support
.bullet)
.It
Serial ports
.(bullet -compact
ttya and ttyb (AKA the serial/printer port) can be used as console if needed
.bullet)
.bullet)
.
.Ss2 Unsupported devices
.(bullet -offset indent
Floppy disk
.(item -offset indent
Though
.Nx*M
can boot from it, there is no kernel support yet
.item)
.It
AWACS internal audio
.bullet)

19
distrib/notes/macppc/legal
View File

@ -1,5 +1,5 @@
.\" $NetBSD: legal,v 1.1 1999/04/12 13:46:25 tsubai Exp $
.Pp
.\" $NetBSD: legal,v 1.2 2000/10/10 12:55:19 lukem Exp $
.
This product includes software developed by Allen K. Briggs.
.Pp
This product includes software developed by Apple Computer, Inc.
@ -10,32 +10,23 @@ This product includes software developed by Bradley A. Grantham.
.Pp
This product includes software developed by Carnegie-Mellon University.
.Pp
This product includes software developed by Charles M. Hannum.
.Pp
This product includes software developed by Chris P. Cputo.
.Pp
This product includes software developed by Christopher G. Demetriou.
.Pp
This product includes software developed by Colin Wood.
.Pp
This product includes software developed by David Huang.
.Pp
This product includes software developed by Gordon W. Ross.
.Pp
This product includes software developed by Internet Reseach Institute, Inc.
This product includes software developed by Internet Research Institute, Inc.
.Pp
This product includes software developed by John P. Wittkoski.
.Pp
This product includes software developed by Open Software Foundation, Inc.
.Pp
This product includes software developed by Per Fogelstrom, Opsycon AB and RTMX Inc, USA.
This product includes software developed by Per Fogelstrom, Opsycon AB and
RTMX Inc, USA.
.Pp
This product includes software developed by Takashi Hamada.
.Pp
This product includes software developed by The NetBSD Foundation, Inc.
.Pp
This product includes software developed by Tools GmbH.
.Pp
This product includes software developed by Tsubai Masanari.
.Pp
This product includes software developed by University of Utah.

6
distrib/notes/macppc/prep
View File

@ -1,4 +1,4 @@
.\" $NetBSD: prep,v 1.2 1999/09/15 04:06:00 ross Exp $
.\" $NetBSD: prep,v 1.3 2000/10/10 12:55:19 lukem Exp $
.
.(Note
Currently
@ -17,8 +17,8 @@ currently does not support Apple's Disk Partition Map.
.Pp
Before you start, you must choose an installation method. If your machine has
an on-board Ethernet and you have the connection to an NFS server that can
provide even ~30M for a diskless-root filesystem, then installation via the net
is best. Next best, if you have another machine that is a running unix-like
provide even ~30 MB for a diskless-root filesystem, then installation via the
net is best. Next best, if you have another machine that is a running unix-like
operating system and has two disk drives (or one, if you live dangerously) is
to copy a diskimage onto one drive. Finally, you can install by using a second
machine as a helper to prepare a bootable

2
distrib/notes/macppc/upgrade
View File

@ -1,3 +1,3 @@
.\" $NetBSD: upgrade,v 1.2 1999/04/15 11:45:58 tsubai Exp $
.\" $NetBSD: upgrade,v 1.3 2000/10/10 12:55:19 lukem Exp $
.
.so ../common/upgrade

2
distrib/notes/macppc/whatis
View File

@ -1,4 +1,4 @@
.\" $NetBSD: whatis,v 1.1 1999/04/12 13:46:26 tsubai Exp $
.\" $NetBSD: whatis,v 1.2 2000/10/10 12:55:19 lukem Exp $
.
.Nx \*V
is the first official release of

14
distrib/notes/macppc/xfer
View File

@ -1,15 +1,13 @@
.\" $NetBSD: xfer,v 1.3 2000/06/17 15:05:26 martin Exp $
.\" $NetBSD: xfer,v 1.4 2000/10/10 12:55:19 lukem Exp $
.
Installation is supported from several media types, including:
.Bl -bullet -compact
.Pp
.It
.(bullet -compact
NFS
.It
FTP
.It
CD-ROM
.El
.bullet)
.(Note
Installing on a "bare" machine requires some bootable device; either an MO
drive or a floppy. When the target has on-board Ethernet, NFS installation is
@ -26,7 +24,7 @@ subdirectories in these two directories:
.Dl Pa \&.../NetBSD-\*V/macppc/installation
.Dl Pa \&.../NetBSD-\*V/macppc/binary
.
.Ss2 Boot/Install from NFS server:
.Ss2 Boot/Install from NFS server
.
If your machine has a disk and network connection and on-board Ethernet, it may
be convenient for you to install
@ -46,5 +44,7 @@ another operating system, consult the documentation that came with it (i.e.
add_client(8) on SunOS).
.Pp
.
Since NetBSD/macppc does not have floppy disk support yet, you need MacOS or
Since
.Nx*M
does not have floppy disk support yet, you need MacOS or
another machine that can write the install kernel image to floppy.

134
distrib/notes/mvme68k/hardware
View File

@ -1,60 +1,108 @@
.\" $NetBSD: hardware,v 1.4 1999/02/20 16:18:11 scw Exp $
.\" $NetBSD: hardware,v 1.5 2000/10/10 12:55:20 lukem Exp $
.
NetBSD/mvme68k \*V runs on Motorola
.Nx*M
\*V runs on Motorola
.Tn MVME147 No and MVME167 No Single Board Computers.
.Pp
The minimal configuration requires 4M of RAM and ~100MB of disk space.
The minimal configuration requires 4 MB of RAM and ~100 MB of disk space.
To install the entire system requires much more disk space (approx.
200MB additional space is necessary for full sources. Double that if you
200 MB additional space is necessary for full sources. Double that if you
want to recompile it all!). To run X (clients only) or compile the system,
more RAM is recommended. Good performance requires 8MB of RAM, or 16 MB
more RAM is recommended. Good performance requires 8 MB of RAM, or 16 MB
when running the X Window System.
.Pp
Here is a table of recommended HD partition sizes for a full install:
.Bd -literal -offset indent
partition: advise needed
root (/) 20M 12M
user (/usr) 100M 80M
swap (2 or 3 * RAM) 8M
.Bl -column -offset indent Partition Suggested Needed
.It Partition Ta Suggested Ta Needed
.It root\ (/) Ta "20 MB" Ta "12 MB"
.It /usr Ta "100 MB" Ta "80 MB"
.It /var Ta "20 MB" Ta "5 MB"
.It swap Ta Em "2-3 *RAM" Ta 6 MB
.El
.(item -offset indent
Anything else is up to you!
.Ed
.item)
.Pp
Note that the \*m installation procedure uses a
Note that the
.Nx*M
installation procedure uses a
.Em miniroot
image which is placed into the swap area of the disk. The swap partition
must be large enough to hold this miniroot image (\*> 6Mb).
.Pp
The following
.Tn VME147 No hardware is supported:
.Bl -tag -width Parallel
.It Em Serial ports (RS232):
built-in console, ttyZ1, ttyZ2 and ttyZ3
.It Em Parallel port:
must be large enough to hold this miniroot image (\*> 6 MB).
.
.Ss2 Supported VME147 hardware
.(bullet -offset indent
Serial ports (RS232)
.(bullet -compact
built-in console
.It
ttyZ1
.It
ttyZ2
.It
ttyZ3
.bullet)
.It
Parallel port
.(bullet -compact
On-board centronics style printer port
.It Em Network interfaces:
.bullet)
.It
Network interfaces:
.(bullet -compact
On-board Lance Ethernet (le)
.It Em SCSI:
(Most SCSI disks, tapes, CD-ROMs, etc.)
On-board wd33c93 SCSI bus interface chip (async only for now).
.It Em Miscellaneous:
Battery-backed real-time clock.
VMEbus RAM cards.
.El
.Pp
The following
.Tn VME167 No hardware is supported:
.Bl -tag -width Parallel
.It Em Serial ports (RS232):
built-in console, ttyC1, ttyC2 and ttyC3
.It Em Parallel port:
.bullet)
.It
SCSI
.(bullet -compact
Most SCSI disks, tapes, CD-ROMs, etc
.It
On-board wd33c93 SCSI bus interface chip (async only for now)
.bullet)
.It
Miscellaneous:
.(bullet -compact
Battery-backed real-time clock
.It
VMEbus RAM cards
.bullet)
.bullet)
.
.Ss2 Supported VME167 hardware
.(bullet -offset indent
Serial ports (RS232)
.(bullet -compact
built-in console
.It
ttyZ1
.It
ttyZ2
.It
ttyZ3
.bullet)
.It
Parallel port
.(bullet -compact
On-board centronics style printer port
.It Em Network interfaces:
On-board Ethernet (ie)
.It Em SCSI:
(Most SCSI disks, tapes, CD-ROMs, etc.)
On-board ncr53c710 SCSI I/O Processor chip.
.It Em Miscellaneous:
Battery-backed real-time clock.
.El
.bullet)
.It
Network interfaces:
.(bullet -compact
On-board Lance Ethernet (ie)
.bullet)
.It
SCSI
.(bullet -compact
Most SCSI disks, tapes, CD-ROMs, etc
.It
On-board ncr53c710 SCSI I/O Processor chip
.bullet)
.It
Miscellaneous:
.(bullet -compact
Battery-backed real-time clock
.bullet)
.bullet)
.
.Pp
If it's not on the above lists, there is no support for it in this release.

77
distrib/notes/mvme68k/install
View File

@ -1,4 +1,4 @@
.\" $NetBSD: install,v 1.8 2000/10/03 23:23:56 lukem Exp $
.\" $NetBSD: install,v 1.9 2000/10/10 12:55:20 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -31,7 +31,6 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.
Installing
.Nx
is a relatively complex process, but if you have
@ -48,9 +47,11 @@ Otherwise, if you have another mvme68k machine running
you can
initialize the disk on that machine and then move the disk.
.
.Ss2 Installing from tape:
.Ss2 Installing from tape
.
Create the NetBSD/mvme68k _VER boot tape as described in the section
Create the
.Nx*M
_VER boot tape as described in the section
entitled "Preparing a boot tape". Then, with the tape in the drive,
type the following at the 1x7Bug prompt:
.Pp
@ -65,15 +66,15 @@ series of status messages. It may be useful if you can capture these
messages to a file, or a scrollable xterm window. In particular, you
should make a note of the lines which describe the geometry of the
SCSI disks detected by NetBSD. They are of the form:
.Bd -literal -offset indent
.(disp
sd0 at scsibus0 targ 0 lun 0: \*<CDC, 94161-9, 2506\*> SCSI1 0/direct fixed
sd0: 148MB, 967 cyl, 9 head, 35 sec, 512 bytes/sect x 304605 sectors
.Ed
sd0: 148 MB, 967 cyl, 9 head, 35 sec, 512 bytes/sect x 304605 sectors
.disp)
.Pp
The information of most interest is the number of sectors; here it's
304605. You will need this number when you come to create a disklabel
for that drive.
.Bd -literal -offset indent
.(disp
RAM address from VMEbus = $00000000
Booting from: VME147, Controller 5, Device 0
@ -82,7 +83,7 @@ Loading: Operating System
Volume: NBSD
IPL loaded at: $003F0000
\*>\*> BSD MVME147 tapeboot [$Revision: 1.8 $]
\*>\*> BSD MVME147 tapeboot [$Revision: 1.9 $]
578616+422344+55540+[46032+51284]=0x11a6e4
Start @ 0x8000 ...
Copyright (c) 1996, 1997 The NetBSD Foundation, Inc. All rights reserved.
@ -101,7 +102,7 @@ clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM
\&.
\&.
.Ed
.disp)
.Pp
.(Note
The exact text of the messages will vary depending on which
@ -109,8 +110,8 @@ MVME147 or MVME167 variant you're using.
.Note)
.Pp
Finally, you will see the following "welcome" message:
.Bd -literal offset indent
Welcome to the NetBSD/mvme68k RAMDISK root!
.(disp
Welcome to the NetBSD/\*M RAMDISK root!
This environment is designed to do only four things:
1: Partititon your disk (use the command: edlabel /dev/rsd0c)
@ -134,7 +135,7 @@ use "halt", then at the Bug monitor prompt use a command like:
To view this message again, type: cat /.welcome
ssh:
.Ed
.disp)
.Pp
You must now create a disklabel on the disk you wish to use for the
root filesystem. This will usually be
@ -146,11 +147,11 @@ the disk.
Partitions are named
.Li sd0a, sd0b, sd0c
.No etc, up to Li sd0h .
The \*m port of
The \*M port of
.Nx
makes some assumptions about the first three partitions on a boot disk:
.Pp
.Bl -tag -compact -width sd0c
.(tag sd0c -compact
.It Li sd0a
The root filesystem.
.It Li sd0b
@ -158,7 +159,7 @@ The swap partition.
.It Li sd0c
The whole disk. Also known as the
.Em raw partition .
.El
.tag)
.Pp
The
.Em raw partition No is special;
@ -230,13 +231,13 @@ blocks or cylinder/track/sector notation. If this is the first time
you've partitioned a disk for NetBSD, it's probably easiest to use block
notation. The above example creates partition 'a', starting at block zero
and with a size of 38000 blocks. Note that the usual size of a block is
512 bytes, so this creates a 19Mb partition.
512 bytes, so this creates a 19 MB partition.
.Pp
The 'type' of the partition should be "4.2BSD", otherwise you won't
be able to create a filesystem on it.
.Pp
Next, create a swap partition (b). Note that the minimum size of this
swap partition should be 8Mb, otherwise you won't be able to use a
swap partition should be 8 MB, otherwise you won't be able to use a
miniroot to complete the
.Nx
installation!
@ -251,10 +252,10 @@ installation!
Here, we specify a value for 'start' such that the swap partition follows
immediately after partition 'a', i.e. 38000. The length of the swap
partition should be a multiple of the amount of RAM you have in your
system. Here, I've chosen 32768, or 16Mb. The next available block on the
system. Here, I've chosen 32768, or 16 MB. The next available block on the
drive is thus 38000 + 32768. We will use this to create partition 'd' for
our /usr filesystem. (Note that for a busy system, or a system with more
than 8Mb of RAM, you'll be better off with a 32 or 64Mb swap partition.)
than 8 MB of RAM, you'll be better off with a 32 or 64 MB swap partition.)
.Pp
.Dl edlabel/modify\*> Ic d
.Dl d (user) 0 (0/00/00) 0 (0/00/00) unused
@ -278,7 +279,7 @@ details you've just entered, to disk. You might also try the 'p' command
to view the partitions. Once written, you can quit back to ssh using 'q'.
.Pp
.Dl edlabel\*> Ic p
.Bd -literal -offset indent
.(disp
type_num: 4
sub_type: 0
type_name: SCSI disk
@ -294,7 +295,8 @@ partition start (c/t/s) nblks (c/t/s) type
b (swap) 38000 (120/05/25)* 32768 (104/00/08)* swap
c (disk) 0 (0/00/00) 304605 (967/00/00) unused
d (user) 70768 (224/05/33)* 233837 (742/03/02)* 4.2BSD
.Ed
.disp)
.Pp
.Dl edlabel\*> Ic w
.Dl edlabel\*> Ic q
.Dl ssh:
@ -336,7 +338,7 @@ Resetting the MVME167 board is very similar.
You should now reboot from that just installed miniroot. See the section
entitled "Booting the miniroot" for details.
.
.Ss2 Installing from NFS:
.Ss2 Installing from NFS
.
Before you can install from NFS, you must have already configured
your NFS server to support your machine as a bootable client.
@ -346,7 +348,7 @@ entitled "Getting the NetBSD System onto Useful Media" above.
To get started on the MVME147, you need to download "sboot" into RAM
(you will find
.Ic sboot
in the
in the
.Pa install
directory of the mvme68k distribution).
You can either do that through the console line or through a 2nd serial
@ -354,11 +356,11 @@ connection. For example, an MVME147 connected to a sun4/110 and accessed via
.Xr tip 1
can be loaded as follows:
.Pp
.Bd -literal -offset indent
.(disp
lo 0
~Ccat sboot
go 4000
.Ed
.disp)
.Pp
Which will look like this:
.Pp
@ -379,7 +381,7 @@ Now, if you want to do it through serial line 1, then connect serial
line one to a machine. At the
.Li 147-Bug\*> No prompt type Ic \&tm 1
You should then login to the machine it is connected to.
Then press Control-A to escape to Bug. do
Then press Control-A to escape to Bug. do
.Ic lo 1;x=cat sboot Em ...
then when that is done you can reconnect
.Ic tm 1 No and logout.
@ -391,13 +393,13 @@ from the server:
.Pp
.Dl \*>\*>\*> b
.Pp
.Bd -literal -offset indent
.(disp
le0: ethernet address: 8:0:3e:20:cb:87
My ip address is: 192.168.1.4
Server ip address is: 192.168.1.1
4800
Download was a success!
.Ed
.disp)
.Pp
See below for the next step in booting MVME147.
.Pp
@ -413,9 +415,9 @@ to type is:
.Pp
For both boards, the boot messages are very similar:
.Pp
.Bd -literal -offset indent
.(disp
Start @ 0x8000 ...
\*>\*> BSD MVME147 netboot (via sboot) [$Revision: 1.8 $]
\*>\*> BSD MVME147 netboot (via sboot) [$Revision: 1.9 $]
device: le0 attached to 08:00:3e:20:cb:87
boot: client IP address: 192.168.1.4
boot: client name: soapy
@ -437,7 +439,7 @@ pcc0 at mainbus0: Peripheral Channel Controller, rev 0, vecbase 0x40
clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM
\&.
\&.
.Ed
.disp)
.Pp
After the boot program loads the RAMDISK kernel, you should see the
welcome screen as shown in the "tape boot" section above.
@ -501,7 +503,7 @@ installing from tape, where it describes how to run 'installboot'.
This is immediately following the part which explains how to copy the
miniroot from tape.
.
.Ss2 Booting the miniroot:
.Ss2 Booting the miniroot
.
Assuming the miniroot is installed on partition 'b' of the disk with
SCSI-id 0, then the 147Bug boot command is:
@ -512,7 +514,7 @@ The corresponding 167Bug boot command is:
.Pp
The command line parameters above are:
.Pp
.Bl -tag -width xxx
.(tag xxx
.It Ic 0
controller (usually zero)
.It Ic ,, or ,,,
@ -520,7 +522,7 @@ bug argument separators
.It Ic \&b:\&
tell the bootstrap code to boot from partition
.Ic b
.El
.tag)
.Pp
You should see a bunch of boot messages, followed by messages from
the miniroot kernel just as you did when the RAMDISK kernel booted.
@ -553,8 +555,7 @@ you through the entire process, and is well automated. Additional
improvements are planned for future releases.
.Pp
The miniroot's install program will:
.Bl -bullet
.It
.(bullet
Allow you to place disklabels on additional disks.
The disk we are installing on should already have
been partitioned using the RAMDISK kernel.
@ -607,7 +608,7 @@ Copy a new kernel onto your root partition.
Install a new boot block.
.It
Check your filesystems for integrity.
.El
.bullet)
.Pp
First-time installation on a system through a method other than the
installation program is possible, but strongly discouraged.

19
distrib/notes/mvme68k/legal
View File

@ -1,18 +1,5 @@
.\" $NetBSD: legal,v 1.3 1999/01/13 07:30:07 ross Exp $
This product includes software developed by the Computer
Systems Laboratory at the University of Utah.
This product includes software developed by the University of
Vermont and State Agricultural College and Garrett A. Wollman.
This product includes software developed by Charles D. Cranor.
This product includes software developed by Adam Glass.
This product includes software developed by Charles Hannum.
.\" $NetBSD: legal,v 1.4 2000/10/10 12:55:20 lukem Exp $
.
This product includes software developed by David Jones.
This product includes software developed by Gordon W. Ross.
.Pp
This product includes software developed by Steve C. Woodford.

14
distrib/notes/mvme68k/prep
View File

@ -1,4 +1,4 @@
.\" $NetBSD: prep,v 1.6 2000/10/05 08:54:55 lukem Exp $
.\" $NetBSD: prep,v 1.7 2000/10/10 12:55:20 lukem Exp $
.
mvme68k machines usually need little or no preparation before installing
.Nx "" ,
@ -8,7 +8,7 @@ on any attached storage devices.
.Pp
The following instructions should make your machine "NetBSD Ready".
.Pp
Power-up your MVME147 board. You should have the
Power-up your MVME147 board. You should have the
.Em bug No prompt:
.(disp
@ -17,8 +17,8 @@ COLD Start
Onboard RAM start = $00000000, stop = $007FFFFF
147-Bug\*>
.disp)
.Pp
Or, if you have an MVME167 board:
.(disp
@ -30,10 +30,10 @@ Local Memory Found =02000000 (&33554432)
MPU Clock Speed =33Mhz
167-Bug\*>
.disp)
Make sure the RAM size looks ok (if you've got an 8Mb MVME147 or a
32Mb MVME167 you should
.Pp
Make sure the RAM size looks ok (if you've got an 8 MB MVME147 or a
32 MB MVME167 you should
have the same value as I do). Also make sure the clock is ticking:
.Pp
.Dl 1x7-Bug\*> Ns Ic time
@ -55,7 +55,7 @@ doesn't use it.
Motorola has acknowledged a year 2000 bug in some versions of the MVME147
whereby the day of the week
doesn't get set correctly by the 147Bug PROM.
.Em It does not affect
.Em \It does not affect
.Nx "" !
.Pp
Also make sure that your board's ethernet address is initialised to

21
distrib/notes/mvme68k/upgrade
View File

@ -1,4 +1,4 @@
.\" $NetBSD: upgrade,v 1.6 2000/10/03 23:23:56 lukem Exp $
.\" $NetBSD: upgrade,v 1.7 2000/10/10 12:55:20 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -31,14 +31,14 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.
It is possible to easily upgrade your existing NetBSD/mvme68k system
It is possible to easily upgrade your existing
.Nx*M
system
using the upgrade program in the miniroot. If you wish to upgrade
your system by this method, simply select the `upgrade' option once
the miniroot has booted. The upgrade program with then guide you
through the procedure. The upgrade program will:
.Bl -bullet
.It
.(bullet
Enable the network based on your system's current
network configuration.
.It
@ -53,22 +53,23 @@ edit the resulting file.
Make new device nodes in your root filesystem.
.It
Copy a new kernel onto your root partition.
NOTE: the existing kernel WILL NOT be backed up; doing
.(Note
The existing kernel WILL NOT be backed up; doing
so would be pointless, since older kernels may not be
capable of running
.Nx \*V
executables.
.Note)
.It
Install a new boot block.
.It
Check your filesystems for integrity.
.El
.bullet)
.Pp
While using the miniroot's upgrade program is the preferred method
of upgrading your system, it is possible to upgrade your system
manually. To do this, follow the following procedure:
.Bl -bullet
.It
.(bullet
Place _at least_ the `base' binary set in a filesystem
accessible to the target machine. A local filesystem
is preferred, since the NFS subsystem in the
@ -132,7 +133,7 @@ To extract these sets, use the following commands:
.Pp
.Dl Ic cd /
.Dl Ic pax -zrvpe -f Ar path_to_set
.El
.bullet)
.Pp
.(Note
You

2
distrib/notes/mvme68k/whatis
View File

@ -1,4 +1,4 @@
.\" $NetBSD: whatis,v 1.4 1999/02/20 16:18:11 scw Exp $
.\" $NetBSD: whatis,v 1.5 2000/10/10 12:55:20 lukem Exp $
.
This is the fifth public release of
.Nx

29
distrib/notes/mvme68k/xfer
View File

@ -1,9 +1,7 @@
.\" $NetBSD: xfer,v 1.5 1999/02/20 16:18:11 scw Exp $
.\" $NetBSD: xfer,v 1.6 2000/10/10 12:55:20 lukem Exp $
.
Installation is supported from several media types, including:
.Bl -bullet -compact
.Pp
.It
.(bullet
Tape
.It
NFS
@ -11,7 +9,7 @@ NFS
CD-ROM
.It
FTP
.El
.bullet)
Note that installing on a "bare" machine requires either a bootable
tape drive or an ethernet to a compatible NFS server. MVME147 may
also need to be booted over an RS232 connection.
@ -26,7 +24,7 @@ subdirectories in these two directories:
.Dl Pa \&.../NetBSD-\*V/mvme68k/installation
.Dl Pa \&.../NetBSD-\*V/mvme68k/binary
.
.Ss2 Creating boot/install tapes:
.Ss2 Creating boot/install tapes
.
Installing from tape is the simplest method of all. This method uses two
tapes, one containing a bootable ramdisk and miniroot, the other containing
@ -58,7 +56,7 @@ set the EOF mark at the end of each tape segment. Consult the
tape-related manual pages on the system where the tapes are created for
more details.
.
.Ss2 Boot/Install from NFS server:
.Ss2 Boot/Install from NFS server
.
If your machine has a disk and network connection, but no tape drive,
it may be convenient for you to install
@ -89,7 +87,8 @@ It will look for a filename derived from the machine's IP address
expressed in hexadecimal, with an extension of ".147". For example,
an MVME147 with IP address 130.115.144.11 will make an TFTP request for
`8273900B.147'. Normally, this file is just a symbolic link to the
NetBSD/mvme68k "netboot" program, which should be located in a place
.Nx*M
"netboot" program, which should be located in a place
where the TFTP daemon can find it (remember, many TFTP daemons run in
a chroot'ed environment). The netboot program may be found in the
install directory of this distribution.
@ -111,7 +110,7 @@ trying to netboot the client.
The client will need access to the miniroot image, which can be
provided using NFS or remote shell. If using NFS, miniroot.gz should be
expanded on the server, because doing so from the RAMDISK shell is not
so easy. The unzipped miniroot takes about 6Mb of space.
so easy. The unzipped miniroot takes about 6 MB of space.
.Pp
If you will be installing
.Nx
@ -121,7 +120,7 @@ as they only use the netbsd-rd kernel. There will be no conflict
between clients because the RAM-disk kernel will not use the NFS root.
No swap file is needed; the RAM-disk kernel does not use that either.
.
.Ss2 Install/Upgrade from CD-ROM:
.Ss2 Install/Upgrade from CD-ROM
.
This method requires that you boot from another device (i.e. tape
or network, as described above). You may need to make a boot tape
@ -131,7 +130,7 @@ miniroot, you can load any of the distribution sets directly from
the CD-ROM. The "install" program in the miniroot automates the
work required to mount the CD-ROM and extract the files.
.
.Ss2 Install/Upgrade via FTP:
.Ss2 Install/Upgrade via FTP
.
This method requires that you boot from another device (i.e. tape
or network, as described above). You may need to make a boot tape
@ -143,16 +142,16 @@ automates the work required to configure the network interface and
transfer the files.
.Pp
This method, of course, requires network access to an FTP server.
This might be a local system, or it might even be ftp.NetBSD.ORG
itself. If you wish to use ftp.NetBSD.ORG as your FTP file
This might be a local system, or it might even be ftp.netbsd.org
itself. If you wish to use ftp.netbsd.org as your FTP file
server, you may want to keep the following information handy:
.Pp
.Dl No IP Address: ftp.NetBSD.ORG
.Dl No IP Address: ftp.netbsd.org
.Dl Login: Ic anonymous
.Dl Password: Ar your e-mail address
.Dl Server path: Ic /pub/NetBSD/NetBSD-\*V/mvme68k/binary
.(Note
If you're not using a nameserver duing installation,
you might find 204.152.184.75 handy; it's the IP address of
ftp.NetBSD.ORG as of January, 1999.
ftp.netbsd.org as of January, 1999.
.Note)

78
distrib/notes/news68k/hardware
View File

@ -1,48 +1,56 @@
.\" $NetBSD: hardware,v 1.1 2000/06/14 10:34:30 tsutsui Exp $
NetBSD/news68k \*V will run on single m68030-based Sony NEWS workstations.
.\" $NetBSD: hardware,v 1.2 2000/10/10 12:55:20 lukem Exp $
.
.Nx*M
\*V will run on single m68030-based Sony NEWS workstations.
They include the NWS-14x0, NWS-15x0, PWS-15x0, NWS-17x0,
and NWS-12x0 machines. NetBSD/news68k does not currently support
and NWS-12x0 machines.
.Nx*M
does not currently support
m68020-based machines (NWS-700, NWS-800) nor I/O processor based
machines (NWS-800, NWS-1800).
.Pp
NetBSD/news68k \*V does not support any framebuffers so
.Nx*M
\*V does not support any framebuffers so
.Em you have to use serial console
to install NetBSD/news68k.
to install
.Nx*M .
.Pp
NetBSD/news68k \*V does not support SCSI on NWS-12x0 machines,
.Nx*M
\*V does not support SCSI on NWS-12x0 machines,
so installations on NWS-12x0 must use a remote NFS filesystem.
.Pp
MIPS based NEWS workstations (NWS-3xxx or NWS-5000) are
supported by NetBSD/newsmips.
.Pp
The following NEWS hardware is supported:
.de section
. El
. Pp
. It Em \\$*
. br
. Bl -bullet -compact
..
.de item
. It
\\$*
..
.Bl -tag -width Disks
. It Em CPUs:
. br
. Bl -bullet -compact
. item 68020-based: none.
. item 68030-based: NWS-12x0, NWS-14x0, NWS-15x0, PWS-15x0, NWS-17x0
. section RS232 interfaces:
. item built in Zilog 8530 Serial Communication Controllers (zsc).
. section Network interfaces:
. item built in LANCE Ethernet (le).
. section SCSI interfaces:
. item built in CXD1180 SCSI interface (si)
. item most SCSI devices
. El
.El
.
.Ss2 Supported hardware
.(bullet -offset indent
CPUs
.(bullet -compact
68020-based: none
.It
68030-based: NWS-12x0, NWS-14x0, NWS-15x0, PWS-15x0, NWS-17x0
.bullet)
.It
RS232 interfaces
.(bullet -compact
built in Zilog 8530 Serial Communication Controllers (zsc)
.bullet)
.It
Network interfaces
.(bullet -compact
built in LANCE Ethernet (le)
.bullet)
.It
SCSI interfaces
.(bullet -compact
built in CXD1180 SCSI interface (si)
.It
most SCSI devices
.bullet)
.bullet)
.Pp
If it's not on this list, there is no official support for it in this release.
More information can also be found at NetBSD/news68k homepage:
More information can also be found at the
.Nx*M
homepage:
.Lk http://www.netbsd.org/Ports/news68k/

3
distrib/notes/news68k/install
View File

@ -1,2 +1,3 @@
.\" $NetBSD: install,v 1.1 2000/06/14 10:34:31 tsutsui Exp $
.\" $NetBSD: install,v 1.2 2000/10/10 12:55:20 lukem Exp $
.
.so ../common/sysinst

4
distrib/notes/news68k/legal
View File

@ -1,2 +1,2 @@
.\" $NetBSD: legal,v 1.1 2000/06/14 10:34:31 tsutsui Exp $
.\" $NetBSD: legal,v 1.2 2000/10/10 12:55:20 lukem Exp $
.

3
distrib/notes/news68k/whatis
View File

@ -1,3 +1,4 @@
.\" $NetBSD: whatis,v 1.1 2000/06/14 10:34:32 tsutsui Exp $
.\" $NetBSD: whatis,v 1.2 2000/10/10 12:55:20 lukem Exp $
.
This is the first public release of NetBSD for the Sony's m68k based
"NET WORK STATION" series of computers.

115
distrib/notes/news68k/xfer
View File

@ -1,114 +1,3 @@
.\" $NetBSD: xfer,v 1.1 2000/06/14 10:34:32 tsutsui Exp $
.\" $NetBSD: xfer,v 1.2 2000/10/10 12:55:20 lukem Exp $
.
NOTE: NetBSD/news68k \*V does not support any framebuffers (yet) so
you have to use serial console on installation procedure.
.Pp
No matter which installation medium you choose, you'll need to have a
1.44M floppy disk. You'll put the boot floppy image onto this disk,
which contains software to install
.Nx
system.
.Pp
If you are using a UN*X-like system (such as NEWS-OS or other
.Nx
machines) to write the floppy images to disks, you should use the
.Xr dd 1
command to copy the file system image(s)
(.fs file) directly to the raw floppy disk. It is suggested that you
read the
.Xr dd 1
manual page or ask your system administrator to determine the correct
set of arguments to use; it will be slightly different from system to
system, and a comprehensive list of the possibilities is beyond the
scope of this document.
.Pp
If you have some i386 machine which runs
.Tn DOS
and use them to write the floppy image(s) to floppy disk,
you can use the
.Li rawrite
utility, provided in the
.Pa i386/utilities
directory of the
.Nx
distribution. It will write a file system image (.fs file) to a floppy
disk.
.Pp
Though NetBSD/news68k uses the floppy disk to boot for the initial
installation, NetBSD/news68k kernel does not support any
floppy device. Some other machines or systems are still required
to write floppy images even after NetBSD/news68k have been installed.
.Pp
SCSI devices on NWS-12x0 machines are not supported (yet), so they
can only run NetBSD/news68k as diskless. No file transfer is
needed, and all you have to do is to prepare files on the server.
More information about diskless setting can be found at
.Lk http://www.netbsd.org/Documentation/network/netboot/
.Pp
The NEWS
.Tn PROM No Ns s
supports also tape boot and network boot, but NetBSD/news68k does not
support them currently.
.Pp
After the boot floppy is prepared, just type "bo fh" on the PROM prompt
to boot it.
.Pp
Installation is supported from several media types, including:
.Bl -bullet -compact
.It
NFS partitions
.It
FTP
.It
CD-ROM
.El
.Pp
The steps necessary to prepare the distribution sets
for installation depend on which installation medium you choose.
The steps for the various media are outlined below.
.Pp
.Bl -tag -width NFS\ Installation
.
.It Em NFS Installation
Place the NetBSD distribution sets you wish to install into a directory
on an NFS server, and make that directory mountable by the machine
on which you are installing or upgrading NetBSD. This will probably
require modifying the
.Pa /etc/exports
file on of the NFS server and resetting its mount daemon (mountd).
Both of these actions will probably require superuser
privileges on the server.
.Pp
You will need to know the IP address of your nameserver or of your NFS
server, and, if the server is not on a network directly connected to the
machine on which you're installing or upgrading NetBSD, you need to know
the IP address of the closest router . Finally, you need to know the IP
address of the NetBSD machine itself. The install program will ask you
to provide this information to be able to access the sets via NFS.
.Pp
If you are using a diskless setup to install NetBSD on your machine,
you can take advantage of the fact that the above has already been done
on your machine's server. So, you can conveniently put the NetBSD file
sets in your machine's root filesystem on the server where the install
program can find them.
.Pp
Once the NFS server is set up properly and you have the information
mentioned above, you can start the actual installation process.
.
.It Em FTP Installation
Determine an FTP site from which you can retrieve the NetBSD
distribution when you're about to install. You will need to know the
IP address of your nameserver or of your ftp site, and, if it's not on
a network directly connected to the machine on which you're installing
or upgrading NetBSD, you need to know the IP address of the closest
router. Finally, you need to know the IP address of the NetBSD machine
itself. The install program will ask you to provide this information to
be able to access the sets via ftp.
.Pp
Once you have this information, you can proceed to the actual
installation.
.
.It Em CD-ROM Installation
If you are installing from a CD-ROM, the distribution sets are
already in the proper format and no special handling is required.
.El
.so ../common/xfer

82
distrib/notes/next68k/hardware
View File

@ -1,42 +1,50 @@
.\" $NetBSD: hardware,v 1.1 1999/04/24 18:47:14 dbj Exp $
NetBSD/next68k \*V will run on 68040-based non-turbo NeXT workstations.
.\" $NetBSD: hardware,v 1.2 2000/10/10 12:55:20 lukem Exp $
.
.Nx*M
\*V will run on 68040-based non-turbo
.Tn NeXT
workstations.
This include the NeXTstation and NeXTstation Color slabs, and the
non-Turbo NeXT Cube. NetBSD/next68k does not currently support 68030
machines or Turbo (33 MHz) machines. NetBSD/next68k \*V does not
non-Turbo NeXT Cube.
machines or Turbo (33 MHz) machines.
.Nx*M
\*V does not
have complete scsi support, so installations must use a remote NFS
filesystem.
.
.Ss2 Supported hardware
.(bullet -offset indent
CPUs
.(bullet -compact
68030-based: none.
.It
68040-based: NeXTstation, NeXTstation color, NeXT Cube.
.bullet)
.It
RS232 interfaces
.(bullet -compact
built in A and B serial ports (zsc).
.bullet)
.It
Network interfaces:
.(bullet -compact
built in ethernet (xe).
.bullet)
.It
Displays
.(bullet -compact
NeXT monochrome display (nextdisplay).
.bullet)
.It
Input devices
.(bullet -compact
NeXT non-adb keyboard (nextkbd).
.bullet)
.It
Miscellaneous
.(bullet -compact
Battery-backed real-time clock.
.bullet)
.bullet)
.Pp
The following NeXT hardware is supported:
.de section
. El
. Pp
. It Em \\$*
. br
. Bl -bullet -compact
..
.de item
. It
\\$*
..
.Bl -tag -width Disks
. It Em CPUs:
. br
. Bl -bullet -compact
. item 68030-based: none.
. item 68040-based: NeXTstation, NeXTstation color, NeXT Cube.
. section RS232 interfaces:
. item built in A and B serial ports (zsc).
. section Network interfaces:
. item built in ethernet (xe).
. section Displays:
. item NeXT monochrome display (nextdisplay).
. section Input devices:
. item NeXT non-adb keyboard (nextkbd).
. section Miscellaneous:
. item Battery-backed real-time clock.
. El
.El
.Pp
.Bl -tag -width (***)
.El
If it's not on this list, there is no official support for it in this release.

15
distrib/notes/next68k/install
View File

@ -1,4 +1,4 @@
.\" $NetBSD: install,v 1.2 2000/10/03 22:43:37 lukem Exp $
.\" $NetBSD: install,v 1.3 2000/10/10 12:55:20 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -32,7 +32,8 @@
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
Begin by creating an area in the server's filesystem for the
NetBSD/next68k image. This area must be exported read-write to the NeXT
.Nx*M
image. This area must be exported read-write to the NeXT
workstation. In the simplest form of installation, the entire image is
exported as a single partition, mounted on / by the target. This
corresponds to a local disk install with just one partition. It is also
@ -41,10 +42,11 @@ exported read-only, and multiple machines can all share the same /usr
partition.
.Pp
To extract the sets into the exported area:
.Bd -literal -offset indent
.(disp
cd /path/to/exported/filesystem
pax -zrvpe -f /path/to/base.tgz
.Ed
.disp)
.Pp
and repeat for any other sets you wish to install. You'll almost
certainly need the etc.tgz set.
.Pp
@ -52,9 +54,10 @@ Edit the files in the etc directory to reflect reality. rc.conf and
fstab will certainly need to be edited.
.Pp
cd into the dev directory in the exported area and run
.Bd -literal -offset indent
.(disp
sh ./MAKEDEV all
.Ed
.disp)
.Pp
to create the various device nodes.
.Pp
Create an empty swap file, and place it somewhere where it can also

8
distrib/notes/next68k/legal
View File

@ -1,7 +1,5 @@
.\"$NetBSD: legal,v 1.1 1999/04/24 18:47:14 dbj Exp $
.\" $NetBSD: legal,v 1.2 2000/10/10 12:55:20 lukem Exp $
.
This product includes software developed by Darrin B. Jewell.
.Pp
This product includes software developed by Matt DeBergalis.
This product includes software developed by Rolf Grossmann.

7
distrib/notes/next68k/prep
View File

@ -1,3 +1,6 @@
.\" $NetBSD: prep,v 1.1 1999/04/24 18:47:15 dbj Exp $
No preparation is necessary, since the NetBSD/next68k sets must be
.\" $NetBSD: prep,v 1.2 2000/10/10 12:55:20 lukem Exp $
.
No preparation is necessary, since the
.Nx*M
sets must be
installed on a server.

5
distrib/notes/next68k/upgrade
View File

@ -1,4 +1,4 @@
.\" $NetBSD: upgrade,v 1.1 1999/04/24 18:47:15 dbj Exp $
.\" $NetBSD: upgrade,v 1.2 2000/10/10 12:55:20 lukem Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -31,4 +31,5 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
NetBSD/\*m does not currently support an upgrade procedure.
.Nx*M
does not currently support an upgrade procedure.

3
distrib/notes/next68k/whatis
View File

@ -1,3 +1,4 @@
.\" $NetBSD: whatis,v 1.1 1999/04/24 18:47:15 dbj Exp $
.\" $NetBSD: whatis,v 1.2 2000/10/10 12:55:21 lukem Exp $
.
This is the first public release of NetBSD for the NeXT series of
computers.

20
distrib/notes/next68k/xfer
View File

@ -1,6 +1,6 @@
.\" $NetBSD: xfer,v 1.1 1999/04/24 18:47:15 dbj Exp $
.\" $NetBSD: xfer,v 1.2 2000/10/10 12:55:21 lukem Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -31,14 +31,18 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
Because NetBSD/next68k must run diskless, the distribution must be
Because
.Nx*M
must run diskless, the distribution must be
installed to a remote machine that NFS exports to the NeXT machine. As
a result, there is no automated install procedure. Begin by retrieving
the netbsd set files onto the serving machine. These can be found at
ftp.NetBSD.ORG. You may want to keep the following information handy:
.Bd -ragged
IP Address: ftp.NetBSD.ORG
the
.Nx
set files onto the serving machine. These can be found at
ftp.netbsd.org. You may want to keep the following information handy:
.(disp
IP Address: ftp.netbsd.org
Login: anonymous
Password: \*<your e-mail address\*>
Server path: /pub/NetBSD/NetBSD-_VER/next68k/binary/sets
.Ed
.disp)

24
distrib/notes/pc532/hardware
View File

@ -1,36 +1,38 @@
.\" $NetBSD: hardware,v 1.6 1999/01/13 07:30:07 ross Exp $
.\" $NetBSD: hardware,v 1.7 2000/10/10 12:55:21 lukem Exp $
.
NetBSD/pc532 \*V runs on a
.Nx*M
\*V runs on a
.Tn PC532
computer. It supports a subset of the
.Dq standard
hardware to date. This is defined as:
.Bl -bullet
.It
4 - MB of memory
.(bullet -compact
4 MB of memory
.It
8 serial lines done by 4 scn2681 chips
.It
the NCR DP8490 SCSI chip (scsi only)
.Bl -hyphen
.It
.(bullet -compact
Most SCSI disks work (fixed and floppy)
.It
A few SCSI tapes work
.It
Some SCSI CD-ROM drives work
.El
.bullet)
.It
The Matthias Pfaller Parallel Port.
.El
.bullet)
.Pp
NetBSD/pc532 currently expects the ROM monitor to be the "autoboot
.Nx*M
currently expects the ROM monitor to be the "autoboot
monitor" of Oct/Nov 1991. It includes support to set up auto booting
of NetBSD, including a secondary boot program that the autoboot monitor
will load that in turn loads the NetBSD kernel from a NetBSD file system.
Source and ROM images of the autoboot monitor are located at
.Lk ftp://ftp.cs.wwu.edu/pub/pc532/mon.auto.tar.gz
.Pp
Most of the pc532 specific development of NetBSD/pc532 was done on a
Most of the pc532 specific development of
.Nx*M
was done on a
machine with 8 MB of memory. It should run with 4 MB of memory
although it may be slower.

78
distrib/notes/pc532/install
View File

@ -1,4 +1,4 @@
.\" $NetBSD: install,v 1.12 2000/10/03 22:32:33 lukem Exp $
.\" $NetBSD: install,v 1.13 2000/10/10 12:55:21 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -32,11 +32,17 @@
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.
(IF you already have NetBSD/pc532 installed and you only want to update
(If you already have
.Nx*M
installed and you only want to update
your system, see the next section.)
.Pp
To install NetBSD/pc532, there are several things you need to know.
First, NetBSD "autoconfigs" the scsi devices.
To install
.Nx*M ,
there are several things you need to know.
First,
.Nx
"autoconfigs" the scsi devices.
.Pa floppy-144.fs
has only
support for disks configured into the kernel. Starting the search at
@ -60,8 +66,7 @@ kernel.
Next you need to know what the install script wants to do. This install
is script on the ram disk root that can do most of the work of configuring
your disk.
.Bl -enum
.It
.(enum
The script assumes your are using the first n sectors of your
disk, where you can specify n. It will allow you to create
up to 5 file system partitions, one swap partition and one
@ -78,10 +83,10 @@ preserving what is there. Then, later you can make a new
file system after you no longer need the stuff there. You
will need to do only one boot to get things working from
the disk.
.El
.Ss2 The Install Procedure:
.Bl -enum
.It
.enum)
.
.Ss2 The install procedure
.(enum
Adjust your console device settings.
The floppy-144.fs kernel will come up with 9600 baud, 7 bits,
even parity and one stop bit. Adjust your terminal to match
@ -91,30 +96,30 @@ these settings. The monitor's baud rate can be changed with
.It
Get floppy-144.fs and boot the kernel from...
.
. Bl -tag -width Serial\ line
. It Em Floppy
.(tag Serial\ line
.It Em Floppy
From Floppy: (and using the autoboot monitor)
If you have a 1.44 meg SCSI floppy drive, you can put floppy-144.fs
onto a 3.5" floppy disk. Insert the disk into your floppy
drive and use the monitor's boot command to boot the default
image from the floppy. The image booted will ask you for a
kernel to load. Answer
. Dl Ic sd Ns Ar x Ns Ic a:/netbsd
.Dl Ic sd Ns Ar x Ns Ic a:/netbsd
Replace
. Ar x
.Ar x
with your drive number. For KLONDIKE,
. Ar x No would be Ic 2 .
.Ar x No would be Ic 2 .
.
. It Em Tape
.It Em Tape
You will need to load a copy of
. Pa floppy-144.fs
.Pa floppy-144.fs
into RAM.
. Dl No \-\ load\ the Pa floppy-144.fs No at\ 0x260000
. Dl No \-\ run at 0x3BE020
.Dl No \-\ load\ the Pa floppy-144.fs No at\ 0x260000
.Dl No \-\ run at 0x3BE020
The boot program will ask you now for a kernel to load. Answer
. Ic md0a:/netbsd.gz
.Ic md0a:/netbsd.gz
.
. Em Serial Line
.Em Serial Line
Provided with the distribution is source for program called
download. (download.c) This program when used as
"download file" will read the contents of the file and
@ -123,15 +128,18 @@ ROM monitor to download a binary file into RAM. Using this
program on a computer connected to the pc532, one can
load a copy of floppy-144.fs into RAM at 0x260000. The boot
sequence is now the same as with tape.
. El
.tag)
.It
The floppy-144.fs will run the new sysinst utility as the standard
setup. It assumes a VT100 compatible terminal. If you don't want
to try using sysinst or you dont' have a VT100, type f followed by
the return. Then following these instructions for installation.
If you want to use sysinst, read the i386 INSTALL instructions to
learn about sysinst. Note: sysinst does not support SLIP or PPP
learn about sysinst.
.(Note
Sysinst does not support SLIP or PPP
connections.
.Note)
.It
Choose a disk geometry. For me, the reported geometry left
some sectors "unallocated". That is, the autoconfig message
@ -171,7 +179,7 @@ the auto-boot monitor), your root partition, your swap partition,
and then any other partitions you may want. For the "other"
partitions, it will ask for a mount point. The mount point will
be "relative to /" and should not include the leading "/". Also,
IF you do not want the partition to have newfs run on it (that is
If you do not want the partition to have newfs run on it (that is
it might be the last one and have a copy of floppy-144.fs) enter "NO"
to the mount point and it will not run newfs on the partition.
It will enter the partition into the disklabel.
@ -185,15 +193,16 @@ You can get it to do it faster by pressing return.
.Pp
If you are not using the autoboot monitor, you will have to
figure out the starting sector of the boot images partition
and manually load the NetBSD boot loader from the disk using
and manually load the
.Nx
boot loader from the disk using
the read command. If you would rather use the autoboot monitor
you can get source and ROM images from the URL
.Lk ftp://ftp.cs.wwu.edu/pub/pc532/mon.auto.tar.gz
.It
Now it is time to load all the other files of the distribution:
You can do this via --
.Bl -bullet
.It
.(bullet
a TCP/IP link (slip, ppp or plip)
you have ifconfig, slattach, route, netstat,
hostname and ftp on the mini-root. You can even
@ -207,7 +216,9 @@ floppy disk
.It
tape
.It
cd-rom (If you have a CD with NetBSD/532, which most likely
cd-rom (If you have a CD with
.Nx*M ,
which most likely
won't happen for a while after \*V release.)
.Dl Ic mount -rt cd9660 /dev/cd0a /mnt
Get the .tgz files from the cd-rom
@ -218,7 +229,7 @@ can be used as the receive end of the download by
using it as "download -r file_to_write". If the CRC is
correct, the file is retained. If the CRC is not
correct, the file is deleted.
.El
.bullet)
.It
Load the .tgz files. Choose a place to put them. I would make
a directory /gz.files and put them there. If you are "short
@ -246,7 +257,7 @@ For "update" extracts, move /etc to /etc.old and then extract
installations, extract all files.
.It
Edit the information in /etc
.Bl -tag -width resolv.conf
.(tag resolv.conf
.It rc.conf
Many things can be configured here
.It hosts
@ -260,7 +271,7 @@ I find "ap" instead of "ep" in the default entry
works better for me.
.It fstab
make sure it includes all partitions you want mounted
.El
.tag)
.Pp
Now you can adjust the kernel's default baud rate to match your
monitor's default baud rate. Do the following:
@ -276,5 +287,6 @@ not be able to reboot... So be carefull!
Reboot the machine and it should come up in multi-user mode *IF*
you got it configured correctly.
.It
Enjoy! And help fix bugs and improve NetBSD/pc532!
.El
Enjoy! And help fix bugs and improve
.Nx*M !
.enum)

55
distrib/notes/pc532/legal
View File

@ -1,22 +1,14 @@
.\" $NetBSD: legal,v 1.4 1999/01/13 07:30:07 ross Exp $
.\" $NetBSD: legal,v 1.5 2000/10/10 12:55:21 lukem Exp $
.
This product includes software developed by the Alice Group.
.Pp
This product includes software developed by Philip L. Budne.
This product includes software developed by Christopher G. Demetriou.
This product includes software developed by Philip A. Nelson.
This product includes software developed by Matthias Pfaller.
.Pp
This product includes software at the Helsinki University of
Technology.
.Em Some files have the following copyright:
Technology.
.Pp
Some files have the following copyright:
.(item -offset indent
Copyright (c) 1992 Helsinki University of Technology
All Rights Reserved.
@ -30,11 +22,10 @@ HELSINKI UNIVERSITY OF TECHNOLOGY ALLOWS FREE USE OF THIS SOFTWARE IN
ITS "AS IS" CONDITION. HELSINKI UNIVERSITY OF TECHNOLOGY DISCLAIMS ANY
LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE
USE OF THIS SOFTWARE.
.Em At least one file contains:
.item)
.Pp
At least one file contains:
.(item -offset indent
Copyright 1990 by Open Software Foundation,
Grenoble, FRANCE
@ -56,12 +47,10 @@ CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
LOSS OF USE, DATA OR PROFITS, WHETHER IN ACTION OF CONTRACT,
NEGLIGENCE, OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
.Em Some files have the following copyright:
.item)
.Pp
Some files have the following copyright:
.(item -offset indent
Mach Operating System
Copyright (c) 1992 Carnegie Mellon University
Copyright (c) 1992 Helsinki University of Technology
@ -85,15 +74,14 @@ School of Computer Science
Carnegie Mellon University
Pittsburgh PA 15213-3890
any improvements or extensions that they make and grant Carnegie Mellon
any improvements or extensions that they make and grant Carnegie Mellon
the rights to redistribute these changes.
.Em The IEEE floating point support in
.item)
.Pp
The IEEE floating point support in
.Pa /usr/src/sys/arch/pc532/fpu
.Em has the following copyright:
has the following copyright:
.(item -offset indent
IEEE floating point support for NS32081 and NS32381 fpus.
Copyright (c) 1995 Ian Dall
All Rights Reserved.
@ -107,3 +95,4 @@ thereof, and that both notices appear in supporting documentation.
IAN DALL ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS" CONDITION.
IAN DALL DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES
WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
.item)

2
distrib/notes/pc532/prep
View File

@ -1,4 +1,4 @@
.\" $NetBSD: prep,v 1.3 1999/01/13 07:30:07 ross Exp $
.\" $NetBSD: prep,v 1.4 2000/10/10 12:55:21 lukem Exp $
.
The major preparation needed is to make sure you can recover any
current bits stored on your pc532. If you don't care about your

22
distrib/notes/pc532/upgrade
View File

@ -1,6 +1,6 @@
.\" $NetBSD: upgrade,v 1.9 1999/01/25 23:34:23 garbled Exp $
.\" $NetBSD: upgrade,v 1.10 2000/10/10 12:55:21 lukem Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -32,7 +32,9 @@
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.
The upgrade to NetBSD \*V is a binary upgrade; it can be quite difficult
The upgrade to
.Nx
\*V is a binary upgrade; it can be quite difficult
to advance to a later version by recompiling from source due primarily
to interdependencies in the various components.
.Pp
@ -43,12 +45,12 @@ of disk space to do the upgrade.
Since upgrading involves replacing the kernel, and most of the system
binaries, it has the potential to cause data loss. You are strongly
advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the
NetBSD partition or on another operating system's partition, before
.Nx
partition or on another operating system's partition, before
beginning the upgrade process.
.Pp
To upgrade your system, follow the following instructions:
.Bl -bullet
.It
.(bullet
Assuming you have space, load the .tgz files onto disk
some place. Then boot the floppy-144.fs image via the
method you use. Under the install system, extract the
@ -57,12 +59,14 @@ notes for how to use sysinst.
.It
Extract the .tgz files.
For example, to extract base.tgz:
.Dl Ic cd /
.Dl Ic cd /
.Dl Ic pax -zrvpe -f /gz.files/base.tgz
.It
Extract all the .tgz files you want. You should carefully
work at upgrading /etc. There may be changes to file formats
depending on what version of NetBSD/pc532 you are running.
depending on what version of
.Nx*M
you are running.
.It
.Em Be careful if you are not running with security.
The \*V distribution does contain support for password encryption.
@ -77,4 +81,4 @@ kernel. Read the last part of the new installation part of
these notes to find out how to change your default speed.)
.It
After reboot, you should make sure you check your new file systems.
.El
.bullet)

7
distrib/notes/pc532/whatis
View File

@ -1,12 +1,11 @@
.\" $NetBSD: whatis,v 1.5 1999/01/13 07:30:08 ross Exp $
.\" $NetBSD: whatis,v 1.6 2000/10/10 12:55:21 lukem Exp $
.
For the pc532 port, there are a few known problems. They include:
.Bl -enum
.It
.(enum
ppp reports a lot of input errors on some machines.
.It
Some tape drives do not work very well. Some have hung the system.
.It
The serial drivers do not have all the desired features. (ttyflags
is the most glaring omission.)
.El
.enum)

27
distrib/notes/pc532/xfer
View File

@ -1,6 +1,8 @@
.\" $NetBSD: xfer,v 1.4 1999/01/13 07:30:08 ross Exp $
.\" $NetBSD: xfer,v 1.5 2000/10/10 12:55:21 lukem Exp $
.
The "standard" method of getting NetBSD/pc532 onto your pc532 is
The "standard" method of getting
.Nx*M
onto your pc532 is
via the console terminal and using the downloading parts of the
ROM monitor. As such, usually another computer has the distribution
on disk and is connected via a serial line to your pc532's console
@ -12,12 +14,21 @@ sends data to the ROM monitor over the serial line.
You may need to find and read the documentation about the ROM monitor
download command and other low level comands.
.Pp
Other methods of getting NetBSD/pc532 on your pc532 may include
Other methods of getting
.Nx*M
on your pc532 may include
SCSI tape or SCSI floppy disk or cloning a disk on a system
already running NetBSD/pc532.
already running
.Nx*M .
.Pp
If you have some operating system already running on your pc532,
you can use that OS to get NetBSD/pc532 on a hard disk much easier than
with the ROM monitor. (NetBSD/pc532 was developed from Minix/pc532
until it was self hosting. You can run NetBSD and Minix or other OS
off the same disk.)
you can use that OS to get
.Nx*M
on a hard disk much easier than
with the ROM monitor.
.Nx*M
was developed from Minix/pc532
until it was self hosting. You can run
.Nx
and Minix or other OS
off the same disk.

7
distrib/notes/pmax/QUICK.INSTALL
View File

@ -1,6 +1,6 @@
Guide for the Impatient
-----------------------
$NetBSD: QUICK.INSTALL,v 1.2 1998/11/16 07:58:38 simonb Exp $
$NetBSD: QUICK.INSTALL,v 1.3 2000/10/10 12:55:21 lukem Exp $
NetBSD 1.3.3 includes the install materials on CD. However, we cannot
make a single CD bootable on a dozen systems, so the CD cannot be
@ -30,7 +30,8 @@ your swap partition (for example a 16MB root filesystem but a 48MB
swap partition), you can move the start of the swap partition forward
and leave a "gap" between the existing root filesystem and the swap
partition. If you have any questions, send them to the NetBSD/pmax
mailling list at port-pmax@NetBSD.ORG .
mailling list at
.Mt port-pmax@netbsd.org .
Under Ultrix, do:
@ -49,7 +50,7 @@ Under Ultrix, do:
PATH=$PATH:/cdrom/NetBSD-1.3/pmax/installation/misc; export PATH
# Check that your swap partition is at least 32Mbytes
chpt -q /dev/rz0c
chpt -q /dev/rz0c
# Look at the "b" partition, you'll need at least 65536 blocks
# Put the netbsd kernel on the root filesystem

130
distrib/notes/pmax/hardware
View File

@ -1,11 +1,12 @@
.\" $NetBSD: hardware,v 1.11 2000/08/25 23:56:08 jhawk Exp $
.\" $NetBSD: hardware,v 1.12 2000/10/10 12:55:21 lukem Exp $
.
NetBSD/pmax \*V runs on the following classes of machines:
.Bl -bullet -compact
.It
.Ss2 Supported machines
.(bullet -offset indent
DECstation 2100 and 3100, also known as
.Em pmin No and Em pmax
.It
DECsystem 5100
.It
Personal DECstations (5000/20, /25 and /33) also known as
.Em MAXINE
.It
@ -21,121 +22,106 @@ DECstation 5000/240 and DECsystem 5900, also known as
DECstation 5000/50, 5000/150, 5000/260 (and DECsystem 5900-260) \- R4000
and R4400 variants of the
.Em MAXINE, 3MIN No and Em 3MAXPLUS
.El
.Pp
NetBSD/pmax \*V does
.Em not
(yet) run on these machines:
.Bl -bullet -compact
.It
DECsystem 5100 (an r3000-based cousin of the DECstation 3100)
.It
DECsystem 5400 and 5500 (Qbus-based systems, similar to the Vax
.bullet)
.
.Ss2 Unsupported machines
.(bullet -offset indent
DECsystem 5400 and 5500 (Q-bus based systems, similar to the Vax
.Em Mayfair No \&or Em Mayfair II ,
but with an r2000a or r3000 cpu instead of a CVAX cpu.)
.It
DECsystem 5800 (xbi-based multiprocessor, a Vax 6200 with
Vax CPU boards replaced with Mips cpu boards)
.El
.bullet)
.Pp
The minimal configuration requires 8M of RAM and ~60M of disk space.
The minimal configuration requires 8 MB of RAM and ~60 MB of disk space.
To install the entire system requires much more disk space, and to run
X or compile the system, more RAM is recommended. (NetBSD with 8M of
RAM feels like Ultrix with 8M of RAM.) Note that until you have
around 16M of RAM, getting more RAM is more important than getting a
faster CPU.
.Pp
Supported devices include:
.Bl -bullet -compact
.It
X or compile the system, more RAM is recommended, as
.Nx
with 8 MB of RAM feels like Ultrix with 8 MB of RAM - slow.
Note that until you have around 16 MB of RAM, getting more RAM is more
important than getting a faster CPU.
.
.Ss2 Supported devices
.(bullet -offset indent
DECstation 2100 and 3100 baseboard video
. Bl -hyphen -compact
. It
one-bit mono or 8-bit pseudocolour frame buffers.
. El
.(bullet -compact
one-bit mono or 8-bit pseudocolor frame buffers.
.bullet)
.It
DECstation 5000 series TurboChannel video
. Bl -hyphen -compact
. It
.(bullet -compact
PMAG-DV Personal DECstation baseboard 1024x768 frame buffer
. It
PMAG-BA 1024x768 8-bit colour frame buffer
. It
PMAGB-BA 1024x768 8-bit colour frame buffer
. It
.It
PMAG-BA 1024x768 8-bit color frame buffer
.It
PMAGB-BA 1024x768 8-bit color frame buffer
.It
PMAG-AA 1280x1024 four-bit greyscale frame buffer
. It
.It
PMAG-C (PX) 2D 8-bit accelerated frame buffer.
. It
.It
PMAG-D (PXG) 3D 8-bit accelerated frame buffer.
. It
.It
PMAG-E (PXG+) 3D 24-bit accelerated frame buffer.
. It
.It
PMAG-F (PXG+ Turbo) 3D 24-bit accelerated frame buffer.
. El
. (Note
.bullet)
.(Note
All supported DECstation video produces sync-on-green.
Be sure to use either a DEC-compatible fixed-sync monitor
or a multisync monitor that supports sync-on-green.
. Note)
.Note)
.It
serial ports:
. Bl -hyphen -compact
. It
Serial ports
.(bullet -compact
ttya and ttyb (can be used as console if needed)
. El
.bullet)
.It
ethernet:
. Bl -hyphen -compact
. It
Ethernet
.(bullet -compact
on-board AMD Lance ethernet
.Pq Em le0 ,
. It
.It
TURBOchannel AMD Lance ethernet cards
.Pq the Em PMAD
. El
.bullet)
.It
SCSI:
. Bl -hyphen -compact
. It
SCSI
.(bullet -compact
on-board DEC
.Em sii
SCSI controller (2100 and 3100)
. It
.It
on-board
.Em asc
SCSI controller (5000 series machines)
. It
.It
TurboChannel
.Em asc No SCSI controller
.Pq the Em PMAZ
. El
.bullet)
.It
DEC (LK-201 or compatible) keyboard
DEC (LK-201 or compatible) keyboard
.It
DEC
.Em hockey puck
or compatible mouse
.El
.Pp
Hardware the we do
.Em not
currently support, but get questions about from time to time:
.Bl -bullet -compact
.It
Q-bus DECsystem machines
.It
DECsystem 5100 machines
.bullet)
.
.Ss2 Unsupported devices
.(bullet -offset indent
Q-bus based DECsystems
.It
PrestoServe NVRAM on DECsystem 5100 and 5000/2xx machines
.It
audio drivers for Personal DECstation machines
Audio drivers for Personal DECstation machines
.It
floppy driver for Personal DECstation machines
Floppy driver for Personal DECstation machines
.It
TurboChannel audio hardware (LoFi)
.El
.bullet)
.(Note
The primary obstacle to supporting the above is non-availability of sample
The primary obstacle to supporting the above is non-availability of sample
hardware for development.
.Note)

Some files were not shown because too many files have changed in this diff Show More