> on, I'd like to see a small message asking me if I want to, "Run the > new kernel that > yum has updated?" With selection buttons such as "Reboot to New > Kernel?" "Remind I think that is beside the point. I think it is an issue for the kernel rpm. There is ample script possibilities in the rpm to launch a system that will ask for reboot. But since you may have custom modules that may not run under the updated kernel it seems to me to be a sensible way not to have yum do this step. Also - after the kernel is copied in place the rpm calls a local script (don't remember the name) which you could alter to include this functionality. I think that would make a better solution. Karsten On Apr 6, 2004, at 16:38, Johnny wrote: > Hi Nigel, > > As a Linux Administrator (self taught, raked over the coals, realtime > disaster fixer), > you've hit the nail on the head. Though what I would like to see, is > that when I log > on, I'd like to see a small message asking me if I want to, "Run the > new kernel that > yum has updated?" With selection buttons such as "Reboot to New > Kernel?" "Remind > me later?" "Let me finish what I am doing and I'll manually reboot!" > > The third option will allow me to verify that I have all my data safe, > config files backed up, > get everyone else off the system, and be ready for any thing that may > go wrong on the boot up. > I'd like that capability more than anything else, having lost a few > configurations in the past. > > Johnny > > Nigel Metheringham wrote: > >> On a good number of my machines I let yum run and update >> automatically - >> on the basis that I would prefer things to be kept up to date and deal >> with breakages if they happen rather than rely on me being able to >> find >> time to ensure things are updated. >> >> This works well, with one exception: kernel updates. >> The kernel updates are applied (subject to me not running out of space >> in /boot :-) ), however yum does not reboot to the new kernel (thats >> fine - I'm not that gung-ho), nor does it notify me that the kernel >> has >> been updated (less fine). >> >> I am therefore wondering if there should additionally be some form of >> reporting for this situation, maybe one of:- >> * yum reporting on this (all programs acquire features until they >> are able to send and receive email) >> * a logwatch report that specifically logs when running kernel is >> not the most recent installed (this might irritate people who >> have a good reason for doing this) >> * a logwatch report that reports on packages changed since ??? >> * a logwatch report that reports on packages changed since ??? >> with extra kernel flagging feature >> >> Not sure how well the yum log (which rolls on a size based criteria) >> will interwork with logwatch which I presume assumes regular log >> rolling? >> >> I'm quite willing to hack together appropriate scripting if theres a >> consensus on the right thing to do. >> >> Nigel. >> > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum >
