-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/14/2015 11:29 PM, Karsten Wade wrote:
If you're going this route, can I beg you to put in this? I've asked the anaconda developers for this before, and it's invaluable for getting your actual ks.cfg saved for reference, rather than that wildly distinct and script discarding 'anaconda-ks.cfg'.
%post --nochroot cp -a /tmp/ks.cfg /mnt/sysimage/root/ks.cfg %end
This kind of thing makes me think, metadata around each kickstart is crucial to this. We can't just have a raw .ks file, unless it's as well documented (#commented) as a Tom Callaway tutorial example.
That's pretty much what I'd like the repo to be.
What I mean is, we need a way to track your comment about why that bit is invaluable for which situations, and how/where it's useful in what sort of kickstart files.
The repository has been cloned to github for community use/improvement. If I made a couple minor changes and updated the README (along with wolfy) so please feel free to review/contribute to https://github.com/CentOS/Community-Kickstarts
- -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77