Sistem Departmanı Stajı

Transkript

1 Sistem Departmanı Stajı 4. Hafta Raporu Ağustos 28, 2010 Zemre Arslan

2 Ubuntu Server üzerine Clonezilla Server Kurulumu İçerik 1. Clonezilla Server Nedir? 2. Clonezilla Server Nasıl Çalışır? 2.1 İstemciyi network üzerinden boot etme 3. Ubuntu Server üzerine Clonezilla Server Kurulumu 4. Kaynakça 1. Clonezilla Server Nedir? Clonezilla Norton Ghost ya da Acronis gibi popüler imaj alma programlarının aksine OpenSource ücretsiz bir disk imajı alma (clone) yazılımıdır. Clonezilla live ve Clonezilla SE (Server edition) olmak üzere iki çeşit Clonezilla yazılımı mevcuttur. Clonezilla live ile tek bir makine için backup alma ve restore(onarım) işlemleri gerçekleştirilebilir. Ancak biz alacağımız imajı birden fazla homojen makineye ağ üzerinden atacağımız için server edition ı tercih edeceğiz. Clonezilla SE, sitesinden ücretsiz olarak indirilebilir. İndirilen iso image ını bir compact disk e yazdıktan sonra, bilgisayarımızı cd den boot edip Clonezilla Server kurulumuna geçebiliriz. 2. Clonezilla Server Nasıl Çalışır? Clonezilla Server, Diskless Remote Boot in Linux (DRBL) kullanmaktadır. DRBL, bir bilgisayarın üzerinde bir sistem olmamasına rağmen network üzerinden boot edilebilmesini sağlar. DRBL, Clonezilla kurulumu sırasında defaultta geliyor; yani özel olarak DRBL için kurulum yapmamıza gerek yoktur. Clonezilla Server kurulumu tamamlandıktan sonra imajı alınacak ya da restore işlemleri gerçekleştirilecek olan LAN daki bilgisayarları network üzerinden boot etmek gerekmekte. Böylelikle network üzerinden boot edilen bilgisayarların DRBL üzerindeki DHCP sunucusundan IP almalarını sağlıyoruz. İstemcimiz, DRBL sunucusu ile iletişime geçmiş oluyor ve gerekli imaj/restore işlemleri, bu şekilde gereçekleştirilebiliyor.

3 2.1 İstemciyi network üzerinden boot etme DRBL sunucusu ile istemcinin irtibatı için bilgisayarın network üzerinden boot edilmesi gerektiğinden bahsetmiştik. Ancak bazı sistemler network üzerinden boot u desteklemeyebilirler. Bizim elimizdeki sistemlerde de network boot yapılamadığından Etherboot projesinin yeni versiyonu olan gpxe den yararlandık. Etherboot projesi takımı yıllardır sistemlerin network üzerinden boot edilebilmesini sağlayan OpenSource kodlar geliştirmekle meşguller; bu kodlar boot edilebilen tüm taşınabilir medyalara yüklenebilmekte. Biz ellerinde hazır olan gpxe iso image larından birini cd ye yazdık ve bilgisayarı CD üzerinden başlattık; böylelikle bilgisayar network üzerinden başlatılmış oldu. Sürekli bir çözüm için gpxe, NIC lerin (ethernet kartı) ROM una da yazılabilmekte; ancak biz imaj alma işlemini de server üzerinden eşzamanlı yaparak zaman kazanmak istediğimizden bunu tercih etmeyeceğiz. Ayrıntılı bilgi için şu link incelenebilir: 3. Ubuntu Server üzerine Clonezilla Server Kurulumu Öncelikle Server kurulu olan sistemimizde ethernet yapılandırması yapmamız gerekmektedir. DRBL sunucusu üzerinde DHCP servisinin çalıştığından bahsetmiştik. Bunun için kendi networkümüzden ayrı bir networkte çalışmak daha sağlıklı bir sonuç elde edilmesini sağlayacaktır. Bu sebeple ethernet kartımızı eth0 a ikincil bir ip (alias) tanımlamamız gerekmektedir. Bunun için /etc/network/interfaces dosyasının içeriğini düzenlemeliyiz. Aşağıda tanımladığımız alias ip satırlarını belirtilen dosyanın altına ekleyelim: auto eth0:1 iface eth0:1 inet static address netmask Kendi networkümüz networkü olduğundan DRBL için farklı bir network tanımladık.(clonezillayı multicast olarak kullanacağımız için) Ayrıca sistemimiz üzerindeki ethernet kartlarını görmek için /etc/udev/rules.d/70-persistent-net.rules dosyası incelenebilir. Bu dosyayı editleyerek onboard ve external ethernet kartı problemlerinizi çözebilirsiniz. Network yapılandırmamızı tamamladık. Şimdi DRBL için dizin oluşturalım. #mkdir usr/src/drbl komutu ile klasörümüzü oluşturduk. Şimdi #cd usr/src/drbl ile dizinin içine girelim zira tüm yapılandırmalarımızı bu dizin içerisinde yapacağız. Şimdi DRBL nin GPG anahtarını indirip import etmemiz gerekmekte. Bunun için; #wget ile anahtarımızı aldık. Şimdi anahtarı #apt-key add GPG-KEY-DRBL ile import edelim. DRBL paketini

4 # wget ile download edelim. Paket drbl i386.rpm formatında gelmektedir. Rpm paketleri RedHat ile uyumludur. Biz bunu debianda import edeceğimiz için; *.deb formatına çevirmemiz gerekmekte. Bunu alien adı verilen bir tool ile yapabilmekteyiz. #apt-get install alien komutu ile önce alien toolu yüklüyoruz. Daha sonra #alien drbl i386.rpm komutu ile rpm paketimizi deb uzantılı pakete çevirmiş bulunmaktayız. Fakat burada dikkatli incelenirse yeni.deb uzantılı pakette alien, versiyon numarasını bir arttırmıştır. (yeni hali drbl_1.9.2_20.i386.deb olmuştur) Bu bir problem teşkil etmemektedir ancak istenilirse k parametresi ile alienın sadece dosya uzantısını değiştirmesi sağlanabilir. Şimdi elimizdeki debian paketini yüklemek için #dpkg -i drbl_1.9.2_20.i386.deb komutu yürütülmelidir. /etc/apt/sources.list dosyası altına aşağıdaki satırlar eklenmelidir: deb lucid main restricted universe multiverse deb drbl stable Herhangi bir hata ile karşılaşılmadıysa DRBL paketi başarıyla yüklenmiş demektir. Şimdi son aşamada # /opt/drbl/sbin/drblsrv i komutunu yürütüyoruz. Sorulan sorulara cevap vereceğiz ve bu doğrultuda drbl paketi bizden otomatik olarak hangi paketleri yüklemesi gerektiği bilgisini alacak.verilmesi gereken cevapları kırmızı olarak renklendirdim; inceleyiniz. 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 Debian Linux... Do you want to install those network installation boot images so that you can let client to install some GNU/Linux distributions (Debian, Ubuntu, RedHat Linux, Fedora Core, Mandriva, CentOS and OpenSuSE...) via network? ///NOTE/// This action will download a lot of files (> 100 MB totally) from Internet, so it might take a few minutes. If your client machine has harddisk and it is possible you will install GNU/Linux into that, say Y here. If you say "no" here, feel free to run drbl-netinstall to install them later. [y/n] n This GNU/Linux distribution uses one kernel to support SMP and non-smp arch. 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] n It's Ubuntu as server, so generic kernel is available.

5 Which CPU architecture kernel do you want to assign for DRBL clients? 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. [2] 0 //Bu kısım biraz uzun sürecektir. Bir işlem yapılmasına ihtiyaç yoktur. Bekleyelim.. Selecting previously deselected package drbl-ntfsprogs. Unpacking drbl-ntfsprogs (from.../drbl-ntfsprogs_ _i386.deb)... Selecting previously deselected package drbl-partimage. Unpacking drbl-partimage (from.../drbl-partimage_ drbl_i386.deb)... Selecting previously deselected package mkswap-uuid. Unpacking mkswap-uuid (from.../mkswap-uuid_ _i386.deb)... Selecting previously deselected package partclone. Unpacking partclone (from.../partclone_ drbl_i386.deb)... Selecting previously deselected package pigz. Unpacking pigz (from.../pigz_ drbl_i386.deb)... Selecting previously deselected package tftpd-hpa. Unpacking tftpd-hpa (from.../tftpd-hpa_5.0-11ubuntu2_i386.deb)... Processing triggers for man-db... Processing triggers for ureadahead... Processing triggers for install-info... Setting up gawk (1:3.1.6.dfsg-4build1)... Setting up libslp1 ( )... Setting up portmap ( ubuntu2)... portmap start/running, process Setting up nis ( )... * Stopping NIS services [ OK ] * Setting NIS domainname to: localdomain * Starting NIS services [ OK ] Setting up aoetools (30-3ubuntu1)... * Starting AoE devices discovery and mounting AoE filesystems * not started. Setting up bc ( )... Setting up clonezilla ( )... Setting up libcurl3 ( ubuntu1)... Setting up curl ( ubuntu1)... Setting up dhcp3-server ( ubuntu3)...

6 Generating /etc/default/dhcp3-server... * Starting DHCP server dhcpd3 * check syslog for diagnostics. [fail] invoke-rc.d: initscript dhcp3-server, action "start" failed. Setting up dialog ( )... Setting up discover-data ( )... Setting up libdiscover2 ( )... Setting up discover ( )... Setting up disktype (9-1)... Setting up etherwake (1.09-3)... Setting up ethtool ( )... Setting up freedos (1.0-15drbl)... Setting up genisoimage (9: ubuntu1)... Setting up gpxe ( drbl)... Setting up grub ( ubuntu60)... Setting up lftp ( )... Setting up libdevmapper-event (2: ubuntu4)... Setting up libdigest-sha1-perl (2.12-1build1)... Setting up libevent ( stable-1)... Setting up libgssglue1 (0.1-4)... Setting up libnfsidmap2 (0.23-2)... Setting up librpcsecgss3 (0.19-2)... Setting up watershed (5)... update-initramfs: deferring update (trigger activated) Setting up lvm2 ( ubuntu4)... update-initramfs: deferring update (trigger activated) Setting up mknbi ( ubuntu1)... Setting up mkpxeinitrd-net (1.5-7)... Setting up mtools ( ubuntu1)... Ignoring install-info called from maintainer script The package mtools should be rebuilt with new debhelper to get trigger support Setting up netcat-traditional ( )... Setting up netcat ( )... Setting up nfs-common (1: ubuntu4)... Creating config file /etc/idmapd.conf with new version Creating config file /etc/default/nfs-common with new version Adding system user `statd' (UID 105)...

7 Adding new user `statd' (UID 105) with group `nogroup'... Not creating home directory `/var/lib/nfs'. statd start/running, process gssd stop/pre-start, process idmapd stop/pre-start, process Setting up nfs-kernel-server (1: ubuntu4)... Creating config file /etc/exports with new version Creating config file /etc/default/nfs-kernel-server with new version * Exporting directories for NFS kernel daemon... [ OK ] * Starting NFS kernel daemon [ OK ] Setting up reiserfsprogs (1: build1)... Setting up sdparm (1.02-1)... Setting up ssh (1:5.3p1-3ubuntu4)... Setting up syslinux (2:3.63+dfsg-2ubuntu3)... Setting up traceroute ( )... update-alternatives: using /usr/bin/traceroute.db to provide /usr/bin/traceroute (traceroute) in auto mode. update-alternatives: using /usr/bin/traceroute6.db to provide /usr/bin/traceroute6 (traceroute6) in auto mode. update-alternatives: using /usr/bin/lft.db to provide /usr/bin/lft (lft) in auto mode. update-alternatives: using /usr/bin/traceproto.db to provide /usr/bin/traceproto (traceproto) in auto mode. update-alternatives: using /usr/bin/traceroute-nanog.db to provide /usr/bin/traceroute-nanog (traceroute-nanog) in auto mode. update-alternatives: using /usr/sbin/tcptraceroute.db to provide /usr/sbin/tcptraceroute (tcptraceroute) in auto mode. Setting up udpcast ( drbl)... Setting up unzip (6.0-1build1)... Setting up vblade (20-1ubuntu1)... * Starting vblade deaemons vblade Setting up wakeonlan ( )... Setting up zip (3.0-2)... Setting up drbl-chntpw ( )... Setting up drbl-etherboot ( )... Setting up drbl-lzop ( drbl)... Setting up drbl-ntfsprogs ( )... Setting up drbl-partimage ( drbl)... Setting up mkswap-uuid ( )... Setting up partclone ( drbl)... Setting up pigz ( drbl)... Setting up tftpd-hpa (5.0-11ubuntu2)... tftpd-hpa start/running, process Processing triggers for libc-bin... ldconfig deferred processing now taking place Processing triggers for initramfs-tools... update-initramfs: Generating /boot/initrd.img generic

8 Trying to upgrade some necessary packages if available... In ayo repository, searching the latest kernel... The latest kernel in the ayo repository is linux-image Use the kernel linux-image from apt repository! Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: fdutils linux-doc linux-source linux-tools The following NEW packages will be installed: linux-image upgraded, 1 newly installed, 0 to remove and 2 not upgraded. Need to get 31.3MB of archives. After this operation, 98.9MB of additional disk space will be used. Get:1 lucid-updates/main linux-image [31.3MB] Fetched 31.3MB in 5min 31s (94.5kB/s) Download complete and in download only mode Install kernel for clients In ayo repository, searching the latest kernel... Now run: drblsrv-offline -c -d -a -l en_us.utf-8 -k /var/cache/apt/archives/linux-image _ _i386.deb "" "" Kernel package /var/cache/apt/archives/linux-image _ _i386.deb is used for client... The version number for your OS: Ubuntu Install kernel for clients The kernel for client is from specific package /var/cache/apt/archives/linux-image _ _i386.deb. tar: Record size = 8 blocks Installing /var/cache/apt/archives/linux-image _ _i386.deb for clients... It might take several minutes to install this kernel, please be patient... done! Generating modules.dep and map files for clients... done! Creating config file for PXE clients... Copying pxelinux.0, gpxelinux.0, menu.c32, vesamenu.c32, chain.c32, mboot.c32, sanboot.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)... Use com32 module: vesamenu.c32 Adding menus for DRBL, local boot, memtest86+, FreeDOS... done! tar: Record size = 8 blocks

9 Creating the image files for PXE and Etherboot client, this will take a few minutes... The latest kernel for DRBL clients is Running mknic-nbi --kernel 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 Setting port for udhcpc request to default... Using the kernel modules from /tftpboot/node_root//lib/modules... The selected kernel for DRBL clients is: Kernel 2.6 was found, so default to use initramfs. Creating the network boot initrd for PXE clients by: mkpxeinitrd-net -k t initramfs Use kernel modules from /tftpboot/node_root//lib/modules/ Calling hook udev... Creating the initramfs image... Initramfs, remove ramdisk_size/ramdisk_block in /tftpboot/nbi_img/pxelinux.cfg/default if exists... Finished! Done! Done! Done yazısı görüldüğünde kurulumun son aşamasına geçilebilir. Kurulumun son aşamasına geçelim: # /opt/drbl/sbin/drblpush i komutu ile yapılandırmayı başlatacağız: 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. Please enter DNS domain (such as drbl.sf.net): [drbl.name] test.local Set DOMAIN as test.net //burada yazılanın çok bir önemi yok; istenilen domain verilebilir. Please enter NIS/YP domain name://enter ile geçelim [penguinzilla] Set DOMAIN as penguinzilla Please enter the client hostname prefix: This prefix is used to automatically create hostname for clients. If you want to overwrite some or all automatically created hostnames,

10 press Ctrl-C to quit this program now, edit /opt/drbl/conf/client-iphostname, then run this program again. [Clonezilla] Set the client hostname prefix as Clonezilla eth0: IP address , netmask eth0:1: IP address , netmask Configured ethernet card(s) found in your system: eth0 eth0:1 The public IP address of this server is NOT found. Which ethernet port in this server is for public Internet accsess, not for DRBL connection? Available ethernet ports in this server: eth0 ( ), eth0:1 ( ), [eth0] //Enter diyelim. The ethernet port you choose for the WAN connection: eth0 The ethernet port(s) for DRBL environment: eth0:1 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 according 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] y OK! Let's do it! request_eth_port:eth0:1 Start detecting MAC address... Enter 1 or press Enter to view the collecting status. Enter 2 or q to finish collecting and quit. //Burada 1 seçeneği seçildikten sonra eğer bir istemciyi networkten başlatmış olsaydık onun mac adresini toplayacaktı ve gösterecekti. Fakat herhangi bir makinayı boot etmediğim için makina dhcp ye istek göndermedi ve görüldüğü üzere hiçbir mac adresini bulamadı. ======================================= Total: 0

11 ======================================= Enter 1 or press Enter to view the collecting status. Enter 2 or q to finish collecting and quit. The collected MAC addresses from [eth0:1] are saved in file(s) separately: macadr-eth0:1.txt. These files are saved in directory /etc/drbl. 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 eth0:1? [y/n] y OK! Please tell me the file name which contains the MAC address of clients line by line for eth0:1. [macadr-eth0:1.txt] Hostmin: 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 eth0:1. [1] 10//İstenilen sayı verilebilir. The file name you set is "macadr-eth0:1.txt". The clients number in this file is 1. We will set the IP address for the clients connected to DRBL server's ethernet network interface eth0:1 By the MAC address file you set, the IP addresses for the clients connected to DRBL server's ethernet network interface eth0:1 as: Accept? [Y/n] OK! Let's continue... The Layout for your DRBL environment: NIC NIC IP Clients DRBL SERVER +-- [eth0] to WAN +-- [eth0:1] to clients group 0:1 [ 1 clients, their IP from ]

12 Total clients: 1 Press Enter to continue... In the system, there are 3 modes for diskless linux services: [0] Full DRBL mode, every client has its own NFS based /etc and /var. [1] DRBL SSI (Single system image) mode, every client uses tmpfs based /etc and /var. In this mode, the loading and necessary disk space of server will be lighter. NOTE! (a) The client machine memory is recommended at least 256 MB. (b) The setting and config files of client will not be saved to the DRBL server! They are just used 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/drbl-gen-ssi-files to create the template tarball in /tftpboot/node_root/drbl_ssi/. (c) If you want to provide some file to overwrite the setting in the template tarball when client boots, check /tftpboot/node_root/drbl_ssi/clients/00_readme for more details. [2] I do NOT want to provide diskless Linux service to client. Which mode do you prefer? [0] 2 No diskless Linux for client is the system. In the system, there are 3 modes available for clonezilla: [0] Full Clonezilla mode, every client has its own NFS based /etc and /var. [1] Clonezilla box mode, every client uses tmpfs based /etc and /var. In this mode, the loading and necessary disk space of server will be lighter than that in Full Clonezilla mode. Note! In Clonezilla box 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! [2] I do NOT want clonezilla. Which mode do you prefer? [0] 1 Clonezilla box mode is set, an elegant mode for clonezilla is on the way! When using clonezilla, which directory in this server you want to store the saved image (Please use absolute path, and do NOT assign it under /mnt/, /media/ or /tmp/)? [/home/partimag] /storage/images (Burada arzu edilen başka bir path de verilebilir.)

13 Directory for clonezilla saved images: /storage/disk-images If there is a local harddrive with swap partition or writable file system in your client machine, do you want to use that swap partition or create a swap file in the writable filesystem so that client has more memory to use? (This step will NOT destroy any data in that harddisk) [Y/n]//Defaultta Yes olduğundan Enter diyip geçelim OK! We will try to create a swap space for your client if it has a local hard drive! What's the maximun size (Megabytes) for the swap space? We will try to allocate the swap space for you, if it's not enough, 60% of the free space will be used. [128]//Enter diyip geçelim 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] 2 The clients will use text mode 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]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]n OK! Let's continue... Do you want to set the boot prompt for clients? [Y/n]Y How many 1/10 sec is the boot prompt timeout for clients? [70] //Entera basalım, default değer olan 70 saniyeyi verelim. OK! Let's continue... Do you want to use graphic background for PXE menu when client boots? Note! If you use graphical PXELinux menu, however client fails to boot, you can switch to text mode by running "/opt/drbl/sbin/switch-pxe-bg-mode - m text". [y/n]n Use graphic PXE Linux menu for client.

14 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? 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. N Note! 0. If you say yes to this option, this will be a very limited environment for client, i.e. NO local access for USB, CD, audio, printer, etc. in client. 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 to run terminal mode? [y/n] OK! Let's continue... Do you want to let DRBL server as a NAT server? If not, your DRBL client will NOT be able to access Internat. //İstemci tarafında herhangi bir değişiklik yapılmayacağından bu soruya hayır diyeceğiz: [Y/n] N This DRBL server does NOT provide NAT service, so your DRBL client will NOT be able to access Internat. The running kernel in the server supports NFS over TCP! Note! If you change the running kernel in the server, and not sure whether 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... Searching installed Etherboot files for dhcpd.conf... done! The calculated NETWORK for eth0:1 is We are now ready to deploy the files to system!

15 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]Y 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 eth0:1... done! Cleaning the stale files of the diskless nodes if they exist... done! Backuping the old MAC address files... done! The version number for your GNU/Linux: CO5.2 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 el5... Trying to update the /tftpboot/node_root/lib/modules/ el5 from server's /lib/modules/... This might take several minutes... Found kernel modules in /lib/modules/ el5 and its arch "i686" matches client's "i686"... Syncing /lib/modules/ el5 to client's common root... Syncing /boot/* el5* to client's common root... Generating the /tftpboot/node_root/lib/modules/ el5/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! Commenting the TCPwrapper related file /tftpboot/node_root/etc/hosts.deny copied from server... done! Commenting the TCPwrapper related file /tftpboot/node_root/etc/hosts.allow copied from server... done! The startup services for DRBL client are: firstboot netfs portmap crond nfslock sshd crond xfs ypbind kudzu haldaemon messagebus acpid gpm cups drblthincli mkswapfile arm-wol Using udev for clients... Warning! Unable to find the fine-tune file /opt/drbl/setup/files/rh/co5.2/rc.sysinit.co5.2.drbl, use /opt/drbl/setup/files/rh/rc.sysinit.default-rh.drbl as /etc/rc.d/rc.sysinit for DRBL clients! This may cause some problems to DRBL clients! Warning! Unable to find the fine-tune file /opt/drbl/setup/files/rh/co5.2/halt.co5.2.drbl, use /opt/drbl/setup/files/rh/halt.default-rh.drbl as

16 /etc/init.d/halt for DRBL clients! This may cause some problems to DRBL 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: Clonezilla Creating DRBL client: Clonezilla Template client for DRBL SSI is Disable the password in pxelinux simple menu for all clients... Disabling PXE password in config file /tftpboot/nbi_img/pxelinux.cfg/default... done! Now add necessary services to this DRBL server: DHCP, TFTP, NFS, NIS... 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 or Full Clonezilla mode, exporting client's directories etc, var, root... The /etc/exports setting is ok now! This DRBL server does NOT provide NAT service, so your DRBL client will NOT be able to access Internet. Now stop the NAT service... Flushing firewall rules: [ OK ] Setting chains to policy ACCEPT: filter [ OK ] Unloading iptables modules: [ OK ] Now set the YP securenets... Backup the original /var/yp/securenets as /var/yp/securenets.drblsave The /var/yp/securenets setting is done! Update YP... Now add the service: dhcpd xinetd portmap iptables ypserv ypbind yppasswdd ypxfrd nfs nfslock Force to add dhcpd service in this RH-like DRBL server... Force to add xinetd service in this RH-like DRBL server... Force to add portmap service in this RH-like DRBL server... Force to add iptables service in this RH-like DRBL server... Force to add ypserv service in this RH-like DRBL server... Force to add ypbind service in this RH-like DRBL server... Force to add yppasswdd service in this RH-like DRBL server... Force to add ypxfrd service in this RH-like DRBL server... Force to add nfs service in this RH-like DRBL server... Force to add nfslock service in this RH-like DRBL server... Now start the service: dhcpd xinetd portmap iptables ypserv ypbind yppasswdd ypxfrd nfs nfslock Starting dhcpd: [ OK ] Starting xinetd: [ OK ] Stopping portmap: [ OK ] Starting portmap: [ OK ] Applying iptables firewall rules: [ OK ] Loading additional iptables modules: ip_conntrack_netbios_n[ OK ] Starting YP server services: [ OK ] Binding to the NIS domain: [ OK ] Listening for an NIS domain server..