I'm to poor to buy a new laptop you jerks. On Aug-7-2021 06:40PM, -pj wrote:

On 8/7/21 3:05 PM, Felix Miata wrote:

...

-pj composed on 2021-08-07 02:37 (UTC-0500):

...

Felix Miata wrote:

...

-pj composed on 2021-08-07 00:46 (UTC-0500):

...

I want to install and lock every possible kernel package relating to 5.13.6-1-pae that can be recommended. sudo zypper al kernel-pae* will keep 5.13.6 from being removed, and prevent zypper and yast from attempting to install any other kernel-pae version. The faulty (for this machine) 5.12.13-1-pae kernel is currently listed as an option in the bootmenu though. Using the above suggested command "sudo zypper al kernel-pae*" seems like it might lock 5.12.13-1-pae also?

Exactly.

...

If the machine is currently booted/operating under the 5.13.6-1-pae then does "zypper al kernel-pae*"  only lock that specific operating kernel instance (this may be what you are pointing out).

If you want to lock only a specific kernel, the version string must be part of the lock string name. e.g.

zypper al kernel-pae-5.13.6*

If you want to lock all kernels of a specific version, then:

zypper al kernel*5.13.6*

If I issue the following command:

zypper al kernel-pae-5.13.6-1-pae it is correct and not zypper al kernel-pae-5.13.6-1.2.i686 correct?

How can zypper be used to unlock a version string or a package? YaST seems to only allow locking of packages with what are contained in the installed repos, in my case the "tiwai 5.11.xx kernel" repo's packages are able to be locked and unlocked using YaST.

Is there a konsole command to list all locked packages on the machine?

...

...

How can I find the exact specific package name for the 5.13.6-1-pae kernel ?

If it's an installed kernel:

rpm -qa | grep nel-pae

e.g. # rpm -qa | egrep 'nel-pae|nel-def' kernel-default-5.7.11-1.2.i586 kernel-default-5.8.15-1.2.i586 kernel-default-5.9.14-1.2.i586 kernel-default-5.10.16-1.3.i586 kernel-default-5.11.16-1.1.i586 kernel-default-5.12.13-1.1.i586

Passing command "rpm -qa | egrep 'nel-pae|nel-def' in the notebook's konsole results as follows:

pj@pj-Compaq-nc6400:/> rpm -qa | egrep 'nel-pae|nel-def' kernel-default-5.11.16-1.1.ge06d321.i586 kernel-pae-5.12.13-1.1.i686 kernel-pae-5.13.6-1.2.i686 pj@pj-Compaq-nc6400:/>

I notice that today there was a kernel update to....kernel-pae-5.13.6-1.2.i686 (machine stable :|)

Can I safely remove kernel-pae-5.12.13-1.1.i686? How can I remove this kernel and all remnants of it with zypper? YaST is not displaying the 5.12.xx kernel or any packages relating to it's series when "kernel" search pattern is used. Then the bootmenu will show the 5.11.xx and 5.13.xx kernels correct?

I see how command "rpm -qa | egrep 'nel-pae|nel-def' shows the above 3 instances listed and not the below instances. This use of grep and egrep is another topic I know.

      1.the kernel-default-base       2.kernel-default-base-rebuild       3.kernel-default-devel       5.kernel-devel       6.kernel-source

...

...

I believe the purge-kernels service is active by default right?

Yes.

...

Currently here multiversion.kernels line 554: 1 multiversion.kernels = latest,latest-1,running

I edited line 554 of /etc/zypp/zypp.conf to the following: > multiversion.kernels = latest,latest-1,running,5.11.16-1.ge06d321

I powercycled (noted no change in boot menu entries) then reverted to default: > multiversion.kernels = latest,latest-1,running

...

...

Would you have any further suggestions or even a potential to keep 4 of the past kernels instead of only 3?

If you have any kernel that works, that one is all you need for normal use. If you expect to ever do any kernel bisection looking for when a bug first appeared, it's convenient not to have deleted older kernels. For most people, there's no point in changing multiversion.kernels. If you're more comfortable keeping more, go ahead and keep more. Another option is to disable purge-kernels.service and delete kernels manually at your pleasure.

I am interested in kernel-sources for 5.13.xx series due to the following, well basically additional documentation:

-----> There was a text file in "/usr/src/linux/Documentation" (if the kernel sources are installed) that described every possible device file in /dev. I can not find it now. Ah! Found it:

/usr/src/linux/Documentation/admin-guide/devices.txt The other important data in /dev is the Major-Minor numbers. <----- Compliments to Carlos E.R.

I know more now in your response within the above paragraph, what you are conveying. What about CVS security patches and such for the latest kernel versions?

...

Something else to consider if your PC seems sensitive to kernel changes is locking all kernels, then only installing a new one when you're so inclined. Locks with wildcards are never deleted by zypper, even though it claims to do so when removal is an option presented in response to an attempt to install (or remove) any version the lock would apply to. What actually happens in such attempts is zypper ignores the lock for that one specific transaction.

 I have reread this above paragraph so it's more sense. Of course I will have to file this for reference.

-Best Wishes