1 <CHAPTER ID="Specials">
2 <!-- <TITLE>Special Cases </TITLE> -->
3 <TITLE>ÆÃÊ̤ʥ±¡¼¥¹</TITLE>
4 <!-- <SECT1><TITLE>Laptops and PCMCIA Cards</TITLE> -->
5 <SECT1><TITLE>¥é¥Ã¥×¥È¥Ã¥× ¤È PCMCIA ¥«¡¼¥É</TITLE>
8 Using the current set of RPM's (and hopefully also .deb packages) putting
9 openMosix on a laptop does not differ from other installation.
10 Actually the only issues you can run into are problems with autodiscovery and promiscious mode, as documented
11 elsewhere in this HOWTO.
13 ¸½¾õ¤Î RPM ¥Ñ¥Ã¥±¡¼¥¸(¤È¤¦¤Þ¤¯¹Ô¤±¤Ð .deb ¥Ñ¥Ã¥±¡¼¥¸¤Ç¤â)¤ò»È¤¨¤Ð¡¢openMosix
14 ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ëºÝ¤Ë¥é¥Ã¥×¥È¥Ã¥×¤È¤½¤ì°Ê³°¤ËÁê°ã¤Ï¤¢¤ê¤Þ¤»¤ó¡£
15 ¼ÂºÝ¤Ë²ÔÆ°¤µ¤»¤ë¤Î¤ËÅö¤¿¤Ã¤ÆÍ£°ìÌäÂê¤Ë¤Ê¤ë¤Î¤Ï¡¢¼«Æ°Ãµº÷¤È¥×¥í¥ß¥¥ã¥¹¥â¡¼¥É
16 ¤Ç¤¹¡£ÀâÌÀ¤Ï¤³¤Î HOWTO ¤Î¾¤Î¤È¤³¤í¤Ë¤¢¤ê¤Þ¤¹¡£
20 However this part might still come in handy when you want to compile
22 a laptop that requires PCMCIA support. It has not been updated recently, but it might be helpful.
24 ¤·¤«¤·¤³¤³¤Ç¤ÎÀâÌÀ¤Ï¡¢PCMCIA ¤Î¥µ¥Ý¡¼¥È¤¬É¬Íפʥé¥Ã¥×¥È¥Ã¥×¤Ç openMosix ¤ò
25 ¥³¥ó¥Ñ¥¤¥ë¤·¤è¤¦¤È¤·¤¿»þ¤ËÊØÍø¤Ç¤¢¤ë¤³¤È¤Ë¤«¤ï¤ê¤¢¤ê¤Þ¤»¤ó¡£ºÇ¶á¹¹¿·¤µ¤ì¤Æ
26 ¤Ï¤¤¤Þ¤»¤ó¤¬¡¢½õ¤±¤Ë¤Ï¤Ê¤ë¤Ç¤·¤ç¤¦¡£
33 If you are installing openMosix on a Laptop, you will have to recompile
34 the PCMCIA sources, because they are distributed as a separate
35 package and not as kernel modules. On a Suse 7.1 machine, in theory,
37 installing the packages and then running
39 ¥é¥Ã¥×¥È¥Ã¥×¤Ç openMosix ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤Ê¤é¡¢PCMCIA ¤Î¥½¡¼¥¹¤òºÆ
40 ¥³¥ó¥Ñ¥¤¥ë¤·¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£¤È¤¤¤¦¤Î¤â¡¢¤½¤ì¤ÏÆÈΩ¤Î¥Ñ¥Ã¥±¡¼¥¸¤È¤·¤Æ
41 ÇÛÉÛ¤µ¤ì¤Æ¤ª¤ê¡¢¥«¡¼¥Í¥ë¥â¥¸¥å¡¼¥ë¤Ç¤Ï¤Ê¤¤¤«¤é¤Ç¤¹¡£Suse 7.1 ¤Î¥Þ¥·¥ó
42 ¤Ç¤Ï¡¢¥Ñ¥Ã¥±¡¼¥¸¤ò SuSE ¤Î¥Þ¥Ë¥å¥¢¥ë(ÆÈÈÇ¤Ç 358 ÊÇ)¤Ë½¾¤Ã¤Æ¥¤¥ó¥¹¥È¡¼¥ë
43 ¤¹¤ì¤ÐÍý¶þ¾å¤ÏÆ°¤¯¤Ï¤º¤Ç¤¹¡£
46 rpm -ba /usr/src/packages/SPECS/pcmcia.spec
50 as described in the SuSE manual [on page 358 of the German
51 edition]. However, the script tends to get confused by the
52 location of the libraries of the vanilla version and the Mosix
53 version, so after running the above line, you will have to go to
54 the sources in /usr/src/kernel-modules/pcmcia and run
56 ¤·¤«¤·¥¹¥¯¥ê¥×¥È¤ÏÁǤΥС¼¥¸¥ç¥ó¤Î¥é¥¤¥Ö¥é¥ê°ÌÃÖ¤ä Mosix ¤Î¥Ð¡¼¥¸¥ç¥ó
57 ¤Ë¤è¤Ã¤Æº®Í𤷤Ƥ·¤Þ¤¦·¹¸þ¤Ë¤¢¤ê¤Þ¤¹¡£¤·¤¿¤¬¤Ã¤Æ¾åµ¤Î¹Ô¤ò¼Â¹Ô¤·¤¿¸å¤Ë¤Ï¡¢
58 /usr/src/kernel-modules/pcmcia ¤Ë°ÜÆ°¤·¤Æ²¼µ¤òµ¯Æ°¤·¤Æ¤¯¤À¤µ¤¤¡£
64 When prompted for the "Module install directory", change the
65 default setting of "/lib/modules/2.2.19" to
67 ¡ÖModule install directory¡×¤Ø¤Î»Ø¼¨¤Ë¤Ê¤Ã¤¿¤é¡¢¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤Ç¤¢¤ë
68 /lib/modules/2.2.19 ¤«¤é²¼µ¤ËÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£
70 /lib/modules/2.2.19-mosix
74 Then run "make" and "make install", which should put the pcmcia
75 modules in /lib/modules/2.2.19-mosix/pcmcia . Note that you must be
76 running the Mosix kernel before you recompile the pcmcia sources.
78 ÀßÄꤷ¤¿¸å¤Ë¡Ömake¡×¤È¡Ömake install¡×¤ò¼Â¹Ô¤¹¤ë¤È¡¢PCMCIA ¥â¥¸¥å¡¼¥ë
79 ¤¬ /lib/modules/2.2.19-mosix/pcmcia ¤ËÆþ¤ë¤Ï¤º¤Ç¤¹¡£¤¿¤À¤·PCMCIA ¥½¡¼¥¹
80 ¤ò¥³¥ó¥Ñ¥¤¥ë¤¹¤ëÁ°¤Ë¡¢Mosix ¥«¡¼¥Í¥ëÆ°¤«¤µ¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£
84 <!-- <SECT1><TITLE>Disk-less nodes</TITLE> -->
85 <SECT1><TITLE>¥Ç¥£¥¹¥¯¥ì¥¹¡¦¥Î¡¼¥É</TITLE>
89 At first you have to setup a DHCP-server which answers the DHCP-request
90 for an ip-address when a disk-less client boots. This DHCP-Server (i call it
91 master in this HOWTO) acts additional as an NFS-server which exports the
92 whole client-file-systems so the disk-less- cluster-nodes (i call them
93 slaves in this HOWTO) can grab this FS (file-system) for booting as soon as
94 it has its ip. Just run a "normal"-MOSIX setup on the master-node. Be
95 sure you included NFS-server-support in your kernel-configuration. There
96 are two kinds (or maybe a lot more) types of NFS:
98 ¤Þ¤º DHCP ¥µ¡¼¥Ð¤òÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£DHCP ¥µ¡¼¥Ð¤Ï¥Ç¥£¥¹¥¯¥ì¥¹¥¯¥é¥¤¥¢¥ó¥È
99 ¤¬¥Ö¡¼¥È¤¹¤ë»þ¤Ë IP ¥¢¥É¥ì¥¹¤ÎÍ×µá¤ËÅú¤¨¤ë¤«¤é¤Ç¤¹¡£¤³¤Î DHCP ¥µ¡¼¥Ð
100 (¤³¤Î HOWTO ¤Ç¤Ï¥Þ¥¹¥¿¡¼¤È¸Æ¤Ó¤Þ¤¹)¤Ï NFS ¥µ¡¼¥Ð¤È¤·¤Æ¤âÆ°ºî¤·¤Æ¤ª¤ê¡¢
101 ¥¯¥é¥¤¥¢¥ó¥È¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¹¤Ù¤Æ¤ò¥¨¥¯¥¹¥Ý¡¼¥È¤·¤Þ¤¹¡£¤½¤·¤Æ
102 ¥Ç¥£¥¹¥¯¥ì¥¹¥Î¡¼¥É(¤³¤Î HOWTO ¤Ç¤Ï¥¹¥ì¡¼¥Ö¤È¸Æ¤Ó¤Þ¤¹)¤Ï¡¢IP ¥¢¥É¥ì¥¹¤ò
103 ¼èÆÀ¤¹¤ë¤È¤¹¤°¡¢¤³¤Î FS(¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à)¤ò¥Ö¡¼¥È¤¹¤ë¤¿¤á¤Ë¼è¤ê¹þ¤ß¤Þ¤¹¡£
104 ¤³¤³¤Ç¡ÖÄ̾ï¤Î¡×MOSIX ¤Î¥»¥Ã¥È¥¢¥Ã¥×¤ò¥Þ¥¹¥¿¡¼¥Î¡¼¥É¤Ç¹Ô¤¤¤Þ¤¹¡£¥«¡¼¥Í¥ë
105 ÀßÄê¤Ç NFS ¥µ¡¼¥Ð¤Î¥µ¥Ý¡¼¥È¤òɬ¤ºÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£NFS ¤Ë¤Ï 2 ¼ïÎà
106 (¤â¤·¤«¤¹¤ë¤È¤â¤Ã¤È¤¿¤¯¤µ¤ó)¤¢¤ê¤Þ¤¹¡£
119 It does not matter which one you use but my experiences shows to use
120 kernel-nfs in "older" kernels (like 2.2.18) and daemon-nfs in "newer"
121 ones. The NFS in newer kernels sometimes does not work properly. If your
122 master-node is running with the new MOSIX-kernel start with one file-system
123 as slave-node. Here the steps to create it: Calculate at least 300-500 MB
124 for each slave. Create an extra directory for the whole cluster-file-system
125 and make a symbolic-link to /tftpboot. (The /tftpboot-directory or link is
126 required because the slaves searches for a directory named
127 /tftpboot/ip-address-of-slave for booting. You can change this only by
128 editing the kernel-sources) Then create a directory named like the ip of
129 the first slave you want to configure, e.g. mkdir /tftpboot/192.168.45.45
130 Depending on the space you have on the cluster-filesystem now copy the
131 whole filesystem from the master-node to the directory of the first slave.
132 If you have less space just copy:
134 ¤É¤Á¤é¤òÍøÍѤ·¤Æ¤â¤«¤Þ¤¤¤Þ¤»¤ó¤¬¡¢·Ð¸³¾å¸Å¤¤¥«¡¼¥Í¥ë(2.2.18 ¤Î¤è¤¦¤Ê)¤Ç¤Ï
135 kernel-nfs ¤ò¡¢¡Ö¿·¤·¤¤¡×¥«¡¼¥Í¥ë¤Ç¤Ï daemon-nfs ¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£¿·¤·¤¤
136 ¥«¡¼¥Í¥ë¤Ç¤Ï NFS ¤¬¤¦¤Þ¤¯Æ°ºî¤·¤Ê¤¤¾ì¹ç¤¬¤¢¤ê¤Þ¤¹¡£¥Þ¥¹¥¿¡¼¥Î¡¼¥É¤¬¿·¤·¤¤
137 MOSIX ¥«¡¼¥Í¥ë¤ÇÁàºî¤·¤Æ¤¤¤ë¤Ê¤é¡¢¥¹¥ì¡¼¥Ö¥Î¡¼¥É¤È¤·¤Æ 1 ¤Ä¤Î¥Õ¥¡¥¤¥ë
138 ¥·¥¹¥Æ¥à¤«¤é¤Ï¤¸¤á¤Æ¤¯¤À¤µ¤¤¡£½ç¤òÄɤäƹԤ¤Þ¤·¤ç¤¦¡£¥¹¥ì¡¼¥Ö¤Ë¤ÏºÇÄã¤Ç¤â
139 300 ¤«¤é 500 MB¤ò¸«ÀѤâ¤ê¤Þ¤¹¡£Á´¥¯¥é¥¹¥¿ÍѤΥե¡¥¤¥ë¥·¥¹¥Æ¥à¸þ¤±¤ËÄɲäÎ
140 ¥Ç¥£¥ì¥¯¥È¥ê¤òºîÀ®¤·¤Þ¤¹¡£¤½¤ì¤ò /tftpboot ¤Ø¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤·¤Æ¤¯¤À¤µ¤¤¡£
141 (/tftpboot ¥Ç¥£¥ì¥¯¥È¥ê¡¢¤â¤·¤¯¤Ï¤½¤Î¥ê¥ó¥¯¤Ï¥¹¥ì¡¼¥Ö¤¬¥Ö¡¼¥È¤¹¤ëºÝ¤Ë
142 ¡Ö/tftpboot/¥¹¥ì¡¼¥Ö¤Î IP ¥¢¥É¥ì¥¹¡×¤ò¸¡º÷¤¹¤ë¤¿¤á¤Ç¤¹¡£¤³¤ì¤òÊѹ¹¤¹¤ë
143 ¤Ë¤Ï¥«¡¼¥Í¥ë¥½¡¼¥¹¤ò½¤Àµ¤¹¤ë¤·¤«ÊýË¡¤¬¤¢¤ê¤Þ¤»¤ó)¡£¤½¤·¤ÆÀßÄꤷ¤¿¤¤¥¹¥ì¡¼¥Ö
144 ¤Î IP ¥¢¥É¥ì¥¹¤Î¤è¤¦¤Ê̾Á°¤Î¥Ç¥£¥ì¥¯¥È¥ê¤òºîÀ®¤·¤Æ¤¯¤À¤µ¤¤¡£Î㤨¤Ð¡¢
145 mkdir /tftpboot/192.168.45.45 ¤È¤¤¤¦¤è¤¦¤Ë¡£
146 ¥¯¥é¥¹¥¿¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òÃÖ¤¯Îΰè¤Ë¤â¤è¤ê¤Þ¤¹¤¬¡¢¥Þ¥¹¥¿¡¼¥Î¡¼¥É¤«¤é¤¹¤Ù¤Æ¤Î
147 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºÇ½é¤Î¥¹¥ì¡¼¥Ö¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë¥³¥Ô¡¼¤·¤Þ¤¹¡£
148 Îΰ褬¾¯¤Ê¤±¤ì¤Ð¡¢²¼µ¤À¤±¤ò¥³¥Ô¡¼¤·¤Æ¤¯¤À¤µ¤¤¡£
159 You can configure that the slave gets the rest per NFS later.
160 Be sure to create empty directories for the mount-points.
161 The filesystem-structure in /tftpboot/192.168.45.45/ has to be similar to
164 ¥¹¥ì¡¼¥Ö¤¬¸å¤Ç NFS ¤òÄ̤¸¤Æ»Ä¤ê¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¼èÆÀ¤Ç¤¤ë¤è¤¦¤ËÀßÄê
166 ¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥ÈÍѤ˶õ¤Î¥Ç¥£¥ì¥¯¥È¥ê¤òɬ¤ººîÀ®¤·¤Æ¤¯¤À¤µ¤¤¡£
167 /tftpboot/192.168.45.45/ ¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¹½À®¤Ï¡¢¥Þ¥¹¥¿¡¼¤Î / ¤ÈƱ¤¸¤Ç
171 /tftpboot/192.168.45.45/etc/HOSTNAME //insert the hostname of the slave
172 /tftpboot/192.168.45.45/etc/hosts //insert the hostname+ip of the slave
176 Depending on your distribution you have to change the ip-configuration of
179 ¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤Ë¤â¤è¤ê¤Þ¤¹¤¬¡¢¥¹¥ì¡¼¥Ö¤Î IP ¥¢¥É¥ì¥¹¤ÎÀßÄê¤ò½¤Àµ
180 ¤·¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£
184 /tftpboot/192.168.45.45/etc/rc.config
185 /tftpboot/192.168.45.45/etc/sysconfig/network
186 /tftpboot/192.168.45.45/etc/sysconfig/network-scripts/ifcfg-eth0
190 Change the ip-configuration for the slave as you like.
192 ¥¹¥ì¡¼¥Ö¤Î IP ¥¢¥É¥ì¥¹¤Ï¼«Í³¤ËÀßÄêÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£
194 <!-- Edit the file -->
195 ½¤Àµ¤¹¤ë¥Õ¥¡¥¤¥ë¤Ï²¼µ¤ÎÄ̤ꡣ
198 /tftpboot/192.168.45.45/etc/fstab //the FS the slave will get per NFScoresponding to
199 /etc/exports //the FS the master will export to the slaves
202 <!-- e.g. for a slave fstab: -->
203 ¤¿¤È¤¨¤Ð¡¢¥¹¥ì¡¼¥Ö¤Î fstab ¤Ï²¼µ¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
206 master:/tftpboot/192.168.88.222 / nfs hard,intr,rw 0 1
207 none /proc nfs defaults 0 0
208 master:/root /root nfs soft,intr,rw 0 2
209 master:/opt /opt nfs soft,intr,ro 0 2
210 master:/usr/local /usr/local nfs soft,intr,ro 0 2
211 master:/data/ /data nfs soft,intr,rw 0 2
212 master:/usr/X11R6 /usr/X11R6 nfs soft,intr,ro 0 2
213 master:/usr/share /usr/share nfs soft,intr,ro 0 2
214 master:/usr/lib /usr/lib nfs soft,intr,ro 0 2
215 master:/usr/include /usr/include nfs soft,intr,ro 0 2
216 master:/cdrom /cdrom nfs soft,intr,ro 0 2
217 master:/var/log /var/log nfs soft,intr,rw 0 2
221 <!-- e.g. for a master exports: -->
222 ¥Þ¥¹¥¿¡¼¤Î exports ¤Ï²¼µ¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
225 /tftpboot/192.168.45.45 *(rw,no_all_squash,no_root_squash)
226 /usr/local *(rw,no_all_squash,no_root_squash)
227 /root *(rw,no_all_squash,no_root_squash)
229 /data *(rw,no_all_squash,no_root_squash)
234 /var/log *(rw,no_all_squash,no_root_squash)
235 /usr/src *(rw,no_all_squash,no_root_squash)
240 If you mount /var/log (rw) from the NFS-server you have on central
241 log-file! (it worked very well for me. just "tail -f /var/log/messages" on
242 the master and you always know what is going on)
244 NFS ¥µ¡¼¥Ð¤«¤é /var/log(rw) ¤ò¥Þ¥¦¥ó¥È¤¹¤ë¤È¡¢¥í¥°¥Õ¥¡¥¤¥ë¤ò½¸Ìó¤Ç¤¤Þ¤¹
245 (»ä¤Î¾ì¹ç¤Ï¤¦¤Þ¤¯¹Ô¤Ã¤Æ¤¤¤Þ¤¹¡£¥Þ¥¹¥¿¡¼¾å¤Ç¡Ötail -f /var/log/messages¡×
246 ¤È¤¹¤ë¤À¤±¤Ç¡¢²¿¤¬µ¯¤³¤Ã¤Æ¤¤¤ë¤Î¤«¤ò¤¤¤Ä¤âÃΤ뤳¤È¤¬¤Ç¤¤Þ¤¹)¡£
252 The cluster-filesystem for your first slave will be ready now. Configure
253 the slave-kernel now. If you have the same hardware on your cluster you
254 can reuse the configuration of the master-node. Change the configuration
255 for the slave like the following:
257 ¤³¤ì¤Ç¥¯¥é¥¹¥¿¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºÇ½é¤Î¥¹¥ì¡¼¥Ö¤Ç»È¤¦½àÈ÷¤¬¤Ç¤¤Þ¤·¤¿¡£
258 ¼¡¤Ï¥¹¥ì¡¼¥Ö¤Î¥«¡¼¥Í¥ë¤ÎÀßÄê¤ò¤·¤Þ¤·¤ç¤¦¡£¥¯¥é¥¹¥¿¤ÇƱ¤¸¥Ï¡¼¥É¥¦¥§¥¢¤ò»ý¤Ã¤Æ
259 ¤¤¤ë¤Ê¤é¡¢¥Þ¥¹¥¿¡¼¥Î¡¼¥É¤ÎÀßÄê¤òήÍѤǤ¤Þ¤¹¡£²¼µ¤Î¤è¤¦¤Ë¥¹¥ì¡¼¥ÖÍѤËÀßÄê¤ò
271 Use as less modules as possible (maybe no modules at all) because the
272 configuration is a bit tricky.
273 Now (it is well described in the Beowulf-HOWTO) you have to create a
275 It is only used for patching the slave-kernel to boot from NFS.
277 ¤Ç¤¤ë¤À¤±¥â¥¸¥å¡¼¥ë¤Î¿ô¤Ï¾¯¤Ê¤¯¤·¤Æ¤¯¤À¤µ¤¤(¤³¤È¤Ë¤è¤ë¤È¥â¥¸¥å¡¼¥ë
278 ¤ò¤Þ¤Ã¤¿¤¯»È¤ï¤Ê¤¤)¡£ÀßÄ꤬¾¯¡¹Æñ¤·¤¯¤Ê¤ë¤«¤é¤Ç¤¹¡£
279 ¼¡¤Ë(Beowulf-HOWTO ¤Ç¤ï¤«¤ê¤ä¤¹¤¯ÀâÌÀ¤·¤Æ¤¢¤ê¤Þ¤¹) nfsroot ¥Ç¥Ð¥¤¥¹¤ò
280 ºîÀ®¤·¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£
281 ¤³¤ì¤Ï ¥¹¥ì¡¼¥Ö¤¬ NFS ¤Ç¥Ö¡¼¥È¤Ç¤¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤À¤±¤ËÍøÍѤµ¤ì¤Þ¤¹¡£
284 mknod /dev/nfsroot b 0 255
285 rdev bzImage /dev/nfsroot
289 Here "bzImage" has to be your diskless-slave-kernel you find it in
290 /usr/src/linux-version/arch/i386/boot after successful compilation.
292 ¡ÖbzImage¡×¤Ï¥Ç¥£¥¹¥¯¥ì¥¹¤Ê¥¹¥ì¡¼¥Ö¤Î¥«¡¼¥Í¥ë¤È¤Ê¤é¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£
293 ¥³¥ó¥Ñ¥¤¥ë¤¬À®¸ù¤·¤Æ¤¤¤ì¤Ð¡¢/usr/src/linux-version/arch/i386/boot ¤Ë
297 Then you have to change the root-device for that kernel
299 ¤½¤Î¥«¡¼¥Í¥ëÍÑ¤Ë root ¥Ç¥Ð¥¤¥¹¤òÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£
303 rdev -o 498 -R bzImage 0
306 <!-- and copy the kernel to a floppy-disk -->
307 ¤½¤Î¥«¡¼¥Í¥ë¤ò¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤Ë¥³¥Ô¡¼¤·¤Æ¤¯¤À¤µ¤¤¡£
310 dd if=bzImage of=/dev/fd0
314 Now you are nearly ready! You just have to configure DHCP on the master.
315 You need the MAC-address (hardware address) of the network card of your
318 ¤³¤ì¤Ç½àÈ÷¤¬¤Û¤È¤ó¤É¤Ç¤¤Þ¤·¤¿¡£¸å¤Ï¥Þ¥¹¥¿¡¼¤Î DHCP ¤òÀßÄꤷ¤Ê¤±¤ì¤Ð
320 ºÇ½é¤Î¥¹¥ì¡¼¥Ö¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥«¡¼¥É¤Î MAC ¥¢¥É¥ì¥¹(¥Ï¡¼¥É¥¦¥§¥¢¥¢¥É¥ì¥¹)
326 The easiest way to get this address is to boot the client with the already
327 created boot-floppy (it will fail but it will tell you its MAC-address). If
328 the kernel was configured alright for the slave the system should come up
329 from the floppy, booting the diskless-kernel, detecting its network-card
330 and sending an DHCP- and ARP request. It will tell you its hardware address
331 during that moment! It looks like : 68:00:10:37:09:83.
333 ¤³¤Î¥¢¥É¥ì¥¹¤ò´Êñ¤Ë¼èÆÀ¤¹¤ë¤Ë¤Ï¡¢ºîÀ®ºÑ¤ß¤Î¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤Ç¥¯¥é¥¤¥¢¥ó¥È
334 ¤ò¥Ö¡¼¥È¤·¤Þ¤¹(¥Ö¡¼¥È¤Ë¤Ï¼ºÇÔ¤·¤Þ¤¹¤¬¡¢MAC ¥¢¥É¥ì¥¹¤Ïʬ¤«¤ê¤Þ¤¹)¡£
335 ¥«¡¼¥Í¥ë¤¬¤¹¤Ù¤Æ´Ö°ã¤¤¤Ê¤¯¥¹¥ì¡¼¥ÖÍѤËÀßÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢¥·¥¹¥Æ¥à¤Ï¥Õ¥í¥Ã¥Ô¡¼
336 ¤«¤éΩ¤Á¾å¤¬¤ê¡¢¥Ç¥£¥¹¥¯¥ì¥¹¤Î¥«¡¼¥Í¥ë¤¬µ¯Æ°¤·¡¢¥Í¥Ã¥È¥ï¡¼¥¯¥«¡¼¥É¤òǧ¼±¤·¡¢
337 DHCP ¤È ARP ¥ê¥¯¥¨¥¹¥È¤òÁ÷¿®¤·¤Þ¤¹¡£¤½¤Î½Ö´Ö¥Ï¡¼¥É¥¦¥§¥¢¥¢¥É¥ì¥¹¤¬Ê¬¤«¤ê¤Þ¤¹¡£
338 68:00:10:37:09:83 ¤È¤¤¤¦´¶¤¸¤Ç¤¹¡£
341 Edit the file /etc/dhcp.conf like the following sample:
343 /etc/dhcp.conf ¤ò²¼µ¤Î¥µ¥ó¥×¥ë¤Î¤è¤¦¤Ë½¤Àµ¤·¤Æ¤¯¤À¤µ¤¤¡£
346 option subnet-mask 255.255.255.0;
347 default-lease-time 6000;
348 max-lease-time 72000;
349 subnet 192.168.45.0 netmask 255.255.255.0 {
350 range 192.168.45.253 192.168.45.254;
351 option broadcast-address 192.168.45.255;
352 option routers 192.168.45.1;
356 hardware ethernet 68:00:10:37:09:83;
357 fixed-address firstslave;
358 server-name "master";
363 Now you can start DHCP and NFS with their init scripts:
365 ¤³¤ì¤Ç init ¥¹¥¯¥ê¥×¥È¤Ç DHCP ¤È NFS ¤òµ¯Æ°¤Ç¤¤Þ¤¹¡£
368 /etc/init.d/nfsserver start
369 /etc/init.d/dhcp start
373 You got it!! It is (nearly) ready now!
375 ¤È¤¦¤È¤¦¤ä¤ê¤Þ¤·¤¿¡£¤³¤ì¤Ç(¤Û¤È¤ó¤É)½àÈ÷´°Î»¤Ç¤¹¡£
379 Boot your first-slave with the boot-floppy (again). It should work now.
380 Shortly after recognizing its network-card the slave gets its ip-address
381 from the DHCP-server and its root-filesystem (and the rest) per NFS.
383 ºÇ½é¤Î¥¹¥ì¡¼¥Ö¤ò¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤Ç(ºÆÅÙ)¥Ö¡¼¥È¤·¤Æ¤¯¤À¤µ¤¤¡£¤â¤¦»È¤¨¤ë¤Ï¤º
385 ¥Í¥Ã¥È¥ï¡¼¥¯¥«¡¼¥É¤òǧ¼±¤·¤Æ¸å¤Û¤É¤Ê¤¯¡¢¥¹¥ì¡¼¥Ö¤Ï IP ¥¢¥É¥ì¥¹¤ò DHCP ¥µ¡¼¥Ð
386 ¤«¤é¼èÆÀ¤·¡¢¥ë¡¼¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à(¤È»Ä¤ê)¤ò NFS ·Ðͳ¤Ç»ý¤Ã¤Æ¤¤Þ¤¹¡£
390 You should notice that modules included in the slave-kernel-config must
392 master too, because the slaves are mounting the /lib-directory from the
394 use the same modules (if any).
396 ¥¹¥ì¡¼¥Ö¤Î¥«¡¼¥Í¥ëÀßÄê¤Ë¤¢¤ë¥â¥¸¥å¡¼¥ë¤Ï¡¢¥Þ¥¹¥¿¡¼¾å¤Ë¤â¸ºß¤·¤Ê¤±¤ì¤Ð¤¤¤±
397 ¤Ê¤¤ÅÀ¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£Íýͳ¤Ï¥¹¥ì¡¼¥Ö¤¬¥Þ¥¹¥¿¡¼¤«¤é /lib ¥Ç¥£¥ì¥¯¥È¥ê¤ò
398 ¥Þ¥¦¥ó¥È¤¹¤ë¤«¤é¤Ç¤¹¡£¤·¤¿¤¬¤Ã¤ÆƱ¤¸¥â¥¸¥å¡¼¥ë¤ò»È¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹(¤¢¤Ã¤¿¤È
404 It will be easier to update or install additional libraries or
405 applications if you mount
406 as much as possible from the master. On the other hand if all slaves have
408 filesystem in /tftpboot your cluster may be a bit faster because of not so
410 hits on the NFS-server.
412 ¥¢¥Ã¥×¥Ç¡¼¥È¤ä¥é¥¤¥Ö¥é¥ê¤â¤·¤¯¤Ï¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤òÄɲäǥ¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤Ë¤Ï
413 ¥Þ¥¹¥¿¡¼¤ò¤Ç¤¤ë¤À¤±¥Þ¥¦¥ó¥È¤·¤Æ¤ª¤±¤Ð´Êñ¤Ë¤Ê¤ê¤Þ¤¹¡£µÕ¤Ë¥¹¥ì¡¼¥Ö¤¹¤Ù¤Æ¤¬
414 ¼«¿È¤Ç´°Á´¤Ê¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò /tftpboot ¤Ë»ý¤Ã¤Æ¤¤¤ì¤Ð¡¢Â¿¾¯Â®¤¯¤Ê¤ê¤Þ¤¹¡£
415 NFS ¥µ¡¼¥Ð¤ËÂФ¹¤ëÆɤ߽ñ¤¤¬¾¯¤Ê¤¯¤Ê¤ë¤«¤é¤Ç¤¹¡£
420 You have to add a .rhost file in /root (for user root) on each
421 cluster-member which should look like this:
423 ¥¯¥é¥¹¥¿¤Î¥á¥ó¥Ð¡¼¤½¤ì¤¾¤ì¤Î /root ¤Ë .rhost ¤òÃÖ¤¤¤Æ¤¯¤À¤µ¤¤(root ¥æ¡¼¥¶ÍÑ)¡£
424 ²¼µ¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
433 You also have to enable remote-login per rsh in the /etc/inetd.conf. You
434 should have these two lines in it
436 ¤Þ¤¿¡¢rsh ·Ðͳ¤Ç¥ê¥â¡¼¥È¥í¥°¥¤¥ó¤Ç¤¤ë¤è¤¦¤Ë /etc/inetd.conf ¤Ë rsh ¤òɬ¤º
437 ¤¤¤ì¤Æ¤¯¤À¤µ¤¤¡£²¼µ¤Î 2 ¹Ô¤Ë¤Ê¤ë¤Ï¤º¤Ç¤¹¡£
441 <!-- if your linux-distribution uses inetd: -->
442 inetd ¤òÍøÍѤ·¤Æ¤¤¤ë Linux ¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤Ê¤é¡¢
445 shell stream tcp nowait root /bin/mosrun mosrun -l -z /usr/sbin/tcpd in.rshd -L
446 login stream tcp nowait root /bin/mosrun mosrun -l -z /usr/sbin/tcpd in.rlogind
450 <!-- And for xinetd: -->
451 xinetd ¤òÍøÍѤ·¤Æ¤¤¤ë¤Ê¤é¡¢
460 server = /usr/sbin/in.rshd
469 server = /usr/sbin/in.rlogind
477 You have to restart inetd afterwards so that it reads the new
480 ¤½¤Î¸å inetd ¤òºÆµ¯Æ°¤·¤Æ¤¯¤À¤µ¤¤¡£¤½¤¦¤¹¤ë¤È¿·¤·¤¤ÀßÄ꤬Æɤ߹þ¤Þ¤ì¤Þ¤¹¡£
483 /etc/init.d/inetd restart
490 There may be another switch in your distribution-configuration-utility
491 where you can configure the security of the system. Change it to "enable
492 remote root login". Do not use this in insecure environments!!! Use SSH
493 instead of RSH! You can use MOSIXVIEW with RSH or SSH.
494 Configuring SSH for remote login without password is a bit tricky. Take a
495 look at the "HOWTO use MOSIX/MOSIXVIEW with SSH?" at this website.
496 If you want to copy files to a node in this diskless-cluster you have now
497 two possibilities. You can use rcp or scp for copying remote or you can
498 use just cp and copy files on the master to the cluster-filesystem of one
499 node. The following two commands are equal:
501 ¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥óÉÕ°¤ÎÀßÄê¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ë¤Ï¡¢¥·¥¹¥Æ¥à¤Î¥»¥¥å¥ê¥Æ¥£¤ò
502 Êѹ¹¤¹¤ëÊ̤ÎÊýË¡¤¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£¡Ö¥ê¥â¡¼¥È ¤«¤é¤Î root ¤Ç¤Î¥í¥°¥¤¥ó¤ò
503 µö²Ä¤¹¤ë¡×¤ËÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£°ÂÁ´¤Ç¤Ï¤Ê¤¤´Ä¶¤Ë¤ª¤¤¤Æ¤Ï¡¢»È¤ï¤Ê¤¤¤è¤¦¤Ë¤·¤Æ
504 ¤¯¤À¤µ¤¤¡£rsh ¤ÎÊѤï¤ê¤Ë ssh ¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£MOSIXVIEW ¤Ç¤Ï rsh ¤« ssh ¤¬
506 ¥Ñ¥¹¥ï¡¼¥É¤Ê¤·¤Ç¥ê¥â¡¼¥È¥í¥°¥¤¥ó¤¹¤ë ssh ¤ÎÀßÄê¤Ï¿¾¯Ê£»¨¤Ë¤Ê¤ê¤Þ¤¹¡£¤³¤Î Web
507 ¥µ¥¤¥È¤Î¡ÖHOWTO use MOSIX/MOSIXVIEW with SSH?¡×¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£
508 ¥Ç¥£¥¹¥¯¥ì¥¹¥¯¥é¥¹¥¿¤Î¤¢¤ë¥Î¡¼¥É¤Ë¥Õ¥¡¥¤¥ë¤ò¥³¥Ô¡¼¤·¤¿¤¤¾ì¹ç¡¢ÊýË¡¤Ï 2 ¤Ä¤¢¤ê
509 ¤Þ¤¹¡£rcp ¤â¤·¤¯¤Ï scp ¤ò»È¤Ã¤Æ¥ê¥â¡¼¥È¤Ë¥³¥Ô¡¼¤¹¤ë¤«¡¢cp ¤ò»È¤Ã¤Æ¥Þ¥¹¥¿¡¼¾å
510 ¤Î¥Õ¥¡¥¤¥ë¤ò¥Î¡¼¥É¤Î¥¯¥é¥¹¥¿¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë¥³¥Ô¡¼¤¹¤ë¤«¤Ç¤¹¡£²¼µ¤Î 2 ¤Ä¤Î
514 rcp /etc/hosts 192.168.45.45./etc
515 cp /etc/hosts /tftpboot/192.168.45.45/etc/
521 Off course you can also reproduce these steps but use PXE boot rather than
524 ¤â¤Á¤í¤ó¡¢¤³¤Î¥¹¥Æ¥Ã¥×¤ò·«¤êÊÖ¤·¤Æ¤â¤«¤Þ¤¤¤Þ¤»¤ó¤¬¡¢¥Õ¥í¥Ã¥Ô¡¼¤è¤ê¤â
525 PXE(?)¥Ö¡¼¥È¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
529 <!-- ¸¶Ê¸¤Ç¥³¥á¥ó¥È¥¢¥¦¥È¤·¤Æ¤¢¤ë¤Î¤ÇÌõ½Ð¤·¤Þ¤»¤ó¡£ -->
531 <SECT1><TITLE>Very large clusters</TITLE>