Kyle McDonald wrote:
> Darren Dunham wrote:
>
>> If the profile turns out to not be powerful enough here, it might be easier
>> to create a pre-install script that fires off 'fdisk' directly. That script
>> would only have to clean up the disk and exit (either destroy the MBR
>> entirely, or create a single solaris partition), allowing the standard
>> installer to create a Solaris partition.
>>
>>
As I have a begin script already that is creating the profile on the fly
this isn't really a bad solution.
However, that begin script really tries to provide a 'framework' for
other scripts to build on, and so, since it's run *after* checkprobes,
and the rules.ok file is processed, then that begin script would need to
be responsible for updating the SI_* variables those probes set to
reflect the changes.
Now that I think about it, I may need to do that anyway. For some reason
I was (naively maybe) thinking that if I put the fdisk commands directly
in the profile, then JumpStart is self would so about updating things
like SI_ROOTDISKSIZE to match the new size of the Solaris partition just
created.
The more I think about it, I think I' definitiely have to do that. Since
the way the begin script constructs the profile, it many areas it needs
to know the size of the Solaris part of the disk while the profile is
being made, and can't wait for the profile to be processed.
-Kyle
