Google search for 'pxe boot floppy' Argon Tech makes rbfg.exe for createing a floppy with a pxe client http://www.argontechnology.ca/rbfg/index.shtml Intel Pro100 rom upgrade http://h18007.www1.hp.com/support/files/armada/us/download/16587.html Bootable movie player... http://freshmeat.net/projects/emovix/?topic_id=113%2C125 ==================================================================== System Imager notes ==================================================================== Package-based installs can be very limiting because they don't have an automated way to deal with non-packaged files. System Imager uses a uncompressed "golden image" Image server should be the dhcpserver SystemImager stores images as an uncompressed directory structure, image server = systemimager-boot package(s), and systemimager-server package. File layout: /etc/ |---->systeminstaller/ | |----> systeminstaller.conf* # | |----> tksis.conf* # | |---->systemimager |----> rsyncd.conf # Autogenerated file, sets uid/gid,timeout,location of scripts,libs,rsyncd |----> systemimager.conf # Sets location for all other files |----> pxelinux.cfg/ | |----> default # Points to default kernel | |----> message.txt # Custom splash screen | |----> syslinux.cfg # | |----> syslinux.cfg.noboot | |----> rsync_stubs/ /var/lib/systemimager/images/ # Where the images are stored # Image is an uncompressed directory tree. # each image has it's own directory, and the directory name identifys the imaged host by name. /var/lib/systemimager/scripts # Where Client Auto Install scripts are stored # i.e. death_AMD_40G_2.4.20+obaq.master or mother20030413.master /usr/share/systemimager/boot # Where files need by autoinstall clients are stored /etc/systemimager/rsyncd.conf # SystemImager's rsyncd.conf file /etc/systemimager/rsync_stubs # where rsync stub files are stored /tftpboot # where tftp and net-boot files are stored ==================================================================== Running mkdhcpserver -creates a dhcpd.conf ==================================================================== If there is an existing file, it will be backed up with the .beforesystemimager extension. Continue? (y/[n]): y What is your DHCP daemon major version number (2 or 3)? [2]: 3 Are you using the fixed-address patch (Y or N)? [n]: n What is the name of your DHCP daemon config file? []: dhcpd.conf What is your domain name? [localdomain.domain]: stilen.com What is your network number? [192.168.1.0]: 192.168.0.0 What is your netmask? [255.255.255.0]: 255.255.255.0 What is the starting IP address for your dhcp range? [192.168.1.1]: 192.168.0.100 What is the ending IP address for your dhcp range? [192.168.1.100]: 192.168.0.150 What is the IP address of your first DNS server? []: 192.168.0.60 What is the IP address of your second DNS server? []: 63.195.58.123 What is the IP address of your third DNS server? []: What is the IP address of your default gateway? [192.168.1.254]: 192.168.0.60 What is the IP address of your image server? [192.168.1.254]: 192.168.0.14 What is the IP address of your boot server? []: 192.168.0.14 What is the IP address of your log server? []: 192.168.0.14 If your log server uses a non-standard port, enter it here: []: Will your clients be installed over SSH? (y/[n]): Will your clients be installed over SSH? (y/[n]): What... is the air-speed velocity of an unladen swallow? []: Wrong!!! (with a Monty Python(TM) accent...) Press to continue... Ahh, but seriously folks... Here are the values you have chosen: ####################################################################### ISC DHCP daemon version: 3 DHCP daemon using fixed-address patch: N ISC DHCP daemon config file: dhcpd.conf DNS domain name: stilen.com Network number: 192.168.0.0 Netmask: 255.255.255.0 Starting IP address for your DHCP range: 192.168.0.100 Ending IP address for your DHCP range: 192.168.0.150 First DNS server: 192.168.0.60 Second DNS server: 63.195.58.123 Third DNS server: Default gateway: 192.168.0.60 Image server: 192.168.0.14 Boot server: 192.168.0.14 Log server: 192.168.0.14 Log server port: SSH files download URL: ####################################################################### Are you satisfied? (y/[n]): y The dhcp server configuration file (/etc/dhcpd.conf) file has been created for you. Please verify it for accuracy. If this file does not look satisfactory, you can run this command again to re-create it: "mkdhcpserver" WARNING!: If you have multiple physical network interfaces, be sure to edit the init script that starts dhcpd to specify the interface that is connected to your DHCP clients. Here's an example: Change "/usr/sbin/dhcpd" to "/usr/sbin/dhcpd eth1". Depending on your distribution, you may be able to set this with the "INTERFACES" variable in either "/etc/default/dhcp" or in your dhcpd initialization script (usually "/etc/init.d/dhcpd"). Also, be sure to start or restart your dhcpd daemon. This can usually be done with a command like "/etc/init.d/dhcpd restart" or similar. Would you like me to restart your DHCP server software now? (y/[n]): y #------------------------- # Now that that's done, put it in place cp dhcpd.conf /etc/ # Restart your dhcp server /etc/init.d/dhcpd restart #-------------------------- ==================================================================== Running mkautoinstalldiskette -creates a bootable disket ==================================================================== 1st. Put amkautoinstalldiskette floppy in the drive. 2nd. Run mkautoinstalldiskette Here is a list of available flavors: standard Which flavor would you like to use? [standard]: This program assumes that you have a 1.44MB floppy drive and that it is /dev/fd0. You can use the -floppy command line option to change this value. If you do use -floppy, this command will run non-interactively!!! Use the -help option to see all options. Insert your floppy diskette now. This will overwrite all information on your diskette. Continue? (y/[n]): y Formatting floppy as 1.44MB ... Double-sided, 80 tracks, 18 sec/track. Total capacity 1440 kB. Formatting ... 6 ==================================================================== http://www.bootix.com/us/index.shtml http://www.bpbatch.org/ http://www.dcs.shef.ac.uk/support/Procedures/cloning.html http://etherboot.sourceforge.net/ http://www.nilo.org/index.html http://www.storagesoft.com/products/imagecast/advanced.asp http://sisuite.org/ http://www.mexia.k12.tx.us/students/webs8/web/cs/DELL/DOCS/ 605Û/setupopt.htm http://systemimager.org/ ================================= On server, installed some of this. ================================= .. MachineConf.txt README.si_xfs_patch dhcpd.conf getimage_v1.5.0_with_-q_option_fixed.tar.gz mkrecovery.html mkrecoveryISO.tgz si_xfs_client-0.1.tar.gz si_xfs_server-0.1.tar.gz sonicadmin2.5.zip systemimager-3.0.0-1.src.rpm systemimager-3.0.0-2.src.rpm systemimager-boot-standard-2.4.20-3.0.0-1.src.rpm systemimager-client-3.0.0-1.noarch.rpm systemimager-client-3.0.0-2.noarch.rpm systemimager-common-3.0.0-1.noarch.rpm systemimager-common-3.0.0-2.noarch.rpm systemimager-i386boot-standard-2.4.20-3.0.0-1.noarch.rpm systemimager-i386boot-standard-3.0.0-1.noarch.rpm systemimager-i386boot-standard-3.0.0-2.noarch.rpm systemimager-server-3.0.0-1.noarch.rpm systemimager-server-3.0.0-2.noarch.rpm systemimager-ssh-1.5.0.tar.bz2 va-systemimager-datasheet-1.4.1.pdf vampire_template.tar.gz # rpm -qa |grep system yast2-agent-system-2.5.14-11 systemconfigurator-2.0.5-1 systemimager-common-3.0.0-1 systemimager-i386boot-standard-3.0.0-1 systemimager-server-3.0.0-1 systeminstaller-1.01-1 systeminstaller-x11-1.01-1 # Couldn't get systeminstaller gui to work. Launch gui called /usr/bin/tksys ====================== On Client ---------------------- 8 rpm -i perl-AppConfig-1.52-3.noarch.rpm 509 rpm -i systemconfigurator-2.0.5-1.noarch.rpm 510 rpm -i systemimager-common-3.0.0-2.noarch.rpm 511 rpm -i systemimager-client-3.0.0-2.noarch.rpm 512 rpm -ql systemimager-client 513 ls /etc/systemimager/ 514 ls /etc/systemimager/client.conf /usr/bin/systemconfigurator I got an error. Error: None of the following bootloaders were successfully setup on your system: YaBoot,Iseries,EFI,Elilo,Lilo,Grub,Palo /usr/sbin/prepareclient See "prepareclient -help" for command line options. Continue? (y/[n]): y /etc/services # Adds 873tcp/udp to service rsync /etc/inetd.conf # *********************************** WARNING *********************************** This utility starts an rsync daemon that makes all of your files accessible by anyone who can connect to the rsync port of this machine. This is the case until you reboot, or kill the 'rsync --daemon' process by hand. By default, once you use getimage to retrieve this image on your image server, these contents will become accessible to anyone who can connect to the rsync port on your imageserver. See rsyncd.conf(5) for details on restricting access to these files on the imageserver. See the systemimager-ssh package for a more secure method of making images available to clients. *********************************** WARNING *********************************** Continue? (y/[n]): y ontinue? (y/[n]): y Using "sfdisk" to gather information about /dev/hda... Using "sfdisk" to gather information about /dev/hdb... done! Starting or re-starting rsync as a daemon.....done! This client is ready to have its image retrieved. You must now run the "getimage" command on your imageserver. had to update /etc/hosts.allow mother:/home/jstile/SystemImager # tail -f /var/log/rsyncd.log ================================= On server, installed some of this. ================================= run get image ro use the gui getimage -golden-client mother \ -image mother20030412 \ -ssh-user root -quiet \ -directory /home/jstile/NetInstalls/ ==========#######========== getimage -golden-client mother -image mother20030413 -update-script YES -ip-assignment static -directory /home/jstile/NetInstalls/ wrote 6379481 bytes read 12830890740 bytes 2163159.53 bytes/sec total size is 12802302680 speedup is 1.00 ------------- mother20030413 IMAGE RETRIEVAL FINISHED ------------- Press to continue... Would you like to run the "addclients" utility now? (y/[n]): y Welcome to the SystemImager "addclients" utility -------------------------------------------------------------------------------- This utility has 3 sections. "Section 1" will ask you for your hostname information. "Section 2" will allow you to create softlinks from each client hostname to your "master" script in the "/var/lib/systemimager/scripts" directory. Example: www297.sh -> web_server_image_v1.master "Section 3" will ask you for IP address information that will be combined with the hostname information provided in Section 1 to create entries in "/etc/hosts" for each of these same clients. New entries will be appended to the end of "/etc/hosts". If you specify new hostnames for existing IP addresses, those entries will be re-written in place to reflect the new host names. Continue? ([y]/n):y addclients -- Section 1 (hostname information) -------------------------------------------------------------------------------- The next series of questions will be used to create a range of hostnames. You will be asked for your domain name, the base host name, a beginning number, and an ending number. For example, if you answer: domain name = systemimager.org base host name = www starting number = 7 ending number = 11 Then the result will be a series of hostnames that looks like this: www7.systemimager.org www8.systemimager.org www9.systemimager.org www10.systemimager.org www11.systemimager.org What is your domain name? []: stilen.com What is the base host name that you want me to use? [mother]: mother Use of uninitialized value in concatenation (.) or string at /usr/sbin/addclients line 258, line 3. What number should I begin with? []: 1 Use of uninitialized value in concatenation (.) or string at /usr/sbin/addclients line 261, line 4. What number should I end with? []: 5 I will work with hostnames: mother1 through mother5 in the domain: stilen.com Are you satisfied? (y/[n]): y --------------------------------------------------------------------------- addclients -- Section 2 (soft links to master script) -------------------------------------------------------------------------------- Would you like me to create soft links to a "master" script so that hosts: mother1 through mother5 can be autoinstalled with that image? ([y]/n): y Here is a list of available autoinstall scripts: daman20030412 mother20030413 Which script would you like these hosts to be installed with? [mother20030413]: Your soft links have been created. Press to continue... --------------------------------------------------------------------------- addclients -- Section 3 (adding or modifying /etc/hosts entries) -------------------------------------------------------------------------------- Your target machines need to be able to determine their host names from their IP addresses, unless their host name is specified in a local.cfg file. The preferred method for doing this is with DNS. If you have a working DNS that has IP address to hostname resolution properly configured for your target machines, then answer "n" here. If you don't have a working DNS, or you want to override the information in DNS, then answer "y" here to add entries to the "/etc/hosts" file on your image server. After adding these entries, the /etc/hosts file will be copied to "/var/lib/systemimager/scripts" where it can be retrieved by your target machines. I will ask you for your clients' IP addresses one subnet at a time. Would you like me to continue? (y/[n]): n No entries will be added to your /etc/hosts file. ==========#######========== Image retrived... press any key to continue. IP Address Assignment # If you don't specify the directory for the image, it will be placed in: # /var/lib/systemimager/images/ --------------------- There are four ways to assign IP addresses to the client systems on an ongoing basis: 1) DHCP ---------------------------------------------------------------- A DHCP server will assign IP addresses to clients installed with this image. They may be assigned a different address each time. If you want to use DHCP, but must ensure that your clients receive the same IP address each time, see "man mkdhcpstatic". 2) STATIC ---------------------------------------------------------------- The IP address the client uses during autoinstall will be permanently assigned to that client. 3) REPLICANT ---------------------------------------------------------------- Don't mess with the network settings in this image. I'm using it as a backup and quick restore mechanism for a single machine. Which method do you prefer? [1]: 2 You have chosen method 2 for assigning IP addresses. Are you satisfied? ([y]/n):y Would you like to run the "addclients" utility now? (y/[n]): elcome to the SystemImager "addclients" utility -------------------------------------------------------------------------------- This utility has 3 sections. "Section 1" will ask you for your hostname information. "Section 2" will allow you to create softlinks from each client hostname to your "master" script in the "/var/lib/systemimager/scripts" directory. Example: www297.sh -> web_server_image_v1.master "Section 3" will ask you for IP address information that will be combined with the hostname information provided in Section 1 to create entries in "/etc/hosts" for each of these same clients. New entries will be appended to the end of "/etc/hosts". If you specify new hostnames for existing IP addresses, those entries will be re-written in place to reflect the new host names. Continue? ([y]/n):y ######################################################## addclients -- Section 1 (hostname information) -------------------------------------------------------------------------------- The next series of questions will be used to create a range of hostnames. You will be asked for your domain name, the base host name, a beginning number, and an ending number. For example, if you answer: domain name = systemimager.org base host name = www starting number = 7 ending number = 11 Then the result will be a series of hostnames that looks like this: www7.systemimager.org www8.systemimager.org www9.systemimager.org www10.systemimager.org www11.systemimager.org What is your domain name? []: stilen.com ######################################################## addclients -- Section 1 (hostname information) -------------------------------------------------------------------------------- The next series of questions will be used to create a range of hostnames. You will be asked for your domain name, the base host name, a beginning number, and an ending number. For example, if you answer: domain name = systemimager.org base host name = www starting number = 7 ending number = 11 Then the result will be a series of hostnames that looks like this: www7.systemimager.org www8.systemimager.org www9.systemimager.org www10.systemimager.org www11.systemimager.org What is your domain name? []: stilen.com What is the base host name that you want me to use? []: daman Use of uninitialized value in concatenation (.) or string at /usr/sbin/addclients line 258, line 3. What number should I begin with? []: 1 Use of uninitialized value in concatenation (.) or string at /usr/sbin/addclients line 261, line 4. What number should I end with? []: 3 I will work with hostnames: daman1 through daman3 in the domain: stilen.com Are you satisfied? (y/[n]): y ######################################################## addclients -- Section 1 (hostname information) -------------------------------------------------------------------------------- addclients -- Section 2 (soft links to master script) -------------------------------------------------------------------------------- Would you like me to create soft links to a "master" script so that hosts: daman1 through daman3 can be autoinstalled with that image? ([y]/n): y Here is a list of available autoinstall scripts: daman20030412 Which script would you like these hosts to be installed with? [daman20030412]: Your soft links have been created. Press to continue... ######################################################## -------------------------------------------------------------------------------- addclients -- Section 3 (adding or modifying /etc/hosts entries) -------------------------------------------------------------------------------- Your target machines need to be able to determine their host names from their IP addresses, unless their host name is specified in a local.cfg file. The preferred method for doing this is with DNS. If you have a working DNS that has IP address to hostname resolution properly configured for your target machines, then answer "n" here. If you don't have a working DNS, or you want to override the information in DNS, then answer "y" here to add entries to the "/etc/hosts" file on your image server. After adding these entries, the /etc/hosts file will be copied to "/var/lib/systemimager/scripts" where it can be retrieved by your target machines. I will ask you for your clients' IP addresses one subnet at a time. Would you like me to continue? (y/[n]): n No entries will be added to your /etc/hosts file. ######################################################## /usr/bin/lsimage ------------------- Available image(s): ------------------- root /etc/init.d/netbootmond /etc/init.d/systemimager /etc/systeminstaller/ |-> systeminstaller.conf |-> tksis.conf /etc/systemimager/ |-> autoinstallscript.conf |-> client.conf |-> mounted_filesystems |-> pxelinux.cfg rsync_stubs |-> rsyncd.conf |-> systemimager.conf |-> updateclient.local.exclude |-> pxelinux.cfg/ |-> message.txt |-> syslinux.cfg |-> syslinux.cfg.noboot ######################################################## daman:/home/jstile # /etc/init.d/inetd start daman:/home/jstile # /etc/init.d/systemimager restart daman:/home/jstile # /etc/init.d/netbootmond start daman:/home/jstile # mkbootserver This script may modify the following files: /etc/services /etc/inetd.conf /etc/xinetd.d/tftp You should already have a kernel and ramdisk to use. Do you wish to continue (y/[n])? y Ok, continuing... Where should tftpd serve files from ([/tftpboot]? /tftpboot doesn't exist, should I create it (y/[n])? y Creating /tftpboot...Checking for a tftp server... found. Checking if tftp server is H. Peter Anvin's tftp server... yup - right on! Checking for a running inetd... Not found. Checking for a running xinetd... Not found. Looking for update-inetd... not found. I couldn't find a running inetd or xinetd. Nothing to configure. Attempt to configure inetd failed. ######################################################## /usr/bin/systemconfigurator --configall /etc/init.d/netbootmond /etc/init.d/systemimager ######################################################## rebuild src rpm of systemimager Prerequisit perl -MCPAN -e 'install Tk' perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install DBI' cramfs rpm - tool allows you to create compressed rom file system. (cramfs) installed docbook-utils rpm for suse8.0 to get docbook2man. ######################################################## Saturday April 19th. ######################################################## SystemImager/ systemimager-i386boot-standard-3.0.0-2 systemimager-common-3.0.0-2 systemimager-client-3.0.0-2 systemimager-server-3.0.0-2 SystemInstaller perl-MLDBM-Sync-0.25-63 libdbdcsv-perl-0.1027-1 perl-MLDBM-2.01-1 systeminstaller-1.01-1 systeminstaller-x11-1.01-1 SystemConfigurator/ perl-AppConfig-1.52-4 systemconfigurator-2.0.6-1 /usr/lib/systemimager/perl/SystemImager/ . .. Common.pm Config.pm Server.pm /usr/lib/systeminstaller/ . .. SIS SystemInstaller Tk Util /usr/lib/systemconfig/ . Boot Hardware Initrd Keyboard.pm Net Network.pm Time UserExit.pm perllocal.pod .. Boot.pm Hardware.pm Initrd.pm Modules Network SCConfig.pm Time.pm Util /var/lib/systemimager/ . .. images overrides scripts Commands for mk stuff rpm -qf /usr/bin/mkautoinstallcd # systemimager-server-3.0.0-2 ---------------------------------- This makes the disk you boot from ----------------------------------- rpm -qf /usr/bin/mkautoinstalldiskette # systemimager-server-3.0.0-2 -floppy /dev/fd0 --or -out-file -flavor of boot media (default "standard") -kernel FILE ( kernel ) -initrd FILE (the ram disk) -append STRING-TO-KERNEL -ssh-key FILE (id_dsa or id_rsa) -config /usr/share/doc/systemimager/local.cfg Config file sets: hostname and config network. NOTE: closeest thing to a sample config file I could find was: /usr/share/doc/systemconfigurator-2.0.6/sample.cfg A sample of the local.cfg file: HOSTNAME=mother5 DOMAINNAME=stemcells DEVICE=eth0 IPADDR=192.168.0.56 NETMASK=255.255.255.0 NETWORK=192.168.0.0 BOADCAST=192.168.0.255 GATEWAY=192.168.0.60 GATEWAYDEV=eth0 IMAGESERVER=192.168.0.14 ------------------------------------------------ This creates the Auto Install Script stored in ------------------------------------------------ rpm -qf /usr/sbin/mkautoinstallscript # systemimager-server-3.0.0-2 rpm -qf /usr/sbin/mkbootserver # systemimager-server-3.0.0-2 rpm -qf /usr/sbin/mkclientnetboot # systemimager-server-3.0.0-2 -clients "HOST1 HOST2" -or- -all-clients tells server what hosts can get an install from this server. rpm -qf /usr/bin/mkcramfs # mkcramfs-1.1-15 rpm -qf /usr/bin/mkdhcpconf # systeminstaller-1.01-1 rpm -qf /usr/sbin/mkdhcpserver # systemimager-server-3.0.0-2 rpm -qf /usr/sbin/mkdhcpstatic # systemimager-server-3.0.0-2 /etc/systemimager/pxelinux.cfg/syslinux.cfg /etc/systemimager/pxelinux.cfg/syslinux.cfg.noboot ------------------------ Found some Docuemnts ------------------------ /usr/share/doc/systemimager-server-3.0.0/README First Things First -------------------------------------------------------------------------------- All documentation is in /usr/share/doc/systemimager-* pushd /usr/share/doc/systemimager-*/manual/ lynx html/index.html or "xpdf systemimager-manual.pdf" DISTRIBUTION CHANGE: The SystemImager team is no longer supporting "installable tarballs", but instead provide packages for RPM and Debian based distributions. --------------------------------------------- running mkautoinstalldiskette without iptions --------------------------------------------- /usr/bin/mkautoinstalldiskette Here is a list of available flavors: standard Which flavor would you like to use? [standard]: This program assumes that you have a 1.44MB floppy drive and that it is /dev/fd0. You can use the -floppy command line option to change this value. If you do use -floppy, this command will run non-interactively!!! Use the -help option to see all options. Insert your floppy diskette now. This will overwrite all information on your diskette. Continue? (y/[n]):y Formatting floppy as 1.44MB ... Double-sided, 80 tracks, 18 sec/track. Total capacity 1440 kB. Formatting ... 10 Formatting ... done Verifying ... done Creating DOS filesystem on floppy... mkdosfs 2.8 (28 Feb 2001) Using "syslinux" to make floppy bootable... Can't exec "syslinux": No such file or directory at /usr/bin/mkautoinstalldiskette line 307, line 2. "syslinux -s /dev/fd0" failed. --------------------------------- Going to download syslinux. --------------------------------- http://syslinux.zytor.com/download.php rpm -i syslinux-1.61-3.i386.rpm /usr/bin/mkautoinstalldiskette I say yes, the Floppy disk formats, and, ,,, It succeeded with the message: Removing temporary mount point... Done! --------------------------------- Tried to boot from disk, and it could not connect to the tftp server. mkdir /var/lib/systemimager/tftpboot mkbootserver -f \ --interface=eth0 --localdhcp=y \ --kernel=/usr/share/systemimager/boot/i386/standard/kernel \ --initrd=/usr/share/systemimager/boot/i386/standard/initrd.img \ --tftpdir=/var/lib/systemimager/tftpboot \ --pxelinux=/usr/lib/syslinux/pxelinux.0 Last command failed with this message: Looking for a pxe daemon... which: no pxe in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin) not found. **************************************************************** I couldn't find a pxe daemon on your system. For RedHat systems, you can install the pxe RPM for your release. For Debian systems, you can try one of the debs i've built from the RedHat package source. These packages should be available from http://dannf.org/systemimager **************************************************************** pxe daemon installation failed --------------------------------- Trying to run mkbootserver with no iptions This script may modify the following files: /etc/services /etc/inetd.conf /etc/xinetd.d/tftp You should already have a kernel and ramdisk to use. Do you wish to continue (y/[n])? *** I tried specifying many different tftp boot areas, (grept ftftp /etc/inetd.conf) *** all failed. *** Next read about systeminstaller. /usr/share/doc/systeminstaller-1.01/README --------------------- Tuns out I need to read syslinux pxelinux.doc directions, "A bootloader for Linux using the PXE network booting protocol" /usr/doc/syslinux-1.61/pxelinux.doc: # Copy any kernel or initrd images you want to boot to /tfptboot/ cp /usr/lib/syslinux/pxelinux.0 /tftpboot/ # The syslinux.conf will live in this directory mkdir /tftpboot/pxelinux.cfg # Looking at setup, I see files cd /tftpboot/pxelinux.cfg ln -s /etc/systemimager/pxelinux.cfg pxelinux.cfg ########################### # Trying a new direction ########################### daman:/tftpboot # mkdhcpserver Welcome to the SystemImager "mkdhcpserver" command. This command will prepare this computer to be a DHCP server by creating a dhcpd.conf file for use with your ISC DHCP server (v2 or v3). If there is an existing file, it will be backed up with the .beforesystemimager extension. Continue? (y/[n]): What is your DHCP daemon major version number (2 or 3)? [2]: 3 Are you using the fixed-address patch (Y or N)? [n]: What is the name of your DHCP daemon config file? [/etc/dhcpd.conf]: What is your domain name? [localdomain.domain]: stilen.com What is your network number? [192.168.1.0]: 192.168.0.0 What is your netmask? [255.255.255.0]: What is the starting IP address for your dhcp range? [192.168.1.1]: 192.168.0.100 What is the ending IP address for your dhcp range? [192.168.1.100]: 192.168.0.225 What is the IP address of your first DNS server? []: 192.168.0.60 What is the IP address of your second DNS server? []: 63.195.58.123 What is the IP address of your third DNS server? []: What is the IP address of your default gateway? [192.168.1.254]: 192.168.0.60 What is the IP address of your image server? [192.168.1.254]: 192.168.0.14 What is the IP address of your boot server? []: 192.168.0.14 What is the IP address of your log server? []: 192.168.0.14 If your log server uses a non-standard port, enter it here: []: Will your clients be installed over SSH? (y/[n]): What... is the air-speed velocity of an unladen swallow? []: african or eruopean? ------------------------------------------ Ahh, but seriously folks... Here are the values you have chosen: ####################################################################### ISC DHCP daemon version: 3 DHCP daemon using fixed-address patch: N ISC DHCP daemon config file: /etc/dhcpd.conf DNS domain name: stilen.com Network number: 192.168.0.0 Netmask: 255.255.255.0 Starting IP address for your DHCP range: 192.168.0.100 Ending IP address for your DHCP range: 192.168.0.225 First DNS server: 192.168.0.60 Second DNS server: 63.195.58.123 Third DNS server: Default gateway: 192.168.0.60 Image server: 192.168.0.14 Boot server: 192.168.0.14 Log server: 192.168.0.14 Log server port: SSH files download URL: ####################################################################### Are you satisfied? (y/[n]): y ------------------------------------------ The dhcp server configuration file (/etc/dhcpd.conf) file has been created for you. Please verify it for accuracy. If this file does not look satisfactory, you can run this command again to re-create it: "mkdhcpserver" WARNING!: If you have multiple physical network interfaces, be sure to edit the init script that starts dhcpd to specify the interface that is connected to your DHCP clients. Here's an example: Change "/usr/sbin/dhcpd" to "/usr/sbin/dhcpd eth1". Depending on your distribution, you may be able to set this with the "INTERFACES" variable in either "/etc/default/dhcp" or in your dhcpd initialization script (usually "/etc/init.d/dhcpd"). Also, be sure to start or restart your dhcpd daemon. This can usually be done with a command like "/etc/init.d/dhcpd restart" or similar. Would you like me to restart your DHCP server software now? (y/[n]):y ------------------------------------------ installed rshd server rpm added + to /etc/hosts.equiv added all stilen.com names to /etc/hosts.allow ----------------- 2003-04-29 ----------------- Tracked down the docs for sytem imager, in trouble shooting area, it mentions the rsync server. so I read the man page on rsync, and found: rsync somehost.mydomain.com:: this would list all the anonymous rsync modules available on the host somehost.mydomain.com. (See the following section for more details.) So I have tested the client to see if rsync 192.168.0.14:: lists any bundles and it does not. ---------------- Added rpm for rsh-server-0.17-199 Added systemimager to the startup using their tool chkconfig --add systemimager insserv: Warning, current runlevel(s) of script `xntpd' overwrites defaults. ssystemimager 0:off 1:off 2:off 3:on 4:off 5:on 6:off ---------------------------------------------- Now when i boot the client it gets a little farther get_boel_binaries_tarball rsync 192.168.0.14::boot/i386/standard/boel_binaries.tar.gz /tmp/ receaving file list ... link_stat /i386/standard/boel_binaries.tar.gz: No such file or directory. done client: do nothing: perhaps you need to specify --recursive ----------------