This Question is Answered
...your are right UUID is ugly and impossible with the means of my pre installation system.
Anyway I found a way by adding my ks.cfg to the initrd.img and appended the ks as ks=file:///ks.cfg
Well, thank you for the support!
Lets hope VMware does not remove this way of configurating, too
Max
...and now what I did to the initrd.img:
#make a temp home for the filesys in initrd.img
mkdir /esx/newinit
cd /esx/newinit
cp ../initrd.img .
#gunzip initrd.img
mv initrd.img initrd.im.gz
gunzip initrd.im.gz
#extract the filesystem in initrd
/esx/bin/cpio -i < initrd.im
copy ks.cfg
cp /esx/ks.cfg .
#clean up the init filesystem
rm initrd.im
#make the new inintrd.im
find .|/esx/bin/cpio -o --format='newc' > ../initrd.im
#compress the initrd.im
cd /esx
gzip initrd.im
#just rename
mv initrd.im.gz initrd.img
Max,
I've figured out how to get the cpio onto the altiris server, and my script (with your new commands) seems to run OK. The problem is still exactly the same ks.cfg does not exist. I know it does exist, as I can cat it from a grub command prompt. Once the kernel loads and weasel starts running, I don't know where the file is anymore (ie how you specifiy a path to it).
I think I'm going to have to redo how pxe is loading the kernel for ESX 4
FYI - I've gotten this to work. Thanks a lot for your help, as we wouldn't have gotten this far without it.
NOTE: In altiris, I had to make a big grub partition for all this unzipping etc. 500MB wasn't big enough, so I went to 2GB and that did the trick
rt,
I didn't change a file or change the size of the grub image - I changed the size of the partition that gets created when the grub image is pushed down. I've attached a screenshot from the altiris job in the deployment console. In the step that pushes down grub.img - click on the advanced button.
Attachments:
-
altiris.jpg (77.8 K)
