<p dir="ltr"><br>
On Jan 9, 2014 6:26 AM, "Chris Adams" <<a href="mailto:linux@cmadams.net">linux@cmadams.net</a>> wrote:<br>
><br>
> Once upon a time, Toshio Kuratomi <<a href="mailto:a.badger@gmail.com">a.badger@gmail.com</a>> said:<br>
> > <nod> Just have yum drop a config file in there that protects the kernel<br>
> > rather than protecting the kernel if some other package chooses to protect<br>
> > something else.<br>
><br>
> The magic "don't delete the running kernel" can't be done with just a<br>
> config file. Something has to detect which kernel version is running<br>
> and match it to an RPM, and then protect just that version of multiple<br>
> installed kernel RPMs.<br>
></p>
<p dir="ltr">Can't the meaning of a package name in the config file simply mean: "make sure one of these packages is always installed"?</p>
<p dir="ltr">That won't protect the running kernel but it will protect a kernel (probably the latest installed). That would seem to address hreindl's use case of wanting to test on multiple systems and when satisfied that things are working cleanup all older packages.</p>
<p dir="ltr">That would still be a difference from the current yum code but less than not having any protection at all and would be more generic.</p>
<p dir="ltr">-Toshio</p>
<p dir="ltr">> I supposed you could do it external to yum/dnf with a boot-time script<br>
> that rewrites a config file to protect kernel-$(uname -r), but that may<br>
> not always work (it would have to handle things like kernel-PAE and<br>
> such).<br>
><br>
> --<br>
> Chris Adams <<a href="mailto:linux@cmadams.net">linux@cmadams.net</a>><br>
> --<br>
> devel mailing list<br>
> <a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
> <a href="https://admin.fedoraproject.org/mailman/listinfo/devel">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
> Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct">http://fedoraproject.org/code-of-conduct</a></p>