-----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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJUt7vpAAoJEBbHyC76Ca13dLkQAMbyXqSazffzJ+q8W3IK9jLb m3oStJ4QOTYX77AY4+cadt8J+dpubUzUPWV30fn70LeE6kIrDOxqYi/hY9yO7HrH vOJkQKkNgQYVI2BZa9bzJ13Ar8SYZW13uEwIwZTyCqNaoyJq0wOIPgsZt/EMir8g qVKhJ2ZJ4/ztQHYn67Eqt88h+TI8dbVqkoQN5t/HhiqW4L0nrtmvTcsdcKZRqrYI P/7Bsc+hAOPHnxsl9K31l+n/+MdYmUXzxnMo6IqMkaAQKaClw0ve1TwdstLz64k6 KJKQSl3uNmgbXXOYXyk5hIXOoVv3pYXfk4EW45hzF/Dc+nuYrNkmP0VowxHhfVfu 14IHCuTVM8FtolQaTKy7NKI8+YTul8kqycq/03IBMqh4OIOCNkJEOo2W19+44lqP Kl27eOmNs4l1RXasROIlGoXONQ6ViaYjEUEyr+K/+d2H8nuoK0eW0itazwvf5smu KbHpHejNrwRb7k07bC5mjP61wZuySH25BAEX50lSGSnsoqZl7zfrAvTypX01rB23 TjX7r6u8Nfas3be0Dfrf8p2uJbGzvdu3oej0wp9MmN1ARq9ruBtV1SlAzxzQ81u5 iK4Yh/4s1+c4ST6o6mqYx6bmOLcGxmNvCqdXsrgD5z6fFgGU1GMD1Gr1OZ23wCUS Fla6YkX1dWCzMPvPzVEp =W9gu -----END PGP SIGNATURE-----