I have a need to perform jumpstart installations across subnets and
will not be able to provide a boot server at each subnet. I can create
jumpstart on a bootable cd, which is essentially a portable (yet local
to the installing client)jumpstart installation system or I can create
profile diskettes to be used for the installation information.

Both of these methods suffer from static data. Should I need to change
anything in the JS installation I will then need to redistribute the JS
CDs or Profile disks to all locations in order to guarantee they have
the most recent data.

I would like to be able to boot the system to be installed (not using a
boot server) but retrieve all my information (sysidcfg, rules, profile)
from the centralized JS system.

How can I do this as the system has no knowledge of it's IP (or router)
address at boot time? It is unable to retreive the miniroot without
this information. We do not use DHCP for server IPs so the DHCP
keyword to 'boot' is out of the question.