Wade Hampton wrote: >> 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.
You have the 256 chars limit depending on the kernel you're using. Anyway in recent kernels this limit has been increased to 2048 characters. If this limit is too small you can define additional parameters via local.cfg: - create a /tmp/local.cfg (see for example doc/examples/local.cfg, or http://svn.systemimager.org/filedetails.php?repname=systemimager&path=%2Ftrunk%2Fdoc%2Fexamples%2Flocal.cfg&rev=0&sc=0) - use si_mkbootpackage to re-create your kernel+initrd.img with your local.cfg included. It is even possible to use BOEL with si_mkbootpackage, for example: # mkdir /tmp/boot-package/ # si_mkbootpackage --destination /tmp/boot-package \ --kernel /usr/share/systemimager/boot/i386/standard/kernel \ --filesystem cramfs --config /tmp/local.cfg --yes > > 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). You can variableize the kernel parameters parsing /proc/cmdline and add the vars to /tmp/variables.txt. For example: cat /proc/cmdline | tr ' ' '\n' | grep '=' > /tmp/kernel_append_parameter_variables.txt > > 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? OK, appending kernel parameters to variables.txt seems a good idea (in a way similar to the script above). In this case we could have all the installation parameters as env variables available for our post-install scripts. > > FEATURE REQUEST: Could we add awk to the default busybox image (good > for pre-install scripts that could use awk)? NACK. I think it's better to have a light initrd.img: this is very very important in massive installation when you have hundreds or thousands of nodes (typically HPC clusters) and the transfer of the initrd.img via TFTP could be a critical bottleneck in these cases. > >>>>> 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? > Correct. If you're using UYOK you have to copy also the UYOK files. -Andrea ------------------------------------------------------------------------- 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
