this post was submitted on 12 Nov 2024
119 points (99.2% liked)

Linux

48446 readers
639 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

Related Communities

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

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] ryannathans@aussie.zone 5 points 3 weeks ago (1 children)

How does it know if the microcode is outdated?

[–] nanook@friendica.eskimo.com 15 points 3 weeks ago (3 children)

@ryannathans @captainkangaroo I'm going to make the wild assumption that the kernel will have a table of the current microcode versions at the time of it's release, but I doubt that
will get updated except by kernel upgrades.

[–] DaPorkchop_@lemmy.ml 3 points 2 weeks ago (1 children)

Debian-based distros (and probably most othera as well) actually have a package called "intel-microcode" which gets updated fairly regularly.

[–] nanook@friendica.eskimo.com 1 points 2 weeks ago

@DaPorkchop_ Oddly, if you build your own kernel and remove the system provided one, the package gets automatically removed as well which is weird, because it is really still needed regardless.

[–] Strit@lemmy.linuxuserspace.show 3 points 3 weeks ago

There's probably an efivar that reads the current microcode version.

[–] ryannathans@aussie.zone 1 points 2 weeks ago (1 children)

If that's the case, why wouldn't they put the microcode in the kernel?

[–] nanook@friendica.eskimo.com 1 points 2 weeks ago (1 children)

@ryannathans Why bloat the kernel with the microcode for every intel processor that might need it (and there is a similar thing for AMD) when you don't have that specific processor? It does make more sense for it to be a separate, especially on memory constrained systems. I mean if you've got 256GB of RAM probably not a big deal but if you've got 256MB a big deal.

[–] ryannathans@aussie.zone 1 points 2 weeks ago* (last edited 2 weeks ago)

The kernel compilation is already configurable between megabytes and gigabyte+

Distros pick their featureset