# Default value for disks (27G layout)
BOOTSIZE=256
ROOTSIZE=8192
VARSIZE=8192
SWAPSIZE=2048
BANKTOOLSIZE=8192
GRIDSIZE=0
# check for small disk sizes < default 27G layout:
if [ ${DISKSIZE} -lt 27648 ]
then
# create small disk (16G layout)
ROOTSIZE=5120
VARSIZE=5120
SWAPSIZE=2048
BANKTOOLSIZE=3072
fi
# force it if it's a VMware system with more than 20G of space
dmidecode | grep Manufacturer | head -1 | grep -q VMware
if [ $? = "0" ]
then
# create small disk xen/vmware (16G layout)
ROOTSIZE=5120
VARSIZE=5120
SWAPSIZE=2048
BANKTOOLSIZE=3072
fi
-----Original Message-----
From: kickstart-list-bounces@xxxxxxxxxx
[mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of John Oliver
Sent: Monday, November 09, 2009 11:33 AM
To: Discussion list about Kickstart
Subject: Re: Kickstart, partitioning, differing disk space
On Mon, Nov 09, 2009 at 11:04:22AM -0800, Shabazian, Chip wrote:
> We have three different partitioning schemes. The kickstart figures
> out how big the disk is, then uses one of three different schemes
based
> on the size. However, if it's a VM, we automatically select the
> smallest partitioning scheme
What are these "three schemes"? How do they know when they're on a VM?
Could you include a copy of the relevant section of your ks file?
Thanks...
--
***********************************************************************
* John Oliver http://www.john-oliver.net/ *
* *
***********************************************************************
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
