On 10/26/19 10:56 AM, home user wrote:
(responding to Ed)
> The easiest way...
done.
The script looks like this:
-
#!/usr/bin/sh
# clean out files left behind by the compiling that follows patching or
# updating the kernel and/or the driver for the nvidia graphics card.
rm -rf /var/cache/a
(responding to Ed)
> The easiest way...
done.
The script looks like this:
-
#!/usr/bin/sh
# clean out files left behind by the compiling that follows patching or
# updating the kernel and/or the driver for the nvidia graphics card.
rm -rf /var/cache/akmods/nvidia/*
exit $?
# done!
-
T
On Fri, 2019-10-25 at 16:42 -0400, Tony Nelson wrote:
> When DNF upgrades the kernel packages, it removes kernels so that
> there are not more than installonly_limit installed. It won't
> remove the running kernel.
>
> How do I protect more than the running kernel from DNF during
> a kernel upgra
When DNF upgrades the kernel packages, it removes kernels so that
there are not more than installonly_limit installed. It won't
remove the running kernel.
How do I protect more than the running kernel from DNF during
a kernel upgrade? I have two that I would like to keep. Neither
excludepkgs n
On Thu, Oct 24, 2019 at 08:15:45PM +, George R Goffe via users wrote:
> problem. I once tried this kind of thing and dnf came back with > 800
> (maybe 1400) packages to remove... including rpm and dnf et. al NOT
> GOOD. It's good that dnf asks if it's ok to proceed. Whew. Bullet dodged.
I'
On 10/24/19 1:15 PM, George R Goffe via users wrote:
The "real" situation is that I have frozen this system's kernel at an older
version because of problems with the newer kernels going crazy... reporting apparent
stalling on cpus (excessive disablement maybe). I thought I had a broken cpu but
