On Tue, 12 Jul 2011 14:29:47 +0100, James Hogarth <[email protected]> wrote:
> Initial tests on day 1.... if /updates/ is enabled along with base > MAKEDEV refuses to install... for the kickstart itself make sure that > updates isn't enabled.... a yum update can be done in post or after > the system is up to bring it up to date. Interesting - I didn't have that issue and I do have Updates available as a child channel (and used during install). I'm using VMware ESXi 4.1u1, if that matters. > Spacewalk still has --enablemd5 in it's kickstart generation by > default and the encrypted root password id md5 encryption... remove > the --enablemd5 from the advanced options page and regenerate the root > password after install (the encrypted form can be put back in > spacewalk if you like) to use the more up to date SHA hash method. Good catch. Mark. -- Mark Watts, BSc RHCE http://www.linux-corner.info/ _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
