[mdv07]~>sudo /opt/drbl/sbin/drblsrv -i
Language | y|  ?.
[0]: English
[1]: Chinese Traditional (Big5) - Taiwan |  (jX) - xW.
[2]: Chinese Traditional (UTF-8, Unicode) - Taiwan | 中 (碼) - 0
[0]
*****************************************************.
Hint! When a yes/no option is available, the default value is uppercase, Ex. (y/N), the default is "N", when you press "Enter", it will use "N". If you are not sure which one to choose, you can just press "Enter" key.
*****************************************************.
*****************************************************.
Installing DRBL for Mandriva Linux...
The version number for your OS: MDV2007.0
*****************************************************.
Do you want to set the proxy server ?
[y/N]
*****************************************************.
*****************************************************.
Which "ayo" repository do you want to use for OS packages ?
0 -> free.nchc.org.tw,
1 -> mdk.linux.org.tw,
2 -> distro.ibiblio.org,
5 -> Enter ayo repository (with OS packages) by yourself.
[0] 5
*****************************************************.
Please enter the hostname or IP address of OS packages reposity with http or ftp prefix...
[http://distro.ibiblio.org] ftp://mdk.linux.org.tw
Enter the path where directories "2007.0" and "updates"exist...
[/pub/Linux/distributions/mandrake/Mandrakelinux/official/] /pub/mandrake-devel
------------------------------------------------------
The url and path you selected: ftp://mdk.linux.org.tw, ftp://mdk.linux.org.tw//pub/mandrake-devel
------------------------------------------------------
*****************************************************.
Which "ayo" repository do you want to use for DRBL packages ?
0 -> free.nchc.org.tw,
1 -> diskless.nchc.org.tw,
2 -> drbl.sourceforge.net,
5 -> To enter repository (with DRBL packages) by yourself.
[0]
*****************************************************.
------------------------------------------------------
The url and path you selected: http://free.nchc.org.tw, drbl-core/i386
------------------------------------------------------
*****************************************************.
Do you want to use the DRBL "unstable" packages which is much more powerful, but maybe very unstable (If you are super brave!!!) (If you downloaded the drbl rpm package from the unstable directory, say "yes" here) ?
[y/N] y
`/etc/urpmi/urpmi.cfg' -> `/etc/urpmi/urpmi.cfg.drblsave'
*****************************************************.
Warning! We have to reset all the existing urpmi setting!
Are you sure you want to continue ?
[Y/n}
Removing the old urpmi setting...
*****************************************************.
nothing to remove (use urpmi.addmedia to add a media)
*****************************************************.
Adding urpmi source...
*****************************************************.
retrieving media.cfg file...
...retrieving done
added medium Main (MDK2007.01)
added medium Contrib (MDK2007.02)
computing md5sum of existing source hdlist (or synthesis)
retrieving source hdlist (or synthesis) of "Main (MDK2007.01)"...
ftp://mdk.linux.org.tw//pub/mandrake-devel/2007.0/i586/media/media_info/synthesis.hdlist_main.cz
found probed hdlist (or synthesis) as ../../..//media/media_info/synthesis.hdlist_main.cz
...retrieving done
examining hdlist file [/var/cache/urpmi/partial/hdlist.Main (MDK2007.01).cz]
examining synthesis file [/var/cache/urpmi/partial/hdlist.Main (MDK2007.01).cz]
examining pubkey file of "Main (MDK2007.01)"...
computing md5sum of existing source hdlist (or synthesis)
retrieving source hdlist (or synthesis) of "Contrib (MDK2007.02)"...
ftp://mdk.linux.org.tw//pub/mandrake-devel/2007.0/i586/media/media_info/synthesis.hdlist_contrib.cz
found probed hdlist (or synthesis) as ../../..//media/media_info/synthesis.hdlist_contrib.cz
...retrieving done
examining hdlist file [/var/cache/urpmi/partial/hdlist.Contrib (MDK2007.02).cz]
examining synthesis file [/var/cache/urpmi/partial/hdlist.Contrib (MDK2007.02).cz]
examining pubkey file of "Contrib (MDK2007.02)"...
performing second pass to compute dependencies

examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Main (MDK2007.01).cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Contrib (MDK2007.02).cz]
found 0 headers in cache
removing 0 obsolete headers in cache
wrote config file [/etc/urpmi/urpmi.cfg]
added medium MDK2007.0-updates
wrote config file [/etc/urpmi/urpmi.cfg]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Main (MDK2007.01).cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Contrib (MDK2007.02).cz]
retrieving source hdlist (or synthesis) of "MDK2007.0-updates"...
ftp://mdk.linux.org.tw//pub/mandrake-devel/updates/2007.0/main_updates/media_info/media_info/synthesis.hdlist.cz

...retrieving failed: curl: (9) Server denied you to change to the given directory
ftp://mdk.linux.org.tw//pub/mandrake-devel/updates/2007.0/main_updates/media_info/synthesis.hdlist_.cz

...retrieving failed: curl: (9) Server denied you to change to the given directory
ftp://mdk.linux.org.tw//pub/mandrake-devel/updates/2007.0/main_updates/media_info/synthesis.hdlist.cz

...retrieving failed: curl: (9) Server denied you to change to the given directory
ftp://mdk.linux.org.tw//pub/mandrake-devel/updates/2007.0/main_updates/media_info/media_info/hdlist.cz

...retrieving failed: curl: (9) Server denied you to change to the given directory
ftp://mdk.linux.org.tw//pub/mandrake-devel/updates/2007.0/main_updates/media_info/hdlist_.cz

...retrieving failed: curl: (9) Server denied you to change to the given directory
ftp://mdk.linux.org.tw//pub/mandrake-devel/updates/2007.0/main_updates/media_info/hdlist.cz

...retrieving failed: curl: (9) Server denied you to change to the given directory
retrieval of source hdlist (or synthesis) failed
no hdlist file found for medium "MDK2007.0-updates"
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.MDK2007.0-updates.cz]
problem reading synthesis file of medium "MDK2007.0-updates"
found 0 headers in cache
removing 0 obsolete headers in cache
wrote config file [/etc/urpmi/urpmi.cfg]
unable to update medium "MDK2007.0-updates"
added medium drbl-stable
wrote config file [/etc/urpmi/urpmi.cfg]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Main (MDK2007.01).cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Contrib (MDK2007.02).cz]
retrieving source hdlist (or synthesis) of "drbl-stable"...
http://free.nchc.org.tw/drbl-core/i386/base/synthesis.hdlist.drbl.cz
found probed hdlist (or synthesis) as synthesis.hdlist.drbl.cz
...retrieving done
examining hdlist file [/var/cache/urpmi/partial/hdlist.drbl-stable.cz]
examining synthesis file [/var/cache/urpmi/partial/hdlist.drbl-stable.cz]
writing list file for medium "drbl-stable"
found 0 headers in cache
removing 0 obsolete headers in cache
wrote config file [/etc/urpmi/urpmi.cfg]
added medium drbl-testing
wrote config file [/etc/urpmi/urpmi.cfg]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Main (MDK2007.01).cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Contrib (MDK2007.02).cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.drbl-stable.cz]
retrieving source hdlist (or synthesis) of "drbl-testing"...
http://free.nchc.org.tw/drbl-core/i386/base/synthesis.hdlist.drbl-testing.cz
found probed hdlist (or synthesis) as synthesis.hdlist.drbl-testing.cz
...retrieving done
examining hdlist file [/var/cache/urpmi/partial/hdlist.drbl-testing.cz]
examining synthesis file [/var/cache/urpmi/partial/hdlist.drbl-testing.cz]
writing list file for medium "drbl-testing"
found 0 headers in cache
removing 0 obsolete headers in cache
wrote config file [/etc/urpmi/urpmi.cfg]
added medium drbl-unstable
wrote config file [/etc/urpmi/urpmi.cfg]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Main (MDK2007.01).cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Contrib (MDK2007.02).cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.drbl-stable.cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.drbl-testing.cz]
retrieving source hdlist (or synthesis) of "drbl-unstable"...
http://free.nchc.org.tw/drbl-core/i386/base/synthesis.hdlist.drbl-unstable.cz
found probed hdlist (or synthesis) as synthesis.hdlist.drbl-unstable.cz
...retrieving done
examining hdlist file [/var/cache/urpmi/partial/hdlist.drbl-unstable.cz]
examining synthesis file [/var/cache/urpmi/partial/hdlist.drbl-unstable.cz]
writing list file for medium "drbl-unstable"
found 0 headers in cache
removing 0 obsolete headers in cache
wrote config file [/etc/urpmi/urpmi.cfg]
--------------------------------------------------------------------
The urpmi setting is finished.
The package(s) are already installed
*****************************************************.
Do you want to install those network installation boot images so that you can let client to install some Linux distribution (Debian, Ubuntu, RedHat Linux, Fedora Core, Mandriva, and OpenSuSE) via network ? (Assume that your client machine has harddisk and it is possible you will install Linux into that, say Y)
[y/N]
Do you want to use the serial console output for clients ?
If you do NOT know anything about this, say "N" here, otherwise clients might show NOTHING on the screen !
[y/N]
*****************************************************.
Which CPU architecture kernel do you want to assign for DRBL clients ? [0/1/2]
0 -> i386 level CPU
1 -> i586 level CPU
2 -> Use the same CPU level with that of this DRBL server
Note! Note Note!  Note!  Note!  Note!  Note!
note!!! If your client machine(s) is not the same level with server, please answer "0" or "1", otherwise your client machine(s) will NOT be able to boot.
If you use wrong CPU level kernel, the glibc and openssl package might use i686 or i386, the kernel might use i686, i586 or i386, which might be not suitable to all your machines.
If you are not sure, "1" is recommended, this will still have good performance and compatibility.
[1]
*****************************************************.
The optimization for your system is set to "i586".
*****************************************************.
Do you want to upgrade operating system ?
[y/N]
*****************************************************.
Preparing the kernel for client...
Only one kernel meets your requirement:  kernel-2.6.17.5mdv-1-1mdv2007.0 (in release), use it.
Chosen kernel: kernel-2.6.17.5mdv-1-1mdv2007.0
Downloading i586 kernel-2.6.17.5mdv-1-1mdv2007.0 from ftp://mdk.linux.org.tw//pub/mandrake-devel/2007.0/i586/media/main/release/kernel-2.6.17.5mdv-1-1mdv2007.0.i586.rpm to /tmp/client_kernel_PKG.qk8769/...
*****************************************************.
2nd, installing the necessary files for DRBL...
*****************************************************.

ftp://mdk.linux.org.tw//pub/mandrake-devel/2007.0/i586/media/main/release/ypbind-1.19.1-4mdv2007.0.i586.rpm
ftp://mdk.linux.org.tw//pub/mandrake-devel/2007.0/i586/media/main/release/dos2unix-1.0.0-2mdv2007.0.i586.rpm
ftp://mdk.linux.org.tw//pub/mandrake-devel/2007.0/i586/media/main/release/nfs-utils-1.0.9-3mdv2007.0.i586.rpm
ftp://mdk.linux.org.tw//pub/mandrake-devel/2007.0/i586/media/main/release/yp-tools-2.9-4mdv2007.0.i586.rpm
ftp://mdk.linux.org.tw//pub/mandrake-devel/2007.0/i586/media/main/release/ntp-4.2.0-30mdv2007.0.i586.rpm
ftp://mdk.linux.org.tw//pub/mandrake-devel/2007.0/i586/media/main/release/tftp-server-0.42-2mdk.i586.rpm
ftp://mdk.linux.org.tw//pub/mandrake-devel/2007.0/i586/media/main/release/dhcp-server-3.0.4-2mdv2007.0.i586.rpm
ftp://mdk.linux.org.tw//pub/mandrake-devel/2007.0/i586/media/main/release/ypserv-2.19-2mdv2007.0.i586.rpm
http://free.nchc.org.tw/drbl-core/i386/base/../RPMS.drbl-testing/drbl-ntfsprogs-1.13.1-4.i386.rpm
http://free.nchc.org.tw/drbl-core/i386/base/../RPMS.drbl-testing/lzop-1.02-0.6drbl.i386.rpm
http://free.nchc.org.tw/drbl-core/i386/base/../RPMS.drbl-testing/partimage-0.6.5_beta3-4drbl.i386.rpm
http://free.nchc.org.tw/drbl-core/i386/base/../RPMS.drbl-testing/ddrescue-1.11_0.0.6-3drbl.i386.rpm
http://free.nchc.org.tw/drbl-core/i386/base/../RPMS.drbl-testing/etherboot-5.4.2-2drbl.i386.rpm
http://free.nchc.org.tw/drbl-core/i386/base/../RPMS.drbl-testing/drbl-chntpw-0.0.20040818-7.i386.rpm
http://free.nchc.org.tw/drbl-core/i386/base/../RPMS.drbl-unstable/clonezilla-1.4.3-16.i386.rpm
http://free.nchc.org.tw/drbl-core/i386/base/../RPMS.drbl-unstable/udpcast-20060921-1drbl.i386.rpm
http://free.nchc.org.tw/drbl-core/i386/base/../RPMS.drbl-unstable/mkpxeinitrd-net-1.1-17.i386.rpm
http://free.nchc.org.tw/drbl-core/i386/base/../RPMS.drbl-unstable/freedos-1.0-11drbl.i386.rpm
installing ypbind-1.19.1-4mdv2007.0.i586.rpm dos2unix-1.0.0-2mdv2007.0.i586.rpm yp-tools-2.9-4mdv2007.0.i586.rpm ntp-4.2.0-30mdv2007.0.i586.rpm tftp-server-0.42-2mdk.i586.rpm dhcp-server-3.0.4-2mdv2007.0.i586.rpm ypserv-2.19-2mdv2007.0.i586.rpm nfs-utils-1.0.9-3mdv2007.0.i586.rpm mkpxeinitrd-net-1.1-17.i386.rpm freedos-1.0-11drbl.i386.rpm etherboot-5.4.2-2drbl.i386.rpm clonezilla-1.4.3-16.i386.rpm partimage-0.6.5_beta3-4drbl.i386.rpm lzop-1.02-0.6drbl.i386.rpm drbl-ntfsprogs-1.13.1-4.i386.rpm ddrescue-1.11_0.0.6-3drbl.i386.rpm udpcast-20060921-1drbl.i386.rpm drbl-chntpw-0.0.20040818-7.i386.rpm from /var/cache/urpmi/rpms
Preparing...                     #############################################
1/18: udpcast               #############################################
2/18: partimage             #############################################
3/18: clonezilla            #############################################
4/18: drbl-chntpw           #############################################
5/18: ddrescue              #############################################
6/18: drbl-ntfsprogs        #############################################
7/18: lzop                  #############################################
8/18: etherboot             #############################################
9/18: freedos               #############################################
10/18: mkpxeinitrd-net       #############################################
11/18: nfs-utils             #############################################
12/18: ypserv                #############################################
13/18: dhcp-server           #############################################
14/18: tftp-server           #############################################
15/18: ntp                   #############################################
16/18: dos2unix              #############################################
17/18: yp-tools              #############################################
18/18: ypbind                #############################################
----------------------------------------------------------------------
More information on package nfs-utils-1.0.9-3mdv2007.0.i586
This package supports secure nfs using kerberos. In order to take advantage of this
you must set SECURE_NFS=yes in the /etc/sysconfig/nfs file and also configure the
kerberos parts.
----------------------------------------------------------------------
*****************************************************.
Install kernel for clients... ...
In ayo repository, searching the latest kernel ...
*****************************************************.
Using kernel package (rpm or deb) for client...
*****************************************************.
The version number for your OS: Mandriva 2007.0
*****************************************************.
Install kernel for clients... ...
Installing /tmp/client_kernel_PKG.qk8769/kernel-2.6.17.5mdv-1-1mdv2007.0.i586.rpm for clients...
It will take several minutes to install this kernel, please be patient...
warning: /tmp/client_kernel_PKG.qk8769/kernel-2.6.17.5mdv-1-1mdv2007.0.i586.rpm: Header V3 DSA signature: NOKEY, key ID 26752624
Preparing...                ########################################### [100%]
1:kernel-2.6.17.5mdv     ########################################### [100%]
done!
Generating modules.dep and map files for clients... done!
*****************************************************.
*****************************************************.
Creating the image files for PXE and Etherboot client, this will take a few minutes ...
The latest kernel for DRBL clients is 2.6.17-5mdv
Running /opt/drbl/sbin/mknic-nbi --kernel 2.6.17-5mdv --all --no-modules
Will client check DHCP server name is "drbl" or not: yes
The maximum times to try to get IP address for a client: 3
The pause time after network card is up: 0
Using the kernel modules from /tftpboot/node_root//lib/modules...
The selected kernel for DRBL clients is: 2.6.17-5mdv
Creating the network boot initrd for PXE clients...
Use kernel modules from /tftpboot/node_root//lib/modules/2.6.17-5mdv.
Creating the EXT2 initrd...
Finished!
Done!
*****************************************************.
Creating config file for PXE clients...
Copying pxelinux.0, menu.c32, vesamenu.c32, chain.c32 and memdisk to /tftpboot/nbi_img...
Copying memtest86+ to /tftpboot/nbi_img...
Copying FreeDOS files to /tftpboot/nbi_img/...
Generating default pxelinux config (/tftpboot/nbi_img/pxelinux.cfg/default)...
Adding menus for DRBL, local boot, memtest86+, FreeDOS...
Adding netinstall-Fedora-5.92-i386 menu...
done!
*****************************************************.
Done!
[mdv07]~>sudo /opt/drbl/sbin/drblpush -i
Language | y|  ?
[0]: English
[1]: Chinese Traditional (Big5) - Taiwan |  (jX) - xW
[2]: Chinese Traditional (UTF-8, Unicode) - Taiwan | 中 (碼) - 0
[0]
******************************************************
Hint! When a yes/no option is available, the default value is uppercase, Ex. (y/N), the default is "N", when you press "Enter", it will use "N". If you are not sure which one to choose, you can just press "Enter" key.
******************************************************
Searching the installed packages for DRBL server...This might take several minutes...
Finished searching the installed packages for DRBL server.
******************************************************
------------------------------------------------------
The interactive mode let you supply the information of your DRBL environment.
------------------------------------------------------
------------------------------------------------------
DOMAIN is unset, please enter DOMAIN now:
[drbl.sf.net]
Set DOMAIN as drbl.sf.net
------------------------------------------------------
NISDOMAIN is unset, please enter NISDOMAIN now:
[penguinzilla]
Set DOMAIN as penguinzilla
------------------------------------------------------
Please enter the client hostname prefix:
[mdv07]
Set the client hostname prefix as mdv07
------------------------------------------------------
Found private IP "192.168.120.207" in eth0 on your system!
Found private IP "192.168.123.254" in eth1 on your system!
Found private IP "192.168.201.254" in eth2 on your system!
Configured ethernet card(s) found in your system: eth0 eth1 eth2
------------------------------------------------------
We are unable to find the public IP address of this server,
Which ethernet port in this server is for public Internet accsess, not for DRBL connection ?
Available ethernet ports in this server:
eth0 (192.168.120.207), eth1 (192.168.123.254), eth2 (192.168.201.254),
[eth0]
The ethernet port you choose for the WAN connection: eth0
The ethernet port(s) for DRBL environment:  eth1 eth2
******************************************************
******************************************************
Now we can collect the MAC address of clients!
If you want to let the DHCP service in DRBL server offer same IP address to client every time when client boot, and you never did this procedure, you should do it now!
If you already have those MAC addresses of clients, you can put them into different group files (These files number is the same number of networks cards for DRBL service). In this case, you can skip this step.
This step helps you to record the MAC addresses of clients, then divide them into different groups. It will save your time and reduce the typos.
The MAC addresses will be recorded turn by turn accroding to the boot of clients,
and they will be put into different files according to the network card in server, file name will be like macadr-eth1.txt, macadr-eth2.txt... You can find them in directory /etc/drbl.
Please boot the clients by order, make sure they boot from etherboot or PXE!
Do you want to collect them ?
[y/N]
******************************************************
OK! Let's continue...
******************************************************
Do you want to let the DHCP service in DRBL server offer same IP address to the client every time when client boots (If you want this function, you have to collect the MAC addresses of clients, and save them in file(s) (as in the previous procedure)). This is for the clients connected to DRBL server's ethernet network interface eth1 ?
[y/N]
******************************************************
OK! Let's continue, we will set the IP address of clients by "first boot gets IP first" instead of fixed one!
******************************************************
What is the initial number do you want to use in the last set of digits in the IP (i.e. the initial value of d in the IP address a.b.c.d) for DRBL clients connected to this ethernet port eth1.
[1]
******************************************************
How many DRBL clients (PC for students) connected to DRBL server's ethernet network interface eth1 ?
Please enter the number:
[12] 2
******************************************************
The final number in the last set of digits in the clients' IP is "2".
We will set the IP address for the clients connected to DRBL server's ethernet network interface eth1 as: 192.168.123.1 - 192.168.123.2
Accept ? [Y/n]
******************************************************
OK! Let's continue...
Do you want to let the DHCP service in DRBL server offer same IP address to the client every time when client boots (If you want this function, you have to collect the MAC addresses of clients, and save them in file(s) (as in the previous procedure)). This is for the clients connected to DRBL server's ethernet network interface eth2 ?
[y/N]
******************************************************
OK! Let's continue, we will set the IP address of clients by "first boot gets IP first" instead of fixed one!
******************************************************
What is the initial number do you want to use in the last set of digits in the IP (i.e. the initial value of d in the IP address a.b.c.d) for DRBL clients connected to this ethernet port eth2.
[1]
******************************************************
How many DRBL clients (PC for students) connected to DRBL server's ethernet network interface eth2 ?
Please enter the number:
[12] 1
******************************************************
The final number in the last set of digits in the clients' IP is "1".
We will set the IP address for the clients connected to DRBL server's ethernet network interface eth2 as: 192.168.201.1 - 192.168.201.1
Accept ? [Y/n]
******************************************************
OK! Let's continue...
******************************************************
The Layout for your DRBL environment:
******************************************************
NIC    NIC IP                    Clients
+-----------------------------+
|         DRBL SERVER         |
|                             |
|    +-- [eth0] 192.168.120.207 +- to WAN
|                             |
|    +-- [eth1] 192.168.123.254 +- to clients group 1 [ 2 clients, their IP
|                             |            from 192.168.123.1 - 192.168.123.2]
|    +-- [eth2] 192.168.201.254 +- to clients group 2 [ 1 clients, their IP
|                             |            from 192.168.201.1 - 192.168.201.1]
+-----------------------------+
******************************************************
Total clients: 3
******************************************************
------------------------------------------------------
Do you want to use Clonezilla box mode only ? If so, some functions about DRBL will be suppressed, and you will have an elegant mode to do clonezilla. Note! In this mode, the setting and config files of client will not be saved to the DRBL server! They just use once and will vanish after the machine shutdowns!
[y/N]
Clonezilla box mode is NOT set, you will have the full functions of DRBL box!
******************************************************
******************************************************
------------------------------------------------------
Do you want to use DRBL SSI (Single system image) mode ? If yes, the loading and necessary disk space of server will be lighter. NOTE! In this mode, (1) The client machine memory at least 256 MB. (2) The setting and config files of client will not be saved to the DRBL server! They just use once and will vanish after the machine shutdowns! Besides, if you modify any file in the template client (located in /tftpboot/nodes/), you have to run /opt/drbl/sbin/gen_ssi_files to create the template tarball in /tftpboot/node_root/drbl_ssi/.
[y/N]
DRBL SSI mode is NOT set, you will have the full functions of DRBL box!
******************************************************
------------------------------------------------------
If there is a local harddrive in your client machine,
do you want to create swap file in it so that client has more memory to use ? (This step will NOT destroy any data in that harddisk!)
[Y/n]
******************************************************
OK! We will try to create a swap file for your client if it has local ard drive !
------------------------------------------------------
What's the maximun size (Megabytes) for the swap file ?
We will try to allocate the size for you, but it's not enough, 60% of the free space will be used.
[128]
maxswapsize=128
******************************************************
------------------------------------------------------
Which mode do you want the clients to use after they boot ?
"1": Graphic mode (X window system) (default),
"2": Text mode.
[1]
The clients will enter graphic mode after booting.
******************************************************
------------------------------------------------------
Which mode do you want when client boots in graphic mode ?
0: normal login, 1: auto login, 2: timed login
[0]
The clients will wait for user to login when they boot.
******************************************************
------------------------------------------------------
Do you want to set the root's password for clients instead of using same root's password copied from server ? (For better security)
[y/N]
OK! Let's continue...
------------------------------------------------------
Do you want to set the pxelinux password for clients so that when client boots, a password must be entered to startup (For better security)
[y/N]
OK! Let's continue...
------------------------------------------------------
Do you want to set the boot prompt for clients ?
[Y/n]
How many 1/10 sec is the boot prompt timeout for clients ?
[70]
OK! Let's continue...
------------------------------------------------------
------------------------------------------------------
Do you want to use graphic background for PXE menu when client boots ?
Note! If client fails to boot, you can switch to text mode by running "/opt/drbl/sbin/switch-pxe-bg-mode -m text".
[Y/n]
OK! Let's continue...
------------------------------------------------------
------------------------------------------------------
By using alias interface, every client can have 2 IPs,
one of them is private IP for clients connected to DRBL server, and the other is public IP for clients directly connected to WAN from switch!
Do you want to setup public IP for clients ?
[y/N]
------------------------------------------------------
Do you want to let DRBL clients have an option to run terminal mode ? i.e. you want to let that client run remote display (which will mostly use resources of server), say "Y" here.
Note!
1. If your server is not powerful, say "no" here.
2. By saying "yes" here, we will turn on xdmcp,
It is never a safe thing to turn on that.  Setting up /etc/hosts.allow and /etc/hosts.deny to only allow local access is another alternative but not the safest.
Firewalling port 177 is the safest if you wish to have xdmcp on.
Read the manual for more notes on the security of XDMCP.
Please set it by yourself!
3. If you say "yes" here, you might have to restart your desktop environment manager (gdm/kdm) later, remember to save your data before you close applications!
Do you want to let client has an option torun terminal mode ?
[y/N]
OK! Let's continue...
------------------------------------------------------
******************************************************
Checking the kernel config "/boot/config-2.6.17-5mdv..."
The running kernel in the server supports NFS over TCP!
Note! If you change the running kernel in the server, and not sure wheither the kernel supports NFS over udp or tcp, you'd better to re-run "drblpush -i" again to avoid the client boots in failure!
Press Enter to continue...
------------------------------------------------------
The calculated NETWORK for eth1 is 192.168.123.0.
The calculated NETWORK for eth2 is 192.168.201.0.
******************************************************
******************************************************
We are now ready to deploy the files to system!
Do you want to continue ?
Warning! If you go on, your firewall rules will be overwritten during the setup!
The original rules will be backuped as iptables.drblsave in system config directory (/etc/sysconfig or /etc/default).
[Y/n]
******************************************************
OK! Let's do it!
------------------------------------------------------
Checking the necessary disk space... done!
Copying the config file to /etc/drbl... done!
Backup the original /etc/hosts as /etc/hosts.drblsave... done!
Generate the /etc/hosts for clients connected to eth1... eth2... done!
Cleaning the stale files of the diskless nodes if they exist... done!
*****************************************************.
*****************************************************.
The version number for your Linux: MDV2007.0
Keeping the old common root files if they exist...
Keeping old nodes if they exist...
Creating common root files... This might take several minutes........... done!
Update the kernel for client if necessary...
The DRBL client uses i686 kernel with version 2.6.17-5mdv...
Trying to update the /tftpboot/node_root/lib/modules/2.6.17-5mdv from server's /lib/modules/... This might take several minutes...
Found kernel modules in /lib/modules/2.6.17-5mdv and its arch "i686" matches client's "i686"...
Syncing /lib/modules/2.6.17-5mdv to client's common root...
Syncing /boot/*-2.6.17-5mdv* to client's common root...
Generating the /tftpboot/node_root/lib/modules/2.6.17-5mdv/modules.dep
Copying the directory /etc/ to clients common root /tftpboot/node_root...
Cleaning the ssh key file ssh_host_dsa_key copied from server... done!
Cleaning the ssh key file ssh_host_dsa_key.pub copied from server... done!
Cleaning the ssh key file ssh_host_key copied from server... done!
Cleaning the ssh key file ssh_host_key.pub copied from server... done!
Cleaning the ssh key file ssh_host_rsa_key copied from server... done!
Cleaning the ssh key file ssh_host_rsa_key.pub copied from server... done!
Needed by script(s) in runlevel 3: acpid(start) acpid(start) acpid(stop) acpid(stop)
Needed by script(s) in runlevel 2: freshclam(start) freshclam(start) freshclam(stop) freshclam(stop)
Needed by script(s) in runlevel 2: sshd(start) sshd(stop) ypserv(start) ypserv(stop)
Needed by script(s) in runlevel 2: ypserv(start) ypserv(stop) ypxfrd(start) ypxfrd(stop) yppasswdd(start) yppasswdd(stop)
Needed by script(s) in runlevel 2: xinetd(start) xinetd(stop)
service udev does not support chkconfig
Needed by script(s) in runlevel 2: ypxfrd(start) ypxfrd(start)
The startup services for DRBL client are:
firstboot netfs portmap crond nfslock sshd crond xfs ypbind harddrake dm alsa sound keytable haldaemon messagebus acpid drblthincli mkswapfile arm-wol
Using udev for clients... Deleting the accounts (except root) in the clients common root template... done!
Enabling the NIS client in the common root template... done!
Creating some necessary files in the clients common root template....... done!
Creating DRBL client: mdv07101 192.168.123.1... The display manager we selected for your DRBL client is "kdm"...
Setting node 192.168.123.1 as normal_login... done!
Creating DRBL client: mdv07102 192.168.123.2... The display manager we selected for your DRBL client is "kdm"...
Setting node 192.168.123.2 as normal_login... done!
Creating DRBL client: mdv07201 192.168.201.1... The display manager we selected for your DRBL client is "kdm"...
Setting node 192.168.201.1 as normal_login... done!
Template client for DRBL SSI is 192.168.123.1
Using template host /tftpboot/nodes/192.168.123.1
Resetting files of /tftpboot/node_root/drbl_ssi for DRBL SSI... done!
Generating SSH host keys for client 192.168.123.1 if they do not exist...done!
Generating the files for DRBL single system image template... etc... var... opt/drbl... Root's openssh public key... done!
Disable the password in pxelinux simple menu for all clients...
done!
Now set the necessary services for DRBL server - dhcp, tftp, nfs, and nis to be on when the machine start up.
Generating the NFS exports for DRBL clients...
Backup the original /etc/exports as /etc/exports.drblsave
Exporting to clients by IP address line-by-line...
Full DRBL mode, exporting client's directories etc, var, root...
The /etc/exports setting is ok now!
Now start the NAT service...
Stop the NAT service first...
bs]ww] ACCEPT G                          [ \ ]
bxs{Wh /etc/sysconfig/iptablesG                    [ \ ]
ip_forward is already on.
Now set the YP securenets...
Backup the original /var/yp/securenets as /var/yp/securenets.drblsave
The /var/yp/securenets setting is done!
Force to turn on dhcpd in this RH-like DRBL server...
Force to turn on xinetd in this RH-like DRBL server...
Force to turn on portmap in this RH-like DRBL server...
Force to turn on iptables in this RH-like DRBL server...
Force to turn on ypserv in this RH-like DRBL server...
netfs is needed by ypserv in runlevel 2
Force to turn on ypbind in this RH-like DRBL server...
Force to turn on yppasswdd in this RH-like DRBL server...
Force to turn on ypxfrd in this RH-like DRBL server...
Force to turn on nfs in this RH-like DRBL server...
Force to turn on nfslock in this RH-like DRBL server...
Force to turn on ntpd in this RH-like DRBL server...
Update YP...
Turn off the DRBL SSI mode in pxelinux config...
Setting drbl_ssi_mode="no" in /etc/drbl/drbl_deploy.conf and /etc/drbl/drblpush.conf... done!
done!
Now start the service:  dhcpd xinetd portmap iptables ypserv ypbind yppasswdd ypxfrd nfs nfslock ntpd
bҰ dhcpdG                                                [ \ ]
b xinetdG                                               [ \ ]
bҰ xinetdG                                               [ \ ]
b portmap AȡG                                         [ \ ]
bҰ portmapperG                                           [ \ ]
bM iptables WhG
[ \ ]
Ұ YP server AȡG                                           [ \ ]
bj NIS ...                                          [ \ ]
ť NIS Alocalhost
bҰ YP passwd AȡG                                       [ \ ]
Ұ YP map AG                                          [ \ ]
bҰ NFS AȡG                                             [ \ ]
Starting NFS daemon:                                            [ \ ]
Starting NFS mountd:                                            [ \ ]
Starting RPC idmapd:                                            [ \ ]
Stopping NFS locking:                                           [ \ ]
Stopping NFS statd:                                             [ \ ]
Starting NFS statd:                                             [ \ ]
bҰ ntpdG                                                 [ \ ]
ip_forward is already on.
The GDM or KDM config file is NOT found! Skip setting the DM! Maybe you will not be able to make this DRBL server as thin client server!
Clean all the previous saved config file if they exist...done!
Turn on the boot prompt for PXE client...done!
Turn off the thin client option in PXE boot menu...done!
*****************************************************.
Enjoy DRBL!!!
http://drbl.nchc.org.tw; http://drbl.sf.net
NCHC Free Software Labs, Taiwan. http://free.nchc.org.tw
*****************************************************.
If you like, you can reboot the DRBL server now to make sure everything is ready...(This is not necessary, just an option.).
*****************************************************.
DRBL server is ready! Now set the client machines to boot from PXE or Etherboot, then turn on them (Refer to http://drbl.sourceforge.net for more details).
Note! If you use Etherboot in your client machine, version 5.4.0 or newer is required!!!.
