Hi Georgi, Good question, The problem is I am assigning partition
size using actual sizes rather than percentages. Production machines will have
plenty of disk space available but trying to create 80+Gb’s of partitions
on xen machine only given 5Gb’s will obviosly fail. I am thus stuck to
using pre unless I can be more creative about my partitioning but that will
require a lot of rethink. Regards From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Hristov, Georgi I understand
you want to distinguish them, but what do you use that for? Is it for some post
install customizations? You will have many more options in the post section
instead of the pre section? -Georgi From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Gerrard Geldenhuis Hi I have the following in a pre-script to detect
whether I am building a xen machine: set $(list-harddrives) vx=$(echo $2|cut -d. -f 1 ) if [ $vx -lt 5120 ]; then echo 'xen'
> /tmp/xen etc… This makes assumptions based on disk size. This is a fairly safe assumption for us because we control
the disk size but I was wondering if anybody could suggest a more sure fire
robust way of detecting whether one is building xen or “normal”.
For normal builds I am using dmidecode which is working very well and I can
even use it for VMWare builds. My aim is to have one kickstart per service type that
adjust itself according to underlying platform which could be IBM, HP, VMWare
or Xen. Regards ______________ |
_______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list