Hi all,
I have a rules.ok file that has only one rule, that supposed to run my
begin script to generate the profile on the fly.
The rules file looks like:
------------------------------------------------------------------------------
memsize 0-1048576 && \
disksize rootdisk 0-10485760 && \
totaldisk 0-104857600 \
\
bin/Begin = bin/Finish
------------------------------------------------------------------------------
Why does it look like this? Why not just use the 'any' keyword? Well
I've found through much trial and error that if I don't use 'memsize',
'disksize', and 'totaldisk', then these variables don't get set at all
(either don't exist or are set to null):
SI_MEMSIZE
SI_NUMDISKS
SI_DISKLIST
SI_DISKSIZES
SI_ROOTDISK
SI_ROOTDISKSIZE
SI_TOTALDISK
(and possibly others.)
But that's not the problem today. Today they are being set:
SI_MEMSIZE=2048
SI_NUMDISKS=1
SI_DISKLIST=c0t0d0
SI_DISKSIZES=0
SI_ROOTDISK=c0t0d0s0
SI_ROOTDISKSIZE=0
SI_TOTALDISK=0
But all the disk size variables are set incorrectly. This has always
worked for me on SPARC, but this is the first time attempting it on x86.
Is this just not possible on x86?
This machine has a single 72GB IBM SCSI drive installed. It has never
had Solaris on it before.
'format' can find the drive, but claims it's not labeled. Attempts to
label it fail.
Is all of this because the drive has no Solaris FDisk partition on it yet?
I was going to let JumpStart create all that for me, but maybe I need to
do it the first time manually?
-Kyle
