I appreciate your assistance... I am currently working with Solaris 10 U6.
We have used jumpstart successfully in the past using a different approach, but this process has never been easy as pie. As I stated, we boot to a Linux based tftp server which initially loads pxe.linux, then chain loads to pxe.grub. So until my current testing we have never used the scripts included with the DVD..it was all hand edited. We used to build a tar file for every server, and the grub entry looks like: title sandbox04 kernel /solaris/multiboot kernel/unix -v -m verbose install http://172.18.99.22/jumpstart/amd64/sandbox04.tar -B install_media=172.18.12.248:/jumpstart/amd64/ module /solaris/x86.miniroot TBH it has not worked since I upgraded our install repository and grub kernels from U4 to U5, luckily for me we have not had to build any new Sun Servers for production use in over a year. Now that U6 is out, I decided to eliminate any issues with our everyday architecture. So I started from scratch following the methods in the big admin article I referenced in my OP - http://www.sun.com/bigadmin/features/articles/jumpstart_x86_x64.jsp After reading this article, a lightbulb appeared over my head because we should no longer need to have a complete tar of the config dir for each server in order to have unique sysidcfg files, instead we could have a common config dir and unique sysidcfgs for each server and let the rules figure out which machine profile to use. That concept is golden, and what I hope to get working. I make a sysidcfg for each system, the goal is to do the small pieces of work up front that will make the system as close to 100% ready to go when the install is done. I did not include it but you should see the ~200 line finish script we have built. It includes hardening, user additions, ssh key distribution, custom ntp sshd and other service configurations, additional filesystems or pools as hardware profiles or application profiles require, etc. We try and build as much into the install profile as possible to reduce both the amount of post install config and knowledge required to rebuild. If/when we have to rebuild or refresh hardware, it's quite useful to have the history of the installation profile, it stands as sort of automatic configuration documentation...though perhaps cryptic to the untrained eye. -- This message posted from opensolaris.org
