HTTP kickstart - using an includes/ directory

John Summerfield debian at herakles.homelinux.org
Sat Apr 14 23:36:05 UTC 2007


kickstartlist wrote:
> Hi-
> 
> I'm doing HTTP kickstart with CentOS44, and as I have done with NFS,
> would like to %include a per-server hostname.inc packages file with
> an %include statement in the kickstart file. Ideally, I'd like to
> have an "/includes" subdirectory in the OS install tree, where HTTP
> is also fetching my kickstart file from.
> 
> With NFS, a path like /mnt/source/includes/ could be used - so in
> the NFS kickstart file:
> 
> %include /mnt/source/includes/hostname.inc
> 
> My installation url/ks file path is:
> http://10.135.135.1/kickstart/CentOS44/os/x86_64/hostname.ks
> 
> This exists:
> http://10.135.135.1/kickstart/CentOS44/os/x86_64/includes/hostname.inc
> 
> This:
> %include includes/hostname.inc
> doesn't work; anaconda doesn't find the path and aborts the install.
> 
> I've tried several different paths for the include statement, and
> also changed the location of the include directory, to no avail,
> even the full method:path doesn't work:
> 
> %include http://10.135.135.1/kickstart/CentOS44/os/x86_64/includes/hostname.inc
> 
> I've also not found any documented mention yet of how this works -
> does anyone know what's going on here - am I stupidly missing
> something simple?
> 
> Many thanks for any insight!
> Harold

In %pre
cd /tmp
wget \ 
http://10.135.135.1/kickstart/CentOS44/os/x86_64/includes/hostname.inc

then
#include /tmp/hostname.inc

or generate the whole thing in cgi, and not bother with the include at all.



-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu

Please do not reply off-list




More information about the Kickstart-list mailing list