On 15/03/06, Ron Loftin <reloftin@xxxxxxxxxxxx> wrote:
> I saw your question in the digest version of the list, and thought you
> might be interested in my solution. I do have it working, and there are
> a couple of points that I didn't see mentioned in the other parts of
> this thread, or just were mentioned in passing.
>
> The following is a kickstart file for a workstation install on my
> network.
>
> ******************** Begin example ks file ***************************
<snip?
> One VERY IMPORTANT point to remember is shown in the "%pre" script.
> This is how to make the modules available to anaconda for processing.
> Just mount the tree where the modules live somewhere on the target
> system where you can tell anaconda to go read it. Here, I just create a
> new directory ( /mnt/ks ) and all %include directives reference that
> tree. Again, all paths must be specified the way that the CLIENT will
> evaluate them.
Ron, everyone else, thanks all for the input, much appreciated.
I've just started having a fiddle on a test box again so fingers crossed.
Cheers guys.
Will.
