Bug 6837
Summary: | pass kickstart a Python object? | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | rumi.gonda |
Component: | rhl-cg | Assignee: | Tammy Fox <tammy.c.fox> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | rumi.gonda |
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: | 2001-01-16 21:34:32 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
rumi.gonda
1999-11-08 22:27:02 UTC
there is no new documentation regarding this in the winston reference guide ... This is now reassigned to the correct docs contact. Thanks! You can put "%installclass" in your kickstart file and then start writing python code which runs to the end of the file. This is not recommended since it can cause many problems if the code is not correct or does not work with the existing Anaconda code. We are not going to mention it in our kickstart documentation. |