On Mon, Feb 10, 2003 at 03:20:26PM -0800, Simon Stanlake wrote:
> I have a custom kernel which I have slightly modified the source for.
> I'm running the kernel on multiple machines. I'm trying to come up with
> a smooth system for keeping the kernels up to date across multiple
> machines without killing the changes I've made. up2date won't work for
> me because as I understand it getting the kernel-src package will wipe
> out my changes.
You've got a few choices. The easiest (and I'm *not* a kernel guy)
would be to grab the sources once, apply your changes as a patch, and
then rebuild the package. Give it a version that will not be superseded
by up2date. By default, up2date will ignore kernels anyway (see the
package skip list in /etc/sysconfig/rhn/up2date).
When running up2date, you can give it a list of source directories for
where to go get the updates (see the --packagedir option). NFS-mount
your kernel package directory and up2date will find your kernel first
which could then be forced. Your version would be higher than Red
Hat's, so your's should be chosen.
When a new kernel comes out, update your patch if required, rebuild your
package, and copy it to your packagedir location (after testing it of
course!).
.../Ed
--
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]
Member #1, Red Hat Community Ambassador Program
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
