boot.8

minix操作系统最新版本（3.1.1）的源代码

.PP
.RS
Standalone with no connection to a network.
.SP
In a small network with no support from a "big" host.
.SP
Connected to a large network with address and name servers.
.RE
.PP
In each situation you need a different set of configuration files.
.SS Standalone
All you need is a name and an IP address.  Suppose the name is "flotsam"
and the IP address is 192.168.0.1 from the private IP space, then this is
put in
.BR /etc/hosts :
.PP
.RS
.ta +\w'192.168.0.1'u+3n
192.168.0.1	flotsam
.RE
.PP
And this in
.BR /etc/dhcp.conf :
.PP
.RS
.nf
host 192.168.0.0/24 {};
interface ip0 flotsam;
.fi
.RE
.SS "Small Network"
A network requires an ethernet driver.  You need to enable one in
<minix/config.h> and you need to tell
.B inet
that it should use that driver by making
.B /etc/inet.conf
look like this:
.PP
.RS
.nf
eth0 DP8390 0 { default; };
.fi
.RE
.PP
The second word (DP8390) must the name of the ethernet driver you've enabled.
It can also be seen among the drivers in the output of
.BR "ps ax" .
See also
.BR inet (8).
.PP
In a small network there may not be a DHCP server for MINIX 3 to obtain its IP
address and name from, so you need specify the ethernet address of your machine
and host names of all machines in the hosts and DHCP configuration files.
Suppose your machine is to be named "flotsam", and another machine in the
network is named "jetsam", and let's use network 192.168.0.0/24 again.  The
file
.B /etc/hosts
now looks like this:
.PP
.RS
.ta +\w'192.168.0.1'u+3n
.nf
192.168.0.1	flotsam
192.168.0.2	jetsam
.fi
.RE
.PP
And
.B /etc/dhcp.conf
like this:
.PP
.RS
.nf
host 192.168.0.0/24 {};
client 0:1:1b:a:68:ce flotsam;
.fi
.RE
.PP
Use
.B hostaddr \-e
to find out what the ethernet address of your network card is.  (The address
above is an example.)
.PP
A host needs to have all hostnames used on your little network in its
host file.  In the DHCP configuration you only need the client entry of the
system itself, but it may be useful to add all client entries to make them all
the same.
.PP
If one of the machines is always on when any of the others is, then you can let
it be a DHCP server.  The other machines don't need a hosts or DHCP file
anymore.  If flotsam is the server then its
.BR /etc/dhcp.conf
looks like this:
.PP
.RS
.nf
.ta +4m
host 192.168.0.0/24 {
	DNSserver flotsam;
};
client 0:1:1b:a:68:ce flotsam { option server; };
client 0:0:c0:3a:12:10 jetsam;
.fi
.RE
.SS "Large Network"
In a network with a central network administration your machine's IP address
and name are given by the DHCP server.  You don't need any configuration
files.  If you want your machine to do more, like being a router or
something, then see
.BR inet (8)
on setting up more than one network interface.
.PP
.SS "Simpler configuration tools"
The
.BR dhcpd
and
.BR nonamed
daemons are complex little programs that try to obtain information about
their surroundings automatically to tell the machine what its place in the
network is.  It should come as no surprise that there are simpler utilities
to configure a machine.  On a memory starved machine it may even be wise to
configure a machine statically to get rid of the daemons.  The first daemon,
.BR dhcpd ,
can be replaced by:
.PP
.RS
.B ifconfig \-h
.I host-IP-address
.B \-n
.I netmask
.br
.B add_route \-g
.I gateway-IP-address
.RE
.PP
to set the IP address and netmask of the machine.  Note that you can only
do this if the machine has a static IP address, or chaos will follow.  Remove
.BR /usr/adm/dhcp.cache
if the DHCP daemon has run before.
.PP
The name daemon,
.BR nonamed ,
can be replaced by an entry in
.B /etc/resolv.conf
that specifies an external name daemon:
.PP
.RS
.B nameserver
.I nameserver-IP-address
.RE
.PP
The
.B ifconfig
and
.B add_route
calls can be placed in the file
.BR /etc/rc.net .
Check
.B /usr/etc/rc
to see how
.BR /etc/rc.net
can be used to override running the normal series of network deamons.
Note that
.BR /etc/rc.net
is sourced, so you can use the same variables and functions that
.BR /usr/etc/rc
uses.
These changes undo all the efforts to make MINIX 3 TCP/IP
autoconfigurable.  Make very sure that all the IP addresses are correct, and
that the IP address of your machine is unique.  (Mistakenly using the
address of a main server will make all other machines look at your machine,
and will make all the users of all other machines look at you.)
.SH FILES
.TP 20n
/boot
MINIX 3 Boot Monitor.
.TP
/minix
Kernel image, or directory containing them.
.TP
/etc/rc
Basic system initialization.
.TP
/usr/etc/rc
Complete system initialization.
.TP
/etc/rc.net
Specialized network initialization.
.TP
/usr/local/etc/rc
Per site initialization.
.TP
/etc/hosts
Name to IP address mapping.
.TP
/etc/dhcp.conf
Network initialization.
.TP
/etc/resolv.conf
Name resolver configuration.
.SH "SEE ALSO"
.BR monitor (8),
.BR init (8),
.BR inet (8),
.BR loadkeys (8),
.BR readclock (8),
.BR fsck (1),
.BR fstab (5),
.BR update (8),
.BR cron (8),
.BR ttytab (5),
.BR getty (8),
.BR hostaddr (1),
.BR ifconfig (8),
.BR dhcpd (8),
.BR nonamed (8),
.BR tcpd (8),
.BR hosts (5),
.BR ethers (5),
.BR resolv.conf (5),
.BR inet (8).
.SH DIAGNOSTICS
.TP 5n
Checking File Systems.
If the system has crashed then
.B fsck
is called for the root and /usr file systems.  It is wise to reboot if the
root file system must be fixed.
.TP
Finish the name of device to mount as /usr: /dev/
The prompt for the
.B \-a
option, or if the name of the /usr file system has not been set in /etc/fstab.
You can type a device name, say
.BR fd0 .
.TP
Unable to obtain an IP address after 10 seconds.
TCP/IP misconfiguration.  The DHCP daemon may have failed because the ethernet
address of the machine is not known to the DHCP server, the DHCP
configuration is not filled in properly, or the DHCP server can not be reached.
Either talk to your Network Administrator, or make a dhcp.conf
and a hosts file.
.TP
1.2.3.4 login:
If you see an IP address instead of a host name then the system failed to
translate the IP address.  Either talk to your Network Administrator to
have the reverse address translation tables fixed, or make a hosts file.
.SH NOTES
The 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 networks can be used for
private networks.  (This so-called CIDR notation names an IP address and
the number of bits in the network number.  So 172.16.0.0/12 includes all
addresses from 172.16.0.0 to 172.31.255.255.)
RFC-1597 will tell you why private networks are good, and RFC-1627 why
they are bad.
.SH BUGS
Indefinite hangs are possible if I/O addresses or IRQ's are wrong.  A driver
may babble about addresses and IRQ's, but that does not mean that what it
says is true, it may just be configured that way.  It is very difficult to
find peripherals on a PC automatically, and MINIX 3 doesn't even try.
.SH AUTHOR
Kees J. Bot <[e-mail]>