hp300 port notes
This commit is contained in:
glass
parent
851fbeb2f3
commit
6af2a2fb60
|
|
@ -0,0 +1,91 @@
|
|||
The hp300-specific portion of the NetBSD 1.0 release is found in the
|
||||
"hp300" subdirectory of the distribution. That subdirectory is layed
|
||||
out as follows:
|
||||
|
||||
.../NetBSD-1.0/hp300/
|
||||
binary/ hp300 binary distribution sets;
|
||||
see below.
|
||||
|
||||
install/ installation utilities and
|
||||
bootstrap root filesystem
|
||||
image; see below.
|
||||
|
||||
security/ hp300 security distribution;
|
||||
see below;
|
||||
|
||||
The NetBSD/hp300 binary distribution sets contain the binaries which
|
||||
comprise the NetBSD 1.0 release for the hp300. There are seven binary
|
||||
distribution sets, and the "security" distribution set. The binary
|
||||
distribution sets can be found in the "hp300/binary" subdirectory of
|
||||
the NetBSD 1.0 distribution tree, and are as follows:
|
||||
|
||||
base10 The NetBSD/hp300 1.0 base binary distribution. You
|
||||
MUST install this distribution set. It contains the
|
||||
base NetBSD utilities that are necessary for the
|
||||
system to run and be minimally functional. It
|
||||
includes shared library support, and excludes
|
||||
everything described below.
|
||||
[ 6.1M gzipped, 16.3M uncompressed ]
|
||||
|
||||
comp10 The NetBSD/hp300 Compiler tools. All of the tools
|
||||
relating to C, C++, and FORTRAN (yes, there are two!).
|
||||
This set includes the system include files
|
||||
(/usr/include), the linker, the compiler tool chain,
|
||||
and the various system libraries (except the shared
|
||||
libraries, which are included as part of the base
|
||||
set). This set also includes the manual pages for all
|
||||
of the utilities it contains, as well as the system
|
||||
call and library manual pages.
|
||||
[ 4.1M gzipped, 12.6M uncompressed ]
|
||||
|
||||
etc10 This distribution set contains the system
|
||||
configuration files that reside in /etc and in several
|
||||
other places. This set MUST be installed if you are
|
||||
installing the system from scratch, but should NOT be
|
||||
used if you are upgrading. (If you are upgrading,
|
||||
it's recommended that you get a copy of this set and
|
||||
CAREFULLY upgrade your configuration files by hand.)
|
||||
[ 51K gzipped, 290K uncompressed ]
|
||||
|
||||
games10 This set includes the games and their manual pages.
|
||||
[ 1.1M gzipped, 2.7M uncompressed ]
|
||||
|
||||
man10 This set includes all of the manual pages for the
|
||||
binaries and other software contained in the base set.
|
||||
Note that it does not include any of the manual pages
|
||||
that are included in the other sets.
|
||||
[ 752K gzipped, 2.9M uncompressed ]
|
||||
|
||||
misc10 This set includes the system dictionaries (which are
|
||||
rather large), the typesettable document set, and
|
||||
man pages for other architectures which happen to be
|
||||
installed from the source tree by default.
|
||||
[ 1.6M gzipped, 5.6M uncompressed ]
|
||||
|
||||
text10 This set includes NetBSD's text processing tools,
|
||||
including groff, all related programs, and their
|
||||
manual pages.
|
||||
[ 782K gzipped, 2.8M uncompressed ]
|
||||
|
||||
The hp300 security distribution set is named "secr10" and can be found
|
||||
in the "hp300/security" subdirectory of the NetBSD 1.0 distribution
|
||||
tree. It contains crypt.c (the source file for the DES encryption
|
||||
algorithm) and the binaries which depend on it. It can only be found
|
||||
on those sites which carry the complete NetBSD distribution and that
|
||||
can legally obtain it. (Remember, because of United States law, this
|
||||
distribution set may not be exported to locations outside of the
|
||||
United States and Canada.) [ 119K gzipped, 270K uncompressed ]
|
||||
|
||||
The hp300 binary distribution sets are distributed as gzipped tar files.
|
||||
Each hp300 binary distribution set also has its own "CKSUMS" file, just
|
||||
as the source distribution sets do.
|
||||
|
||||
The instructions given for extracting the source sets work equally
|
||||
well for the binary sets, but it is worth noting that if you use that
|
||||
method, the files are extracted "below" the current directory. That
|
||||
is, if you want to extract the binaries "into" your system, i.e.
|
||||
replace the system binaries with them, you have to run the "tar xvfp"
|
||||
from /. Also note that if you upgrade or install this way, those
|
||||
programs that you are using at the time will NOT be replaced. If you
|
||||
follow the normal installation or upgrade procedures, this will be
|
||||
taken care of for you.
|
||||
|
|
@ -0,0 +1,66 @@
|
|||
NetBSD/hp300 1.0 will run on most HP 9000/300 series machines.
|
||||
The lowest amount of RAM that has been tested is 7.5M, though it
|
||||
may run with less. Certainly, if you wish to run X, more RAM is
|
||||
recommended. Until you reach 16M, more RAM is more important than
|
||||
a faster CPU.
|
||||
|
||||
Here is a table of recommended HD partition sizes for a full install:
|
||||
partition: advise needed
|
||||
root (/) 15M 15M (see note below)
|
||||
user (/usr) 80M 45M
|
||||
swap ----- 2M for every 1M of RAM -----
|
||||
local (/local) up to you
|
||||
|
||||
NOTE: Because of the nature of the hp300 bootstrap procedure, the root
|
||||
filesystem is a _fixed_size_! You may want to consider placing /var and
|
||||
/tmp on their own partitions. This, of course is up to you and your
|
||||
judgement. Also, note that the recommended size of /usr is 15M greater
|
||||
than the needed size. This is to allow room for kernel source and
|
||||
compile areas, as you may want to compile your own kernel.
|
||||
|
||||
The following HP hardware is supported:
|
||||
|
||||
CPUs:
|
||||
68020-based: 318, 319, 320, 330, and 350.
|
||||
68030-based: 340, 345, 360, 370, 375, and 400.
|
||||
68040-based: 380, 425, and 433.
|
||||
|
||||
Disks:
|
||||
HP-IB/CS80: 7912, 7914, 7933, 7936, 7937, 7945, 7957,
|
||||
7958, 7959, 2200, and 2203.
|
||||
SCSI-I, including magneto-optical and CD-ROM. SCSI-II
|
||||
drives should work if they can talk SCSI-I.
|
||||
|
||||
Tape drives:
|
||||
Low-density CS80 cartridge: 7914, 7946, 9144.
|
||||
High-density CS80 cartridge: 9145.
|
||||
SCSI: HP DAT and Exabyte.
|
||||
|
||||
RS232 interfaces:
|
||||
98644 built-in single port (dca).
|
||||
98642 4-port (dcm).
|
||||
98638 8-port (dcm).
|
||||
|
||||
Network interfaces:
|
||||
98643 built-in and add-on LAN cards.
|
||||
|
||||
Displays:
|
||||
98544, 98545, and 98547 color and monochrome Topcat.
|
||||
98548, 98549, and 98550 color and monochrome Catseye.
|
||||
98700 and 98710 Gatorbox.
|
||||
98720 and 98721 Renaissance.
|
||||
98730 and 98731 DaVinci.
|
||||
A1096A monochrome Hyperion.
|
||||
|
||||
Input devices:
|
||||
General interface supporting all HIL devices: keyboard,
|
||||
2 and 3 button mice, and ID module.
|
||||
|
||||
Miscellaneous:
|
||||
Battery-backed real-time clock.
|
||||
98625A and 98625B built-in HP-IB interface.
|
||||
98658A built-in SCSI interface.
|
||||
Printers and plotters on RS232 and HP-IB.
|
||||
SCSI autochanger.
|
||||
|
||||
If it's not on this list, there is no support for it in this release.
|
||||
|
|
@ -0,0 +1,222 @@
|
|||
NOTE: In the following examples you will see references to
|
||||
disk devices. For those not familiar with NetBSD, the following
|
||||
prefixes are used to denote drive types:
|
||||
|
||||
sd SCSI disk
|
||||
rd HP-IB disk
|
||||
|
||||
In the examples that follow, `rd' will be used. The steps are
|
||||
exactly the same for `sd' disks. Only the names have changed
|
||||
to protect the innocent.
|
||||
|
||||
Assuming you have read this document thoroughly and kept good notes
|
||||
about your partitions, the rest should be fairly straight forward.
|
||||
|
||||
Before you begin, you must have already prepared the target disk
|
||||
as detailed in the section on preparing your system for install.
|
||||
|
||||
The following is a walk-through of the steps necessary to finish
|
||||
what the preparation process has already begun. You may choose to
|
||||
stop the process at any time, but if you do, it's recommended that
|
||||
you start over from scratch.
|
||||
|
||||
First you need to boot off of the target disk which
|
||||
you have made in the preparation process. To do this,
|
||||
halt HP-UX, power-cycle your machine, and hit the space
|
||||
bar during the boot ROM's probing/testing sequence.
|
||||
You should eventually be presented with a list of systems
|
||||
from which to boot. You want the one called `SYS_PBOOT'.
|
||||
|
||||
After selecting `SYS_PBOOT', your system should load the
|
||||
NetBSD boot block and ask you for a kernel to load.
|
||||
Enter the following to boot NetBSD into single-user mode.
|
||||
(Note: it will come into single-user anyway, as there is
|
||||
not yet an fstab, but this makes it happen more gracefully.)
|
||||
|
||||
netbsd -s
|
||||
|
||||
The kernel will now load, and configure your hardware.
|
||||
Make a note of the device it lists when mounting the
|
||||
root filesystem. It should look something like this:
|
||||
|
||||
Changing root device to rd0a
|
||||
|
||||
The message above is an example only. Your message may
|
||||
be different.
|
||||
|
||||
Check the root filesystem. Use the raw flavor of the
|
||||
device listed during the `Changing root device...'
|
||||
message. Example:
|
||||
|
||||
fsck -p /dev/rrd0a
|
||||
|
||||
Mount the root filesystem:
|
||||
|
||||
mount /dev/rd0a /
|
||||
|
||||
It's now time to newfs all of the other partitions you
|
||||
listed in your disk label. So, for example, if rd0e and
|
||||
rd0f were to have filesystems put on them, you would
|
||||
do the following:
|
||||
|
||||
newfs /dev/rrd0e
|
||||
newfs /dev/rrd0f
|
||||
|
||||
Ensure that the mount-points for these filesystems are clean.
|
||||
If these filesystems are to be /var and /usr, respectively,
|
||||
just check that there are no files in those directories.
|
||||
There shouldn't be. Once you've made sure, go ahead and
|
||||
mount those filesystems.
|
||||
|
||||
It's now time to get the distribution sets onto the root
|
||||
or other filesystem. There are several programs in /ibin
|
||||
to help you with this. At your disposal, you have:
|
||||
|
||||
ftp
|
||||
gzip
|
||||
tar
|
||||
extract
|
||||
|
||||
Except for extract, which is just a script to help the
|
||||
process along, these are statically-linked versions of
|
||||
themselves, which normally appear in /usr/bin.
|
||||
|
||||
If you placed the distribution sets on tape, go to the
|
||||
directory where you wish to temporarily place them and
|
||||
extract them from tape, using /dev/nrstX for SCSI tapes
|
||||
or /dev/nrctX for HP-IB cartridge tapes, where X is the
|
||||
unit number of the tape, probably 0.
|
||||
|
||||
tar xvf /dev/nrst0
|
||||
|
||||
If this extracts the sets directly into your current
|
||||
directory, terrific. Otherwise, go to the directory in
|
||||
which they live. Skip on to extracting the sets.
|
||||
|
||||
If you will be grabbing the sets off of the network somehow,
|
||||
configure your network interface:
|
||||
|
||||
ifconfig le0 inet <ipaddr> <netmask> <broadcast>
|
||||
route add default <addr-of-default-router>
|
||||
|
||||
If you will be ftp'ing the sets from one of the NetBSD ftp
|
||||
sites, go to the directory where you wish to temporarily
|
||||
place them and download them from the ftp site of your choice.
|
||||
Since you haven't yet created a resolv.conf, you'll need to
|
||||
use the IP address.
|
||||
|
||||
/ibin/ftp <ftp_ipaddr>
|
||||
|
||||
If you will be getting the sets from an NFS server, mount
|
||||
the filesystem on the server which has the sets, and go
|
||||
to the directory that has them. Again, you'll need to use
|
||||
the IP address of the server.
|
||||
|
||||
mount -t nfs <serv_ipaddr>:<server_dir> <mount_point>
|
||||
|
||||
At this point, you have everything necessary to label any
|
||||
additional disks that you wish to label. If you created
|
||||
additional labels in the preparation phase, and have
|
||||
access to them now, go ahead and label the disks they
|
||||
correspond to:
|
||||
|
||||
disklabel -W rd1
|
||||
disklabel -r -R rd1 rd1.label
|
||||
where:
|
||||
rd1 additional disk you wish to label
|
||||
rd1.label file containing disk label information
|
||||
|
||||
You may check these labels once they are on the disk:
|
||||
|
||||
disklabel -r rd1
|
||||
where:
|
||||
rd1 additional disk you wish to label
|
||||
|
||||
A problem with a partition (such as overlaps or not falling
|
||||
on a cylinder boundary) will be noted with a `*'. If you see
|
||||
these, re-edit your label by the method of your choice (on
|
||||
another machine, perhaps, or with ed(1), for the brave),
|
||||
transfer it to a place that's usable (if necessary) and
|
||||
label the disk again.
|
||||
|
||||
Once these disks have been labeled, you may newfs the
|
||||
partitions that are to contain filesystems and mount them.
|
||||
|
||||
You should now be ready to extract the filesets. The program
|
||||
/ibin/extract should help you with this. For example:
|
||||
|
||||
/ibin/extract base
|
||||
-or- /ibin/extract base.tar.gz
|
||||
|
||||
Do this for all of the filesets you wish to extract. As your disk
|
||||
fills up, you may wish to remove the sets once you have extracted
|
||||
them.
|
||||
|
||||
You should have everything necessary to use an editor by now.
|
||||
Set your TERM environment variable:
|
||||
|
||||
setenv TERM hp300h (csh)
|
||||
-or- export TERM=hp300h (sh)
|
||||
|
||||
hp300h is the terminal type for the HP 9000/300 ITE console.
|
||||
If you are using a serial console, change the TERM variable
|
||||
appropriately. Now, initialize the terminal:
|
||||
|
||||
tset
|
||||
|
||||
You should be able to use vi now.
|
||||
|
||||
Create an /etc/fstab. Example fstabs are provided in
|
||||
/etc/fstab.sd and /etc/fstab.rd.
|
||||
|
||||
Edit your host table, /etc/hosts. In it, place the IP
|
||||
address of this host and the IP address of your default
|
||||
router.
|
||||
|
||||
Edit the file /etc/myname. In it, place the symbolic name
|
||||
of your machine.
|
||||
|
||||
Edit the file /etc/defaultdomain. In it, place the name
|
||||
of your YP domain. If you will not be using YP, simply
|
||||
enter the domain name of your site.
|
||||
|
||||
Edit the file /etc/mygate. In it, place the name of
|
||||
your default router, as your listed it in /etc/hosts.
|
||||
|
||||
Edit the file /etc/hostname.le0. In it, place the following
|
||||
information:
|
||||
|
||||
inet <myname.my.domain> <netmask> <broadcast>
|
||||
|
||||
where:
|
||||
<myname.my.domain> is the name corresponsing to
|
||||
the IP address for that interface, as you listed in
|
||||
/etc/hosts.
|
||||
|
||||
<netmask> is the netmask for your network.
|
||||
|
||||
<broadcast> is the broadcast address for your network.
|
||||
|
||||
Repeat this step for any additional network interfaces you
|
||||
may have.
|
||||
|
||||
Edit the file /etc/ttys. Make sure that the entries are
|
||||
correct for whichever console type you have. /dev/console
|
||||
is correct for ITE, /dev/tty0 for console on dca, and
|
||||
/dev/tty00 for console on dcm. You may get more information
|
||||
about /etc/ttys by doing `man ttys', providing you have
|
||||
installed the system manual set.
|
||||
|
||||
Ok, cross your fingers and reboot:
|
||||
|
||||
sync; sync; sync; reboot
|
||||
|
||||
Providing you entered all information correctly, your
|
||||
machine will boot into multi-user mode. Your system
|
||||
will need a few tweaks here and there (like /etc/sendmail.cf
|
||||
and /etc/netstart, perhaps), but that's the easy stuff.
|
||||
|
||||
CONGRATULATIONS! You have successfully installed NetBSD
|
||||
onto your hp300! Pat yourself on the back. This might also
|
||||
be a good time to remove /ibin, as you will no longer need
|
||||
it, and it is provided solely for bootstrapping purposes.
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
This product includes software developed by Adam Glass.
|
||||
|
||||
This product includes software developed by Jason R. Thorpe.
|
||||
|
|
@ -0,0 +1,125 @@
|
|||
NOTE: These instructions are explicitly for installing NetBSD
|
||||
from an HP-UX system, version 7 or later. It has not been
|
||||
tested with HP-UX versions earlier than 7, and has also not
|
||||
been tested with HP-UX 8, although it is presumed to work.
|
||||
For the creative, similar steps may be taken from a system such
|
||||
as Utah's 4.3BSD release for the hp300, although bootstrapping
|
||||
from such a system has not been tested.
|
||||
|
||||
Bootstrapping the hp300 is a complicated process, but it's a lot
|
||||
easier than it used to be. For this process you need the
|
||||
following items from the install/ directory:
|
||||
|
||||
boot NetBSD/hp300 boot block for
|
||||
HP-IB and SCSI disks
|
||||
|
||||
rootimage.gz bootstrap root filesystem
|
||||
image
|
||||
|
||||
label prototype disk label
|
||||
|
||||
makedisk a program for HP-UX that will
|
||||
write a NetBSD disk label,
|
||||
boot block, and root filesystem
|
||||
image to the target disk
|
||||
(NOTE: This is an HP-UX 7.x binary.
|
||||
while it will work under HP-UX 9.x,
|
||||
you may want to compile this yourself.
|
||||
The source may be found in makedisk.tar.gz)
|
||||
|
||||
VERY IMPORTANT NOTE: This procedure will destroy all data on the
|
||||
target disk. Because NetBSD uses a different filesystem format than
|
||||
HP-UX, your old data will be useless. If you wish to save anything,
|
||||
use tar(1) instead of dump(1M), again because of filesystem differences.
|
||||
|
||||
First of all, you must have a second disk on which to install NetBSD.
|
||||
If possible, this disk should first be prepared with mediainit(1M).
|
||||
Once this disk is spotless, you should generate a disk label for it.
|
||||
Using the prototype label provided, fill in all of the necessary
|
||||
information. Remember, if you derive geometry information from an
|
||||
HP-UX disktab, your partition size will be off. This is because HP-UX
|
||||
uses a 1024-byte sector size, while NetBSD uses a 512-byte sector size.
|
||||
To avoid the problem, you may simply double the number of cylinders.
|
||||
(That's what I do...works great. -- JRT)
|
||||
|
||||
IMPORTANT: Partition 'a' must be offset one cylinder. Since
|
||||
partition information is expressed in sectors, the offset of
|
||||
partition 'a' must be the value of `sectors/cylinder'. This is
|
||||
to leave room for the boot block.
|
||||
|
||||
When you create your disklabel, be sure to specify whether or not
|
||||
the disk is HP-IB or SCSI in the `type:' field.
|
||||
|
||||
Below is an example of what a disk label should look like. This
|
||||
is an example only! Do not attempt this at home!
|
||||
|
||||
|
||||
|
||||
# Sample disklabel for example only. This is a comment.
|
||||
type: HP-IB
|
||||
disk:
|
||||
label: INSTALL-1_0
|
||||
flags:
|
||||
bytes/sector: 512
|
||||
sectors/track: 36
|
||||
tracks/cylinder: 7
|
||||
sectors/cylinder: 252
|
||||
cylinders: 1013
|
||||
rpm: 3600
|
||||
interleave: 1
|
||||
trackskew: 0
|
||||
cylinderskew: 0
|
||||
headswitch: 0 # milliseconds
|
||||
track-to-track seek: 0 # milliseconds
|
||||
drivedata: 0
|
||||
|
||||
7 partitions:
|
||||
# size offset fstype [fsize bsize cpg]
|
||||
a: 30744 252 4.2BSD 1024 8192 16 # (Cyl. 1 - 122)
|
||||
b: 32760 30996 swap # (Cyl. 123 - 252)
|
||||
c: 255276 0 boot # (Cyl. 0 - 1012)
|
||||
e: 20412 63756 4.2BSD 1024 4096 16 # (Cyl. 253 - 333)
|
||||
f: 40824 84168 4.2BSD 1024 8192 16 # (Cyl. 334 - 495)
|
||||
g: 130284 124992 4.2BSD 1024 8192 16 # (Cyl. 496 - 1012)
|
||||
|
||||
NOTE: Due to the nature of the bootstrapping procedure, your 'a'
|
||||
partition must be at least 30744 sectors long. Increase the size of
|
||||
your 'a' partition just enough to make it end on a cylinder boundary.
|
||||
If you make it any larger, you will just be wasting space, as the
|
||||
filesystem ends after 30744 sectors.
|
||||
|
||||
Remember to write down the names of the partitions and what you
|
||||
will be using them for (i.e. 'a - root, b - swap, e - /usr, etc.')
|
||||
as you will need this information later on in the installation
|
||||
process.
|
||||
|
||||
Once you are satisfied with your disklabel, you can write the
|
||||
root filesystem image to the target disk. Use the `makedisk'
|
||||
program for this. So, under HP-UX, do:
|
||||
|
||||
./makedisk /dev/rdsk/c7d0s0 mylabel boot rootimage.gz
|
||||
|
||||
where:
|
||||
/dev/rdsk/c7d0s0 raw flavor of target disk device
|
||||
|
||||
mylabel disk label you just wrote
|
||||
|
||||
boot supplied boot block
|
||||
|
||||
rootimage.gz gzipped root filesystem image
|
||||
NOTE: This requires that gzip be
|
||||
installed on your HP-UX system.
|
||||
If it is not, a gzip binary is
|
||||
provided in the install/ directory.
|
||||
Source for gzip may be found in the
|
||||
gsrc10 distribution set. Again, this
|
||||
gzip is an HP-UX 7.x binary.
|
||||
|
||||
If you wish to label any additional disks, you will have to do this
|
||||
from NetBSD, although you will not have an editor at your disposal.
|
||||
To do this, simply generate the labels now, and then grab them at
|
||||
the same time and by the same method you use to grab the distrubtion
|
||||
sets.
|
||||
|
||||
Once this is done, you should be ready to boot NetBSD from the target
|
||||
disk.
|
||||
|
|
@ -0,0 +1 @@
|
|||
There is no previous release of NetBSD/hp300 to upgrade.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
This is the first public release of NetBSD for the HP 9000/300 series of
|
||||
computers.
|
||||
|
|
@ -0,0 +1,78 @@
|
|||
Installation is supported from several media types, including:
|
||||
Tape
|
||||
NFS partitions
|
||||
FTP
|
||||
|
||||
The steps necessary to prepare the distribution sets
|
||||
for installation depend on which method of installation
|
||||
you choose. The various methods are explained below.
|
||||
|
||||
To prepare for installing via a tape:
|
||||
|
||||
To install NetBSD from a tape, you need to somehow
|
||||
get the NetBSD filesets you wish to install on
|
||||
your system on to the appropriate kind of tape,
|
||||
in tar format.
|
||||
|
||||
If you're making the tape on a UN*X system, the easiest
|
||||
way to do so is:
|
||||
|
||||
tar cvf <tape_device> <files>
|
||||
|
||||
where "<tape_device>" is the name of the tape device
|
||||
that describes the tape drive you're using (possibly
|
||||
something like /dev/nrst0, but we make no guarantees 8-).
|
||||
Under HP-UX, this would be something like /dev/rmt/c0ed03inb.
|
||||
Again, your mileage may vary. If you can't figure it out,
|
||||
ask your system administrator. "<files>" are the names
|
||||
of the "set_name.nnn" files which you want to be placed
|
||||
on the tape.
|
||||
|
||||
Once you have done this, you can proceed to the next
|
||||
step in the installation process, preparing your
|
||||
system for NetBSD installation.
|
||||
|
||||
To prepare for installing via an NFS partition:
|
||||
|
||||
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.
|
||||
|
||||
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 the new NetBSD machine,
|
||||
if the NFS server is not on a network which is
|
||||
directly attached to the NetBSD machine.
|
||||
|
||||
Once you have done this, you can proceed to the next
|
||||
step in the installation process, preparing your
|
||||
system for NetBSD installation.
|
||||
|
||||
To prepare for installing via FTP:
|
||||
|
||||
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.
|
||||
|
||||
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
|
||||
|
||||
Once you have done this, you can proceed to the next
|
||||
step in the installation process, preparing your
|
||||
system for NetBSD installation.
|
||||
Loading…
Reference in New Issue