Specifications

option domain-name-servers ns.local.net;
host trgt { hardware ethernet 00:30:BF:01:02:D0;
fixed-address 192.168.20.38;
option root-path "/opt/eldk-5.2/armv5te/rootfs";
option host-name "m28";
next-server 192.168.1.1;
filename "/tftpboot/duts/m28/uImage";
}
}
With this configuration, the DHCP server will reply to a request from the target with the ethernet address
00:30:BF:01:02:D0 with the following information:
The target is located in the subnet 192.168.0.0 which uses the netmask 255.255.0.0.•
The target has the hostname m28 and the IP address 192.168.20.38.•
The host with the IP address 192.168.1.1 will provide the boot image for the target and provide
NFS server function in cases when the target mounts it's root filesystem over NFS.
The host listed with the next-server option can be different from the host that is running the
DHCP server.
•
The host provides the file /tftpboot/duts/m28/uImage as boot image for the target.•
The target can mount the directory /opt/eldk-5.2/armv5te/rootfs on the NFS server as root filesystem.•
4.8. Configuring a NFS Server
For a development environment it is very convenient when the host and the target can share the same files
over the network. The easiest way for such a setup is when the host provides NFS server functionality and
exports a directory that can be mounted from the target as the root filesystem.
Assuming NFS server functionality is already provided by your host, the only configuration that needs to be
added is an entry for your target root directory to your /etc/exports file, for instance like this:
/opt/eldk-5.2/armv5te/rootfs 192.168.0.0/255.255.0.0(rw,no_root_squash,sync)
This line exports the /opt/eldk-5.2/armv5te/rootfs directory with read and write permissions to all hosts on the
192.168.0.0 subnet.
After modifying the /etc/exports file you must make sure the NFS system is notified about the change, for
instance by issuing the command:
# /sbin/service nfs restart
5. Das U-Boot
5.1. Current Versions♦
5.2. Unpacking the Source Code♦
5.3. Configuration♦
5.4. Installation
5.4.1. Before You Begin
5.4.1.1. Installation Requirements⋅
5.4.1.2. Board Identification Data⋅
◊
♦
•
4.7. Configuration of a BOOTP / DHCP Server 34