File: bootp.xml

package info (click to toggle)
installation-guide 20070319
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k
  • size: 29,356 kB
  • ctags: 53
  • sloc: xml: 184,383; sh: 1,023; perl: 403; awk: 200; makefile: 65
file content (125 lines) | stat: -rw-r--r-- 5,024 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
<?xml version="1.0" encoding="EUC-JP"?>
<!-- retain these comments for translator revision tracking -->
<!-- original version: 43558 -->


  <sect2 condition="supports-bootp" id="tftp-bootp">
<!--
  <title>Setting up a BOOTP server</title>
-->
  <title>BOOTP Ф</title>
<para>

<!--
There are two BOOTP servers available for GNU/Linux. The first is CMU
<command>bootpd</command>. The other is actually a DHCP server: ISC
<command>dhcpd</command>. In &debian; these are contained in the
<classname>bootp</classname> and <classname>dhcp3-server</classname>
packages respectively.
-->
GNU/Linux ǻȤ BOOTP Ф 2 Ĥޤ
ҤȤĤ CMU  <command>bootpd</command> Ǥ
⤦ 1 Ĥϼºݤ DHCP ФǤISC  <command>dhcpd</command> Ǥ
&debian; Ǥϡ
<classname>bootp</classname> ѥå <classname>dhcp3-server</classname>
ѥåˤ줾äƤޤ

</para><para>

<!--
To use CMU <command>bootpd</command>, you must first uncomment (or
add) the relevant line in <filename>/etc/inetd.conf</filename>.  On
&debian;, you can run <userinput>update-inetd -\-enable
bootps</userinput>, then <userinput>/etc/init.d/inetd
reload</userinput> to do so. Just in case your BOOTP server does not
run Debian, the line in question should look like:
-->
CMU <command>bootpd</command> Ȥϡޤ <filename>/etc/inetd.conf</filename> ե
Ԥ򥢥󥳥 (ޤɲ) ɬפޤ
&debian; Ǥ <userinput>update-inetd --enable bootps</userinput> ¹Ԥ
³ <userinput>/etc/init.d/inetd reload</userinput> Ȥ OK Ǥ
BOOTP Ф Debian ưʤϡʲΤ褦ˤޤ

<informalexample><screen>
bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120
</screen></informalexample>

<!--
Now, you must create an <filename>/etc/bootptab</filename> file.  This
has the same sort of familiar and cryptic format as the good old BSD
<filename>printcap</filename>, <filename>termcap</filename>, and
<filename>disktab</filename> files.  See the
<filename>bootptab</filename> manual page for more information.  For
CMU <command>bootpd</command>, you will need to know the hardware
(MAC) address of the client.  Here is an example
<filename>/etc/bootptab</filename>:
-->
Ǽ <filename>/etc/bootptab</filename> ޤ
Υեν񼰤ϡ
<filename>printcap</filename>, <filename>termcap</filename>, 
<filename>disktab</filename> եʤɤǤߤΡ
Τ狼ˤˤʤäƤޤ
ܺ٤ <filename>bootptab</filename> ޥ˥奢ڡ򸫤Ƥ
CMU <command>bootpd</command> Ǥϡ
饤ȤΥϡɥ (MAC) ɥ쥹ΤäƤʤФʤޤ
<filename>/etc/bootptab</filename> 򼨤ޤ

<informalexample><screen>
client:\
  hd=/tftpboot:\
  bf=tftpboot.img:\
  ip=192.168.1.90:\
  sm=255.255.255.0:\
  sa=192.168.1.1:\
  ha=0123456789AB:
</screen></informalexample>

<!--
You will need to change at least the <quote>ha</quote> option, which
specifies the hardware address of the client.  The <quote>bf</quote>
option specifies the file a client should retrieve via TFTP; see
<xref linkend="tftp-images"/> for more details.
-->
ʤȤ⥯饤ȤΥϡɥɥ쥹ꤷƤ
<quote>ha</quote> ץѹɬפǤ礦
<quote>bf</quote> ץϥ饤Ȥ TFTP ǼեꤷƤޤ
ܺ٤ <xref linkend="tftp-images"/> 򻲾ȤƤ

<phrase arch="mips">
<!--
On SGI machines you can just enter the command monitor and type
<userinput>printenv</userinput>.  The value of the
<userinput>eaddr</userinput> variable is the machine's MAC address.
-->
SGI ΥޥǤϡ
ޥɥ˥ <userinput>printenv</userinput> ϤƤ
<userinput>eaddr</userinput> ѿޥ MAC ɥ쥹Ǥ
</phrase>

</para><para>

<!--
By contrast, setting up BOOTP with ISC <command>dhcpd</command> is
really easy, because it treats BOOTP clients as a moderately special
case of DHCP clients.  Some architectures require a complex
configuration for booting clients via BOOTP.  If yours is one of
those, read the section <xref linkend="dhcpd"/>.  In that case, you
will probably be able to get away with simply adding the
<userinput>allow bootp</userinput> directive to the configuration
block for the subnet containing the client, and restart
<command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server
restart</userinput>.
-->
оŪˡISC <command>dhcpd</command> ȤäƤ BOOTP ϼ¤˴ñǤ
<command>dhcpd</command> ǤϡBOOTP 饤Ȥ
ü DHCP 饤ȤȤƼ갷ޤ
ƥˤäƤϡBOOTP ˤ륯饤Ȥεưˤ
ʣ꤬ɬפˤʤޤ
˳Ƥޤä顢<xref linkend="dhcpd"/> ɤǤ
ξ硢饤Ȥδޤޤ륵֥ͥåȤ֥å
<userinput>allow bootp</userinput> Ȥǥ쥯ƥ֤ɲä
<userinput>/etc/init.d/dhcpd3-server restart</userinput> 
<command>dhcpd</command> ƵưǤ

</para>
  </sect2>