We have to do diskless workstations
Linuxaid.com.cn
Old ash
〖
Back to〗 Forward〗
Now the system is basically doing, 8 nodes are rampant, the client supports RSH, and the parallel environment is MPICH-1.2. Special thanks to friends who have given me a lot of trouble, I have added a lot of trouble to them, the main credit is them! Thank you! They are: A_HA, Andrew_lee, Badman_big, chern_yf, fengguang_wu, marquis_weng, qun_liu, richard_tao, rone_gao, who_ever, zqiang_zhou, etc.! Thank you! In order to reward everyone and exchange experience, I wrote it, please advise! More welcome to make suggestions, please send lihm@mail.ustc.edu.cn in the school, please send lihm0@263.net, thank you! (BTW: I just started learning Linux, answering questions now, I think I have nothing this, sorry!) Welcome http://202.38.85.81/linux/ Reference literature: Linux Remote Start http://www.linuxaid.com .cn / (or http://202.38.85.81/linux/aid.htm) Almost like (// shy) one, the remote start principle client is both before starting, there is no operating system, no startup Floppy or hard drive, it only has basic components of the computer: CPU, memory, motherboard, etc. But the most important thing must have a network card and boot bootrom. The client can only obtain an operating system over the network. Linux's diskless remote boot is different from Novell, Winnt's diskless startup technology, not using RPL (Remote Initial Program Loader), but is based on standard BootP / DHCP and TFTP protocols and establishes file systems through NFS file systems. It is more versatility and adaptability relative to the first two. DOS, WIN95, WINNT, and Linux customers can be launched based on Linux systems. Due to your own network card (3C905B-TPO100, there is bug, according to Etherboot) No corrections, now use the floppy disk instead of the network card EPROM, not much, please ask yourself to http://sourceforge.net/ download required source code Wait or compile the source code you need. The following brief introduction Linux boot principle: 1. After the client is boot, you will do your self-test before TCP / IP Bootrom get control. 2. Bootprom gives the Bootp / DHCP requirements to get IP. 3. If the server receives the request sent by the personal computer, it will be returned back to the Bootp / DHCP, including the client's IP address, preset gateway, and boot video files. Otherwise, the server will ignore this requirement. 4. Bootprom by TFTP The communication protocol downloads the power-on file file from the server. 5. Personal computer boots through this boot video file, this boot file can be just a simple boot program or an operating system. 6. The boot image file will contain Kernel Loader and compressed Kernel, This kernel will support NFS root system. 7. Remote client starts machine according to the downloaded file. Everything is OK !!! Simple! Ok! Let's show how to establish Linux Remote start. Second, remote boot instance as an example definition below : Linux Server: Server (IP: 192.168.0.254) First Client: PC01 (IP: 192.168.0.1) Second Client: PC02 (IP: 192.168.0.2) All Remote Start Customer Directory: / Client First Remote start-up client directory: / client / pc01 Second remote boot client directory: / client / pc02 support RSH First recompile Linux kernel.
Make MenuConfig pays attention to network support, NFS-root support, BootP (DHCP) support must be included. Make Cleanmake DEPMAKE BZIMAGEMAKE MODULESMAKE MODULES_INSTALL Once you've discovered that the client launched image file in the / usr / src / linux / i386 / boot directory, after compiling the new kernel, use MKNBI-Linux (Mknbi-Linux Bzimage Vmlinuz. Nb) Processing, place VMLinuz.nb on / tftpboot. The following command is then performed: MKNOD / DEV / NFSROOT B 0 255 Modify the startup device to point to NFSRoot. The following is a remote client to modify the server to establish a remote client's file system. Add: / Client / PC01 192.168.0.1 (RW, NO_ROOT_SQUASH) / Client / PC02 192.168.0.2 (RW, NO_ROOT_SQUASH) / Home 192.168.0.1/255.255.255.0 (RW, NO_ROOT_SQUASH) Using DHCP, Add support for remote customers in /etc/dhcpd.conf, where the Server address is 192.168.0.254:# dhcpd.conf # Global OptionsOption Domain-name "server.ustc.edu.cn"; option Domain-name-servers 202.38. 64.1; # Intranetsubnet 192.168.0.0 netmask 255.255.255.0 {range 192.168.0.1 192.168.0.250; default-lease-time -1; # option root-path "/ client / pc01"; option dhcp-server-identifier 192.168.0.254; Option Broadcast-Address 192.168.0.255; #boption routers 198.168.0.254; server-name "server"; Next-Server 192.168.0.254; filename "/ boot / vmlinuz"; host pc01 {option root-path "/ client / pc01" Hardware Ethernet 00: 01: 02: 96: 65: 92; Fixed-Address 192.168.0.1;} Host PC02 {Option Root-path "/ client / pc02"; Hardware Ethernet 00: 01: 02: 98: 92: 55 Fixed-address 192.168.0.2;}} Subnet 202.38.64.0 Netmask 255.255.255.0 {} See: DHCP-HOWTO Create a remote client directory on the server: / client / client / pc01 / client / pc02 talks about PC01 Practice. PC01 directory included: bin, dev, etc C, Home, LIB, MNT, Proc, root, sbin, tmp, usr, var directory.
We are copying BIN, DEV, ETC, LIB, SBIN, USR, VAR directly, HOME, MNT, PROC, ROOT, TMP is a newly built empty directory, (at the time, it was reinstalled, including DHCP, NFS, RSH, etc. Supported as small as possible, try to clean up Linux, then completely copy them, so there will be a lot of unnecessary things can be deleted, but unfortunately, now the level is not successful, and I have to use this province. Air: (, wait after slowly removing unnecessary files) Note You must modify /client/pc01/etc/rc.d startup file: change mount -avt nonfs to mount -av. Allow NFS root file system. (We It is debian Woody, this file is changed to /client/pc01/etc/init.d/mountall.sh, and we are mount -a -t noproc, nosmbfs to modify / client / pc01 / etc / fstab files in the following format : 192.168.0.254: 192.168.0.254: / client / pc01 / nfs defaults, rw 0 0192.168.0.254:/Home / Home NFS RW, BG 0 0 0PROC / PROC PC DEFAULTS 0 0 Modified Client / PC01 / etc / hostname: PC01 Modify Client / PC01 / ETC / HOSTS: 127.0.0.1 localhost192.168.0.0.1 PC00192.168.0.1 PC01192.168.0.2 PC02 Modified Client / PC01 / etc / hosts.equiv: serverpc01pc02 Modified Client / PC01 / ETC / MTAB: 192.168.0.254: / Client / PC01 / NFS RW 0 0Proc / Proc Proc RW 0 0DEVPTS / DEV / PTS Devpts RW, GID = 5, MODE = 620 0 0192.168.0.254:/Home / Home NFS RW, BG, AddR = 192.168.0.254 0 0 Modifications Client / PC01 / ETC / NETWORK / Interfacesface Eth0 INET staticaddress 192.168.0.1Netmask 255.255.255.0Network 192.168.0.0broadcast 192.168.0.255gateway 192.168.0.254 The next chain must be established to link the IP address of the remote client to the / client / pc01 directory. $: ln -s pc01 192.168.0.1 Making PC02 can copy the PC01 and modify the above files. The following is set in the personal directory: home / username /.rhosts192.168.0.1 UserName192.168.0.2 UserName Finally confirms whether NFSD, TFTPD, and BootPD daemons on the server are started.
