Sarah Jelinek wrote:
>> ld be interesting to me.
>> In the current Jumpstart, begin and finish script are running in
>> miniroot environment and so all the tools may not be available.
>> Depending on how the image is setup in the new AI environment, there
>> may be some restrictions placed on the begin/finish scripts.
> Exactly correct. But, we have the ability with the DC to allow users to
> create their own distributions they can include things in the microroot
> that they deem necessary.
Why not make this simpler?
1) The new AI gets booted and devices probed, etc.
The system is examined and a hardware config profile,
image selection, additional software and customer-supplied
finish script are selected from information obtained via
install server.
2) disks allocated according to hardware profile,
zpool is created, image laid down, and system is rebooted.
3) post-boot, additionally desired software is installed from
repository and customer supplied finish script is run in
actual system environment.
The job of the AI is to lay down either a stock or customer
created working image, and setup post-boot customization
operations.
- Bart
--
Bart Smaalders Solaris Kernel Performance
barts at cyber.eng.sun.com http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
