Hi, actually systemconfigurator should help you to keep it simple:
IMAGED=/var/lib/systemimger/images/XXX - put the rpms to a shared directory, for example cp kernel*.rpm /home/.rpms/ - update the kernel in the image rpm -Fhvr $IMAGED /home/.rpms/*.rpm - edit the systemconfigurator script in the image to reflect the new kernel version vi $IMAGED/etc/systemconfig/systemconfig.conf - push the edited systemconfig.conf to the client nodes cpush $IMAGED/etc/systemconfig/systemconfig.conf /etc/systemconfig/ (don't forget the trailing "/") - update the kernel on the clients cexec rpm -Fhv /home/.rpms/*.rpm - run systemconfigurator on the client nodes cexec systemconfigurator --configrd --configboot --runboot Regards, Erich -- Dr. Erich Focht <[EMAIL PROTECTED]> NEC High Performance Computing Europe GmbH, EHPCTC On Wednesday 04 February 2004 02:06, Frank Crawford wrote: > Andy, > You can almost do an rpm -U xxx.rpm for kernel updates, but there are a > couple of little fix ups you need after it. You need to update lilo (it > generally survives it), rename the initrd file and update the system > configurator script. I've again attached a script I used recently to do > it (however, the script did a lot more updates than just the kernel, it > also did glibc and other outstanding patches). Just run it with "cexec > upit.sh". > > You also need to apply all this to the images directory (i.e. rpm -Uvh > --root /var/lib/systemimage/images/XXX/ *.rpm) ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
