From: Joseph L. Casale <jcasale@xxxxxxxxxxxxxxxxx>
> You don't need to do that. Add the updates repo as a 'repo' line
> in the ks, it will install anything new at once saving time and cruft.
The thing is that I setup the kickstart with the target network
configured (which will not work in our office), and then, in the post
script, I temporarily switch to a temporary network config...
I set it up this way because in the past I wanted to be able to make
a whole install without needing network access...
I guess I would need to reverse the configs now.
From: Keith Roberts <keith@xxxxxxxxxxxx>
> So are you telling me you do a fresh installation AND an
> update all in one go?
I do *everything* in the chrooted post, so that I can just shutdown
after install and the server is ready to be plugged.
It used to work fine with 5.x...
Everything also seems to work fine for 6.x, except for grubby.
I caught a "Grubby fatal error : unable to find a suitable template".
Found many bug reports (some as old as 2004), but no real fix...
For now, I just add the entry to grub.conf in my script and it boots
fine on the new kernel.
I noticed that if I run the new-kernel-pkg after the reboot, it does not
complain anymore and the root in grub.conf is different:
The one added by new-kernel-pkg (after a reboot):
kernel /vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=LABEL=/
The one I added (that works too):
kernel /vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=UUID=abd50638...
Original:
kernel /vmlinuz-2.6.32-71.el6.x86_64 ro root=UUID=abd50638...
Thx,
JD
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
