mbw
parent
d876b5d59e
commit
a90ddef4ce
|
|
@ -1,4 +1,4 @@
|
|||
.\" $NetBSD: prep,v 1.25 2002/04/22 00:37:01 mbw Exp $
|
||||
.\" $NetBSD: prep,v 1.26 2002/05/03 05:19:27 mbw Exp $
|
||||
.
|
||||
.Ss2 Prepare yourself
|
||||
.
|
||||
|
|
@ -1718,172 +1718,7 @@ Skip forward to
|
|||
.br
|
||||
(All Open Firmware versions)
|
||||
.Pp
|
||||
Set up the DHCP daemon in BOOTP compatible mode, the TFTP daemon, and
|
||||
the NFS daemons on your netboot server.
|
||||
Tell Open Firmware to boot over ethernet, and it will send a BOOTP
|
||||
request, which will tell Open Firmware what your system's IP address
|
||||
is, and where its bootloader can be downloaded via TFTP.
|
||||
Once Open FIrmware has downloaded the bootloader via TFTP, it will
|
||||
then load the installation kernel via an NFS connection.
|
||||
.Pp
|
||||
Follow these instructions to configure a
|
||||
.Nx
|
||||
machine as your netboot server. If you intend to use a different platform
|
||||
as your netboot server, follow the directions in the Diskless HOW-TO:
|
||||
.Lk http://www.netbsd.org/Documentation/network/netboot
|
||||
.Pp
|
||||
We will use
|
||||
.Sq Li CC:CC:CC:CC:CC:CC
|
||||
as the MAC address (ethernet hardware address) of your netboot client machine
|
||||
that you wish to install
|
||||
.Nx
|
||||
on. We use
|
||||
.Sq Li 192.168.1.10
|
||||
as the IP address of your client, and
|
||||
.Sq Li client.test.net
|
||||
as the name. The server name is
|
||||
.Sq Li server.test.net ,
|
||||
and the path on the server to the NFS exported directory is
|
||||
.Pa /export/client/root No .
|
||||
.Pp
|
||||
You should replace all of these with the names, addresses, and paths
|
||||
appropriate to your environment.
|
||||
.Pp
|
||||
Now, set up your
|
||||
.Ic dhcpd
|
||||
server. Make sure the following lines are in
|
||||
.Pa /etc/dhcpd.conf :
|
||||
.(disp
|
||||
ddns-update-style none;
|
||||
# Do not use any dynamic DNS features
|
||||
#
|
||||
allow bootp; # Allow bootp requests, thus the dhcp server
|
||||
# will act as a bootp server.
|
||||
#
|
||||
authoritative; # This is the authoritative DHCP server for this subnet
|
||||
#
|
||||
subnet 192.168.1.0 netmask 255.255.255.0 {
|
||||
# Which network interface the server will
|
||||
# listen on. The zeros indicate which
|
||||
# range of addresses are allowed to connect.
|
||||
}
|
||||
group {
|
||||
# Set of parameters common to all clients
|
||||
# in this "group".
|
||||
#
|
||||
option broadcast-address 192.168.1.255;
|
||||
option domain-name "test.net";
|
||||
option domain-name-servers dns.test.net;
|
||||
option routers router.test.net;
|
||||
option subnet-mask 255.255.255.0;
|
||||
#
|
||||
# An individual client.
|
||||
#
|
||||
host client.test.net {
|
||||
hardware ethernet CC:CC:CC:CC:CC:CC;
|
||||
fixed-address 192.168.1.10;
|
||||
#
|
||||
# Name of the host (if the fixed address
|
||||
# doesn't resolve to a simple name).
|
||||
#
|
||||
option host-name "client";
|
||||
#
|
||||
# Name of the bootloader or kernel
|
||||
# to download via tftp.
|
||||
#
|
||||
filename "ofwboot.xcf";
|
||||
#
|
||||
# The path on the NFS server.
|
||||
#
|
||||
option root-path "/export/client/root";
|
||||
}
|
||||
}
|
||||
.disp)
|
||||
.Pp
|
||||
You will need to make sure that the
|
||||
.Pa dhcpd.leases
|
||||
file exists.
|
||||
.Pp
|
||||
.(disp
|
||||
.No # Ic "touch /var/db/dhcpd.leases"
|
||||
.disp)
|
||||
.Pp
|
||||
You will need to
|
||||
.Ic kill
|
||||
the
|
||||
.Ic dhcpd
|
||||
and restart it to get it to re-read its configuration file.
|
||||
If the server is running
|
||||
.Nx 1.5 ,
|
||||
you can achieve this with:
|
||||
.Pp
|
||||
.(disp
|
||||
.No # Ic "/etc/rc.d/dhcpd restart"
|
||||
.disp)
|
||||
.Pp
|
||||
Now, place a copy of the
|
||||
.Pa installation/ofwboot.xcf
|
||||
bootloader in
|
||||
.Pa /tftpboot
|
||||
.Pp
|
||||
.(disp
|
||||
.No # Ic "cp ofwboot.xcf /tftpboot"
|
||||
.disp)
|
||||
.Pp
|
||||
Now, you should edit
|
||||
.Pa /etc/inetd.conf
|
||||
and make sure that the line starting with
|
||||
.Li tftp
|
||||
is uncommented. You will need to
|
||||
.Ic kill -HUP
|
||||
the
|
||||
.Ic inetd
|
||||
process to enable tftp if this line was previously commented out. The next
|
||||
step is to set up NFS exports. Create the directory you are exporting for
|
||||
the netboot client:
|
||||
.Pp
|
||||
.(disp
|
||||
.No # Ic "mkdir -p /export/client/root"
|
||||
.disp)
|
||||
.Pp
|
||||
Put the following line in
|
||||
.Pa /etc/exports
|
||||
to enable NFS sharing:
|
||||
.Pp
|
||||
.(disp
|
||||
/export/client/root -maproot=root client.test.net
|
||||
.disp)
|
||||
.Pp
|
||||
If your server is currently running NFS services, you only need to
|
||||
.Ic "kill -HUP"
|
||||
the
|
||||
.Ic mountd
|
||||
process. Otherwise, you need to run:
|
||||
.Pp
|
||||
.(disp
|
||||
.No # Ic "/usr/sbin/mountd"
|
||||
.No # Ic "/usr/sbin/nfsd -tun 4"
|
||||
.disp)
|
||||
.Pp
|
||||
Now, you need to place the files your netboot client will need.
|
||||
As noted above in the section
|
||||
.Sx Preparing your System for NetBSD installation
|
||||
you have several options when choosing a location to store the
|
||||
distribution
|
||||
filesets. However, the easiest way is to put the distribution
|
||||
files into the exported directory for your client on the server.
|
||||
.Pp
|
||||
.(disp
|
||||
.No # Ic "mv *.tgz /export/client/root"
|
||||
.disp)
|
||||
.Pp
|
||||
Your client will need a kernel to boot (use
|
||||
.Pa installation/netbsd.ram.gz ) .
|
||||
.Pp
|
||||
.(disp
|
||||
.No # Ic "gunzip netbsd.ram.gz"
|
||||
.No # Ic "mv netbsd.ram /export/client/root/netbsd"
|
||||
.disp)
|
||||
.so ../common/netboot
|
||||
.Pp
|
||||
Skip forward to
|
||||
.Sx Installing the NetBSD System
|
||||
|
|
|
|||
Loading…
Reference in New Issue