Bug 97571
Summary: | kickstart %pre poorly documented | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Travis Crawford <travis_b_crawford> |
Component: | anaconda | Assignee: | Tammy Fox <tammy.c.fox> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-08-19 15:40:30 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Travis Crawford
2003-06-17 20:31:39 UTC
You can't do this in 2.1 (it's why the %include directive was added). Assigning to Tammy to double-check what's currently there for the next release. The latest step of docs for kickstart show how to use the %pre section to determine information and then include it later in the kickstart file. Like Jeremy said, the %include directive was added after RHEL 2.1. Is this the type of example you are looking for? In the kickstart-mailing list there have been reports of regenerating an entire kickstart file in the %pre section, and writing it to /tmp/ks.cfg so that the new version will be reread after %pre. grep'ing through /usr/lib/anaconda does not find that string, but I did find /tmp/anaconda-ks.cfg. So I tried writing to both of these locations in %pre but without success. Is regenerating the entire kickstart file in %pre possible in AS 2.1? Thanks. The next version will include %include, and the next version of the docs will include an example of how to use %pre to create a file and include it with %include. |