Darren Dunham wrote:
>> Am I right in interpreting the docs to say that I
>> can't specify to
>> delete the fdisk partition in fdisk partition slot X
>> (where X is 1-4?)
>>
>> That seems like a pretty useful thing to do, why not?
>>
>
> Some of Solaris's historical support of MBR partitions seems to come from
> coding to published specifications rather than common usage.
>
> But when I read the docs, it suggests that creating a partition with "all"
> will delete all the other ones:
>
> x86: fdisk Profile Keyword
>
> fdisk disk_name type size
>
> fdisk defines how the fdisk partitions are set up on an x86 based system. You
> can specify fdisk more than once. When fdisk partitions an x86 based system,
> the following occurs:
>
> * All fdisk partitions on the disk are preserved unless you delete the
> partitions with the fdisk keyword by assigning size the value of delete or 0.
> Also, all existing fdisk partitions are deleted when size is set to all.
> [...]
>
> I haven't tried it to see if it works or not.
>
>
I did see that. I guess I'll use it too if I have to.
I was hoping to preserve the first partition and delete 2-3.
If deleting partitions by type is the only way, then I may try creating
several fdisk lines that delete the types I'm most likely to run into,
and add to that list over time I guess.
I suppose if deleting by slot number isn't possible, the next best thing
would be a "delete all but these types" command, since the only ones I
want to keep are mostly type 0x12, and 0xDE.
Then again, I might jist dothe deletes with fdisk myself in the begin
script before I create the profile.
I was hoping to just write the profile and lest jumpstart take care of
it, but...
-Kyle
>> I have many x86 systems that come with small vendor
>> DIAG partitions in
>> partition slot 1. (Dell, IBM, etc.) I don't care what
>> is in slots 2-3,
>> and I want to wipe them before I tell Jumpstart to
>> create a 'maxfree'
>> solaris partition.
>>
>> What's the best way to do this?
>>
>
> 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.
>
>
