Linux diskless workstation approach
 

First, the rule

remote start before the start of the client,Lacoste UK, neither operating system nor the boot floppy alternatively hard disk, it is merely the computer's basic components: CPU, memory, motherboards and so on. But the maximum major must have a network card and start the BootRom. Client operating system can only be obtained through the network. Diskless Remote Boot Linux, and Novell,Lacoste Carnaby Trainers, WinNT diskless boot technology is not beneath the same,Womens Lacoste Observe Trainers, not with RPL (Remote Initial Program Loader), but on the standard BootP / DHCP and TFTP protocols, and through the NFS file system a file system. Relative to the first two, but also has its versatility and plasticity. Linux systems can be based remote boot Dos, Win95, WinNT, and Linux clients.

because of his card (3c905b-tpo100, a BUG, ​​not edited in agreement with the directions etherboot success, it is now replaced with a floppy disk adapter for EPROM, not a lot of that, please also go directly to their own http://sourceforge. web / download the needed source code and other source or compile their own needs.

following is a brief Linux boot principle:
1. the client PC is cornered on, the TCP / IP Bootrom do first before access control self-test.
2.Bootprom mail BOOTP / DHCP request to win IP.
3. If the server receives the request sent by the PC will return BOOTP / DHCP response, including the client's IP address, default gateway and boot image files. Otherwise, the server will bypass the request.
4.Bootprom at the TFTP protocol to download the boot image file from the server.
5. PC boot through the boot image file, the boot files can simply boot the operating system code can also be.
6. boot image file will involve the kernel loader and the ziped kernel, the kernel will advocate NFS root system.
7. remote clients along download file to start the machine.

all OKAY!!! simple! cozy to use it! The following describes how to build a characteristic Linux remote boot.

Second, remote start instance
define the following as examples:
Linux server: server (IP: 192.168.0.254)
premier client: pc01 (IP: 192.168.0.1)
second client: pc02 (IP: 192.168.0.2)
All remote boot client directory: / client
first client remote boot directory: / client/pc01
second client remote boot directory: / client/pc02
support rsh

First, recompile the Linux kernel.
make menuconfig
attention to network support, NFS-Root support, BootP (DHCP) support must be included.
make clean
make dep
make bzImage
make modules
make modules_install
on command, you will ascertain the picture document the client starts in / usr/src/linux/i386/boot catalogue, compile the fashionable kernel, the use of mknbi-linux (mknbi-linux bzImage vmlinuz.nb) treatment,Womens Lacoste Trainers, the vmlinuz.nb above the / tftpboot of buttons.
and then perform the following command: mknod / dev / nfsroot b 0 255 to modify boot device to point to NFSRoot.

the following changes to the remote client server for a remote file system client.

in the server / etc / exports to 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, the / etc / dhcpd.conf joined to the remote buyer support, which server address is 192.168.0.254:
# dhcpd.conf

# Global options
option domain-name br> option domain-name-servers 202.38.64.1;

# Intranet
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.1 192.168.0.250;
default-lease- period -1;

# discretion root-path # alternative routers 198.168.0.254;

server-name br> option root-path
option root-path
subnet 202.38.64.0 netmask 255.255.255.0

see: DHCP-Howto

a remote client on the server machine directory:
/ client
/ client/pc01
/ client/pc02

said the retinue about the train of pc01.

pc01 directory includes: bin, dev, etc, home, lib, mnt, proc, root, sbin, tmp, usr, var directory.
We are the bin, dev, etc, lib, sbin, usr, var instantly copied completely, home, mnt, proc, root, tmp namely a new blank directory, (then is to re-install a including DHCP, NFS, RSH and additional support as small as possible, try to clean Linux, and then completely copied them completely, so that there must be a lot of unnecessary things can be cleared, yet unfortunately not according to current levels, according to References do not succeed, but to retention distress in another course with this: (, so delete needless files that later)
consideration to the need to modify / client/pc01/etc/rc.d startup file: change the mount-avt nonfs to mount-av. allows the use of NFS Root file system. (we are Debian Woody, this file into the / client/pc01/etc/init.d/mountall.sh,Lacoste Protect Laser Trainers, and we are mount-a-t noproc, nosmbfs)

in the following formats to modify / client/pc01/etc/fstab file:
192.168.0.254: / client/pc01 / nfs defaults, rw 0 0
192.168.0.254: / home / home nfs rw, bg 0 0
proc / proc proc defaults 0 0

modify client/pc01/etc/hostname:
pc01

modify client/pc01/etc/hosts :
127.0.0.1 localhost
192.168.0.254 pc00
192.168.0.1 pc01
192.168.0.2 pc02

modify client/pc01/etc/hosts.equiv:
+
server
pc01
pc02

modify client/pc01/etc/mtab:
192.168.0.254: / client/pc01 / nfs rw 0 0
proc / proc proc rw 0 0
devpts / dev / pts devpts rw, gid = 5, mode = 620 0 0
192.168.0.254: / family / home nfs rw, bg, addr = 192.168.0.254 0 0

Modify client/pc01/etc/network/interfaces
face eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
web 192.168.0.0
announce 192.168.0.255
gateway 192.168.0.254

have to then build a necklace of remote client IP address linked to / client/pc01 directory.
$: ln-s pc01 192.168.0.1

pc01 pc02 do come, you can copy and modify the look of several documents.

the emulating settings in the personal directory rsh support:
home / username / .rhosts

192.168.0.254 username
192.168.0.1 username
192.168.0.2 username

Finally make sure the server nfsd,Lacoste Observe Strap Trainers, tftpd and bootpd daemons are started.
entire get away! about ten seconds, the remote start soon tin enjoy Linux.
on NFS, TFTP, BOOTP (DHCP) settings, amuse refer to the How-to.

namely the voice of experience, the best of all client files to a separate section on the inside, This partition can be fitted which gives a basic system (the same for natural installation). and then as the root for changes (suggested Debian, easier to hack). If you need to install anyone software on the client, you can do:
chroot / client/pc01
dselect or apt-get

This article comes from the beautiful and the articles very useful where he discusses the subject of Linux diskless workstation approach it is really a great article