[snip] > > Basically, the box was previously setup with IP, network, netmask, > > gateway. When I reimage the box, it would be nice to reuse the old > > settings of the box without having to copy the MAC address to a file > > or add to the DHCP server. [snip] > In this case, if you can setup grub.conf, a solution could be to add the > opportune installation parameters to the kernel command line. > > See: http://wiki.systemimager.org/index.php/Installation_Parameters > > The parameters you need should be the following: > > HOSTNAME=hostname > DOMAINNAME=domainname > DEVICE=ethi > IPADDR=x.x.x.x > NETMASK=x.x.x.x > NETWORK=x.x.x.x > BROADCAST=x.x.x.x > GATEWAY=gateway > > Simply append them in your grub.conf in the "kernel" line (in a single line).
Note: you are limited to 256 characters in the kernel command line (see the docs for the 2.6.22 kernel and include/asm/setup.h). This works, but since my names on the server were dhcp1, dhcp2, etc., I had to also use SCRIPTNAME=dhcp1.sh. I will have to write a post-install script to get these from variables.txt and setup networking on the new image (e.g., 98all.setup_networking). > >> If you want to access them as env variables in your post-install scripts > >> source the file /tmp/variables.txt on the top of your scripts. > > > > Can I add my own variables to this file? > > Yes. How can I add my own? I see how the kernel*txt file contains my own vars, but they don't make it to variables.txt (for example, I defined USER1=X,Y,Z). FEATURE REQUEST: Maybe a couple user variables could be added to si such as USER1=string, USER2=string, and these could be copied to variables.txt. Another feature might be to also copy the kernel variables file to /tmp/post-install? FEATURE REQUEST: Could we add awk to the default busybox image (good for pre-install scripts that could use awk)? > >> > >> > I am installing CentOS 5 using Systeminstaller 3.8.1. > >> > > >> > Also, I would like to mirror my systemimager server, but to a separate > >> > network. The instructions expect the networks to be connected. What > >> > directories would I need to copy > >> > besides /var/lib/systemimager, /usr/share/systemimager, and /tftpboot? > >> > > >> > >> Install the systemimager server packages in the mirror and simply use > >> si_cpimage: > >> > >> mirror:~/# si_cpimage --server <orig_image_server> source_image > >> destination_image > > > > That will work if they are on the same network or are connected. I > > need to copy the image to a DVD then move it to the other, > > non-connected network. > > > > Unfortunately you can't use si_cpimage if your image servers are not connected > to a network. > > So, to copy your image using a DVD you have to manually do the following > steps: > > 1) copy your image to the mounted DVD: > > # cp -af /var/lib/systemimager/images/<your_image> /media/dvd/ > > 2) copy the rsync_stub: > > # cp -p /etc/systemimager/rsync_stubs/40<your_image> /media/dvd What about /usr/share/systemimager/boot and /tftpboot? > 3) umount the DVD and insert it in your mirror server > > 4) copy the image back to the mirror image server: > > # cp -af /media/dvd/<your_image> /var/lib/systemimager/images/ > > 5) copy the rsync_stub: > > # cp -p /media/dvd/40<your_image> /etc/systemimager/rsync_stubs > > 6) Re-create rsyncd.conf in the mirror server: > > # si_mkrsyncd_conf > > 7) create the default override: > > # mkdir /var/lib/systemimager/overrides/<your_image> > > 8) re-create the master autoinstall script: > > # si_mkautoinstallscript --image <your_image> --post-install reboot > > This should be fully implemented in si_cpimage in the future releases (I'm > considering this a feature request). Thanks! -- Wade Hampton ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
