Jumpstart installs more then SUNWCmreq cluster
Hi,
I've encountered something odd, I recently created a simple profile that looks like:
install_typeinitial_install
system_typestandalone
partitioningexplicit
cluster SUNWCmreq
filesys rootdisk.s0 15360/
filesys rootdisk.s1 4096swap
filesys rootdisk.s3 15360/var
As you can see I'm declaring the SUNWCreq cluster, yet when I perform the install I'm getting far more installed that the mreq cluster. In fact it looks like it's installing SUNWCall.
Anyone seen anything like this before?
[557 byte] By [
mithril] at [2007-11-26 11:10:07]

# 1
Well, the cluster you should use in this case is SUNWCreq, which is the required/minimal installation.
You specified "SUNWCmreq", which is an internal cluster and not selectable by your profile;
METACLUSTER=SUNWCmreq
NAME=Minimal Core System Support
DESC=Internal private metacluster not installable by end users.
VENDOR=Sun Microsystems, Inc.
HIDDEN=y
REQUIRED=y
I can imagine that if you specify an unknown/invalid cluster the installation will default to SUNWCall, i'ld suggest that you use SUNWCreq rather than SUNWCmreq.
.7/M.