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

update.

This commit is contained in:
oki 1996-08-15 09:15:06 +00:00
parent 1ab419ba00
commit b57279a974
3 changed files with 27 additions and 56 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
distrib/notes/x68k/contents
View File

@ -32,15 +32,15 @@ Installation floppy:
This disk contains the software necessary to prepare your hard
drive for NetBSD and install the NetBSD distribution. It is
not bootable, and must be used in conjunction with one of the
kernel-copy floppies. This floppy is named "inst12.fs".
not bootable, and must be used in conjunction with the kernel-
copy floppy. This floppy is named "inst12.fs".
Upgrade floppy:
This disk contains the software to be used in upgrading the
system from a previous version of NetBSD. It is not bootable,
and must be used in conjunction with one of the kernel-copy
floppies. This floppy is named "upgr12.fs".
and must be used in conjunction with the kernel-copy floppy.
This floppy is named "upgr12.fs".
The NetBSD/x68k binary distribution sets contain the binaries which
comprise the NetBSD 1.2 release for the x68k. There are seven binary
@ -97,7 +97,7 @@ distribution tree, and are as follows:
[ 0.8M gzipped, 2.9M uncompressed ]
For other platform, there is a security distribution named "secr12"
is provided. It contains the files which cannot be exported outside
provided. It contains the files which cannot be exported outside
the United States and Canada. Since all the developers of the NetBSD/x68k
live in Japan, the x68k security distribution is not provided in the
binary form.

9
distrib/notes/x68k/hardware
View File

@ -1,19 +1,18 @@
NetBSD/x68k 1.2 runs on the Sharp X68030 series PCs with TRUE
MC68030 MPU (not MC68EC030) and FPU. Since the processor of
the X68030 series is MC68EC030RC25, you need to replace it
with MC68030RC25 (Simply remove the old chip and put the new one
the X68030 series is MC68EC030, you need to replace it with
MC68030 (Simply remove the old chip and put the new one instead.
instead. The largest difficulty might be to open your X68030).
In addition, some accelerators are supported:
Xellent030
Xellent030S
Xellent30 series
040turbo
Jupiter-X (040 / 060)
This means all models of X680x0 series PC except for CZ-600C
and CZ-674C, by using the appropriate accelerator, can run NetBSD!!
Note that the processor of Xellent030 series is MC68EC030, so
Note that the processor of Xellent30 series is MC68EC030, so
you need to replace your processor as well as for X68030.
The minimal configuration requires 4M of RAM and about 65M of

64
distrib/notes/x68k/install
View File

@ -303,57 +303,29 @@ process again from scratch.
probably pick a directory under /mnt/usr.) The
default is /mnt/usr/distrib.
Configure the appropriate ethernet interface (e.g.
ed0, ep0, etc.) up, with a command like:
Configure the SLIP interface, with the following
command sequence:
ifconfig <ifname> <ipaddr> [netmask <netmask>]
slattach -h -s <speed> tty00
ifconfig sl0 <my_ipaddr> <peer_ipaddr>
where "<ifname>" is the interface name, like those
listed above, and "<ipaddr>" is the numeric IP address
of the interface. If the interface has a special
netmask, supply the word "netmask" at and that netmask
at the end of the command line. (The brackets
indicate that those arguments are optional.) For
instance, to configure interface ed0 with IP address
129.133.10.10, use the command:
where "<speed>" is the network speed, and "<my_ipaddr>"
is the numeric IP address of the machine you are going
to install NetBSD/x68k, while "<peer_ipaddr>" is the
address of the peer machine connected with your machine.
You might have to configure the peer SLIP interface
with similar sequence (depending on the peer system).
ifconfig ed0 129.133.10.10
For instance, the sequence
and to configure interface ep0 with IP address
128.32.240.167 and a special netmask, 0xffffff00, use
the command:
slattach -h -s 38400 tty00
ifconfig sl0 192.168.0.1 192.168.0.10
ifconfig ep0 128.32.240.167 netmask 0xffffff00
If your board selects software selection of the
ethernet interface to use, you might have to add
special flags to the "ifconfig" command you use.
Consult the table below for the appropriate flags:
Interface Type Connector Flags
--------- ---- --------- -----
ed with WD/SMC* BNC [none necessary]
ed with WD/SMC* UTP [none necessary]
ed with WD/SMC* AUI link0
* Older WD boards do not support software configuration,
and must be configured via jumpers. These flags
will have no effect on them.
In other words, if, in the last example, the AUI port
of the board were being used, you would use the
command:
ifconfig ep0 128.32.240.167 netmask 0xffffff00 link0
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:
route add default <gate_ipaddr>
where <gate_ipaddr> is your gateway's numeric IP
address.
configures the SLIP interface for the network between
your machine (with IP address 192.168.0.1) and the peer
(192.168.0.10) with speed 38400 bps. Note that IP
addresses 192.168.*.* are the private IP addresses
described in RFC 1597.
If you are NFS-mounting the distribution sets, mount
them on the temporary directory with a command like: