> I don't have any love for general initrds, but using an initrd for
> microcode allows early loading - for a few intel machines with buggy
> microcode, that is the only available method.
Sure, if it comes to that being necessary. Otherwise, I'll opt for late
loading whenever possible. AFAICT, none of my machines are members of that
"few".
>
> But since you aren't going to load new microcode without knowing
> what it does (I suppose that means knowing what it claims to fix,
> otherwise you would not be looking at microcode at all), for your
> older machines I guess you will never apply any.
>
> ĸen
I don't know. I suspect there's a chance Intel *may* start publishing a
Changelog. It really need not be so detailed that it reveals "trade secrets".
And I could make-do with a report that certain updates *do* mitigate Spectre.
Intel has withdrawn some of the updates because they caused new problems.
Updating microcode can be a dangerous thing. I've never found a need to live
on the bleeding edge of technology.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
