Hi, I think it makes no sense to use Tumbleweed if you plan to compile and use a custom kernel, as kernel is being updated very frequently due to rolling release nature of Tumbleweed, in a week or so you may exhaust the availability of kernel entries in grub, i am yet to investigate what this number is but for sure you will exhaust it sooner or later. Using a LTS is not an option for me, drivers are too old for my rtl8723be wifi chip, low signal, slow download speed, lost connection etc problems that i had to battle until 4.17 that so far has been working great, Is there a way to do some kind of package stickiness within the same oficial repositores? this way the kernel won’t be updated so often until i am ready and have the time to recompile it, Somehow a twisted DYI LTS kernel version.
On Fri 27 Jul 2018 05:16:03 AM CDT, miguel mirandag1975 wrote:
Hi, I think it makes no sense to use Tumbleweed if you plan to compile
and use a custom kernel, as kernel is being updated very frequently due
to rolling release nature of Tumbleweed, in a week or so you may exhaust
the availability of kernel entries in grub, i am yet to investigate what
this number is but for sure you will exhaust it sooner or later. Using a
LTS is not an option for me, drivers are too old for my rtl8723be wifi
chip, low signal, slow download speed, lost connection etc problems
that i had to battle until 4.17 that so far has been working great, Is
there a way to do some kind of package stickiness within the same
oficial repositores? this way the kernel won’t be updated so often until
i am ready and have the time to recompile it, Somehow a twisted DYI LTS
kernel version.
Hi
Why a custom compile, what options are you setting?
Just add a lock to the kernels you don’t want via zypper al
<some_package>.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-23-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
My primary goal es apply the kernel-pf patch and test the MoQSS scheduler