>There is no ITU keyword that can be used to enable the ITU process
>during jumpstart. We are planning to encorporate this in to the next gen
>installer we are currently working on. I don't know exactly how the ITU
>works, but I imagine since it happens prior to the installation process
>it has to load the drivers in memory and attach the specific devices.
>And, make sure that these drivers really get installed on the media at
>the appropriate time. So... the process of invoking the ITU service is
>specific, and would require some changes to jumpstart to enable this.
>
>However, maybe this ITU functionality could be mimicked in a jumpstart
>begin script. You would need to load the drivers, get them attached, and
>then you could read the devices you have loaded them for. The finish
>script could be written to install them on the media.
The "Install ITU" option modifies the in-memory miniroot; is it
perhaps possible to modify the on-server miniroot to mimick this
effect.
As I understand it, the ITU has two effects:
- make the driver available to the x86 miniroot
- install the driver when installation is finished
I know how to do #1 (except that update_drv -b is broken) but
how about #2 without doing a finish script?
Casper
