# Rocky Linux kernel naming convention

**URL:** <https://forums.rockylinux.org/t/rocky-linux-kernel-naming-convention/15935>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-8\
**Created:** [September 24, 2024, 3:07am UTC](https://forums.rockylinux.org/t/rocky-linux-kernel-naming-convention/15935 "2024-09-24T03:07:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![greatlong](https://avatars.discourse-cdn.com/v4/letter/g/7ea924/32.png) [@greatlong](https://forums.rockylinux.org/u/greatlong)\
**Post date:** [September 24, 2024, 3:07am UTC](https://forums.rockylinux.org/t/rocky-linux-kernel-naming-convention/15935/1 "2024-09-24T03:07:37Z")

</div>

Could any expert explain the naming convention of Rocky Linux kernel?  
Take Rocky Linux 8.8 as example: the kernel version is 4.18.0-477.10.1.  
My understand:  
4: Major version  
18: Minor version  
0-477: ?  
10: ?  
1: ?  
I don’t know 0-477, 10 and 1’s naming.  
Could any expert help clarify?  
Thanks in advance!

---

<div class="post-metadata">

**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\
**Post date:** [September 24, 2024, 3:16am UTC](https://forums.rockylinux.org/t/rocky-linux-kernel-naming-convention/15935/2 "2024-09-24T03:16:39Z")

</div>

The kernel version starts out as a normal kernel version that you would see from [kernel.org](http://kernel.org). Also read about [semantic versioning](https://semver.org/).

```auto
4: Major version
18: Minor version
0: Micro/Patch version
1-553.X.Y: Package Release version

```

Replace X and Y accordingly.

---

<div class="post-metadata">

**Author:** ![greatlong](https://avatars.discourse-cdn.com/v4/letter/g/7ea924/32.png) [@greatlong](https://forums.rockylinux.org/u/greatlong)\
**Post date:** [September 24, 2024, 3:19am UTC](https://forums.rockylinux.org/t/rocky-linux-kernel-naming-convention/15935/3 "2024-09-24T03:19:42Z")

</div>

> [@label](#):
>
> `1-553.X.Y: Package Release version`

Thanks a lot for your quick clarification!

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [September 24, 2024, 8:19am UTC](https://forums.rockylinux.org/t/rocky-linux-kernel-naming-convention/15935/4 "2024-09-24T08:19:06Z")

</div>

[When will the Red Hat Enterprise Linux package be updated to the upstream version? - Red Hat Customer Portal](https://access.redhat.com/solutions/2074) does also tell about the versioning.  
The main points:

> At the time that a RHEL major version is released, a particular version of each of the software component has been selected …
> 
> During the lifecycle of a RHEL major release, bug/security fixes and feature enhancements are _backported_ from upstream projects to RHEL packages.
> 
> For example, if a RHEL release includes package version `software-2.10` of a particular piece of software, Red Hat changes will likely follow a numbering scheme like `software-2.10-1` then `software-2.10-2` then `software-2.10-3` and so on. Even if upstream change the software to `software-2.11`, the RHEL package will likely remain on `software-2.10-n` and features/fixes from the later upstream releases may be backported into the RHEL `software-2.10-n` packages and the RHEL-specific version suffix will increase.

You can look at changelog of (installed) package with:

```bash
rpm -q --changelog kernel-4.18.0-477.10.1* | less

```

You can also list the kernels that you have at some point installed:

```plaintext
dnf history info kernel | grep Install.*kernel-4

```

Lets generalize the “4.18.0-477.10.1” into “X.Y.Z-A.B.C” (the A.B.C is _Package Release version_). For RHEL 8 (and hence Rocky 8) kernel, the X.Y.Z does not change – always `4.18.0`.  
The A increases as features are backported. It remains constant within point update. The el8\_0 had A=80, the el8\_8 had A=477, and el8\_10 has A=553. Bug and security fixes released for point updates’ kernel are in the B.C.

---

<div class="post-metadata">

**Author:** ![greatlong](https://avatars.discourse-cdn.com/v4/letter/g/7ea924/32.png) [@greatlong](https://forums.rockylinux.org/u/greatlong)\
**Post date:** [September 24, 2024, 9:18am UTC](https://forums.rockylinux.org/t/rocky-linux-kernel-naming-convention/15935/5 "2024-09-24T09:18:01Z")

</div>

Thanks a lot for the detailed clarification!  
It helps a lot.  
One more query, for such kernel Package Release version update from 4.18.0-477 to 4.18.0-553 (OS update from 8.8 to 8.10)， will there be any performance impact (especially performance degrade)?

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [September 24, 2024, 12:45pm UTC](https://forums.rockylinux.org/t/rocky-linux-kernel-naming-convention/15935/6 "2024-09-24T12:45:41Z")

</div>

> [@greatlong](#):
>
> One more query, for such kernel Package Release version update from 4.18.0-477 to 4.18.0-553 (OS update from 8.8 to 8.10)， will there be any performance impact (especially performance degrade)?

I think you have already seen answer to that in [How to get the kernel changes between Rocky Linux 8.8 and 8.10 - #6 by nazunalika](https://forums.rockylinux.org/t/how-to-get-the-kernel-changes-between-rocky-linux-8-8-and-8-10/15922/6)

* * *

Overall, Red Hat has RHEL major version _X_ that is at point update _Y_. For example, RHEL 8.9.  
Red Hat has paying customers; they sell support subscriptions for RHEL 8.  
They did release new point update, _Y+1_ – RHEL 8.10. An assumption is that most users auto-upgrade 8.9 → 8.10. It would not be good for business to introduce performance degradations, would it? (Workarounds to security issues may cause some degradation, but not on every update.)

---

<div class="post-metadata">

**Author:** ![greatlong](https://avatars.discourse-cdn.com/v4/letter/g/7ea924/32.png) [@greatlong](https://forums.rockylinux.org/u/greatlong)\
**Post date:** [September 25, 2024, 2:15am UTC](https://forums.rockylinux.org/t/rocky-linux-kernel-naming-convention/15935/7 "2024-09-25T02:15:21Z")

</div>

> [@jlehtone](#):
>
> . It would not be good for business to introduce p

Yes, I see the answers. I ask again here in case if you have different understanding and insight.  
Anyway, you clarification is very helpful. Thanks a lot!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [November 24, 2024, 2:16am UTC](https://forums.rockylinux.org/t/rocky-linux-kernel-naming-convention/15935/8 "2024-11-24T02:16:20Z")

</div>

Closed on November 24, 2024, 2:16am UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
