server| -- perl-AppConfig-1.52-4.noarch.rpm| -- systemconfigurator-2.2.11-1.noarch.rpm| -- systemimager-common-4.1.6-1.noarch.rpm| -- systemimager-i386boot-standard-4.1.6-1.noarch.rpm` -- systemimager-server-4.1.6-1.noarch.rpm
[root@localhost server]# rpm -ivh *.rpmerror: failed to stat /media/RHEL_5.4 i386 DVD: No such file or directoryPreparing... ########################################### [100%]1:perl-AppConfig ########################################### [ 20%]2:systemconfigurator ########################################### [ 40%]3:systemimager-common ########################################### [ 60%]4:systemimager-server ########################################### [ 80%]Stopping xinetd: [ OK ]Starting xinetd: [ OK ]5:systemimager-i386boot-s########################################### [100%][root@localhost server]#
client/| -- perl-AppConfig-1.52-4.noarch.rpm| -- systemconfigurator-2.2.11-1.noarch.rpm| -- systemimager-client-4.1.6-1.noarch.rpm| -- systemimager-common-4.1.6-1.noarch.rpm` -- systemimager-i386initrd_template-4.1.6-1.noarch.rpm
[root@qiuri client]# rpm -ivh *.rpmPreparing... ########################################### [100%]1:perl-AppConfig ########################################### [ 20%]2:systemconfigurator ########################################### [ 40%]3:systemimager-common ########################################### [ 60%]4:systemimager-client ########################################### [ 80%]5:systemimager-i386initrd########################################### [100%][root@qiuri client]#
[root@qiuri ~]# si_prepareclient --server 172.16.0.10Welcome to the SystemImager si_prepareclient command. This command may modifythe following files to prepare your golden client for having it's imageretrieved by the imageserver. It will also create the /etc/systemimagerdirectory and fill it with information about your golden client. All modifiedfiles will be backed up with the .before_systemimager-4.1.6 extension./etc/services:This file defines the port numbers used by certain software on your system.Entries for rsync will be added if necessary./tmp/fileO0rkKZ:This is a temporary configuration file that rsync needs on your golden clientin order to make your filesystem available to your SystemImager server.inetd configuration:SystemImager needs to run rsync as a standalone daemon on your golden clientuntil it's image is retrieved by your SystemImager server. If rsyncd isconfigured to run as a service started by inetd, it will be temporarilydisabled, and any running rsync daemons or commands will be stopped. Then ,an rsync daemon will be started using the temporary configuration filementioned above.See "si_prepareclient --help" for command line options.Continue ? (y/[n]): y #输入“y”,继续。*********************************** WARNING ***********************************This utility starts an rsync daemon that makes all of your files accessibleby anyone who can connect to the rsync port of this machine. This is thecase until you reboot, or kill the 'rsync --daemon' process by hand. Bydefault , once you use si_getimage to retrieve this image on your imageserver,these contents will become accessible to anyone who can connect to the rsyncport on your imageserver. See rsyncd.conf(5) for details on restrictingaccess to these files on the imageserver. See the systemimager-ssh packagefor a more secure method of making images available to clients.*********************************** WARNING ***********************************Continue ? (y/[n]): y #再次输入"y"。-rw-r --r-- 1 root root 1855956 Apr 10 21:31 /etc/systemimager/boot/kernelStarting or re-starting rsync as a daemon.....done!This client is ready to have its image retrieved. You must now runthe "si_getimage" command on your imageserver.Your client has been successfully prepared. Boot kernel (copied fromthis Linux distribution) and an initrd.img (generated by theinitrd_template package) can be found in /etc/systemimager/boot.Automatically create configuration file for systemconfigurator:>> /etc/systemconfig/systemconfig.conf[root@qiuri ~]#
[root@qiuri ~]# ps -ef |grep rsyncroot 3812 1 0 15:46 ? 00:00:00 rsync --daemon --port=873 --config=/tmp/filerqgMEGroot 3846 3539 0 15:47 pts/2 00:00:00 grep rsync
[root@localhost ~]# si_getimage --golden-client 172.16.0.2 -image vfast_backup--post-install reboot -directory /systemimager/This program will get the "vfast_backup" system image from "172.16.0.2"making the assumption that all filesystems considered partof the system image are using ext2, ext3, jfs, FAT, reiserfs, or xfs.This program will not get /proc, NFS, or other filesystemsnot mentioned above.*********************************** WARNING ***********************************All files retrieved from a golden client are, by default , made accessible toanyone who can connect to the rsync port of this machine. See rsyncd.conf(5)for details on restricting access to these files on the imageserver. See thesystemimager-ssh package for a more secure (but less effecient) method ofmaking images available to clients.*********************************** WARNING ***********************************See "si_getimage --help" for command line options.Continue ? ([y]/n):y #输入"y"继续
usr/share/zoneinfo/right/Navajo => usr/share/zoneinfo/right/US/Mountainusr/share/zoneinfo/ right /America/Denver => usr/share/zoneinfo/ right /US/Mountainusr/share/zoneinfo/ right /America/Shiprock => usr/share/zoneinfo/ right /US/Mountainusr/share/zoneinfo/ right /America/Los_Angeles => usr/share/zoneinfo/ right /US/Pacificusr/share/zoneinfo/ right /Pacific/Pago_Pago => usr/share/zoneinfo/ right /US/Samoausr/share/zoneinfo/ right /Pacific/Samoa => usr/share/zoneinfo/ right /US/Samoasent 3524467 bytes received 3232535951 bytes 1941830.43 bytes/sectotal size is 3411616325 speedup is 1.05------------- vfast_backup IMAGE RETRIEVAL FINISHED -------------Press <Enter> to continue ...
There are three ways to assign IP addresses to the client systems on anongoing basis:1) DHCP----------------------------------------------------------------A DHCP server will assign IP addresses to clients installed withthis image. They may be assigned a different address each time .If you want to use DHCP, but must ensure that your clientsreceive the same IP address each time , see "man si_mkdhcpstatic" .2) STATIC----------------------------------------------------------------The IP address the client uses during autoinstall will bepermanently assigned to that client.3) REPLICANT----------------------------------------------------------------Don 't mess with the network settings in this image. I' m usingit as a backup and quick restore mechanism for a single machine.Which method do you prefer? [1]: #直接回车You have chosen method 1 for assigning IP addresses.
Are you satisfied? ([y]/n):Would you like to run the "si_clusterconfig" utility now? (y/[n]):
本文出自 “学习吧!Linux” 博客,谢绝转载!