Linux

49154 readers

566 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

A noticeable difference in kernels? (lemmy.ml)

submitted 2 days ago by [email protected] to c/[email protected]

28 comments fedilink hide all child comments

I have the following kernels installed:

linux-zen (Zen)
linux-rt (RealTime)
linux-hardened (Security Hardened)
linux-lts (Long Term Support)
linux-tr-lts (Realtime LTS)

When I boot up, I try the different kernels from time to time just to see if anything interesting happens. It never does.

My question: How do I actually physically notice the difference between these kernels? If I use RT, does Firefox spawn quicker (in my testing, no, not really)?

What are some use cases when I can really see the difference in these kernels?

you are viewing a single comment's thread
view the rest of the comments

[–] Codilingus 5 points 2 days ago (1 children)

There's a systemd OOM service that can be setup. I use CachyOS and they have it as a checkbox to turn it on or off.

[–] [email protected] 2 points 2 days ago (1 children)

Going to look into this, thanks!

[–] [email protected] 1 points 2 days ago

I've had this exact same gripe and can thankfully report that running EarlyOOM has fixed this for me.